Client downloads / platforms and architectures
Choose Clash Plus, Clash Verge Rev, or FlClash for your operating system. Check your processor architecture before downloading. For subscription import and connection setup, see the user guide.
Platform index
Each platform lists available clients in a consistent order. The primary button links to the usual installer, with other architectures shown alongside it. Version details appear only when valid release data is available; verify file compatibility with your system.
The desktop installers here are x64. Check your system type under Settings → System → About. On an ARM device, confirm that Windows can run the app before downloading; an x64 installer is not a native ARM64 build.
Manage subscription imports, proxy group selection, and everyday connections from a graphical interface. After installing, load your configuration, check the listening port, then enable the system proxy. If you need to capture traffic from more apps, configure TUN separately and grant the required permissions. Avoid changing several network settings at once.
For desktop users who want to manage configuration, overrides, and service options. After importing a subscription, check which configuration is active. When changing GUI settings, consider how they interact with subscription fields. Service mode and virtual network adapter features may require administrator access.
A cross-platform GUI for a similar experience on desktop and mobile. The installer is convenient for everyday use; with a ZIP archive, you’ll need to extract and manage the app directory yourself. Whichever format you choose, quit the old process and back up your configuration before updating.
Another desktop interface for managing configurations, suited to users with existing Clash configurations who want to compare workflows. When migrating, don’t just copy UI settings: check the core, rule references, and DNS configuration too. On first launch, test connectivity with the system proxy before enabling additional traffic-capture features.
Archived download for legacy compatibility and configuration migration. Don’t expect ongoing support for newer systems or protocols. Before migrating from an older version, export your configuration and note your subscription source. Check field support in the new client, and don’t run both apps with the system proxy enabled.
| Check | Requirements and steps |
|---|---|
| Processor | This section provides x64 installers; they won’t run directly on 32-bit systems. |
| Windows version | Minimum Windows versions vary by release. Check the release notes before installing on an older version of Windows. |
| Permissions | Standard system proxy use and service mode require different permissions. Follow system prompts when installing a service or enabling TUN. |
| Port conflicts | Quit other proxy clients and make sure the local listening port is free before enabling the system proxy. |
Open Apple menu → About This Mac to identify your Mac as Apple Silicon or Intel. Clash Plus offers builds for both architectures. For some projects below, both download links currently point to the same Intel build; this is noted on the card. Don’t assume a link labeled for Apple Silicon is a native ARM build.
Choose the DMG for your chip. Open the disk image, drag the app to Applications, and launch it from there. After importing a subscription, check your proxy groups and system proxy settings. If you need a background service or TUN, follow the client’s instructions to grant system permissions rather than repeatedly running the installer.
For managing multiple configurations and desktop proxy settings. Both the Apple Silicon and Intel links in the current listing return x64 files. Before using them on Apple Silicon, check that Rosetta can run the app. System proxy and TUN capture traffic differently: verify a basic connection first, then decide whether you need an auxiliary service.
For users who want a similar cross-platform interface. Both current macOS downloads are amd64 (Intel) builds. Apple Silicon users need to check Rosetta compatibility. After migrating a configuration, review local paths, rule set references, and proxy permissions; paths from another operating system may not work as-is.
Archived client for reference when working with older configurations. Both downloads in the current listing are x86_64 builds, so Apple Silicon users will need a compatible runtime. For new installs, consider a maintained client. Back up older configurations before migrating, and check that the new core supports your DNS, rules, and protocol fields.
| Check | Requirements and steps |
|---|---|
| Chip | Use an arm64 build on Apple Silicon and an x64 build on Intel. Compatibility mode depends on your system meeting the required conditions. |
| Windows version | Check the current release notes for the minimum macOS version. Archived projects may not work with newer systems. |
| Network permissions | System proxy, auxiliary services, and virtual network adapters may each request separate permissions. Grant only what your setup requires. |
Most recent phones use ARM64, but check the ABI supported by your device. When you connect for the first time after installing the APK, Android usually prompts you to authorize VPN access. Only one VPN app can capture traffic at a time.
This download is an ARM64 build. After installation, import a subscription or configuration, select a proxy group, then connect and approve the Android VPN prompt. If the connection drops when the screen locks, check background activity and battery restrictions before assuming the proxy node is unavailable.
An Android client for managing configurations and connections. If you know your device’s ABI, choose ARM64 or ARMv7; if not, consider the universal build, which is usually larger. After importing, check for configuration parsing errors. If a field isn’t supported, check the core version and subscription contents instead of reinstalling repeatedly.
For users who want a similar setup on desktop and Android. Choose ARM64 or ARMv7 based on your system ABI. A 64-bit capable processor doesn’t necessarily mean the device’s installed system provides a 64-bit runtime. After connecting, use the logs to check rule matches and adjust per-app traffic capture if needed.
An alternative Android configuration client for users with compatible existing configurations. Surfboard uses a different configuration syntax from Clash YAML; changing the file extension alone won’t make a file importable. Before downloading, check which formats and protocols your provider supports, and keep the original configuration so you can compare rule behavior after conversion.
| Check | Requirements and steps |
|---|---|
| System and ABI | Check your Android version and support for arm64-v8a or armeabi-v7a. Refer to the release notes for the minimum supported version. |
| Install source | When prompted, grant permission only to the app performing the installation. You can revoke it afterward. |
| Connection permissions | Approve the Android VPN prompt. Switch between VPN apps rather than running them simultaneously, to avoid one replacing the other’s connection. |
| Background activity | Battery optimization can affect connection stability. Check your device’s background activity restrictions. |
Check the App Store listing for Clash Plus compatibility, system requirements, and current availability. After installing, follow the app’s setup flow to import a configuration and grant network access when connecting for the first time.
Check the App Store listing for compatible devices and system versions before installing. Add subscription URLs, local rules, and proxy groups in the app; desktop settings won’t sync to your phone automatically. After connecting, check the VPN status in iOS and the app logs. Verify the basic connection before adjusting routing rules.
Client website: clashplus.io
| Check | Requirements and steps |
|---|---|
| Windows version | Check the compatibility details on the App Store listing to make sure your device meets the requirements. |
| Configuration | Have a subscription or configuration ready to import, and check that the client supports its format and protocols. |
| Network permissions | Follow the system prompt to add a VPN configuration the first time you connect. After switching VPN apps, check that the connection is active again. |
GUI clients are for desktop environments. The builds here are amd64: choose DEB for Debian- or Ubuntu-based distributions, or RPM for distributions that use RPM package management. For servers and routers, see the standalone core below.
For Linux desktop users who want graphical configuration management. Choose DEB or RPM for your distribution, and check desktop runtime dependencies before installing. Whether apps honor the system proxy depends on the desktop environment and each app. For TUN, also check service permissions, routing, and interactions with other network management tools.
This section provides an amd64 DEB for desktop systems that support the package format and meet its runtime dependencies. After installing, launch the app from your applications menu, load your configuration, and check the logs. If terminal apps don’t use the desktop system proxy, configure their proxy settings separately. A connected status in the client doesn’t mean all traffic is being routed through it.
| Check | Requirements and steps |
|---|---|
| Architecture | Desktop builds here are amd64 / x86_64; they can’t be installed directly on ARM routers. |
| Distribution | Check that the package format, system libraries, and GUI dependencies meet the client’s requirements. |
| Runtime environment | GUI clients need a desktop session. A standalone core is a better fit for headless servers. |
| Permissions and routing | TUN and policy routing require appropriate permissions. Check existing firewall and network service settings before enabling them. |
core / Mihomo
For users running services on servers or routers, or managing deployments themselves. Most desktop users should choose a GUI client above. The standalone core parses configuration and handles traffic, but has no subscription management interface and won’t configure the system proxy automatically when started.
| Target system | Processor architecture | File | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP | Download Windows AMD64 |
| Windows | ARM64 | ZIP | Download Windows ARM64 |
| macOS | Intel / AMD64 | GZ | Download macOS Intel |
| macOS | Apple Silicon / ARM64 | GZ | Download macOS ARM64 |
| Linux | AMD64 | DEB | Download Linux AMD64 DEB |
| Linux | AMD64 | GZ | Download Linux AMD64 GZ |
| Linux | ARM64 | GZ | Download Linux ARM64 |
| Linux | ARMv7 | GZ | Download Linux ARMv7 |
| Linux | MIPS soft-float | GZ | Download Linux MIPS soft-float |
For a standalone deployment, plan the configuration directory, log location, and process management yourself. First run the core in the foreground to confirm the configuration loads and DNS and rule resources work, then set up a persistent service. Before changing routes on a remote device, keep a management connection available in case a configuration error cuts off access.
The same interface name doesn’t guarantee the same core features, and a standalone core may be on a different release schedule from a client’s bundled core. If a protocol or field isn’t supported, check which core is actually running, then verify the subscription format. See the protocol guide for protocol support and configuration differences.
A download solves installation, not connection issues. Getting connected also depends on configuration, permissions, and how traffic is routed. For a first setup, check each in order; it’s easier to find problems than by changing several settings at once.
Open the client, import a subscription or local configuration, and check for parsing errors. Then select a proxy group referenced by your rules. Start by testing with the system proxy; consider TUN only if an app doesn’t honor the system proxy. A successful import means the configuration loaded, not that every proxy in the subscription is available.
Local file paths, service permissions, and background restrictions vary by platform. Preserve protocol and rule sections when copying a configuration, but recheck fields that depend on the system environment. Subscription URLs often contain access credentials; don’t share them in public screenshots, forums, or logs.
See the first-time import and connection guide →Before updating, save your local configuration, overrides, and any essential UI settings, and note the port in use. Quit the old client before launching the new one to prevent the old process from holding the listening port. When switching clients, don’t assume their settings use the same names or work the same way.
After upgrading, check configuration parsing, proxy group selection, and rule matches. Then verify startup settings and background services. A client UI update doesn’t necessarily update the core too, especially if your subscription uses new protocols or fields. Check the actual core version to confirm compatibility.
Read about core versions and compatibility →Download FAQs
Answers about choosing files, permissions, and updates. Select a question to expand it; answers remain available without JavaScript.
For your first install, choose a client with a graphical interface. Clients offer subscription import, proxy group selection, logs, and system proxy controls. The Mihomo core is mainly for servers, routers, or users who manage configuration and services themselves. Downloading the core alone does not install a client.
Check your processor and system architecture in your system settings. Windows x64 and Linux amd64 usually refer to the same instruction set; ARM64 is for a different processor architecture. If you’re unsure which ABI your Android device supports, choose the client’s universal build. For macOS, check the architecture of the actual download. Apple Silicon Macs need a compatible runtime to use Intel builds.
The installer contains the client application, but does not provide proxy service. After installation, import a subscription or configuration file you’re authorized to use, then check your proxy groups, rule mode, and system proxy settings. Follow the user guide on this site, and treat subscription URLs as sensitive information.
First, make sure the file matches your system and architecture, then read the system prompt. On Android, temporarily allow the app performing the installation to install unknown apps. Desktop service mode and TUN usually require additional permissions. Don’t permanently disable system security to run an app. If installation fails, note the exact error and check the release notes.
Archived clients may help with legacy compatibility and configuration migration. Once a project is unmaintained, don’t expect ongoing support for newer systems, protocols, or bug fixes. For a new install, choose a maintained client. Back up your configuration before migrating, and check that the new client supports your subscription format and fields.
Keep your subscription source, local configuration, overrides, and any essential UI settings. Note the current listening port and traffic-capture method. Quit the old process before upgrading so two clients don’t compete for the same port. After the update, check that the configuration loads, proxy groups are correct, and the system proxy points to the current port.