CLIENT PACKAGES / PLATFORMS & ARCHITECTURES
Choose an operating system, then check the processor architecture. Download FlClash, Clash Plus, and Clash Verge Rev below. See the guides and documentation for subscription imports and rule configuration.
DESKTOP / WINDOWS
The desktop clients below offer x64 installers. For a new setup, start with Clash Plus; compare it with Clash Verge Rev if you need service mode and more desktop controls. Check your system type in Settings → System → About before installing. Do not treat an x64 installer as a native ARM64 build.
A good fit if you want to get started with subscription imports, proxy selection, and everyday connections. Add a configuration after installation, then check the system proxy status. If you used another client, disable its traffic routing first to avoid conflicting system settings.
For desktop users who want a graphical interface for subscription management, configuration, and TUN controls. Before using a virtual network interface, check that the service is installed and authorized. For basic browser proxying, start with the system proxy to keep troubleshooting simple.
Built on the Clash Meta core, with configuration, proxy, connection, and log controls in one interface. A good fit if you want a similar workflow on desktop and Android. After importing a subscription, activate the configuration and choose an outbound mode.
Another desktop GUI option for users familiar with Clash configurations. When migrating, check where configurations are stored, the proxy ports, and TUN permissions. Don't just copy interface settings without confirming which configuration is actually active.
Archived downloads are provided for migrating older setups and reproducing compatibility issues. Choose a maintained client for new devices. Older cores may not support newer protocols or rule fields; check the logs for configuration parsing warnings when importing a newer subscription.
| Check | Installation notes |
|---|---|
| OS and architecture | Use a supported 64-bit Windows version where possible. Check the selected client's installer for its minimum OS version. No native ARM64 installer is available in this section. |
| Network permissions | System proxy and TUN are different traffic-routing methods. TUN typically requires administrator approval or client service support. Follow the system prompts the first time you enable it. |
| Migrating from an older client | Turn off the old app's system proxy and startup setting, then quit it. After installation, check the proxy port to make sure no old proxy address is still configured. |
DESKTOP / MACOS
Check About This Mac in the Apple menu to see whether your Mac has Apple Silicon or an Intel chip. Clash Plus offers separate builds for each. Some clients below currently link to the same Intel package from both chip options; the button label identifies this, but does not mean the package is native to your Mac.
Choose the DMG for your chip, mount it, and follow the installer prompts to move the app into Applications. Import a configuration before first use. If you need to route traffic from more apps, check the relevant network permissions and routing settings.
A good fit if you prefer desktop configuration management and rule editing. Both chip options in the current listing provide an x64 DMG. Apple Silicon users should check Rosetta compatibility; confirm the actual package architecture before installing.
Keep a familiar FlClash layout for configuration, proxy, and log controls on macOS. The current listing provides an AMD64 DMG, and both chip options link to the same file. Apple Silicon users should check compatibility requirements; for a clearly labeled native build, see Clash Plus above.
Kept as an archived option for migrating an existing menu bar workflow. The current listing is an x86_64 DMG, and both chip options link to the same file. Check core compatibility separately for older setups. This archived client is not recommended as the default for a new device.
| Check | Installation notes |
|---|---|
| Chip and macOS version | Apple Silicon uses ARM64; Intel Macs use x64 or AMD64. Check the package for its minimum macOS version. Compatibility through translation is not the same as native support. |
| First launch | If macOS blocks the app, check its source and read the system alert. Then review the specific reason under System Settings → Privacy & Security. Don't disable system-wide security protections. |
| Traffic routing | Quit other proxy apps before authorizing the system proxy or virtual network interface. If your network behaves unexpectedly after quitting the client, check whether the current network service still has old proxy settings. |
MOBILE / ANDROID
Most recent Android phones use ARM64, but check your device's actual architecture. After downloading an APK, grant installation permission only to the app you'll use to open it. The first connection usually asks for VPN permission; other VPN or proxy apps on the device may compete for the same system connection.
ARM64 build available. After installing, add your own subscription and choose an available proxy policy, then follow the prompts to connect. If battery optimization stops the app in the background, adjust battery settings as needed; you don't need to grant every background permission at once.
An Android client for Clash Meta configurations. If you know your device architecture, choose the matching build; otherwise, use the universal build. If a subscription fails to parse, check its format and the logs rather than repeatedly installing packages for the same architecture.
Its navigation and configuration concepts are similar to the desktop app. After importing a subscription, make sure the right configuration is selected, then choose an outbound in the Proxy tab. Background restrictions, VPN permissions, and subscription availability are separate issues and should be checked independently.
For users whose configurations and workflow are supported by Surfboard. Don't assume Clash YAML can be imported as-is. Confirm the supported format with your subscription provider, then check that the rules and proxy groups meet the client's requirements.
| Check | Installation notes |
|---|---|
| Processor architecture | arm64-v8a and armeabi-v7a target compatible 64-bit and 32-bit ARM devices, respectively. If the installer reports incompatibility, check the architecture and minimum Android version first. |
| VPN permission | Android requires confirmation to create a local VPN connection. Other VPNs, work profiles, or always-on VPN settings may affect connectivity; check the settings on your device. |
| Installing over an existing app | Installing over an existing app usually requires the same signing key. If you encounter a signature conflict, back up your configuration before deciding whether to uninstall the old app; uninstalling may erase app data. |
MOBILE / IOS
Install Clash Plus on iPhone or iPad through the App Store. Check the store listing for compatible OS versions, app details, and pricing. Installing the app and setting up a subscription are separate steps: after downloading, import your own configuration and authorize the VPN connection.
Check supported devices and update notes on the App Store listing. For first use, import a subscription, then check your proxy selection and connection status. If your device is managed by an organization, VPN access may be restricted by its policies; check the relevant device settings.
Official website: clashplus.io
| Check | Installation notes |
|---|---|
| Device compatibility | Check the App Store's Compatibility section to confirm your device and OS meet the requirements. The App Store handles installation and updates. |
| Connection permissions | Follow the system prompts to add a VPN configuration the first time you connect. If you already use another VPN, check which one is currently active. |
| Subscriptions and configuration | After installation, add a compatible subscription or configuration and check your proxy groups. A connection icon only confirms that the VPN tunnel is established; it doesn't mean all traffic uses the same outbound. |
DESKTOP / LINUX
This section is for desktop AMD64 / x86_64 systems. For Debian- and Ubuntu-based distributions, choose DEB; for distributions using an RPM package manager, choose RPM. A matching package format does not guarantee that all system libraries are compatible. If installation fails, keep the dependency details reported by your package manager.
DEB and RPM desktop installers are available. Choose the format for your distribution and let its package manager handle dependencies. Before enabling TUN, check the service, permissions, and routing. Desktop apps must read system proxy settings for the proxy to take effect.
AMD64 DEB available for desktop users who prefer the FlClash interface. After installation, verify your subscription and rules using the system proxy, then enable TUN if needed. Servers and routers don't need a desktop environment; see the core section to deploy Mihomo directly.
| Check | Installation notes |
|---|---|
| Architecture and distribution | Use uname -m to check your processor architecture. The GUI packages in this section are AMD64 / x86_64. Required libraries and desktop components must also meet the installer's requirements. |
| Package format | DEB and RPM use different package management systems. Don't install one by simply changing the file extension. For missing dependencies, use your distribution's package repositories where possible. |
| TUN and routing | Make sure the system supports TUN and that you have the required permissions. Before changing routes on a remote device, prepare a way to restore your connection so you don't lose access. |
ENGINE / MIHOMO
Mihomo is part of the Clash Meta core ecosystem. This section is for users running services on servers or routers, or managing their own deployments. A core package is not a desktop client with subscription management; most users should choose a GUI client above and don't need to install a separate core.
Before deployment, check the operating system, CPU instruction set, and package format. With an archive, you'll need to set up the configuration directory, run permissions, and service startup yourself. Install DEB packages with the appropriate package manager. Before changing DNS, routes, or TUN on a remote server, make sure you have a way to restore administrative access.
| Operating system | Architecture | Package format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 |
| Windows | ARM64 | ZIP | Download ARM64 |
| macOS | Intel · AMD64 | GZ | Download Intel |
| macOS | Apple Silicon · ARM64 | GZ | Download Apple Silicon |
| Linux | AMD64 | DEB | Download AMD64 · DEB |
| Linux | AMD64 | GZ | Download AMD64 · GZ |
| Linux | ARM64 | GZ | Download ARM64 |
| Linux | ARMv7 | GZ | Download ARMv7 |
| Linux | MIPS · softfloat | GZ | Download MIPS softfloat |
| Check | Deployment notes |
|---|---|
| Hardware and instruction set | ARMv7, ARM64, and MIPS are not interchangeable. For MIPS, also check the device's endianness and floating-point support; don't choose a package based on the router brand alone. |
| Configuration and permissions | Prepare a valid YAML configuration and make sure the file is readable. On Linux, the extracted executable needs execute permission. Enabling TUN or changing system routes also requires additional permissions. |
| Service and management interface | Set up process supervision, logging, and restart behavior yourself. Restrict the external control interface's listening address and access to avoid exposing it directly to the public internet. |
AFTER INSTALLATION
The installer only gets the client running. Check subscriptions, outbounds, and traffic routing separately.
DOWNLOAD FAQ
For Windows, macOS, Android, and iOS, start with Clash Plus; for Linux, start with Clash Verge Rev. Choose FlClash if you want a similar interface on desktop and Android. Check your operating system and processor architecture first, then compare subscription management and TUN controls.
On Windows and Linux, x64 and AMD64 usually refer to 64-bit Intel or AMD processors. Android arm64-v8a builds are for 64-bit ARM devices, while armeabi-v7a builds are for compatible 32-bit devices. On macOS, check your chip in About This Mac. Package architectures are listed on this page; if you run an Intel build on Apple Silicon, check Rosetta compatibility.
The client installer does not include a working subscription. Import your subscription or local configuration, activate it, and select an outbound policy in a proxy group. Then enable the system proxy or TUN as needed. Check requests and logs to confirm that app traffic is reaching the core.
Export or back up your local configuration, override files, and custom rules. Note your current subscription and network settings. Quit the old client before installing the update, and avoid running multiple clients that control the system proxy or TUN at the same time. After updating, check that your configuration is active and the required permissions are in place.
These clients are listed here as archived downloads because they are no longer maintained. They may be useful when migrating an older setup or reproducing a compatibility issue. For new devices, choose a maintained client. Support for newer protocols and rule fields in older configurations depends on the core in use.
Desktop clients provide a graphical interface for subscriptions, proxy groups, logs, and system proxy settings. The Mihomo core package is intended mainly for servers, routers, and users managing their own services; you must provide the configuration, launch method, and permissions. For most desktop and mobile use, choose a graphical client.