Find guidance by setting, from configuration sources to traffic routing. Selecting a tab stops automatic rotation.
Clash Download CenterCONFIG EDITOR
Import and Update Subscription Links
A subscription link retrieves a configuration file; installing a client does not provide working proxy nodes. Open “Subscriptions” or “Profiles,” paste the full URL from your service provider, and choose “Import.” Once downloaded, set the profile as active and check the “Proxies” page to confirm its groups are available. Updating fetches the source again; it does not repair an unavailable service. To customize rules, use the client’s override feature where possible. Direct edits to a subscription file may be overwritten on the next update. Treat tokens in subscription URLs as credentials and redact them before sharing screenshots or asking for help.
# Client settings example
Subscriptions → New → Remote URL
Import complete → Set as active profile
Auto-update → Follow provider recommendations
In rule mode, rules are checked from top to bottom, and the first match determines the outbound. Domain suffix rules work well for specific sites; rule sets help manage groups of destinations; and a final MATCH catches everything else. Policy group names referenced by rules must exactly match the configuration, or it may fail to load. After editing, reload the configuration, then check the matched rule and outbound on the “Connections” page. Global mode bypasses normal rule selection, so it is not a reliable way to test whether a domain rule works. Unlike a simple per-app toggle, split routing can send different destinations along different paths at the same time.
mode: rule
rules:
- DOMAIN-SUFFIX,example.com,DIRECT
- MATCH,Select automatically
# Define the automatic selection group under proxy-groups
Proxy groups combine multiple outbounds under a name that rules can reference. Use select for manual choice, url-test to choose based on probe results, and fallback to find an available option in listed order. Automatic selection does not combine connections to increase speed, nor does it guarantee the same results for every site. Set interval with both switching speed and probe volume in mind; groups that support tolerance can use it to avoid switching for minor fluctuations. When setting up a group, first confirm its members exist, then review probe results in the logs. If a destination still fails, check routing rules and DNS rather than repeatedly changing the group type.
System proxy settings work mainly with apps that actively read them; some terminals and programs do not. TUN mode routes traffic through a virtual network interface, which can help with those apps but requires appropriate service permissions and routing configuration. Before enabling it, make sure a regular proxy connection works, then check the client's service mode and permissions. If other VPNs, virtual adapters, or network filters are running, rule out routing conflicts one at a time. After enabling TUN, test the same destination and review the connection log. If the network goes down, disable TUN first to restore a baseline. Avoid changing DNS, routes, and rules all at once.
tun:
enable: true
stack: mixed
auto-route: true
auto-detect-interface: true
# Illustrative snippet only; requires a complete configuration and appropriate system permissions
The client handles subscription management, tray access, system proxy settings, and permission prompts. The core parses configuration and handles connections. Even clients using similar cores can differ in menu names, override workflows, and service installation. When choosing one, check the operating system, processor architecture, and maintenance status before comparing interface preferences; similar names do not mean installers are interchangeable. When moving to another device, you can keep the subscription source, but recheck local ports, file paths, and TUN settings. Mobile platforms also impose VPN authorization and background limits, and desktop settings that depend on local scripts or paths cannot be copied over unchanged.
Choose an installer:
Operating system → Processor architecture → System requirements
After migration, check:
Active profile / Proxy mode / Local port / System permissions
Check your operating system and processor architecture first, then find client details and installers on the downloads page.
A subscription can be used with different clients that support its configuration format, but installers are not cross-platform. On desktop, check your device architecture and system requirements; on mobile, confirm system permissions and configuration compatibility. The links below open the relevant platform section on the downloads page, where available clients, maintenance status, and installation instructions are listed. The homepage does not duplicate individual packages, keeping client selection separate from choosing an installer.
Windows
For desktop use with tray controls, launch-at-startup options, and system proxy support. Start by comparing Clash Plus with clients such as Clash Verge Rev, including their features and system requirements.
Before installing, check your system type under “Settings → System → About.” After the first launch, import a configuration and enable the system proxy. If an app does not use system proxy settings, follow the guide to install the service and try TUN mode. If a system warning blocks installation, verify the source and read the specific warning rather than disabling security protections altogether.
Choose the installer for Apple Silicon or Intel, then compare menu bar controls, subscription management, and service permissions. The downloads page lists options such as Clash Plus and Clash Verge Rev.
Check your chip under “About This Mac.” After installation, move the app to “Applications” and grant network or service permissions as prompted. System proxy and TUN are different ways to route traffic; you do not need to enable both when getting started. When migrating an old configuration, check local file paths and ports so settings from another device are not carried over by mistake.
Routes app connections through the system VPN interface. The downloads page links to Clash Plus, Clash Meta for Android, FlClash, and Surfboard; configuration compatibility depends on each client's supported formats.
Check your device architecture first. If you’re unsure, check system information or the downloads page. After importing a subscription, select the active profile, tap Start, and approve the VPN connection request. If the connection drops when the app moves to the background, check battery optimization and background activity restrictions. If another VPN is active on the device, disconnect it before testing this client to avoid mistaking a VPN conflict for a broken subscription.
Install Clash Plus from the App Store. Its official website is clashplus.io. Open its App Store listing from the downloads page and check device compatibility, then import a subscription using the configuration options in the app.
The first connection requires permission to add a VPN configuration. Once connected, check the target app to confirm it can reach the network. A VPN icon only means the tunnel is active; it does not guarantee that every rule and outbound works. If you use other network tools, check which VPN configuration is currently active. If the app reports an unsupported subscription format, check its supported formats and source rather than assuming a desktop-only configuration will work.
Desktop users can compare Clash Verge Rev and FlClash, choosing a package supported by their distribution. For servers, routers, and gateway devices, consult the mihomo core deployment guides instead of following desktop installation steps.
Before installing, check your distribution, processor architecture, and desktop environment. A desktop system proxy usually does not cover every terminal program; command-line apps need proxy environment variables, or you can use TUN after understanding its routing effects. Running the core directly also involves configuration directories, service permissions, and startup management. Before changing network settings remotely, keep your current session open and prepare a way to stop the service and roll back.
Know which project, client, and configuration source you’re dealing with to make updates and troubleshooting more precise.
Project History and Scope
Clash began as a rule-based proxy core, followed by a range of desktop and mobile clients. After the original project stopped being maintained, the community continued developing implementations that support compatible configuration formats. Clash Meta is a name commonly seen in this evolution; mihomo is the name of a related core project today. Older guides may use these terms interchangeably, so check which core you actually use before deciding whether their instructions apply.
Clash Download Center brings together client downloads, guides, and troubleshooting resources without implying that different projects share a maintainer or team. Similar client names do not mean they share release schedules or features. Before downloading, check the specific project's system requirements. For older guides, first identify the concepts that still apply, then verify that menu labels, configuration fields, and permission steps match the current interface.
Source Code and Configuration References
mihomo source code, release notes, and issue discussions are available in its public repository. When checking whether a field is supported or why behavior changed, project documentation and the relevant release notes are more reliable references than secondhand explanations. Public code lets the community review implementations and submit fixes, but graphical clients have their own configuration management layers. When troubleshooting, note the client name, core in use, and steps that triggered the issue so interface problems are not mistakenly reported to the core project.
The command below retrieves mihomo source code for reviewing its implementation or contributing to development. Most users can simply choose a graphical client; there is no need to clone the repository. Cloning the source does not install a runnable program. Follow the project documentation for compilation, dependencies, and usage.
The Core, Client, and Subscription Source
The core handles protocols, rules, DNS, and connections; the client provides subscription imports, mode switching, and system integration; the subscription source provides the actual configuration and outbound details. Each updates separately and has different responsibilities. If a link will not import, check the source and network. If configuration parsing fails, check the format and fields. If only one app bypasses the proxy, check how traffic is being routed. Pinpointing the failing part is more effective than repeatedly reinstalling the client.
Proxy names and policy group names in a configuration are references, not fixed feature buttons. Changing subscriptions may also change group names and rules; an override that still references an old name can prevent the configuration from loading or send traffic to the wrong group. Keep a working copy before migrating, then check the active profile, mode, and default policy group afterward. Finally, test the destinations you need to reach.
Update Order and Rollback Planning
Updating the client, core, and subscription are three separate operations. A client update may change menus or service installation; a core update may add fields or change behavior; a subscription update replaces source content. If something goes wrong, note which layer you changed most recently instead of updating everything at once. Read the release notes before updating, and keep the previous configuration and overrides so you can compare changes.
Verify connections with a repeatable test: first confirm the device has network access, then check that the configuration loads, and finally review the matched rule and outbound in the connection log. If TUN causes a problem, disable it and test again. If access still fails after closing the client, check for leftover system proxy settings. Before sharing logs, remove subscription URLs, authentication details, and personally identifying network information while keeping the error context needed for troubleshooting.
Starting with rule matching order, this guide covers common patterns for direct connections in mainland China and proxy routing elsewhere, plus how to reference and update rule sets with rule-providers.
A browser extension overriding proxy settings and a terminal that ignores the system proxy are two common causes. This guide covers checks in order, proxy environment variables, and TUN mode as an alternative.
Learn how the three automatic proxy group types choose routes, what the interval and tolerance probe settings mean, and how configuration examples differ for common use cases.