Choose your operating system, then pick a package. Use a graphical client on desktop or mobile; use the Mihomo core on servers and routers.
For everyday use, start with Clash Plus. For desktop overrides and configuration management, compare Clash Verge Rev, FlClash, and Clash Nyanpasu.
A good fit for everyday use, from installation and subscription import to switching modes. After opening the app, add a configuration and make sure it's active. Don't enable the system proxy without first importing a subscription.
Official website: clashplus.io
A desktop client based on mihomo for managing subscriptions, proxy groups, and overrides. After installation, test the connection in Rule mode with the system proxy enabled. Turn on TUN if apps you need to route don't follow the system proxy.
Follow the client prompts to grant permissions when enabling service mode or a virtual network adapter.
A good option if you want a similar experience on desktop and Android. After importing your configuration, check that the proxy groups have available options before connecting. Each device still needs its own system proxy, VPN, or TUN permissions.
When switching clients, reimporting your subscription is safer than copying the entire data directory.
Includes a desktop interface for configuration and proxy management. A good choice if you want to compare desktop workflows. Before migrating, note your local ports, overrides, and rule references so you don't lose custom settings when moving your subscription.
Core features vary by release. Check for configuration parsing warnings after importing.
Archived downloads are available for legacy setups and configuration migration. New users should choose one of the maintained clients above. Older cores may not recognize newer protocols or configuration fields; if an import fails, avoid repeatedly overwriting your original configuration.
Before switching to an alternative, save your subscription URL and migrate any custom local rules.
| Check | How to choose | After installation |
|---|---|---|
| Operating system | Use a Windows version that is still supported. Check the release notes for the package's minimum requirements. | If the installer reports a missing runtime, follow its instructions before launching the app. |
| Processor architecture | Go to Settings → System → About and check System type. This section primarily offers x64 builds. | On ARM devices, first check whether Windows and the app support x64 compatibility. |
| Traffic routing | For regular browser use, start with the system proxy. Consider TUN only if you need to route other traffic. | Let only one client manage the system proxy to avoid conflicting settings when you exit. |
When the download finishes, run the installer, keep a backup of your existing configuration, and then launch the client. For your first test, don't run multiple proxy apps at once. If the app starts but your browser can't connect, make sure the configuration is enabled, Rule mode is selected, and a proxy group target is chosen; then check the system proxy setting. See the full Clash setup guide.
Check your chip in Apple menu → About This Mac. Choose the native arm64 build for Apple silicon and the x64 build for an Intel Mac.
Offers separate downloads for Apple silicon and Intel Macs. Open the DMG, move the app to Applications, then launch it from there. Import an existing subscription and follow the prompts to configure traffic routing.
Official website: clashplus.io
A good fit for desktop use with subscription management, Rule mode, and overrides. Back up your configuration before editing it. After a subscription update, check whether your changes were written directly into the remote configuration.
Both links currently point to an x64 fallback package. Before using it on Apple silicon, check compatibility with Rosetta; this is not a native ARM build.
A good fit for Mac users who prefer a mobile-style interface. After installation, reimport your subscription and check the configuration, proxy groups, and connection status. VPN permission granted on your phone does not carry over to your Mac.
The fallback for the Apple silicon link is also an AMD64 build. Check the actual package architecture before installing.
For existing configurations and legacy setups. New users should choose a maintained client above. Before migrating, note your menu bar proxy settings, local configuration path, and custom rules so you don't miss any exceptions you need.
Both links currently point to the same x86_64 package. On Apple silicon, check that it can run through translation.
| Check | How to choose | Notes |
|---|---|---|
| Chip | If About This Mac shows an Apple chip, choose arm64; if it shows Intel, choose x64. | Some architecture links on this page currently point to the same x64 fallback package. Check the notes on each download card. |
| Operating system version | Check the client's release notes for its macOS version requirements. | If your macOS version is older, check compatibility first. A DMG opening successfully doesn't guarantee the app will run. |
| Install location | Move the app to Applications before launching it. | If macOS blocks the app on first launch, verify its source and check the specific message under Privacy & Security. |
Before connecting, quit other apps that manage network traffic, then grant permissions as prompted by the client. System proxy and TUN route traffic differently, so start with a basic test using the system proxy. If an app still connects directly, check whether it follows the system proxy. For permission issues, read the system prompt rather than disabling macOS security protections altogether.
Most recent Android phones use arm64-v8a. Older 32-bit devices need an ARM build. If you don't know your device's architecture, check its specifications or choose a universal build.
A good fit for importing subscriptions and switching proxy modes on your phone. After installing the APK, open the configuration page and add an existing subscription. The first time you connect, allow Android to create a VPN connection, then check for the connection indicator in the status bar.
Official website: clashplus.io
A Clash Meta client for Android. Choose a package that matches your device architecture. After importing a configuration, update it and set it as active. If the connection drops when you switch apps, check battery management and background activity restrictions.
Choose the universal build if you can't confirm your device's architecture. There's no need to install multiple builds on the same device.
A good fit if you use the client on both desktop and Android. Android manages background activity separately, so desktop settings don't apply. Test the connection in the foreground first, then adjust background permissions as needed.
If package parsing fails, check the supported Android version and processor architecture first.
A good fit for Android users with an existing compatible configuration. Surfboard uses a different configuration syntax from Clash YAML, so you can't use the same file just by renaming it. Before installing, check whether your subscription provider offers a compatible format.
After converting a configuration, check the protocols, rules, and proxy groups. A file that parses successfully may not behave exactly the same.
| Check | How to choose | After installation |
|---|---|---|
| Architecture | Recent phones usually use arm64-v8a. For older devices, check whether they only support 32-bit apps. | If package parsing fails, recheck the architecture and Android version rather than repeatedly trying to install over the existing app. |
| Install permissions | When prompted, allow installation only for the app you used to download or manage the file. | You can revoke permission for that source after installation if you wish. |
| VPN & background activity | Allow the client to create a VPN configuration. Set background restrictions according to your phone's operating system. | Avoid running another app that uses the VPN connection at the same time. Test the connection in the foreground first. |
If Android says the app wasn't installed, check for an existing version signed differently as well as the architecture. Export your configuration before uninstalling; don't assume app data will be preserved. If the connection drops when the screen locks, check battery optimization, auto-start, and background activity settings. Relax restrictions only for clients that need to stay active; you don't need to change every battery-saving setting.
Install Clash Plus from the App Store. After installation, import a compatible subscription and allow iOS to add a VPN configuration the first time you connect.
Open the App Store listing on your iPhone or iPad and check device compatibility before installing. In the client, import an existing subscription, then choose a proxy mode and proxy group. The first connection requires system VPN permission.
Official website: clashplus.io
| Check | Where to check | What to do |
|---|---|---|
| System compatibility | Compatibility details on the App Store listing. | Make sure your iPhone or iPad meets the installation requirements. |
| VPN configuration | The system permission prompt shown on your first connection. | Allow the VPN configuration, then return to the client and check the connection status. |
| Subscription & configuration | The client's configuration list and proxy group screen. | Use a compatible format, and make sure the configuration is updated and enabled. |
iOS routes network traffic differently from desktop system proxy settings, so you don't need to copy your computer's local port settings. When switching clients, disconnect the existing VPN before starting the new client's VPN configuration. Rules, protocols, and proxy groups still depend on the configuration. Successful installation only means the client is ready; connecting requires a valid configuration and a working network service.
Choose deb for Debian- and Ubuntu-based distributions, or rpm for distributions that use RPM packages. This section offers AMD64 desktop builds; see the core downloads below for servers and routers.
A good fit for Linux desktop users who want a graphical interface. Let your package manager handle dependencies, then import a subscription after launch. Whether apps use the system proxy depends on your desktop environment and their own settings.
Service mode and TUN require system permissions. Test the configuration with a regular proxy first, then set up traffic routing.
A graphical Linux desktop client for users already familiar with FlClash. After importing a configuration, check the proxy groups and mode. For command-line apps, configure proxy environment variables or traffic routing separately.
The AMD64 desktop builds in this section aren't suitable for ARM servers. Choose a core build that matches your device architecture.
| Check | How to check | How to choose |
|---|---|---|
| Distribution | cat /etc/os-release | Check which package management system your distribution uses. Don't rename a deb package to make it look like an rpm. |
| Architecture | uname -m | x86_64 matches the AMD64 desktop build. ARM devices need the corresponding core build. |
| Desktop environment | Make sure you're logged into a desktop session and meet the package's runtime dependencies. | For a server with SSH access only, running Mihomo directly is usually a better fit. |
Install through your distribution's graphical installer or package manager. If you encounter a dependency error, read the full message instead of deleting system libraries manually. Terminal tools may not use desktop proxy settings. If a browser works but terminal apps don't, check their proxy options, environment variables, or TUN routing before changing your subscription.
The core doesn't include a desktop configuration interface. Most users should choose one of the GUI clients above. Download a core build if you plan to manage YAML, startup options, and service processes yourself.
| System | Architecture | Format | Local downloads |
|---|---|---|---|
| Windows | AMD64 / x64 | zip | Download AMD64 |
| Windows | ARM64 | zip | Download ARM64 |
| macOS | Intel / AMD64 | gz | Download Intel |
| macOS | Apple Silicon / ARM64 | gz | Download ARM64 |
| Linux | AMD64 | deb | Download deb |
| Linux | AMD64 | gz | Download AMD64 |
| Linux | ARM64 | gz | Download ARM64 |
| Linux | ARMv7 | gz | Download ARMv7 |
| Linux | MIPS softfloat | gz | Download MIPS |
On Linux, run uname -m to check the architecture. For routers, also verify the system ABI, byte order, and firmware compatibility. ARMv7 and ARM64 aren't interchangeable based on the device name alone; MIPS softfloat isn't a universal build for all MIPS devices either. If you get an executable format error, check the binary architecture first.
Create a configuration directory and add config.yaml. Test the configuration before starting the service. You can name the extracted binary mihomo. These commands are for Unix-like systems; on Windows, use the path to the corresponding executable.
./mihomo -t -d ./config
./mihomo -d ./configThe client, subscription configuration, and system traffic routing are separate parts of setup. Check them in order to narrow down problems faster.
Open the configuration page and add a compatible subscription or import a local YAML file. Once it appears in the list, set it as the active configuration. Subscription URLs may contain credentials; don't share screenshots or paste them into unfamiliar online conversion tools.
For everyday use, start with Rule mode and choose a suitable target from the proxy groups provided by your configuration. Global mode is useful for temporary comparison tests; Direct mode can help troubleshoot your local network. A mode only determines how traffic is routed—it can't replace a valid subscription and working nodes.
On desktop, enable the system proxy or TUN as needed; on mobile, authorize the VPN connection. Test the apps you use most. If only some apps fail, check the connection logs for matched rules and errors, then verify DNS, ports, and app proxy settings one by one.
Check your installation setup and client choice before troubleshooting connection issues.
Start with Clash Plus on Windows, macOS, Android, or iOS; for Linux, consider Clash Verge Rev. Compare client documentation if you need specific overrides, scripts, or UI features. Most desktop and mobile users should choose a client with a graphical interface. Mihomo core builds are for users who manage configuration and processes themselves.
Check your device's processor first. Windows x64 and Linux amd64 usually refer to the same architecture; Apple Silicon uses arm64, while Intel Macs use x64. Recent Android devices generally use arm64-v8a; older 32-bit devices use armeabi-v7a. If you're unsure, try the client's universal build. When the download label and filename differ, use the filename and check the client's supported architectures.
The installer includes the client, not a working subscription. Open the configuration page, import a compatible subscription or local YAML file, activate the configuration, then choose a mode and suitable proxy group. On desktop, enable the system proxy or TUN as needed. On mobile, allow the system to create a VPN configuration the first time you connect.
For the same client, you can usually quit the app and install the update over the existing version. First export your configuration and note any overrides, ports, and proxy settings. When switching clients, disable the old client's system proxy or VPN before importing your subscription into the new one. Data locations and features vary, so avoid replacing the new client's entire data directory with the old one.
Both clients are discontinued. This page keeps archived downloads for migration and configuration reference. New users should choose a maintained client; older clients may not support newer protocols, subscription fields, or operating system versions. When migrating, keep your subscription URL and any custom rules you need, then configure them again in the new client.
Check your operating system version, processor architecture, and package format, then review system messages and client logs. On Linux, distinguish between deb and rpm packages; on macOS, check whether your Mac has an Intel processor or Apple silicon; on Windows, verify the system type. If the filename says x64, don't assume it's a native ARM build based on the download label alone. Check the release notes for installation requirements.