Download desk · packages by platform and architecture
Clash Plus, Clash Verge Rev, and FlClash: choose your operating system, then check your CPU architecture. Use a graphical client on desktop and mobile; use the standalone core on servers and routers.
Client downloads
Clients are listed in a consistent order for each platform. Version details appear on each card when available. A package filename may show a different version from the client’s overall release label; use the version listed in the actual package details.
For most Intel and AMD PCs, choose the x64 installer. On an ARM PC, don’t assume “64-bit” in the processor name means x64. Check “Settings → System → About” for the system type. The graphical client installers here are x64; verify separately whether they’ll run in the Windows on ARM compatibility environment.
For everyday configuration management on Windows. A good starting point for importing a subscription, choosing a proxy group, and using rule mode.
After installation, import your config before enabling the system proxy. If you need to route apps that don’t use the system proxy, check TUN permissions and routing settings. Product information: clashplus.io.
For users who want desktop configuration management and rule controls. Before migrating an existing config, check which fields the core supports.
If you’re prompted for permission when installing the service or enabling TUN, complete the standard installation first, then follow the app’s prompts. Avoid running two clients that both control the system proxy.
A cross-platform alternative for users who prefer a similar experience across desktop and mobile.
Use the installer for a standard setup. Extract the ZIP archive fully before running the app; don’t run it from the archive preview. Back up your config directory before upgrading.
For users comparing desktop interfaces. Clients may look different, but subscription formats and rule names still need to match your configuration.
When switching from another client, check the system proxy, mixed port, and startup settings again. Don’t assume your old interface preferences will carry over with the YAML file.
Archived installer for reproducing older setups and comparing configs during migration. For a new installation, choose a maintained client above.
Older cores may not recognize newer protocols or configuration fields. Before migrating, export your subscription and custom rules. Afterward, check the config loading log before enabling network routing.
| Requirement | Check before downloading |
|---|---|
| Operating system | Windows 10 or 11 is recommended. Check each client’s release notes for its minimum requirements. |
| Processor architecture | The graphical installers here are x64 / AMD64, not native Windows ARM64 packages. |
| Installation permissions | Installing a system service or virtual network adapter, or enabling TUN, may require administrator approval. |
| After installation | Turn off the system proxy and TUN in your old client before starting the new one to avoid port or routing conflicts. |
Open “About This Mac”: choose ARM64 for Apple silicon or x64 for an Intel processor. Check both the download link and the file’s actual architecture; the chip name on a button alone doesn’t identify the package type.
Choose a build for your Mac’s processor. Suitable for a first install or everyday use after migrating from an older client.
Open the DMG and follow the installer to place the app, then launch it from Applications. Official site: clashplus.io. Configure proxy settings and permissions individually after launch.
An alternative for desktop configuration management. The current download is x64, and the Apple silicon link points to the same file.
Before using this on Apple silicon, check compatibility. If macOS reports that the architecture isn’t supported, recheck the package type rather than repeatedly changing permissions.
For users who prefer a cross-platform interface. Both chip links currently point to an AMD64 installer.
After switching clients, select your current config and proxy group again. The system proxy port used by your previous client won’t automatically become FlClash’s listening port.
Archived download for users familiar with the older menu bar workflow or checking legacy configs. Not recommended for new deployments.
Check compatibility between archived clients, your current system, and protocol extensions. Keep your original YAML when migrating, and first verify that the new client loads it completely.
| Requirement | Check before downloading |
|---|---|
| macOS version | Use a supported macOS release. Minimum version requirements vary by client build; check the app’s requirements. |
| Processor architecture | Apple silicon uses ARM64; Intel uses x64 / AMD64 / x86_64. |
| Running x64 apps | On Apple silicon, check that Rosetta is available and that the app supports running under it. |
| Permission prompts | Follow macOS “Privacy & Security” prompts for opening the app and granting network access. Avoid disabling system security globally. |
Most recent Android phones use ARM64, but a 64-bit-capable processor doesn’t guarantee a 64-bit system environment. If installation reports “Not compatible,” check the system architecture first. If you’re unsure, use the client’s universal build if available. Grant APK installation permission only to the app you’ll use to open the installer.
Recommended for everyday Android use, with an ARM64 installer. Import your subscription and grant the system VPN permission after installation.
A system VPN authorization prompt the first time you connect is expected. There’s no need to connect before importing a config. If the app is often stopped in the background, check battery optimization settings. Official site: clashplus.io.
Choose ARM64, ARMv7, or universal according to your device. An option for Android users who want to keep using Clash-style configuration management.
Universal packages are convenient when you’re unsure of the device architecture, but they usually take up more storage. Updating an app with the same name also requires a matching signing key; back up your config before uninstalling anything.
Offers ARM64 and ARMv7 builds. An alternative if you want a similar interface on Android and desktop.
After importing your config, check that the proxy group has an available option selected. If the app stops working in the background, check Android’s background restrictions instead of repeatedly switching installers.
For Android users with configs in its supported format. Its configuration structure differs from Clash YAML, so don’t assume the two can be imported directly into each other.
Before downloading, confirm with your configuration provider that the format is supported. Changing the file extension won’t convert it; proxy protocols, policy groups, and rule fields all need to be compatible.
| Requirement | Check before downloading |
|---|---|
| Android version | Check the installer and client release notes for the minimum Android version; requirements vary by client. |
| Architecture labels | arm64-v8a is 64-bit ARM; armeabi-v7a is 32-bit ARM; universal packages include files for multiple architectures. |
| Installation and updates | Allow app installation from the source you’re using. If you encounter a signing conflict, back up your data before deciding whether to remove the old app. |
| Connection permissions | Approve the system VPN prompt. Multiple apps that use the VPN service usually can’t route connections at the same time. |
Install Clash Plus on iPhone or iPad from the App Store. Check the store listing for current OS and device compatibility. After installation, prepare a supported config or subscription before importing it and authorizing connections.
Install and update through the App Store. Check the app’s compatibility requirements and description on its store page before downloading.
Official site: clashplus.io. The first time you connect, follow the system prompt to add a VPN configuration. If another network tool is connected, disconnect it before testing.
| Requirement | Check before downloading |
|---|---|
| Compatible systems | Check the current App Store listing for minimum iOS / iPadOS versions and supported devices. |
| Installation source | Use the Clash Plus App Store listing above. App Store manages updates. |
| Prepare a configuration | Have a compatible subscription URL or config file ready; installing the app doesn’t create a working configuration. |
| System authorization | When prompted the first time you connect, allow the VPN configuration to be added. Manage connection status in the client afterward. |
These are AMD64 desktop clients with a graphical interface. Choose DEB for Debian- and Ubuntu-based systems, or RPM for Fedora and other RPM-based distributions. The distribution name alone doesn’t guarantee runtime compatibility. For headless servers, the standalone Mihomo core in the next tab is usually a better fit.
A top pick for Linux desktops. Choose DEB or RPM to match your distribution’s package manager, then launch the app from the application menu.
Use your system package manager to resolve dependencies. If the desktop app won’t start, check the terminal error first to distinguish a missing runtime library, a display environment issue, or a config loading failure.
AMD64 DEB package for Debian- and Ubuntu-based desktop users who prefer the FlClash layout.
Check device permissions and service configuration before enabling TUN. The system proxy only affects apps that use it; command-line tools may also need proxy environment variables set separately.
| Requirement | Check before downloading |
|---|---|
| CPU architecture | The desktop packages here are AMD64 / x86_64. Run uname -m to check your architecture. |
| Package format | DEB and RPM are for different package management systems. Don’t just change the file extension and try installing it with another package manager. |
| Runtime dependencies | Requires a working desktop session and the runtime libraries needed by the client. Compatibility depends on the build environment and Linux distribution. |
| Network routing permissions | TUN and service operation may require additional permissions. Follow the client’s setup instructions, and avoid running the entire desktop app with elevated privileges long-term. |
For servers, routers, and command-line deployments. The core loads configuration, applies rules, and handles proxy connections; it doesn’t include a graphical configuration interface. Most users can choose a graphical client for their platform above and don’t need to install the standalone core as well.
| Operating system | Architecture | 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 |
| Requirement | Check before deployment |
|---|---|
| Configuration file | Prepare a compatible YAML file and check proxy groups, rule references, and relative file paths. Overrides set in a graphical client won’t automatically carry over with the file. |
| Working with packages | Extract ZIP archives before running. Extract GZ files and set executable permissions as required by your system. Install DEB packages with the appropriate package manager. |
| Network permissions | Standard listening ports don’t require the same permissions as TUN. Start the core in the foreground and check its logs first; configure a background service once it’s working. |
| Exposed interfaces | By default, bind the management interface to localhost only. If you need remote access, configure access controls and network boundaries separately. |
To compare core families, protocol support, and configuration compatibility, see the Protocol and Core Technical Reference. Understanding the config structure before deployment makes troubleshooting easier than copying a complete set of service commands.
After installation
A successful installation only means the app starts. Connecting also depends on your config, proxy group, and routing method. Follow the checks below; don’t mistake a configuration issue for an installer problem.
Before upgrading or switching clients, export your current YAML and note your subscription URL, mixed port, selected proxy groups, and custom rules. Save subscription overrides, scripts, and extensions separately; they may not be included in the exported main config.
Don’t enable the system proxy or TUN in both the old and new clients at the same time. Stop the old client from routing traffic, then import your config into the new one. If the new config reports an error, check the field and line number instead of deleting all your rules. Remove the old setup only after migration is complete and your usual apps work.
Compare client options and migration differences →Use a subscription format compatible with your client, and confirm the imported config is enabled. In rule mode, check that proxy group names referenced by rules match the groups actually defined. A selected, working proxy group is essential; an enabled system proxy alone doesn’t mean the connection path is complete.
On desktop, test the basic connection with the system proxy first; enable TUN only if needed. On mobile, grant VPN permission when prompted. If something goes wrong, check config loading, the selected proxy group, listening ports, and connection logs in that order. Change one setting at a time so you can tell what fixed the problem.
Follow the steps to import a subscription and connect for the first time →Download troubleshooting
Check your operating system, architecture, and package format first. For connection issues, see the FAQ.
Start with Clash Plus on Windows, macOS, Android, or iOS; for Linux, start with Clash Verge Rev. Check your operating system and CPU architecture before downloading. Clients provide a configuration and connection interface, but you’ll still need a compatible config file or subscription URL.
x64 and AMD64 usually refer to the same 64-bit x86 architecture, used by most Intel and AMD PCs. ARM64 is for compatible ARM devices. Universal Android builds include files for multiple architectures, which is useful if you’re unsure what your device needs, but they’re usually larger. Check your device’s system information and the architectures supported by the installer.
In the current download list, some clients link to the same x64 installer for both Apple Silicon and Intel. A link labeled Apple Silicon doesn’t mean the file is a native ARM64 build. Choose a package explicitly marked arm64 when available. Before using an x64 package, make sure it can run through Rosetta; check the client’s requirements for compatibility details.
An installer isn’t a connection configuration. First import a working Clash YAML config or compatible subscription, then select a proxy group and use rule mode. Enable the system proxy or TUN as needed. Check that the configuration loaded successfully, then review the connection log. Avoid changing several network settings at once.
Clash for Windows and ClashX Meta are kept here as archived downloads for checking older configs or planning a migration. For a new setup, choose a maintained client. Before migrating, export your configuration and note your ports, proxy groups, and rule overrides. Uninstall the old client only after confirming the new one works.
Most desktop and phone users should choose a client with a graphical interface. The standalone Mihomo core is for server, router, and command-line users who manage their own configuration, services, and network permissions. Extract archives before running them; install Linux DEB packages with a package manager. The right option depends on your system architecture and deployment.