Before you install
Choose a client for your operating system, then check the processor architecture. Downloads for Clash Plus, Clash Verge Rev, and FlClash are organized by platform, with core packages listed separately.
Clients load configurations and manage outbound connections. Installers don’t include a subscription service; you’ll need a subscription link or local configuration to get started.
Platforms and architectures
Each platform lists popular clients first, followed by alternatives. Check the system requirements below each card before installing; packages aren’t interchangeable between operating systems.
The desktop installers below are for x64 devices. Find your system type under “Settings → System → About.” Don’t treat an x64 package as a native ARM build. Compatibility on ARM devices depends on your Windows version and the app’s dependencies.
For users who want to manage configurations, proxy groups, and proxy modes through a GUI after installation.
After installation, import a configuration and choose an outbound option in a proxy group. System proxy and TUN are different ways to route traffic. For your first connection, try enabling the system proxy and checking the connection logs; there’s no need to change every network setting at once.
Official site: clashplus.io ›For users who want to manage subscriptions, rules, and service mode on desktop.
Complete the standard installation first, then install or start the related service if you need TUN. Service installation requires system permissions. If it fails, note the message—repeatedly clicking Start won’t resolve permission, driver, or port conflicts.
For users who want a similar configuration management workflow on desktop and mobile.
AMD64 also works with Intel processors that support the x64 instruction set; it isn’t an AMD-only package. When migrating configurations, check local file paths, overrides, and DNS options. A similar interface doesn’t mean system permissions work the same way on every platform.
For users who prefer a different desktop interface for configuration and connection management.
Before installing alongside another client, disable the old client’s system proxy and traffic routing. If multiple apps compete for the same local ports or change the system proxy at once, it becomes difficult to tell what’s affecting connection tests and app traffic.
Archived download for migration reference and reproducing configurations in existing setups.
For new installations, choose a maintained client. Archived clients may include a core with a different feature set from current mihomo releases, so newer protocol fields or rule syntax may not load. Keeping a configuration doesn’t mean you need to keep using the old executable.
| Check | What to look for | Before installing |
|---|---|---|
| Operating system | Use a supported 64-bit version of Windows; check each package for its minimum version | Note your Windows version and system type from System Information |
| Processor | Packages in this section are x64 / AMD64 | Check compatibility separately for ARM devices |
| Permissions and components | Standard installation, system services, and TUN have different permission requirements | Grant permissions only when clearly requested |
If Store apps can’t access the network through the local proxy, the cause may be the UWP loopback restriction—not a damaged installer. First check whether regular desktop apps work, then see FAQ troubleshooting. Don’t mistake a traffic-routing issue for an installation failure.
Check your chip type under Apple menu → About This Mac. Apple Silicon and Intel apps use different native architectures. Both download options are listed below, with a note where the current release listing points to the same x64 file for both.
Choose the DMG for your chip. Manage subscriptions and proxy settings through the desktop interface.
Open the disk image and follow the instructions to install the app in Applications, then launch it from there. When setting up a system proxy or network extension for the first time, read the macOS permission prompt and verify the app name before continuing.
Official site: clashplus.io ›For users who want desktop configuration management and rule views. Check the architecture note below before installing.
Both chip options in the current listing point to the same x64 file; it isn’t a native ARM release. Apple Silicon users should check Rosetta requirements first. If you need a native build, compare other clients in this section.
For users who want a consistent configuration workflow across desktop and mobile.
Both architecture links currently point to a DMG labeled AMD64. Test a standard proxy connection after installation before enabling features that require additional permissions. If macOS reports an architecture incompatibility, renaming the file won’t fix it.
Archived download for reference when migrating an existing menu bar client setup.
Both chip options currently point to an x86_64 file. The menu layout, permissions, and bundled core in an older client don’t represent how the current ecosystem works by default. For a new device, consider a maintained option and keep a recoverable copy of your configuration.
| Check | What to look for | Before installing |
|---|---|---|
| Chip | Choose ARM64 for Apple Silicon and x64 / x86_64 for Intel | Check the actual filename and package architecture too |
| Operating system version | Minimum version varies by client release | Compare your macOS version with the installation requirements; the same chip doesn’t guarantee compatibility |
| Permissions | System proxy, VPN, and network extensions may each require separate approval | Follow system prompts and check the app’s source and requested permissions |
Quit the client before updating, then replace the app. If the disk image is still mounted, make sure you’re launching the copy in Applications so you don’t confuse it with the mounted installer during a later update.
Most recent phones use ARM64. Older devices may need a 32-bit ARM package. If you’re unsure, check the device’s supported ABIs or choose a universal package if available. A 64-bit processor doesn’t necessarily mean the installed Android system is 64-bit.
ARM64 download for importing configurations and switching proxy modes on your phone.
The first connection requires approval for Android’s VPN request. Android usually allows only one standard VPN service to use the VPN channel at a time, so check that no other VPN or similar network tool is running before you connect.
Official site: clashplus.io ›Choose the APK for your device’s ABI, or use the universal package for multiple architectures.
After importing a remote configuration, select it and start the service. Updating a subscription and connecting through a proxy are separate actions. If a subscription update fails, check that the link is still valid and your network is working; repeatedly reinstalling the app won’t help.
ARM64 and 32-bit ARM packages are available. Choose the one supported by your system.
If the connection drops after the screen has been locked for a while, check whether battery management is restricting background activity, then review the app logs. Background operation, auto-start, and VPN permission are separate settings; the notification icon alone doesn’t confirm that everything is working.
An Android client with its own configuration format, for users who already have compatible configurations.
Surfboard isn’t a mihomo GUI, and you shouldn’t assume it can import Clash YAML directly. Before downloading, confirm that your configuration provider supports its format and protocols. Changing a file extension won’t convert the format or add missing fields.
| Check | What to look for | Before installing |
|---|---|---|
| System and ABI | arm64-v8a is ARM64; armeabi-v7a is 32-bit ARM | Check the ABIs supported by your system and the client’s minimum Android version |
| Install permissions | Android may ask you to allow app installs from the current source | Grant the required permission only to the browser or file manager you’re using |
| Installing over an existing app | An update can fail if the old app and new package have different signing certificates | Export your configuration first; address the existing installation after identifying the cause |
Universal packages usually take up more download and storage space; they don’t make connections faster. After installation, check that the configuration loads before setting up per-app routing and background behavior. This keeps first-time troubleshooting simpler.
Install Clash Plus on iPhone or iPad from the App Store. Check the store listing for current compatibility, app permissions, and release details, then import the configuration you need after installation.
Get the app from the App Store. The first time you connect, follow the system prompt to allow a VPN configuration.
After installation, paste a subscription link or import a configuration file using a method supported by the app. A successful import only means the configuration was saved: you still need to select it, check the proxy groups, and start the connection. Subscription links may contain credentials, so don’t post them in public forums or include them in shared screenshots.
Official site: clashplus.io ›| Check | What to look for | After installation |
|---|---|---|
| System compatibility | Check the App Store compatibility section | Make sure your iOS / iPadOS version meets the requirements |
| Network permissions | A system VPN configuration requires approval to connect | Check the app name before approving the system request |
| Configuration source | The app must support the subscription format and protocols | After importing, check the parse results and proxy groups |
If another VPN configuration is already set up on your device, check which one is active so you don’t mistake another app’s connection status for Clash Plus. See the user guide for import and verification steps.
GUI clients are suited to Linux devices with a desktop environment. The DEB and RPM packages here are for AMD64; for servers, routers, and other processor architectures, see the core section. Even when the package format matches, dependency versions may differ between distributions.
Choose DEB or RPM for your distribution. Manage configurations and the system proxy on desktop.
Debian, Ubuntu, and related distributions usually use DEB packages; Fedora and similar distributions usually use RPM. Prefer a package manager that handles dependencies. If the interface won’t start, check the terminal error first, then inspect runtime libraries and the desktop environment.
AMD64 DEB package for desktop systems that support this format and meet the runtime requirements.
After installation, whether the system proxy affects an app depends on the desktop environment and the app’s own settings. Command-line tools may not use desktop proxy settings. When testing, check browsers, terminals, and background services separately rather than drawing conclusions from a single webpage.
| Check | What to look for | Before installing |
|---|---|---|
| Architecture | Packages in this section are AMD64 / x86_64 | Check the machine architecture with uname -m |
| Package management | Choose DEB or RPM as supported by your distribution | Check dependencies; renaming a file won’t convert its package format |
| Runtime environment | GUI clients need a compatible desktop environment and runtime libraries | For headless systems, consider the standalone core |
| Network permissions | TUN and standard local proxy mode have different permission requirements | Set up services or grant only the permissions required by the client |
Linux desktop proxies, environment variables, and transparent traffic routing are configured at different levels. Start with a local proxy for a basic connection, then add TUN if needed. Back up existing network settings before changing routes, especially on remote hosts where you need a way to restore access.
For users managing services on servers or routers. The core loads configurations and processes traffic; it isn’t a GUI client. Most desktop and mobile users should choose a GUI client above instead of managing services, logs, and permissions themselves.
| System | Architecture | Format | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP | Download AMD64 ZIP |
| Windows | ARM64 | ZIP | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ | Download ARM64 GZ |
| Linux | AMD64 | DEB | Download AMD64 DEB |
| Linux | AMD64 | GZ | Download AMD64 GZ |
| Linux | ARM64 | GZ | Download ARM64 GZ |
| Linux | ARMv7 | GZ | Download ARMv7 GZ |
| Linux | MIPS soft-float | GZ | Download MIPS GZ |
| Check | Requirement | Common pitfall |
|---|---|---|
| Architecture and ABI | Match the instruction set, endianness, and floating-point ABI | Don’t use MIPS and MIPSel interchangeably just because their names look similar |
| Working directory | Configuration and required data files must be readable; required directories must be writable | Downloading a binary doesn’t automatically provide a working subscription |
| Permissions and ports | Listening ports must be available; TUN and other features need the required permissions | A successful standard proxy launch doesn’t mean TUN is enabled |
| System environment | The OS kernel, instruction set extensions, and package dependencies must meet the build requirements | ARM or Linux in the name doesn’t guarantee that every package is compatible |
Before choosing a router package, check the device firmware notes and architecture information. If you get an “exec format error,” check the architecture and endianness first instead of changing network rules. See the protocol guide for protocol capabilities and core families.
Installation and migration
Install the client and load a configuration before changing how traffic is routed. Change one setting at a time to make issues easier to track down.
After downloading, check that the file format matches your operating system: EXE for Windows installers, DMG for macOS, APK for Android, and DEB or RPM for the corresponding package manager. Archives need to be extracted; they aren’t installers.
If the system reports an incompatibility, note the full message and check the architecture, OS version, and dependencies. Installation steps that request permission should have a clear purpose. Don’t disable all system security features to work around an unknown error, or install extra components from an unclear prompt.
After installing the client, open the configuration page and import a subscription link or local YAML file. Confirm that it parses successfully and select it. Check that the proxy groups contain a usable outbound, choose a rule mode, then start the proxy or VPN feature appropriate for your platform.
Finally, verify the connection using the logs and the app’s actual network behavior. A successful latency test only means that the test request received a response; it doesn’t verify app traffic. If a site behaves unexpectedly, check the matched rule, selected proxy group, and DNS behavior.
Before switching clients, keep your subscription URL, local rules, override files, and any interface settings you need. Remote subscriptions can usually be imported again, but script paths, rule-set caches, and client-specific fields may need separate handling. Verify everything in the new setup before removing the old client.
While testing the migration, disable the old app’s system proxy, TUN, and auto-start to prevent multiple clients from routing traffic at once. Archived apps can help you compare configurations, but don’t assume they support current protocols and configuration fields.
The client version describes the interface and bundled features; the core version determines support for many protocols and configuration options. They may not advance in sync. After updating the interface, check which core the client actually uses. Replacing the core alone may not change the version shown in the interface.
Cards on this page display a version only when non-empty version information is available. No version shown doesn’t mean the installer won’t work, and it doesn’t indicate when it was last updated. Check the package’s release notes, in-app information, and runtime logs for changes and compatibility details.
See the user guide for setup steps, client comparisons for interfaces and use cases, and the quick reference for configuration, proxy group, and DNS terminology.
Download FAQs
For rules, subscriptions, and DNS issues during connection, see the FAQ.
Start with Clash Plus on Windows, macOS, Android, or iOS; for Linux, consider Clash Verge Rev. Check your operating system, processor architecture, and package format before choosing based on interface preferences. After installing a client, you’ll still need a working configuration; the installer does not include a subscription service.
x64 and AMD64 usually refer to the same 64-bit desktop instruction set, regardless of processor brand. ARM64 is for devices with the corresponding architecture; on Android, armeabi-v7a means 32-bit ARM. Universal packages include multiple architectures and are usually larger. Check your system information, the package’s actual architecture, and the client’s requirements before choosing.
Some upstream release listings currently point both Apple Silicon and Intel links to the same file, labeled x64 or x86_64. Don’t assume it’s a native ARM build based on the button label alone. Apple Silicon users should check whether the package requires Rosetta and whether it’s supported on their version of macOS.
Keep a copy of your existing configuration, then import the subscription link or local YAML file into the new client. Clients using the same core can often reuse most configuration fields, but override scripts, extended fields, interface preferences, and local paths may not carry over. After importing, check the logs, proxy groups, DNS, and TUN settings. Disable the old client only after everything works.
Make sure the download finished, the package format is right for your operating system, and the processor architecture matches. Note the full error message from the system. On desktop, also check supported OS versions, available disk space, and whether another installation is running. On Android, check permission to install from the chosen source and whether the existing app has a conflicting signature. Don’t disable all system security features to work around an unknown error.
The mihomo core reads configuration and handles network traffic, but usually doesn’t include a desktop GUI. Choose a core package if you manage services yourself on a server or router; most desktop and mobile users should start with a GUI client. Extracting the core alone doesn’t configure it—you’ll also need a configuration file, a working directory, and the required permissions.