Choose a package and architecture
Choose your operating system, then your processor architecture. For everyday use, download a graphical client; for servers and routers, consider the standalone core.
Desktop clients
For a first installation, start with Clash Plus. The desktop downloads below are mainly x64. If you’re using Windows on ARM, check app compatibility first; an x64 installer is not a native ARM64 build.
For users who want to manage subscription imports, proxy groups, and everyday connections in a graphical interface. Install the x64 version, then import your configuration using the documentation.
Before connecting, check the active configuration and system proxy status. Project website: clashplus.io.
For desktop users who need to manage subscriptions, rules, and overrides. After installation, make sure the configuration loads correctly, then enable the system proxy or TUN as needed.
Service mode and TUN may require administrator privileges. If a subscription import fails, check the logs first instead of changing all your network settings right away.
Consider FlClash if you want a similar experience on desktop and mobile. Choose the EXE for a standard installation; choose the ZIP only if you need to manage the application directory yourself.
Extract the ZIP completely before running the program; don’t launch it from within an archive utility. The ZIP package may still require additional runtime components.
Another option for managing desktop configurations. When migrating from another client, import the original subscription first and verify its rules and proxy groups before moving overrides over one at a time.
Options may have different names across clients. Don’t overwrite another client’s entire data directory, and take particular care to preserve existing subscriptions and rule files.
Kept for reproducing older setups and migration comparisons, not recommended for a first installation. Older cores may not support fields in current subscriptions. A client opening successfully doesn’t mean the configuration will work.
Before migrating, note your ports, system proxy settings, and custom rules. Quit the old client before starting the new one to prevent both instances from claiming the same listening port.
| Check | How to check | Before installing |
|---|---|---|
| Operating system | Use a supported version of Windows 10 or 11 where possible. Check the installer notes for the specific minimum version. | For older systems, check runtime and UI component requirements first. |
| Processor architecture | Go to Settings → System → About → System type and check whether it’s x64. | The Windows desktop packages listed here are not native ARM64 builds. |
| Permissions | Start the client normally. Grant permissions only if prompted to install a service or create a virtual network adapter. | A regular system proxy and TUN have different permission requirements. |
After installation, start one client, import a subscription, and make sure the configuration is selected before enabling the system proxy. If you still can’t access the network after quitting the app, check whether Windows proxy settings still point to 127.0.0.1 and an old port. Reinstalling repeatedly won’t fix a configuration issue.
Mac desktop clients
First, check your chip type under Apple menu → About This Mac. Choose the package for Apple Silicon or Intel. Some current download buttons still point to the same x64 package, so read the architecture notes on each card before downloading.
Separate packages are available for Apple Silicon and Intel. Choose ARM64 for newer M-series Macs and x64 for Intel Macs, then import your subscription after installation.
Open the DMG and move the app to your Applications folder. Project website: clashplus.io.
For users who need desktop rule management and configuration overrides. Both Mac download buttons in the current listing point to an x64 DMG; Apple Silicon users should check Intel app compatibility before installing.
Running Intel apps on Apple Silicon may require Rosetta. The button reflects the current download listing; it does not indicate a native ARM64 package.
For users who prefer FlClash’s familiar workflow. The current Apple Silicon and Intel download buttons both point to an amd64 file, so confirm your device can run apps built for that architecture before installing.
Here, amd64 and x64 refer to the same processor architecture. The amd64 filename doesn’t mean the app only works with AMD processors.
Kept for migration and comparison with existing setups. Both Mac download buttons currently point to the same x86_64 DMG. For new installations, consider a maintained client listed above.
Before migrating, back up the configuration directory and custom rules, then quit the old menu bar app to prevent its proxy settings from conflicting with the new client.
| Check | How to check | Before installing |
|---|---|---|
| macOS version | Go to Apple menu → About This Mac to check your macOS version. | Minimum requirements vary by client; check the notes for the package you’re downloading. |
| Chip type | Choose Apple Silicon for an Apple M-series chip, or x64 for an Intel processor. | If the listing currently provides an x64 package, check Rosetta compatibility separately. |
| Installation and permissions | Move the app to your Applications folder, then launch it from there. | Grant permission for network extensions, helper services, and the system proxy only when required by the features you use. |
If macOS says the app can’t be opened, first check the download source, system version, and package architecture. Then review the specific warning under System Settings → Privacy & Security. Don’t disable system protection entirely just to launch an app. After migrating clients, also confirm that the new client has taken over the proxy settings for Wi-Fi or Ethernet.
Phones and tablets
Most recent Android phones use ARM64, but choose a build based on the ABI your device supports. If you’re unsure, check the device specifications. Clash Meta for Android also offers a universal build.
For everyday subscription imports and connection management on ARM64 devices. After installation, select a configuration, approve Android’s VPN prompt on first connection, and check the connection status in the notification shade.
Allow app installation only for the browser or file manager you’re using. Project website: clashplus.io.
Choose from these three builds if you need to select a specific ABI or support an older ARM device. The universal build is usually larger; it won’t improve connection speeds or bypass system version requirements.
You’ll still need to select a configuration after importing it. If Android says the app wasn’t installed, check the architecture, available storage, and whether the installed version uses a different signing key.
For users who want a workflow similar to the desktop version. Choose ARM64 for most newer devices or ARMv7 for older 32-bit ARM devices.
If the connection drops when your screen locks, check battery optimization and background activity permissions first. Switching nodes usually won’t help if the system is terminating the app.
For users with a compatible configuration. Surfboard uses a different configuration format from Clash YAML; changing the file extension alone won’t make it importable.
Before downloading, check whether your subscription provider offers a Surfboard-compatible format and supports the protocols you need. If you only have Clash YAML, choose a compatible client above.
| Check | How to check | Before installing |
|---|---|---|
| System and ABI | Check your Android version and which ABIs your device supports: arm64-v8a / armeabi-v7a. | A 64-bit processor doesn’t necessarily mean the device’s operating system supports 64-bit apps. |
| Installation permissions | When prompted, allow app installation from the current source. | Grant installation permission only to the download or file manager app you’re using. |
| VPN and background activity | Approve the VPN permission prompt on first connection and allow background activity if needed. | Another VPN app may be using the same system connection. Quit it before connecting. |
After installation, check subscription updates, configuration selection, and VPN startup separately. If it works with the screen on but disconnects when locked, check battery optimization, auto-start, and background restrictions first. If it never connects, check the subscription’s validity, node status, and logs. Don’t confuse background restrictions with configuration errors.
iPhone and iPad
Check Clash Plus compatibility, the current app description, and installation details on the App Store. After installation, import a subscription and approve the system VPN prompt.
Install directly from the App Store listing on iPhone or iPad. Check the listing for supported systems, compatible devices, and current app details.
Project website: clashplus.io. After importing your configuration, choose a proxy group before connecting.
| Check | How to check | Before installing |
|---|---|---|
| Device and system | Go to Settings → General → About to check your iOS or iPadOS version. | Compare your device details with the App Store compatibility information. |
| Install from | Open the Clash Plus App Store listing. | Check the App Store listing for the app name and developer details. |
| Connection permissions | On your first connection, follow the system prompt to allow adding a VPN configuration. | Installing the app, importing a subscription, and starting a connection are separate steps. |
If the app is installed but your browser still can’t reach a site, first check that the client has a usable configuration and that the connection is actually on. A VPN icon only means the network extension is running; it doesn’t guarantee that every node in your subscription works. Test with a proxy group you know is available, then check your rules and DNS.
Linux desktop
Choose a graphical client if you have a desktop environment. Debian and Ubuntu typically use DEB packages; Fedora typically uses RPM. The desktop packages listed here are AMD64 and aren’t for direct installation on ARM routers.
For Linux users who need subscription management and a desktop control panel. Choose a package format for your distribution; the package manager will prompt for and handle dependencies during installation.
Desktop components and dependencies vary across distributions. If installation fails, read the package manager’s error instead of forcing the installation past dependency checks.
A DEB package for Debian-based desktop systems. For users who prefer the FlClash interface they know from other platforms; check your system architecture before installing.
The desktop system proxy mainly affects apps that honor proxy settings. Command-line tools may need proxy environment variables configured separately, so the tray icon doesn’t tell you whether all traffic is routed.
| Check | How to check | Before installing |
|---|---|---|
| Processor | Run uname -m; x86_64 corresponds to the AMD64 desktop packages listed here. | Don’t use these desktop packages on aarch64, armv7l, or other architectures. |
| Distribution | Check /etc/os-release and choose DEB or RPM for your distribution. | The same package format doesn’t guarantee that every release of every distribution meets the dependencies. |
| Desktop and permissions | Check that you have a graphical environment, desktop dependencies, and permission to install services. | For a headless server, deploying the Mihomo core directly is usually a better fit. |
Install local packages with your distribution’s package manager so you can see how dependencies are resolved. Before enabling TUN or a system service, verify the configuration with a regular proxy port. This helps distinguish configuration parsing errors from issues involving permissions, routing, or the desktop environment.
Server and router deployment
The core reads configuration, applies rules, and routes connections; it doesn’t include a full desktop interface. Most desktop and mobile users should download a graphical client above. Choose a standalone core from the table below only if you need to manage the service, permissions, and logs yourself.
Check the architecture in your system information or with uname -m. MIPS devices also depend on endianness, floating-point ABI, and firmware environment, so “MIPS” alone isn’t enough to choose a package. A standalone core isn’t a router management plugin; deployment must match your firmware environment.
| System | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP, x64 command-line environment | Download AMD64 · ZIP |
| Windows | ARM64 | ZIP, Windows ARM64 environment | Download ARM64 · ZIP |
| macOS | Intel / AMD64 | GZ，Intel Mac | Download Intel · GZ |
| macOS | Apple Silicon / ARM64 | GZ, Mac with an M-series chip | Download Apple Silicon · GZ |
| Linux | AMD64 | DEB, install with a Debian-based package manager | Download AMD64 · DEB |
| Linux | AMD64 | GZ, executable for manual deployment | Download AMD64 · GZ |
| Linux | ARM64 | GZ, aarch64 environment | Download ARM64 · GZ |
| Linux | ARMv7 | GZ, 32-bit ARMv7 environment | Download ARMv7 · GZ |
| Linux | MIPS softfloat | GZ, MIPS environment with soft-float ABI | Download MIPS softfloat · GZ |
| Check | What you need | How to verify |
|---|---|---|
| Runtime environment | An executable that matches your operating system, CPU instruction set, and ABI. | Run the version command first to check for architecture or instruction errors. |
| Configuration directory | Valid YAML, rule files, and any other resources referenced by the configuration. | Test the configuration before starting and confirm that relative paths resolve from the expected directory. |
| Permissions and ports | A regular listening port, a service account, and network permissions granted as needed. | Check the listening logs. Before enabling TUN, confirm you have permission to create a virtual network adapter and modify routes. |
A GZ file usually extracts to an executable, not a graphical app you can install by double-clicking. On Linux and macOS, make it executable and specify a configuration directory when launching it. Run it in the foreground first and check the logs before handing it over to a service manager. Don’t configure it to start at boot before verifying the configuration.
Linux / macOS · after extracting and naming the executable mihomo
chmod +x ./mihomo
./mihomo -v
./mihomo -t -d ./config
./mihomo -d ./configSave a valid configuration as ./config/config.yaml. A successful test only confirms that the configuration parses; check proxy groups, DNS, and listening ports separately to verify connectivity. See YAML common fields for field details.
Post-install checks
Verify your configuration first, then check the connection. Reinstalling the client won’t fix every subscription, port, or DNS issue.
Download FAQs
For Windows, macOS, Android, and iOS, start with Clash Plus; for Linux, start with Clash Verge Rev. Most desktop and mobile users should choose a graphical client. Choose the Mihomo core if you’re managing a server, router, or service yourself. You’ll still need a working subscription or configuration file after downloading.
ARM64 and x64 target different processor instruction sets, so you can’t choose based on the operating system alone. In Windows, check System type under Settings → System → About. On macOS, check the chip or processor under About This Mac. On Android, choose an ABI supported by your device. The Android universal build supports multiple architectures and is usually larger.
In some clients, the current listing maps both Apple Silicon and Intel buttons to the same x64 file. This page preserves the original mapping rather than relabeling the x64 file as ARM64. If you have an Apple Silicon Mac, check the package notes first. Running Intel apps may require Rosetta; the button label does not mean the download is a native ARM64 build.
The client loads your configuration and routes traffic; the installer does not include a ready-to-use proxy service. Import a valid subscription or local YAML file, update and select the configuration, then choose a proxy group and start the connection. Enable the system proxy or grant VPN permission if needed. Check subscription expiry, unavailable nodes, and port conflicts separately.
Both projects are discontinued. They’re kept here as archived options for reproducing older setups or comparing migration paths, not as first choices for new installations. Choose a maintained client instead. Before migrating, export your configuration and note your ports, proxy groups, and overrides. Avoid letting old and new clients control the system proxy at the same time.
Routine upgrades within the same client usually preserve user data, but installation method changes, migration between clients, or major version updates may change the data directory. Before upgrading, back up subscription URLs, local YAML files, overrides, and rule files, and note your ports and startup method. Quit the old instance first, then check the active configuration, system proxy, and service status after upgrading.