Disclaimer

Last updated: November 2026

This disclaimer explains the scope of our content and download links, and outlines key considerations when accessing, configuring, and using software.

1. About This Site

This is a Clash website operating under the name Clash Meta Official Site. We provide user guides, configuration instructions, troubleshooting, and download links for Clash Meta, the mihomo core, and related clients. Our documentation helps explain software settings and does not promise compatibility with any specific network environment.

The Clash ecosystem includes different components, such as cores, graphical clients, rule sets, and subscriptions. Introducing a project or linking to its downloads does not mean that we developed or operate all of its features. Refer to each project's own published information for its licensing terms, maintenance status, and conditions of use.

2. Software and Configuration Risks

Decide whether the software is suitable for your device, operating system version, and network environment. Use it only as permitted by local laws and your organization's network policies. You are responsible for confirming the source of any subscription, your access permissions, and your eligibility to use it. Our documentation does not recommend or endorse any subscription service.

Changing system proxy, DNS, or routing settings, or enabling TUN mode, may affect network access for other apps. Before making changes, back up your configuration, note your current network settings, and learn how to disable the proxy and restore those settings. Before granting administrator privileges, allowing LAN access, or exposing an external control interface, assess the permissions and access scope. Keep subscription URLs and control keys secure.

Users are responsible for assessing connection interruptions, data loss, and other risks arising from device incompatibility, incorrect configuration, third-party service outages, or improper operation. If a problem occurs, first disable the affected feature and restore a known working configuration before troubleshooting. Avoid piling on repeated changes.

3. Tutorial Accuracy and Version Differences

Tutorials reflect the version current when they were written or revised. Updates to clients and the mihomo core may change menu locations, interface labels, configuration fields, and default behavior. Client support for the same fields may also differ. The steps and examples in our articles are not a substitute for the documentation for your specific version.

Configuration snippets explain specific features and are generally not complete, ready-to-run configurations. Before copying one, check indentation, proxy group names, rule references, and prerequisites, then use your client's configuration checker to confirm it can be loaded. Understand what a system command does before running it; do not blindly apply commands to production devices.

We update content when we can verify changes, but cannot guarantee every page stays in sync with every software version or that examples will produce the same results in all environments. For important changes, consult project release notes, configuration check results, and system prompts together.

We may link to project websites, app stores, code repositories, and other reference materials. External pages and services are managed by their respective operators, and their content, availability, pricing, and data handling policies may change independently. Links are provided for convenience and do not constitute an ongoing guarantee of any external service.

Before leaving this site, verify the destination URL, software name, and publisher, and review the applicable terms. Download links do not create a transaction between this site and you for any third-party service. For accounts, payments, subscriptions, or support, follow the provider's rules.

5. Liability and Issue Resolution

This disclaimer applies to the extent permitted by law. It does not exclude or limit liability that cannot lawfully be excluded or limited, or affect any rights you have under applicable law. Whether liability applies, and its scope, depend on the specific facts, applicable law, and the conduct of the parties involved.

For configuration or connectivity issues, start with Troubleshooting and Getting Started, and follow the relevant steps to reproduce and isolate the problem. When reporting an issue, include the client name, operating system version, steps taken, and error messages. Remove subscription URLs, passwords, and other sensitive information first. We will update this page if the disclaimer changes; check the date at the top for the latest revision.