Download for your system
Choose the client for Windows, macOS, Linux, Android, or iOS on the download page, install it, and open the main interface.
Open-source project · Client and configuration resources
Clash Official Download Site
Client and Setup Guides
Choose a client by operating system and find everything needed for installation and everyday maintenance, with a focus on Mihomo core, subscription setup, and routing rules.
- Always free
- Open-source code
- Five platform entries
- Chinese documentation
OPEN SOURCEClash / Mihomo
PLATFORMSWindows · macOS · Linux · Android · iOS
FOCUSConfiguration · Rules · Troubleshooting
Configuration map
Understand Clash from connection entry points to routing exits
Clash clients expose many settings, but configuration files, proxy modes, rule order, and system integration usually have the greatest impact. The sections below break these topics into practical routing checkpoints.
Rules / Routing
Send each connection to the right proxy group
Rule mode does not simply send all traffic through one node. It evaluates domain, IP, process, or geographic rules in order, then passes each result to the matching proxy group. After importing a configuration, confirm that the rule provider and proxy group names loaded correctly, then review the client’s connection log to see which rules actually match. Custom rules usually belong in the rules section of the configuration, where order matters: specific domain rules should come before broader fallback rules, with MATCH reserved for the final catch-all. This keeps everyday access predictable and makes it easier to determine why a site used a direct or proxied connection.
Best for: connections that need separate handling by website, application, or address type.
Subscription / Subscriptions
Create a rollback point before updating a configuration
A subscription link usually returns a complete configuration or an encoded collection of proxy nodes. Before importing one for the first time, verify that it comes from a trusted service and that the client recognizes the three essentials: proxies, proxy groups, and rules. Keep the currently working configuration before updating. Afterward, compare proxy group names, proxy ports, and DNS settings. If the update is empty or fails to parse, switch back to the previous configuration instead of repeatedly updating while the client is broken. For multiple configurations, use clear names for work, home, and testing to avoid accidentally making a test file the startup configuration.
Best for: users who update nodes regularly while keeping multiple configuration files.
Mode / Modes
Rules, global, and direct modes serve different troubleshooting goals
Rule mode routes traffic according to conditions in the configuration and is best for everyday use. Global mode sends proxyable connections to the selected proxy group, making it useful for checking whether a site or application is affected by the rules. Direct mode bypasses the proxy and helps test the local network, provider DNS, or the destination site itself. Switching modes changes traffic decisions only; it does not update subscriptions or fix an incorrect port. For troubleshooting, test the route in global mode first, return to rule mode to verify the expected behavior, and use direct mode as a comparison.
Best for: separating rule issues from proxy-path and local-network issues.
TUN / System integration
Bring apps that ignore system proxies into the proxy path
TUN mode receives system traffic through a virtual network interface, covering some applications that do not read HTTP or SOCKS system proxy settings. Before enabling it, confirm that the client has administrator access or the required system extension, and consider how DNS interception, LAN access, and existing VPN software may interact. Record the current network state first, enable only one traffic-capture entry, and test a browser, terminal, and LAN device. If local printing, file sharing, or development services become unreachable, check LAN bypass rules before repeatedly toggling TUN.
Best for: terminals, game launchers, and other programs that ignore system proxy settings.
Ports / Port settings
Confirm the listening port before checking whether an app is actually connected
HTTP, SOCKS, mixed, and control ports serve different purposes. Browsers and system proxies should use the proxy port exposed by the client; the control port is for external dashboards or API management and must not be substituted for it. After changing a port, check system proxy settings, browser extensions, terminal environment variables, and LAN permissions. If only one application cannot connect, verify whether it has its own proxy settings. Start with the local listening state and the client connection log; this is usually more revealing than immediately switching nodes.
Best for: cases where an import succeeds but a browser, terminal, or single app still cannot connect.
Quick start
Complete your first connection in three steps
The guides follow one clear path: install the client, import a configuration, and verify proxy behavior. When a problem branches off, return to the relevant section for a focused check.
Import a subscription
Paste the subscription URL in the configuration or subscription manager, then confirm that the proxy list, proxy groups, and rules are populated.
Choose a mode and verify
Start with rule mode, then visit a test address or inspect the connection log. If the result is unexpected, check ports, DNS, and rule order one by one.
Platform entry
Find the right client for your device
Platform links point to the relevant section on the download page. Client details, system requirements, and package notes are maintained there.
WindowsDesktop client and installerGo to downloads →
macOSApple Silicon and IntelGo to downloads →
AndroidMobile setup and appsGo to downloads →
iOSApp Store client entryGo to downloads →
LinuxDesktop and server optionsGo to downloads →
View all clients →
Open source context
Separate the client, core, and configuration
In the Clash ecosystem, the graphical client handles the interface and system integration, while Mihomo parses configuration, matches rules, and establishes connections. Understanding this division helps distinguish client names, core capabilities, and subscription services.
The early Clash project helped popularize rule-based configuration and proxy groups. Later, the community developed distinct projects around core capabilities, desktop packaging, and mobile support. Clients such as Clash Plus, Clash Verge Rev, and FlClash differ in interface and release cadence, but all rely on configuration files to determine proxy behavior. When downloading, check the operating system first, then confirm that the client supports the required core features.
Mihomo updates can affect configuration fields, DNS, TUN, inbound ports, and rule processing. Clients may not release synchronized updates, so when a setting is missing, check both the client release notes and the supported core features. This site explains common concepts separately so you can locate information by problem instead of memorizing where a particular button appears.
Repository reference
Use real configuration syntax as a troubleshooting starting point
When you need to inspect core behavior or prepare a test configuration, consult documentation and examples from the open-source repository. The commands below illustrate standard Git operations; use the project’s currently published repository address in practice.
git clone https://github.com/MetaCubeX/mihomo.git
Project history: The Clash ecosystem combines clients, cores, and configuration rules. Download links and usage guides should be considered separately.
Maintenance: The version list only updates download buttons; volatile version numbers are not placed in the homepage title or decorative areas.
Practical advice: When connections fail, keep the current configuration and record changes to mode, ports, DNS, and rules one by one for easier rollback and reproduction.
Common checks
Quick paths for common questions
These short answers help narrow down the likely direction. For the full procedure, open the relevant guide or FAQ.
What if no proxy groups appear after importing a subscription?
Check whether the subscription response can be parsed by the current client, then confirm that the configuration was updated and selected as the active one.
Go to Troubleshooting →How should I choose between rule and global mode?
Use rule mode for everyday traffic. Temporarily switch to global mode to test a proxy path, then return to rule mode for verification.
View mode details →Why doesn’t an application use the system proxy?
Some terminals, games, and background services ignore system proxy settings. Check the application’s own proxy options first, then consider TUN integration.
View TUN terminology →Why can’t my browser connect after changing the port?
Make sure the browser, system proxy, and client listening port match, and check whether an old process is still using the original port.
View port checks →Field notes
Recent articles: from client selection to troubleshooting
These articles cover client relationships, Platform Deployment, proxy modes, and common network errors, making them useful after the basic installation is complete.
Windows UWP apps cannot use the Clash proxy
Learn how UWP loopback isolation works, how to remove the restriction, and which proxy port and app-scope settings to check if connectivity still fails.
Read the full article →An overview of Mihomo router and bypass-router deployment
Compare main-router and bypass-router deployments, with an explanation of transparent proxying, forwarding paths, and use cases for running the core directly.
Read the full article →Clash open-source ecosystem projects and client selection
Map common projects across three layers—core, graphical client, and platform support—to clarify what similarly named software actually handles.
Read the full article →