x64Windows 10 / 11 · Installer and portable build
Choose your OS, then check the architecture. For a new install, start with Clash Plus; for an existing setup, see the archived Clash for Windows build.
This site lists client downloads and guides; it is not the official Clash for Windows project website. Installing the app and configuring a proxy are separate steps—you’ll still need to import your own configuration.
Desktop · Intel / AMD 64-bit
Check your system type in Windows under Settings > System > About. The downloads below are primarily for x64 PCs. For ARM devices, confirm that emulation is supported; a 64-bit OS alone doesn’t guarantee compatibility. For a new setup, use one client to configure your proxy and avoid multiple apps changing system proxy settings.
A good place to start if you’re new to using Clash on Windows. After installing, import a subscription or local configuration, make sure a proxy group is available, then enable the system proxy. Installing the client does not configure your connection.
If you plan to switch between desktop and mobile, first compare which configuration options each platform supports; don’t copy the entire app folder. See clashplus.io for product details.
A good fit if you want to manage subscriptions, rules, and desktop proxy settings. When migrating an existing configuration, import a copy first and check that it parses correctly. Then enable overrides and TUN one at a time to make troubleshooting easier.
Installing a service or virtual network adapter may require administrator approval. If you only need the system proxy, there’s no need to enable every option just to make the setup feel complete.
Consider FlClash if you want a similar workflow across multiple devices. For regular desktop use, choose the installer. Choose the ZIP if you want to manage the program folder yourself; extract it fully before running the app, rather than launching it from within an archive utility.
Portable changes how files are deployed; it doesn’t remove TUN or service permission requirements. Export your configuration and exit the running app before moving its folder or updating over an existing build.
Another Windows GUI client to consider. Compare how easily you can import configurations, switch proxy groups, and access logs—not just how the interface looks. If you use complex overrides, check the effective configuration after migrating.
Different clients may store configurations in different locations. Before uninstalling an old app, back up subscription URLs, local rules, and any settings you want to keep separately.
Primarily for preserving an existing setup, reproducing a configuration, or viewing the legacy interface. The original project is discontinued. The archived download is still available, but it won’t receive new protocol support, OS compatibility updates, or security fixes.
For a new PC, don’t default to the old client just because you’re familiar with its General page. Read the guide to choosing a client after discontinuation before deciding whether to keep your old setup or migrate. The archive currently offers an installer; for a portable option, see FlClash above.
| Check | What to look for |
|---|---|
| OS and architecture | Prefer Windows 10 or 11 on x64; check each client’s installer for its specific minimum OS requirements. |
| Administrator access | May be needed to install a service or driver, or enable TUN. Don’t treat a regular launch or system proxy setup as the same step. |
| Port conflicts | Exit other proxy apps first; two processes can’t listen on the same port at once. |
Desktop · Check your chip
Choose About This Mac from the Apple menu to check whether your Mac has Apple Silicon or an Intel processor. A DMG is a disk image; you’ll usually need to open it and drag the app to Applications. If macOS blocks the first launch, check the download source and app details rather than disabling system security settings altogether.
Choose Apple Silicon for an M-series chip and Intel for an Intel processor. Install the app first, then import your configuration and check the system proxy settings. Don’t confuse the CPU architecture with the protocol used by a configuration file.
If you use multiple devices, review the product details at clashplus.io first, then follow each platform’s permission steps to set up your connection.
Consider this client if you want to manage subscriptions, rules, and proxy modes on desktop. Both download options currently point to the same x64 image; the platform label doesn’t mean the file is a native ARM build.
When migrating a configuration from Windows, check local file paths, scripts, and network interface names. These usually can’t be reused across operating systems as-is.
A good fit if you want a consistent interface across multiple operating systems. The current listing offers an AMD64 image; Apple Silicon users should check compatibility before running it. After installation, make sure the proxy toggle is on and the configuration is working.
Before switching to another proxy app, turn off the proxy in the current client and quit it to reduce conflicts over system settings.
Use this archive if you need to keep an older menu bar workflow. Since the project is discontinued, don’t expect ongoing fixes for macOS upgrades, permission changes, or protocol compatibility. For a new install, compare the clients above first.
Back up your configuration before switching clients. An old app launching successfully doesn’t guarantee that its rules and DNS behavior will match those of a new core.
| Check | What to look for |
|---|---|
| Chip | Check About This Mac for Apple Silicon or Intel, then verify the downloaded file’s actual architecture. |
| OS version | Requirements vary by client. Check the app details and installer prompts; there’s no single minimum macOS version for every DMG. |
| Compatibility | Before running an x64 app on Apple Silicon, check Rosetta requirements. Compatibility mode is not native ARM support. |
Mobile · ARM64 / ARM
For most newer phones, first check whether the ARM64 build is suitable; consider ARM or universal builds for older devices. 64-bit hardware doesn’t guarantee that the OS supports apps of every bitness. When installing an APK, grant install permission only to the browser or file manager you’re using, then revoke it afterward if you wish.
A good choice if you want to get set up on your phone. After installing, import a subscription, select a proxy group, then approve Android’s VPN connection request. The VPN icon means a tunnel is active; it doesn’t guarantee that every node in your subscription can connect.
See clashplus.io for product details. If the connection drops frequently when the app is in the background, check whether the system’s battery settings are restricting it before making changes.
Consider this if you already use a Clash-style configuration. Choose the build for your device’s architecture; if you’re unsure, check whether the universal build works for your device. A universal APK won’t fix an outdated OS or a signing conflict.
If you’ve installed an app with the same name from another source, a different signing key may prevent an update. Export your configuration before deciding whether to uninstall, so you don’t lose local subscriptions or rules.
If you already use FlClash on desktop, compare its mobile workflow. Export and re-import your configuration when migrating; don’t copy the app’s private data folder directly.
A phone can usually have only one app using the system VPN tunnel at a time. Disconnect other VPNs, accelerators, or similar tools before starting, so a permission conflict isn’t mistaken for a node failure.
A good fit if you already have a compatible configuration and understand its syntax. Surfboard isn’t a drop-in replacement that can always import Clash YAML unchanged. Before downloading, check the format your subscription provides and the protocols you need.
If you only have a Clash configuration and don’t plan to convert it, start with one of the Clash-style clients above. Different formats can differ in more than file extensions; their rules and proxy group definitions may work differently too.
| Check | What to look for |
|---|---|
| App architecture | Check whether your device uses arm64-v8a or armeabi-v7a, and confirm that the OS supports apps of that bitness. |
| OS compatibility | Check the specific APK’s minimum Android version. A universal build doesn’t support every older OS. |
| Connection permissions | The app needs VPN permission to start proxying. Background reliability also depends on your device’s battery settings. |
iPhone / iPad · App Store
On iPhone or iPad, open the app’s App Store listing. Before installing, check its current OS compatibility, release notes, and supported devices. These details can change with app updates, so they’re more reliable than a single fixed requirement for every device.
After installing, import a subscription or configuration you’re authorized to use, then allow the app to add a VPN configuration when prompted. Select a rule mode and proxy group, then test the connection in an app you use. Don’t rely on the status bar icon alone to tell you where all your traffic is going.
Official site: clashplus.io. If you use other network tools, disconnect them before testing to avoid multiple configurations competing for the connection.
| Check | What to look for |
|---|---|
| OS and device | Check Compatibility in the App Store listing for the app’s supported iPhone and iPad models. |
| Install source | Use the App Store listing above; see clashplus.io for product details. |
| First connection | Prepare a working configuration and allow the app to add a VPN configuration when prompted. |
Desktop builds · AMD64 / x86_64
Check your distribution’s package format, then confirm your CPU architecture. Debian- and Ubuntu-based systems usually use DEB; Fedora and openSUSE commonly use RPM. Dependency requirements still depend on your distribution version. These are desktop GUI clients; for servers without a desktop environment, see the Mihomo Core section.
A good fit for Linux desktop users who want a GUI to manage their configuration. If a runtime library is missing, check the dependency information with your distribution’s package manager; don’t copy library files from another distribution.
Which apps use the system proxy depends on your desktop environment and whether each app honors the setting. If terminal apps aren’t proxied, check environment variables or the client’s TUN setup instead of repeatedly reinstalling the software.
A good fit for users who want a cross-platform interface on Debian- or Ubuntu-based desktops. Check that the package architecture matches your system; an AMD64 package won’t run natively on ARM hardware.
If you need to route apps that don’t honor the system proxy, look into TUN permissions and routing. Get the basic configuration working first, then expand the traffic you route so it’s easier to troubleshoot.
| Check | What to look for |
|---|---|
| CPU architecture | Run uname -m in a terminal; these desktop packages are for x86_64 / AMD64. |
| Package format | Choose DEB or RPM for your distribution, and use the system package manager to handle dependencies. |
| Runtime environment | GUI clients need a working desktop environment and supporting libraries. TUN also requires device permissions and routing configuration. |
Servers / routers · Command-line setup
Check the operating system and CPU before confirming the runtime environment. Windows AMD64 is for common 64-bit Intel and AMD processors; ARM64 is for 64-bit ARM systems. Linux ARMv7, ARM64, and MIPS builds are not interchangeable. MIPS also depends on byte order, floating-point ABI, and device firmware, so the router brand alone isn’t enough to determine compatibility.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · 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 softfloat · GZ | Download MIPS GZ |
After extracting a ZIP, locate the executable. GZ files usually contain a single binary, not a GUI installer. On Unix-like systems, you may also need to grant execute permission. Install DEB files with a package manager; their file layout differs from a manually placed binary. Don’t mix these deployment methods by overwriting files.
Prepare a configuration the current core can parse before setting up a background service. Start by listening on localhost only. If you need LAN access, also consider the listen address, authentication, and firewall. Don’t expose the management interface directly to the public internet. TUN requires a virtual device, permissions, and routing; downloading the core doesn’t set it up automatically.
| Check | Before deployment |
|---|---|
| Architecture and ABI | Check the CPU, bitness, byte order, and firmware runtime requirements, especially on ARM and MIPS devices. |
| Configuration file | Provide a valid YAML file; references between nodes, proxy groups, and rules must match. |
| Services and permissions | Set up the service account, configuration path, logs, and required network permissions. Avoid running multiple services that listen on the same port. |
EXE, DMG, APK, DEB, and RPM are for different operating systems; changing a file extension won’t convert a package. Extract archives before use and follow your OS’s installation process for installers. If an error appears, save the full message, then check the architecture, OS version, and file permissions.
Clients and subscriptions are provided separately. After importing, make sure the configuration parses, then check its proxy groups and rules. Subscription links may contain credentials, so hide the full URL in screenshots. Remove node passwords and private addresses before sharing a configuration.
Test the system proxy or mobile VPN first, then look into TUN if needed. Don’t run multiple proxy clients at once. If the connection fails, check the logs, rule matches, and DNS before deciding whether to update the app; reinstalling isn’t a fix for every problem.
Follow the setup guide to connect for the first time →Installation and subscription FAQ →
For a new install, start by comparing Clash Plus. For desktop configuration management, also consider Clash Verge Rev, FlClash, and Clash Nyanpasu. Clash for Windows is discontinued; archived builds are mainly for preserving existing setups, with no expectation of new protocol support or compatibility fixes.
Check your system type under Settings > System > About. Most 64-bit Intel or AMD PCs should use the x64 installer. Choose FlClash's portable ZIP if you want to manage the program files yourself. Portable does not eliminate every service or permission requirement; check the client's prompts before enabling TUN.
Check your chip in About This Mac. Clash Plus offers separate Apple Silicon and Intel installers. In the current listings, the macOS downloads for Clash Verge Rev, FlClash, and ClashX Meta both point to the same x64 file. Apple Silicon users should confirm Rosetta compatibility before using these downloads; they are not native ARM builds.
ARM64 is for devices that support 64-bit ARM apps; ARM is for older 32-bit ARM environments. Universal builds include more architectures and are usually larger. Availability also depends on which app bitness your OS supports. If installation fails, check the OS version, architecture, and signing of any existing app instead of repeatedly installing over it.
The installer contains the client app, not working nodes or a subscription. Import a subscription you’re authorized to use or a local configuration, choose a proxy group, then enable the system proxy or VPN permission for your platform. Subscription URLs may contain credentials; don’t include them in public screenshots or comments.
Mihomo is a proxy core, not a complete desktop GUI client. Server and router users need to provide their own configuration, launch method, and permissions, and check the CPU architecture and runtime environment. Desktop and mobile users should start with one of the GUI clients above.