Choose a client for your platform, then pick the installer for your architecture.
Desktop and mobile users should start with a GUI client. Clash Plus is recommended for Windows, macOS, Android and iOS; Linux users should choose Clash Verge Rev. Import a subscription or YAML config after installation—downloading the app alone won’t connect you to a proxy.
Choose a platform, then review its installer cards. After switching platforms, you can copy the address bar URL to save a link to the current selection.
The GUI clients in this section provide x64 installers. Find your system type under Settings → System → About. On Windows ARM devices, first check compatibility with x64 apps and their networking components. Being able to launch a desktop app does not guarantee that its TUN driver will work.
A good place to start for a first install. After installation, import your configuration, check your policy groups and rule mode, then enable the system proxy. Configure TUN and grant permissions separately if you need to route traffic from more apps.
Official site: clashplus.io · View setup steps
A good fit if you want a desktop interface for managing configurations, policies and traffic routing. When migrating an existing subscription, import a copy of your configuration and test its rules first. Recheck service mode and launch-at-startup settings on this device.
Package: EXE · Architecture: x64
A good fit if you want a similar workflow across multiple devices. AMD64 and x64 refer to the same processor architecture; AMD64 does not mean the app only works on AMD processors. After importing your configuration, check the local proxy port.
Package: EXE · Architecture: AMD64
Includes a desktop interface for managing configurations. If you already have a local YAML file, check the policy group names in a copy before importing it. Override and merge options may work differently across clients, even when their labels sound similar.
Package: EXE · Architecture: x64
Kept for compatibility checks and migration from existing setups. For new installations, choose one of the clients above. The older core may not recognize newer protocols or configuration fields; avoid importing a complete configuration written for a newer core.
Archived for legacy setups · Explore alternatives
| Item | What to check before installing |
|---|---|
| Operating system | Use a Windows version that is still supported by Microsoft. Check the selected client's installer notes for its minimum supported version. |
| Processor | Downloads in this section are primarily for x64; they won't work on 32-bit systems. On ARM devices, check compatibility layers and networking components separately. |
| Permissions | Configure standard proxy settings separately from service installation. TUN or service components may require administrator approval. |
| First launch | Quit any old client first to avoid proxy port conflicts. Set the app to launch at startup only after confirming that your configuration loads correctly. |
Check your chip under About This Mac in the Apple menu. Apple Silicon Macs generally need ARM64; Intel Macs need x64. Some compatibility builds are noted below—don't assume a file is a native build based on the chip name in its download button.
Choose the DMG that matches your chip. Open it and follow the installer prompts to move the app to Applications. Launch it from Applications, then configure the system proxy and grant any required network permissions. Quit the client and back up your configuration before replacing an older app.
Official site: clashplus.io
Manage desktop configurations and proxy policies. Grant the required permissions when enabling a service or TUN for the first time. The Apple Silicon link currently points to an x64 build, so check compatibility before installing.
Package: DMG · Current build: x64
A good fit if you already use FlClash on other devices and want a familiar workflow. Importing a configuration won't carry over system permissions or network routing settings from another device; set up traffic routing again on your Mac.
Package: DMG · Current build: AMD64
Archived downloads are available for keeping legacy setups running and migrating configurations. After a macOS upgrade, older permission components or configuration fields may no longer work as expected. For new installations, choose a client that is still maintained.
Both links currently point to x86_64 files.
| Item | What to check before installing |
|---|---|
| Operating system | Check the app's release notes and macOS installer prompts for the minimum supported version. |
| Chip and compatibility layer | Identify whether your Mac has Apple Silicon or an Intel processor. On Apple Silicon, x64 apps require Rosetta compatibility. |
| Install location | Move the app to Applications instead of running it long-term from a mounted DMG. |
| Network permissions | System proxy, background service and TUN permissions differ. Grant only the permissions needed for the features you use. |
Most recent phones can use the ARM64 build, but a 64-bit processor doesn't guarantee that Android supports the same ABI. If the installer reports that it's incompatible, check your system architecture instead of repeatedly trying packages from different sources.
For first-time setup, import a subscription, start a connection and approve Android's VPN prompt. If the system stops the app in the background, check battery management and background activity restrictions instead of reinstalling it repeatedly.
Official site: clashplus.io · Architecture: arm64-v8a
Choose from ARM64, ARM and universal packages. If you're unsure which ABI your device supports, check its device information or use the universal build. After importing a configuration, select it and return to the home screen to start the service.
The universal build can simplify installation when your device architecture is unclear, but your system must still meet the app's requirements.
Choose the installer for your device's system architecture. You can import a YAML file used on desktop, but don't copy desktop proxy ports, LAN listening or permission settings to your phone. Start by testing the default connection flow.
Package: APK · ARM64 / ARMv7
For users who already have a compatible configuration source. Surfboard uses a different configuration format from Clash YAML, so don't follow Clash subscription import instructions. First check which format your provider supplies.
Package: APK · Check configuration format separately
| Item | What to check before installing |
|---|---|
| System and architecture | Check your Android version and system ABI. Refer to the installer prompt and app documentation for the minimum supported version. |
| Install permissions | If prompted, allow the browser or file manager you used to open the APK to install apps. |
| Connection permissions | Starting a proxy usually requires VPN permission. Don't let another VPN app compete for the connection at the same time. |
| Background activity | Check battery restrictions in your device manufacturer's settings. Allow background activity only as needed. |
Install Clash Plus from the App Store. Check the store listing for supported devices, iOS compatibility and update history. After installing, prepare a valid configuration and follow the app prompts to connect.
Open the App Store listing to check the app details and install it. On your first connection, follow the iOS prompts to add a VPN configuration, then return to the client to choose a configuration and proxy policy. The VPN status in Settings shows whether the tunnel is connected; it doesn't confirm that every route in your subscription can reach its destination.
Official site: clashplus.io · Updates are managed through the App Store
| Item | What to check before installing |
|---|---|
| System compatibility | Check the Compatibility section on the App Store listing for supported iOS versions and devices. |
| Install source | Open the app listing through the store link on this page. The App Store handles installation and updates. |
| Connection authorization | Follow the system prompts to add a VPN configuration. If another VPN is already connected, check which one is active. |
| Configuration setup | Prepare a valid subscription or compatible configuration. After importing it, select a policy and start the connection. |
The GUI clients in this section provide AMD64 packages. Debian, Ubuntu and compatible distributions generally use DEB; Fedora and other RPM-based distributions use RPM. Desktop dependencies and service permissions vary by distribution, so check your package manager before installing.
A good choice for Linux users who want to manage configurations from a desktop interface. Install through your distribution's package manager to help resolve dependencies. The desktop system proxy may not cover terminal apps or background services; check each app's proxy settings separately.
Architecture: AMD64 / x86_64 · Package formats: DEB, RPM
A DEB installer for AMD64 desktops. Check that your distribution meets the GUI dependencies before importing a configuration. If you only need a proxy service on a server, skip the GUI client and see the Mihomo core downloads below.
Architecture: AMD64 · Package format: DEB
| Item | What to check before installing |
|---|---|
| Distribution and dependencies | Check whether your system uses DEB or RPM packages. Refer to your package manager's dependency prompts for desktop library requirements. |
| Processor architecture | This section provides AMD64 / x86_64 builds. For ARM servers, check the core downloads below; don't install the desktop AMD64 package. |
| Desktop environment | GUI clients require a working desktop session. On a headless server, run the core instead. |
| Traffic routing | The system proxy, terminal environment variables and TUN routes work separately. TUN also requires the appropriate device and network management permissions. |
The core parses configurations, applies rules and handles proxy connections; it doesn't include a desktop configuration window. Most desktop and mobile users should choose a GUI client above. Server and router users should select a core for their OS and CPU architecture, then configure startup options, the config path and service permissions themselves.
ZIP and GZ are compressed archives; after extracting, you'll still need to choose a run directory and startup method. Install DEB files with a package manager. For routers, check the firmware architecture, available storage and runtime environment first.
| System | Architecture | File format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download ZIP |
| Windows | ARM64 | ZIP | Download ZIP |
| macOS | Intel / AMD64 | GZ | Download GZ |
| macOS | Apple Silicon / ARM64 | GZ | Download GZ |
| Linux | AMD64 | DEB | Download DEB |
| Linux | AMD64 | GZ | Download GZ |
| Linux | ARM64 | GZ | Download GZ |
| Linux | ARMv7 | GZ | Download GZ |
| Linux | MIPS softfloat | GZ | Download GZ |
Before installing over an existing client, quit it and export your configuration or back up its directory. Save subscription links, local rules and override settings separately. Never post files containing personal subscription details in public forums. When switching clients, start with a copy of your YAML file rather than replacing the entire app data directory.
After installation, import your subscription and make sure the configuration is selected, then choose a policy in rule mode. On desktop, enable the system proxy; on mobile, approve the VPN prompt. Test a browser first, then check terminal and other apps. Enable TUN only if you need broader traffic routing; starting with the basics makes permission and routing issues easier to diagnose.
If a configuration won't load, check the logs for invalid fields or indentation. If a subscription won't update, check the link and network connection. Installers, configuration files and proxy nodes are separate parts of the setup, so reinstalling usually won't fix an expired subscription. See the complete setup guide, or continue troubleshooting in subscription help.
Start with Clash Plus on Windows, macOS, Android and iOS; Linux users should start with Clash Verge Rev. Check your device architecture and the package notes, then follow the setup guide to import your configuration. Client interfaces and permission settings vary, so avoid enabling system proxy or TUN in multiple clients at once.
On Windows, check System type in System Information; on a Mac, check the chip under About This Mac; on Android, check the processor and supported ABI in Device information. ARM64 means 64-bit ARM; x64 and AMD64 mean 64-bit x86. If you can't confirm your Android architecture, choose the universal build if available. Some macOS architecture links currently point to the same x64 file. On Apple Silicon, check Rosetta and app compatibility before installing.
The app installer does not include a ready-to-use personal subscription. Import a valid subscription or YAML configuration, select an available policy, then enable the system proxy or VPN connection for your platform. Terminal apps may also need proxy environment variables. For apps that ignore the system proxy, consider TUN mode after checking permissions and routing.
Export your configuration or back up its directory. Note your subscription source, local overrides, rules and DNS settings, then quit the old client. When switching clients, don't overwrite the entire data directory; import the YAML separately and reconfigure system permissions. Restore your settings from the backup if anything goes wrong.
Both clients are no longer maintained. Archived downloads remain available for compatibility with existing setups and migration. For a new installation, choose a maintained client. Older cores may not support newer configuration fields or protocols, so back up your configuration before migrating and check how rules, DNS and TUN behave.
Mihomo is a core that handles proxy protocols, rules and network connections—not a desktop app with a configuration import window. Server and router users need to provide their own configuration, startup method and permissions. Most desktop and mobile users should choose a GUI client above. For core packages, check the operating system, CPU architecture and archive format.