Clash
Windows
Ideal for everyday desktop use. Check the system architecture before installing. After the first launch, import a subscription, select Rule mode, and enable the system proxy. TUN requires the appropriate system permissions.
Go to downloads
Open-source clients and Chinese configuration guides
Clash Release Hub · Cross-platform clients
Find Windows, macOS, Android, iOS, and Linux client downloads in one place, with Chinese documentation covering subscription imports through rule troubleshooting. Choose a client for your operating system, then follow the guide to configure the system proxy, proxy mode, and configuration updates.
Free forever
Open source
Multi-platform
Chinese docs
Core capabilities
Subscriptions, routing, DNS, and system proxies
Clash clients mainly handle four areas. Understanding each one before changing settings helps prevent broken rules, DNS resolution problems, and traffic that bypasses the system proxy.
01 / PROFILE
Subscription imports and config updates
Subscription URLs are usually generated by the service provider. The client fetches them and saves the result as a selectable configuration. When importing for the first time, make sure the URL is complete, reachable, and selected in the configuration list. Enable the system proxy only after that to avoid using a built-in example or an old configuration.
An update only fetches the configuration again; it does not repair a broken URL. If the request times out, returns empty content, or shows an error page, check the subscription URL first, then the current network and server status. Keep one known-good configuration, and make a copy before editing rules so you can quickly recover from syntax errors.
View the subscription import steps →
Config
Current config
Remote subscription
✓
Local rule copy
config.yaml
Edit
Auto-update interval
Set as needed
02 / ROUTING
Rule mode and request routing
Rule mode matches domains, IPs, processes, or rule sets in the order defined by the configuration. A match sends the request to its assigned policy group; unmatched requests fall through to the final rule. Unlike Global mode, Rule mode lets different sites use different policies while preserving normal access for local-network and required direct traffic.
When troubleshooting rules, start with the actual domain and matched entry in the logs, then confirm that custom rules appear before general ones. Rules run from top to bottom, so an overly broad rule near the top can override a later, more precise rule. Reload the configuration after editing; switching nodes alone does not refresh the rule file.
Read the rule configuration guide →
rules.yaml
rules:
- DOMAIN-SUFFIX,example.org,Proxy
- DOMAIN,localhost,DIRECT
- IP-CIDR,192.168.0.0/16,DIRECT
- MATCH,ProxyPlace specific rules before broad rules, and keep a fallback policy at the end.
03 / DNS
DNS resolution and Fake-IP
Clash's DNS module brings domain resolution into rule evaluation. With Fake-IP enabled, the local module first returns a mapped address; when the connection is established, the domain is restored and matched against routing rules. This preserves domain information, but some local-network devices, games, and applications that require real addresses may need to be added to the filter list.
DNS issues often appear as inaccessible websites, unexpected resolution results, or only some applications working. Troubleshoot system DNS, browser encrypted DNS, and client DNS separately to avoid multiple resolution paths running at once. After changing nameserver, fallback, or hijack settings, clear the system DNS cache and test again.
Read the DNS settings guide →
dns
dns:
enable: true
enhanced-mode: fake-ip
nameserver:
- system
fake-ip-filter:
- "*.lan"
- localhostAdjust configuration items to match the current client core and local network environment.
04 / SYSTEM
System proxy and TUN mode
A system proxy works well for browsers and desktop apps that follow the operating system's proxy settings. Once enabled, the client writes its local listener address to those settings. Some applications ignore system proxies; use TUN mode when you need to capture more network connections. They solve different problems and do not need to be enabled together in every environment.
TUN mode usually requires administrator privileges and may conflict with other VPNs, virtual network adapters, or security software. For a first setup, verify the subscription and nodes with the system proxy, then test TUN separately. If the internet stops working after closing the client, check whether the system proxy was restored and verify the virtual adapter status.
View connection and verification steps →
Settings
System proxyWrite to the operating system proxy settings
TUN modeRequires system network permissions
Allow LAN connectionsEnable only when explicitly needed
Platform downloads
Choose a Clash client for your operating system
Client interfaces, core integration, and system permission requirements vary by platform. Open the relevant platform page first, then choose a package based on maintenance status, processor architecture, and intended use.
macOS
When downloading, distinguish Apple Silicon from Intel builds. The first launch may require you to confirm the app's source; enabling the system proxy or TUN may also require granting network permissions as prompted.
Go to downloadsAndroid
Suitable for phones and tablets. After importing a subscription, the system displays a VPN connection authorization prompt; allow it so the client can handle app traffic. Battery-saving restrictions may affect background operation, so adjust them for your device.
Go to downloadsiOS
Get the corresponding client through the App Store. The first connection requests permission to add a VPN configuration; confirm it to use subscriptions and rule-based routing. iOS manages the configuration and system proxy permissions.
Go to downloadsLinux
Choose a desktop graphical client or run the Mihomo core directly. On servers and routers, you manage the configuration files, service process, startup permissions, and firewall rules yourself.
Go to downloads
Getting Started
Complete these three settings after installation
Interface labels may differ slightly across platforms, but the initial setup order is largely the same. Completing the steps in order helps separate download, configuration, and connection issues.
View the complete guide →-
01
Import a subscription
Open the configuration or subscription page, paste the complete URL, and run an update. After the import succeeds, select the newly fetched item in the configuration list. If the list is empty, first check the URL in a browser; do not rush to change proxy mode or DNS.
-
02
Choose Rule mode
Open the proxy mode settings and choose Rule mode first. Then open the policy groups and select an available policy from the configuration. Global mode sends more requests through one policy and is usually for temporary testing, not the first step in troubleshooting rules.
-
03
Enable the proxy and verify
On desktop, enable the system proxy first. On mobile, confirm VPN authorization, then visit a regular webpage to verify the connection. If the browser works but other apps do not, check whether those apps follow the system proxy; consult the TUN and system permissions guide if needed.
Projects and resources
Open-source ecosystem, Mihomo core, and maintenance scope
Clash has grown into an open-source ecosystem of cores, graphical clients, rule projects, and configuration tools. Understanding how these parts relate makes it easier to identify update sources and determine where a problem belongs.
Project history and client ecosystem
Clash first became widely used as a rule-driven proxy core and configuration format, followed by graphical clients for different operating systems. Some early clients are no longer maintained, although their names remain common in older guides and search results. When choosing a client today, prioritize maintenance status, core support, system compatibility, and installation source rather than relying on an old name alone.
Graphical clients mainly manage subscriptions, policy switching, system proxies, logs, and the core's lifecycle. The core usually performs rule matching, DNS handling, and connection forwarding. Similar interfaces do not necessarily mean identical core capabilities or configuration compatibility.
Mihomo and Clash configuration compatibility
Mihomo continues and extends the Clash configuration system, and many actively maintained clients integrate Mihomo. Common sections such as proxies, proxy-groups, rules, and dns remain central, but extension fields may differ across cores and clients. Before copying a configuration snippet, confirm that its fields are supported by the current core.
The core itself usually does not provide a complete desktop interface. Most users are better served by a graphical client with the core integrated; servers, software routers, and automated environments can run the core directly and manage startup through configuration files, command-line arguments, or system services.
How this site updates and maintains content
The download page organizes client links by platform and distinguishes actively maintained projects from archived ones. Version and installer details are handled on the download page, while the home page provides platform navigation so users do not retrieve outdated files from old articles or search snippets. Guides focus on stable workflows and are updated when interface labels change.
Troubleshooting resources break issues down into subscriptions, configuration, nodes, rules, DNS, and system integration. This makes the same diagnostic approach useful even when client interfaces differ. This site does not provide proxy subscriptions or network services; its documentation focuses on client installation, configuration structure, and local troubleshooting.
Featured FAQs
Review these questions before downloading or configuring for the first time. More complete categorized answers are available in the Help Center.
What should I use now that Clash for Windows is no longer maintained?
Choose a client from the download page that is still maintained and compatible with your current system. During migration, reimport the subscription instead of copying all internal settings from the old client. If the old configuration contains custom rules, save a copy and migrate them to the new client one by one.
The subscription imported successfully. Why can't I connect?
Confirm that the current configuration is selected, the policy group has a choice, and the system proxy or mobile VPN permission is enabled. Then check the runtime logs to distinguish subscription content, node connectivity, DNS resolution, and rule-matching issues.
Do system proxy and TUN mode have to be enabled together?
No. The system proxy is for software that follows the operating system's proxy settings, while TUN captures more types of network connections. Test the system proxy first after installation, then enable TUN only if a specific application requires it.
Why didn't my custom rule changes take effect?
Check the rule syntax, ordering, and current proxy mode, then reload the configuration. Rules are matched in order, so a broad rule near the top may handle the request first. Match records in the logs can confirm which rule actually ran.
Configuration and troubleshooting articles
Recent Clash guides
Practical guides covering subscription updates, HTTPS certificate errors, and DNS settings. Each article focuses on one specific problem, making it easier to find the right steps by symptom.
Clash subscription update failed: common causes and auto-update intervals
Fetch timeouts, 404 responses, and empty content are three common causes of failed subscription updates. This article checks the network, URL, and server in order, then explains how to set the auto-update interval.
Read moreBrowser certificate error after enabling Clash: understanding HTTPS errors and proxies
Invalid certificates and NET::ERR_CERT errors may involve the node route, system time, or local traffic-capture software. This article explains the possible causes and provides a step-by-step checklist.
Read moreClash DNS configuration guide: how to set nameserver, fallback, and DNS hijacking
The DNS section affects the resolution path and rule matching. This article explains the purpose and combinations of nameserver, fallback, fallback-filter, and hijacking settings.
Read more