PACKAGE SHELF / CLIENTS & CORE
Choose a package for your operating system, then confirm the processor architecture.
Clients such as Clash Plus, Clash Verge Rev, and FlClash provide interfaces for importing configurations and managing proxies. Desktop and mobile users should choose a GUI client; server and router users can download the standalone Mihomo core.
Start with the operating system your device runs, not the computer brand. Then check the chip type in system information and choose the matching package format. Most devices only need one client; running multiple clients with the system proxy or TUN enabled can cause them to override each other's settings.
The client reads your configuration, manages proxy groups, and routes traffic. Proxy service and subscriptions must be obtained separately. Having no proxies on first launch doesn't mean the installation failed. Once you have a valid configuration, follow the getting-started guide to import it, then check that the rules match and the connection is working.
01 / GUI clients
Switch tabs to see clients for each platform. Share a link with a platform anchor to open that platform directly. Standalone core downloads are further down.
Start with Clash Plus. If you need a different interface or configuration workflow, compare the other clients below. The Windows installers here are primarily for x64. On ARM devices, check Windows compatibility before installing; the operating system name alone doesn't guarantee compatibility.
A good starting point for importing a configuration, choosing a proxy group, and setting up the system proxy. After installation, check that the imported configuration is active; adding a subscription alone won't enable it.
Official website: clashplus.io
Manage subscriptions, configurations, and rules on your desktop. Get the system proxy working first, then decide whether to enable TUN based on which apps need traffic routing. If installing a service, follow the client's permission prompts.
A good fit if you want a similar workflow on desktop and mobile. The Windows installer uses the amd64 architecture. When migrating from another client, check the listening port and where configurations are saved.
Another option for managing configurations on desktop. After importing, check that the configuration fields are supported by the core. A client's UI settings file is not a general-purpose proxy configuration.
Kept for migrating older setups and referencing legacy configurations. Archived releases may not receive compatibility or security updates. For a new installation, choose one of the clients above. Interface labels in older guides may also differ from current clients.
| Check | What to look for |
|---|---|
| Operating system | Use a Windows version that still receives security updates. Check each client's installer and release notes for its minimum supported version. |
| Processor architecture | The x64 and AMD64 packages above are for 64-bit Intel and AMD systems. Check compatibility before installing on an ARM device. |
| Installation permissions | Make sure you can write to the installation directory. System proxy settings usually apply to the current user; service mode and TUN may require additional permissions. |
Quit any older client before installing. If it enabled the system proxy, turn it off when quitting so your browser doesn't keep sending requests to a port that's no longer listening. Don't test a new package by running two proxy clients at once.
Check your chip in About This Mac: Apple M-series models use Apple Silicon; choose x64 for Intel Macs. Open the downloaded DMG and follow the installer. Installing the app and granting network extension or service permissions are separate steps.
Download the DMG for your chip. After the first launch, import a configuration and choose an available proxy group before enabling the system proxy. Installing the app alone doesn't route traffic through a proxy.
Official website: clashplus.io
A desktop option for managing multiple configurations. Both downloads are x64 files. Apple Silicon users should check compatibility requirements before choosing this package.
Offers a configuration workflow similar to the mobile app. The current Mac file is labeled amd64, and both options point to the same file. Before migrating, back up your configuration and set up traffic routing again.
Kept as an archived option for older Mac setups. The current file is x86_64; check whether it works with your version of macOS. For a new installation, consider one of the actively supported clients above.
| Check | What to look for |
|---|---|
| Chip type | Apple Silicon uses arm64; Intel uses x64. Native and compatibility-mode apps are not the same. |
| macOS version | Check the client's release notes. Being able to open a DMG doesn't mean the app supports your version of macOS. |
| Permission prompts | Check the specific message under System Settings → Privacy & Security. Grant network and accessibility permissions as needed. |
If macOS blocks startup, first check the download source, file architecture, and system alert. Don't run commands that disable system security protections. After switching clients, quit any old menu bar app and check which port the system proxy is using.
Most current Android phones use ARM64; older 32-bit devices may need an ARM package. After downloading the APK, allow installation from the current source when prompted. VPN permission lets the app route traffic locally; it doesn't provide a working subscription.
An ARM64 installer is available. After installing, import a configuration and check the proxy groups before connecting. If Android restricts background activity, review your device's battery optimization settings to prevent the connection from being paused when the screen is locked.
Official website: clashplus.io
Choose an installer based on your device's ABI. If you know your device uses 64-bit ARM, choose ARM64. If you're unsure, use the universal package; it usually includes more architectures and may be larger.
Offers Android downloads for ARM64 and 32-bit ARM. Configurations can come from a subscription or a local file. When migrating from desktop, check whether platform-specific paths, listening settings, and client overrides still apply.
Another proxy configuration option for Android. Surfboard and Clash YAML use different syntax; changing the file extension won't convert one format into the other. Check that your subscription provider supports the format you need.
| Check | What to look for |
|---|---|
| Device architecture | arm64-v8a is 64-bit ARM; armeabi-v7a is 32-bit ARM. Check which ABIs your device supports. |
| macOS version | Check the installer's compatibility result and the client's requirements. A phone's release date doesn't tell you its Android version. |
| Network and background activity | Confirm the system VPN permission when connecting. You may need to adjust your device manufacturer's background and battery management settings to keep the connection active. |
Android usually allows only one standard VPN connection at a time. Connecting another VPN, packet capture tool, or VPN-based filtering app may replace the current connection. If Android says the app isn't installed, check the architecture, available storage, and signature of any existing app before uninstalling and risking your configuration.
Install Clash Plus from the App Store. The listing shows compatibility with your device, system requirements, and app details. After installation, import a configuration and follow the system prompts to add a VPN configuration.
Open the App Store listing to review and install the app. Before connecting for the first time, import a valid configuration, choose a suitable proxy group, and read the system's VPN permission prompt. Check app installation, configuration import, and network connectivity separately.
Official website: clashplus.io
| Check | What to look for |
|---|---|
| System compatibility | Check the system requirements shown for your device on the App Store listing. |
| Installation source | Open the Clash Plus App Store listing from this page, verify the app name, and install it. |
| Connection permissions | Follow the system prompt to add a VPN configuration. Managed devices must also follow their organization's network and device policies. |
Before upgrading, keep a record of where your configuration came from and any custom settings you need. If another VPN configuration is on your device, check which one is active before connecting. The VPN icon in the status bar only indicates that a tunnel is established; test actual access to confirm that your rules and proxies are working.
For desktop Linux, start with Clash Verge Rev; FlClash is another option. Choose DEB or RPM based on your distribution, then confirm your processor is AMD64. Headless servers are usually better served by the standalone core below.
Available in DEB and RPM formats. Debian- and Ubuntu-based distributions typically use DEB; Fedora and other RPM-based distributions use RPM. Let your system's package manager handle dependencies during installation.
This is an AMD64 DEB package. After installation, check that the GUI launches before importing a configuration. Desktop system proxy settings and proxy environment variables used by terminal apps are separate.
| Check | What to look for |
|---|---|
| Processor | The GUI packages above are for AMD64 / x86_64. ARM servers should use the standalone core, not these desktop packages. |
| Distribution | Choose DEB or RPM according to your distribution's package management system. Changing the file extension won't convert one format into the other. |
| Desktop and permissions | GUI clients require compatible desktop libraries. TUN and service startup may also require checking permissions, routes, and firewall settings. |
Use uname -m to check the machine architecture; x86_64 corresponds to AMD64 here. If the installer reports missing dependencies, review the package manager output first. Don't mix software repositories from different distributions. Before changing the default route on a remote server, keep a management connection you can use to recover access.
02 / Standalone core
For users managing servers, routers, or their own services. Most desktop and mobile users can use a GUI client above and don't need to install the core separately.
Mihomo reads your configuration and handles proxy and rule processing. A standalone setup requires you to provide the configuration file, runtime directory, startup command, and permissions. For routers, also check the CPU architecture, firmware environment, and available storage. The same architecture label doesn't guarantee compatibility with every system.
Start with a minimal configuration and confirm it runs before adding DNS, rule providers, and TUN. Don't expose the control interface directly to the public internet. For a step-by-step explanation of configuration, see the beginner-to-advanced guide.
| Operating system | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP / 64-bit Intel and AMD | Download ZIP · AMD64 |
| Windows | ARM64 | ZIP / 64-bit ARM | Download ZIP · ARM64 |
| macOS | Intel / AMD64 | GZ / Intel Mac | Download GZ · Intel |
| macOS | Apple Silicon / ARM64 | GZ / Apple M series | Download GZ · Apple Silicon |
| Linux | AMD64 | DEB / Debian-based package manager | Download DEB · AMD64 |
| Linux | AMD64 | GZ / Standalone binary | Download GZ · AMD64 |
| Linux | ARM64 | GZ / 64-bit ARM | Download GZ · ARM64 |
| Linux | ARMv7 | GZ / 32-bit ARMv7 | Download GZ · ARMv7 |
| Linux | MIPS-softfloat | GZ / MIPS soft-float | Download GZ · MIPS |
ZIP files need to be extracted. GZ files are compressed; after extracting, set executable permissions as required by your system. Install DEB packages with a package manager. MIPS users should also check endianness and floating-point ABI—having a MIPS processor alone isn't enough to determine compatibility.
03 / Setup and migration
A successful installation only means the program is ready. Import a subscription or local configuration, then check the update status, proxy groups, and current mode. For an initial test, use rule mode, select an available proxy, and then enable the system proxy or TUN if needed.
Browser access doesn't mean all apps are routed through the proxy. Terminal tools, games, and some apps may use different network paths. Decide which traffic you need to route before enabling TUN. Avoid changing many settings at once, which makes problems harder to diagnose.
See installation and first-time setup steps →Before migrating, export your configuration and custom rules, and note the subscription source, listening ports, DNS settings, and proxy group selections. Subscription links may contain credentials, so store backups somewhere private and don't share full URLs in logs or screenshots.
Quit the old client and restore the system proxy settings before installing the new client. After importing, verify rules and connectivity one by one; clean up old data only after confirming everything works. Client-specific override scripts and UI settings may not transfer directly, so check them separately.
See configuration and maintenance tips →04 / Download FAQ
Start by choosing your device's operating system. For Windows, macOS, Android, and iOS, consider Clash Plus; for Linux, start with Clash Verge Rev. Check the processor architecture and installation requirements before downloading. After installing a client, you'll still need to import a valid configuration or subscription—the installer does not include proxy service.
AMD64 and x64 usually refer to 64-bit Intel and AMD processors; ARM64 and aarch64 refer to 64-bit ARM. Android's armeabi-v7a targets 32-bit ARM. If you're unsure which architecture your Android device uses, check its system information or choose a universal package. The download label doesn't guarantee a native build, so check the filename and installer prompts before installing.
Make sure the download has finished, the file extension is correct, and the package matches your operating system and processor architecture. Then check the specific reason shown in the system security prompt; don't disable security protections outright. On Windows, check app installation permissions; on macOS, review the Privacy & Security alert; on Android, check permission to install from the current source; on Linux, review the package manager output.
These downloads are provided for migrating older setups and reference to legacy configurations. Archived packages should not be treated as actively maintained releases. For a new installation, choose a client that is maintained and compatible with your current system. Before migrating, export your configuration and note your ports and proxy group settings; then check whether the new client supports the fields you use.
Whether your data is preserved depends on the client, installation method, and configuration directory. Before upgrading, export your subscription configuration, override files, and custom rules, and note the current listening port. Whenever possible, upgrade within the same client. When switching clients, don't overwrite the entire data directory. After importing, verify the rule mode and proxy selection before enabling the system proxy or TUN.
Usually not. GUI clients typically include or manage the core, so most desktop and mobile users only need to install the client for their device. The standalone Mihomo package is for users managing servers, routers, or their own services; you'll need to provide the configuration, permissions, and startup method yourself.
Already installed but having connection issues? Visit the Help Center to troubleshoot subscriptions, mode, system proxy, and DNS in order.