Disclaimer
Last updated: September 2026
This disclaimer applies to clash-tunnel.com and its Simplified Chinese pages. By visiting this site, reading its guides, or using its download links, you acknowledge the boundaries of responsibility below. The site helps readers understand the relationships between clients, cores, configuration files, and subscription services; it does not replace a project's own documentation, license terms, or system security requirements.
1. The Site’s Relationship with Clash Projects
This site is an independently maintained usage guide and download directory. It is not affiliated with or representative of the developers, maintainers, or distributors of Clash, mihomo, Clash Verge Rev, FlClash, Clash Plus, or other related projects. Project names, software names, and related marks appear only to identify the relevant software, platform, or procedure; all rights belong to their respective owners.
Clients, proxy cores, and subscription services are separate components. A client typically provides the graphical interface, configuration management, and system integration controls, while the core handles proxy protocols, DNS, and rule evaluation. Subscription services are operated independently by their respective providers. This site does not provide subscription services and makes no promises about subscription content, node quality, availability, or continuity.
2. Software Use and Operational Risks
Users independently decide whether to download, install, authorize, configure, or run software and assume the associated risks. Different clients may request network extensions, VPN configuration, administrator privileges, background execution, or virtual network adapter access. The purpose and impact of these permissions should be assessed against the specific version, operating-system prompts, and project documentation. Obtain software through an entry point suited to your platform and architecture, and understand the potential network impact before changing system proxy, DNS, routing, or firewall settings.
Incorrect configuration may cause network outages, DNS resolution problems, inaccessible local-network resources, failed application connections, or traffic to take an unintended path. Cores used on servers, routers, and command-line environments typically require additional permission management and service configuration; desktop-client instructions should not be applied to them without adjustment. The party performing the installation, configuration changes, or commands is responsible for any resulting direct or indirect loss.
3. Guide Accuracy and Version Differences
The guides are compiled from the client interfaces, core behavior, and system versions available when they were written or updated, with operating prerequisites described where possible. Software may change menu labels, default ports, permission flows, configuration fields, and supported platforms. Screenshot-based descriptions and button paths may therefore differ from later versions. If the interface does not match, first verify the client name, version, core, and operating system, then consult the project's current release notes.
Configuration examples explain field structure and rule logic. Do not use them directly in production without understanding policy groups, DNS, listen addresses, and access-control conditions. Names such as PROXY in examples may need to be defined by the user. This site revises content as known changes emerge, but cannot guarantee that every page will always match every branch, derivative version, or third-party modification.
4. Download Links and File Sources
The download page organizes client and core links by platform, helping users distinguish Windows, Android, iOS, macOS, Linux, and different processor architectures. Version releases, maintenance status, compatibility, and license terms are determined by the relevant project or distribution channel. This site cannot guarantee that a particular version will remain available or that an old configuration can be migrated directly to a new release.
Before downloading, verify the software name, target platform, system architecture, and maintenance status. Software that is no longer maintained may still be listed for legacy compatibility, but this is not a recommendation to prioritize it. Users should also assess whether the software complies with applicable laws, organizational network policies, device-management rules, and their intended use case.
5. External Links and Feedback
Some pages may link to software project pages, app stores, release channels, or other external websites. Those sites are controlled by their respective operators, and their content, availability, privacy rules, terms of service, and future changes are outside this site's control. A link only indicates that the address is relevant to the topic at hand; it does not mean this site endorses all content on the external page or guarantee any transaction, service, or continued availability.
If a guide differs from the current client interface, first consult the installation, configuration, and Troubleshooting entries in the Help Center; when you need to recheck the import, mode selection, connection, or verification process, refer to the Tutorial. When submitting or discussing an issue, avoid exposing subscription URLs, access credentials, or other sensitive configuration details.