Clients · Installers · Core
Choose an installer for your system, then import a subscription.
For Windows, macOS, Android, and iOS, start with Clash Plus. On Linux, start with Clash Verge Rev. Other clients and archived options are listed below for comparison and migration.
Desktop apps
The desktop installers here are primarily for x64. Check your system type under Settings → System → About before downloading. After installation, avoid running multiple clients with the system proxy enabled, as one may overwrite another's settings when it exits.
A good place to start for a first installation. Download the x64 installer, then import your subscription from the configuration page. Make sure the configuration is enabled and a node is available in a proxy group before turning on the system proxy. If you need to route more app traffic, check the TUN permission requirements.
Official site: clashplus.io
A good fit for desktop users who want a GUI to manage subscriptions, rules, and routing modes. After installing, connect once with the default settings before changing overrides one at a time. Service mode and TUN may require additional permissions; follow the client prompts and your system's permission settings.
Consider FlClash if you want a similar workflow across desktop and mobile. This page provides the AMD64 installer. After importing your existing subscription, recheck your proxy group selection and local ports; GUI settings usually don't migrate with a subscription file.
Another Windows GUI client to consider, especially if you're already familiar with it. When switching, exit the old client first to avoid port conflicts. If a configuration fails to load, check the logs for unsupported fields or protocols before repeatedly changing routing modes.
This archived download is mainly for migrating older setups and comparing legacy configurations. For a new installation, choose a maintained client listed above. Older cores may not support newer protocols or configuration fields. Keep a backup before migrating, and don't assume similarly named clients are fully configuration-compatible.
| Check | Requirements and notes |
|---|---|
| Processor | These installers are for x64 / AMD64. On ARM devices, confirm compatibility with your OS and its app emulation support. |
| Operating system | Use a supported 64-bit version of Windows. Check the client's current release notes for its minimum OS version. |
| Installation permissions | Standard and service installations may request administrator access. Install any TUN components as prompted by the client. |
| Before connecting | Have a working subscription ready and make sure another app isn't using the local proxy port. |
Desktop apps
Open About This Mac from the Apple menu to check whether your Mac has Apple silicon or an Intel processor. Open the downloaded DMG and follow the installer prompts to move the app to Applications. Check each file's actual architecture below; the download label alone doesn't guarantee a native ARM app.
Apple silicon and Intel installers are available. Choose the one that matches your Mac's chip. After the first launch, import your subscription before enabling the system proxy. If you need TUN, check the client's permission and helper-service prompts. Quit the app before upgrading so an old process doesn't keep running.
Official site: clashplus.io
A GUI option for managing subscriptions and overrides. Both Mac links in the fallback manifest currently point to the same x64 DMG, not separate builds. Intel users can use x64. Apple silicon users should check Rosetta and app compatibility, and choose a client with a confirmed native ARM build when possible.
Use FlClash for a similar experience across platforms. Both Mac links in the current manifest are AMD64 DMGs. Whether they run on Apple silicon depends on Rosetta and app compatibility. After importing your subscription, configure the system proxy, startup behavior, and connection mode on this Mac.
This archived option is for comparing configurations in existing setups. For a first installation, choose a maintained client above. The current fallback file is an x86_64 DMG, and both links point to the same file. Before upgrading macOS or migrating a subscription, check core compatibility and keep a restorable configuration backup.
| Check | Requirements and notes |
|---|---|
| Chip architecture | For Apple silicon, choose ARM64. For Intel, choose x64 / AMD64 / x86_64. |
| Compatibility | Intel packages on Apple silicon require Rosetta and a compatible client; they are not native ARM builds. |
| macOS version | Check the client's current system requirements. Minimum macOS versions vary by client. |
| Permissions | Follow macOS prompts for first launch and helper-service permissions. If an app is blocked, verify its source and review the warning before proceeding. |
Phones and tablets
Most recent Android phones use ARM64, but check your device's actual architecture. When installing an APK, grant installation permission only to the app you're using to open it. On the first connection, approve the system VPN prompt, then check your configuration and proxy groups.
This download is an ARM64 APK. After installation, paste your subscription link into the configuration import page, wait for it to download, and enable the configuration. Allow the system VPN request on first connection. If the connection drops when the screen turns off, check battery optimization, background activity, and auto-start settings instead of reinstalling repeatedly.
Official site: clashplus.io
ARM64, ARM, and universal APKs are available for different device architectures. If you're unsure, check your device information or use the universal build. Confirm the configuration loads successfully before connecting; Android's VPN service generally can't be shared by multiple similar apps at once.
ARM64 and ARM builds are available for users who want a similar workflow on phone and desktop. After importing a configuration, check whether you need to select a node manually. Background connections are also affected by your phone manufacturer's battery policies; allow background activity and test the connection with the screen off.
Before installing this alternative Android client, confirm that your configuration provider offers a format supported by Surfboard. Its configuration format differs from Clash YAML, so don't assume the same file will work without changes. This page provides a universal APK; import subscriptions and configure rules in a supported format.
| Check | Requirements and notes |
|---|---|
| Package format | APK; choose ARM64, ARM, or universal based on your device. |
| macOS version | Check the installer's requirements and the client's current system requirements. If you see an incompatibility warning, verify your Android version and device architecture first. |
| VPN permission | Approve the system prompt the first time you connect. Disconnect other apps using the VPN service first. |
| Background activity | For persistent connections, check battery optimization and background restrictions. Change only the permissions you need. |
iPhone and iPad
Install Clash Plus from the App Store. Check the store listing for system requirements and device compatibility. After importing a configuration, follow the client prompts to allow a VPN configuration, then connect. Check the App Store page for updates, installation progress, and app details.
After installing from the App Store, get a subscription link or compatible configuration from your provider. Once imported, check that the configuration is enabled and proxy groups have nodes before approving the system VPN prompt. If the connection acts up when switching between Wi-Fi and cellular, check the logs and subscription status before reconnecting.
The client and subscription service are separate: installing the app doesn't create usable nodes. Subscription links may contain account credentials, so don't share them in public screenshots, shared notes, or group chats. If you have other VPN configurations, check which one is currently active.
Official site: clashplus.io
| Check | Requirements and notes |
|---|---|
| System and device | Check compatibility on the App Store listing and make sure your device meets the requirements. |
| Download | The Clash Plus app listing in the App Store. |
| First connection | Allow the VPN configuration when prompted by iOS and make sure the configuration is enabled. |
| Subscription setup | Use a configuration source supported by the client, then check nodes and proxy groups after importing. |
Desktop distributions
The GUI packages below are for AMD64 desktops. Choose DEB for distributions such as Debian and Ubuntu, or RPM for distributions that use RPM package management. For headless servers and routers, go to the Mihomo core section instead of installing a full desktop environment.
DEB and RPM packages are available for managing subscriptions and connection settings in a desktop environment. Install with your distribution's package manager and resolve any dependencies it reports. Linux desktop proxy settings may not affect command-line tools; terminal apps may need proxy environment variables set explicitly.
This AMD64 DEB package is for desktop distributions that use the matching package system. After installing, make sure the GUI launches before importing a subscription. Before enabling TUN, check your routes and permissions. On a remote machine, keep a way to restore your connection.
| Check | Requirements and notes |
|---|---|
| Architecture | GUI packages are for AMD64 / x86_64. For other architectures, see the core downloads. |
| Package manager | Use the DEB or RPM format supported by your distribution; don't mix package types. |
| Runtime environment | Requires a desktop environment and client dependencies. Check package manager messages for required library versions. |
| Traffic routing | System proxy, terminal environment variables, and TUN affect different traffic. Configure the option that fits your needs after installation. |
Servers · Routers · Self-hosted setups
This section provides a command-line core, not a desktop app with a subscription import window. Most users should choose a GUI client above. For a self-hosted setup, prepare a configuration file, working directory, permissions, and service manager, and decide which devices can access the proxy ports.
Check the target device's operating system and CPU architecture before choosing a download. ZIP and GZ files are archives; after extracting them, set executable permissions and startup options. Install DEB packages with the appropriate distribution package manager. ARMv7 and MIPS-softfloat are used by some embedded devices, but the label "router" alone doesn't tell you which build is compatible.
| System | Architecture | 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 DEB |
| Linux | AMD64 | GZ | Download AMD64 |
| Linux | ARM64 | GZ | Download ARM64 |
| Linux | ARMv7 | GZ | Download ARMv7 |
| Linux | MIPS-softfloat | GZ | Download MIPS |
On Linux, run uname -m to check the architecture. For example, x86_64 usually means AMD64, and aarch64 usually means ARM64. Embedded devices also require checks for ABI, endianness, and OS compatibility. Before starting the service, use the core's configuration test to validate the YAML and confirm it parses successfully.
mihomo -t -f config.yaml
mihomo -f config.yamlThese commands assume the executable is already in your PATH. Define access permissions for configuration files, logs, and the service account; expose listening ports only to devices that need them. Before changing TUN or routes on a remote machine, prepare a rollback plan to avoid losing your management connection.
After downloading
Copy the full subscription URL from your configuration provider. In the client, open Configuration or Subscriptions and add a remote profile. Once it downloads, select and enable it, then choose a node in a proxy group. Importing a subscription and enabling a configuration are separate steps; seeing its name in the list doesn't mean the active connection is using it.
If a subscription update fails, check that the link is still valid, your account has available traffic, and whether the error occurred during download or parsing. If fields aren't supported, check which core the subscription requires. Don't post the full subscription link publicly when asking for help.
Subscription import steps →For your first connection, start with rule mode and select an available node in a proxy group. A node's latency test measures its response to a particular test address; it doesn't predict how every site will perform. Consider the region, exit route, and traffic multiplier too. If only one site has an issue, check the matching rule and target proxy group in the logs.
The system proxy mainly affects apps that follow system settings. TUN usually routes more traffic, but also involves permissions and routing. Get one method working before trying another to reduce the number of variables when troubleshooting.
Compare Clash node selection →Wait until manual connections are stable before enabling the client's startup option. Launch at startup, connect automatically on launch, and enable the system proxy automatically are usually separate settings, so check each one. In service mode, distinguish the GUI process from the background service; closing the window doesn't necessarily stop the core.
Note the current behavior before upgrading, then check that the expected proxy state is restored afterward. On Android, auto-start and background restrictions depend on both system and manufacturer settings; adjust them based on how the connection behaves with the screen off.
Startup and restore settings →Some Windows apps that use app containers may be blocked from accessing a local proxy by loopback restrictions. If a browser connects but another app doesn't, check whether that app uses the system proxy and whether requests appear in the logs. Then decide whether to enable loopback access for that specific app.
Loopback access isn't a universal fix for Windows apps. Enable it only for apps that need it and note which apps you changed. If the client isn't receiving traffic, switching nodes alone is unlikely to help.
Windows app loopback guide →Download FAQs
For Windows, macOS, Android, and iOS, start with Clash Plus for your platform. On Linux, consider Clash Verge Rev. Check your device architecture and package format first, then compare subscription management and traffic routing features. If you already have a configuration, back it up and confirm the new client's core supports its fields.
x64 and AMD64 usually refer to the same 64-bit Intel or AMD architecture; ARM64 is a different processor architecture. If you're unsure which architecture your Android device uses, choose the universal build if available. On macOS, check both your chip and the file's architecture: x64 or amd64 packages aren't native ARM builds, and Apple Silicon compatibility depends on Rosetta and the app.
A client installer doesn't include a subscription service. Get a working subscription link or configuration file, import and enable it on the configuration page, then choose a node in a proxy group. Subscription links may contain account credentials, so keep them private. Set up the system proxy or TUN only after nodes appear and the configuration loads successfully.
First, make sure your internet connection can load other pages, then click the installer link again. The page will try to fetch the current download manifest; if that request fails, the links already on the page remain available. Restart interrupted downloads and check your browser's download history, disk space, and security software alerts. Don't disable all system security protections to troubleshoot a download.
Both clients are kept here as archived options for migrating older setups and comparing configurations. For a new installation, start with a client that's still maintained. Before migrating, export your configuration and note your proxy ports and rules. Check whether the target core supports the fields and protocols in your old configuration.
A GUI client is usually best for everyday desktop and mobile use: it's easier to import subscriptions, switch configurations, and view logs. Mihomo is better suited to servers, routers, and self-hosted setups, where you'll need to provide your own configuration, startup method, permissions, and firewall rules. Downloading the core alone won't configure your desktop's system proxy.