Client Downloads / Platforms and Architectures
Find clients for Windows, macOS, Android, iOS, and Linux. Choose your operating system first, then the processor architecture. Use a GUI client for everyday use; see the Mihomo core section for servers and routers.
Choose by platform
Clash Plus is recommended for Windows, macOS, Android, and iOS; Clash Verge Rev is listed first for Linux. Each client is maintained independently, so features, configuration locations, and supported systems may differ.
The GUI installers in this section are x64 builds for most 64-bit Intel and AMD PCs. On Windows on ARM, first check whether your system can run x64 apps. The ARM64 core archive is not a GUI installer. Start with one client to import your configuration and test the connection before considering a switch.
Clash Plus is a good starting point for a first installation. After setup, import your subscription or local configuration, then check the proxy mode and system proxy status. The general configuration approach carries across platforms, but don’t copy system-specific paths directly.
Official site: clashplus.io ↗
A good fit for desktop users who manage subscriptions, rule overrides, and service mode. This client uses the Mihomo core; check that the service is installed before enabling TUN. If your browser connects but other apps don’t, check whether traffic is handled by the system proxy or the virtual network adapter.
A good fit if you want a similar experience on desktop and Android. Check the configuration, policy groups, and traffic routing in that order; selecting a policy alone won’t route traffic unless routing is enabled. Review local overrides separately when switching clients.
A good fit if you prefer a different desktop interface for managing configurations. After importing, check any configuration parsing warnings and confirm that the selected core supports the fields you use. DNS, rule-set, and protocol support vary by core; a configuration opening successfully doesn’t mean every feature will work.
This archived download is for migrating older configurations and reproducing legacy setups, not for new installations. Older cores may not recognize newer protocols or fields in current subscriptions. Export your configuration and rules first, then import them into a maintained client. Don’t overwrite the old directory.
| Check | Before installing |
|---|---|
| System | Use a supported 64-bit version of Windows 10 or 11. Check the installer for the specific minimum version required. |
| Processor architecture | These installers are x64 / AMD64. They won’t run on 32-bit Windows. Check compatibility separately on ARM devices. |
| Permissions and runtimes | Installing services or creating a virtual network adapter may require administrator permission. Install any missing runtime components requested by the installer. |
Quit other proxy clients before running the installer. For your first test, use the system proxy. If an app doesn’t follow it, enable TUN using the configuration guide.
In the Apple menu, open About This Mac to check whether your Mac has Apple Silicon or an Intel processor. Both architecture links are shown below, but some clients may currently serve the same x64 file from either link. The button label identifies the download entry, not necessarily a native ARM build. Check the downloaded file and installer details to confirm compatibility.
Choose the build for your chip, open the disk image, and follow the installation instructions. On first launch, import your configuration and confirm that the system proxy points to the local listening port. Review any system permission prompts before enabling background services.
Official site: clashplus.io ↗
Includes a desktop interface for managing subscriptions and rules. Both download links may currently point to the same Intel build, so Apple Silicon users should check translation compatibility. Test a basic proxy connection after installation, then configure service mode and advanced DNS options as needed.
A good fit if you want to keep using FlClash across platforms. AMD64 and x64 both refer here to 64-bit Intel architecture, not to a specific processor manufacturer. Apple Silicon users should check the actual build rather than relying on the link label.
For maintaining and migrating existing setups. The archived download points to an x86_64 file; it is not a native ARM build. The older core has limited support for newer configurations. If it can’t parse a field, consider moving to a maintained client.
| Check | Before installing |
|---|---|
| macOS version | Minimum macOS versions vary by project. Check the installer or app documentation rather than relying on a single version requirement. |
| Chip type | Choose an ARM64 build for Apple M-series chips and x64 for Intel. If only an Intel build is available, confirm that translation is supported on your system. |
| System permissions | Grant system proxy, network extension, or service permissions when prompted. Leave features you don’t need disabled. |
Quit any old menu bar client before upgrading. If the system proxy still points to an exited process, reset the proxy settings and relaunch the new client. This helps distinguish a stale setting from a failed installation.
For most recent phones, start by checking for an ARM64 build; choose ARMv7 for older 32-bit devices. If you’re unsure about your architecture, Clash Meta for Android offers a universal build. Installing the APK and granting VPN permission are separate steps. After installation, import a configuration and start the connection manually.
For 64-bit ARM Android devices. After installation, check the configuration before allowing a VPN connection. If the connection drops when the app is in the background, check battery management and background activity restrictions instead of reinstalling the same APK.
Official site: clashplus.io ↗Choose from builds for different CPU architectures. The universal version is useful if you can’t identify your architecture, but its file is usually larger. After importing a configuration, check the app access controls: excluded apps won’t be routed through the client in the same way.
A good fit if you want a similar interface on desktop and Android. Check that the Android VPN icon matches the client’s connection status. Phones typically allow only one app to use the VPN interface at a time, so disconnect any existing VPN before testing.
For users with an existing Surfboard-compatible configuration. Surfboard is not a Clash YAML client, so check the subscription’s response format before importing. Similar file extensions don’t guarantee compatible fields; after conversion, review policy groups and rule behavior.
| Check | Before installing |
|---|---|
| Architecture | arm64-v8a is 64-bit ARM; armeabi-v7a is 32-bit ARM. Emulators may use a different architecture. |
| Installation | Your Android version must meet the app’s requirements. Grant the browser or file manager you use to install the APK permission to install apps. |
| Connecting | Allow VPN access when prompted for the first connection. Battery optimization may also affect background activity. |
If Android reports “App not installed,” check for an architecture mismatch, an outdated OS version, insufficient storage, or a signature conflict. If you need to uninstall the existing app, export your configuration first; uninstalling may also delete app data.
Install Clash Plus from the App Store on iPhone or iPad. The store listing shows the current OS requirements, compatible devices, and release notes; check the information displayed on your device before installing. Prepare a working configuration before connecting and review the system prompt to add a VPN configuration.
After installation, import a subscription or configuration, select it, then allow the app to add a VPN configuration. If a website works but an app doesn’t, check rule matching and connection logs to distinguish a policy issue from the app’s own network requirements.
Official site: clashplus.io ↗| Check | Before installing |
|---|---|
| Compatible devices | Check the App Store listing for supported iPhone and iPad models and iOS versions. |
| Installation source | Use the App Store link above to view app details. Install future updates through the store. |
| Network permissions | Allow the app to add a VPN configuration when prompted. If another VPN is installed, check its connection status first. |
Subscription URLs are often linked to your account. Keep them secure and don’t show the full link in public screenshots. When moving between devices, transfer only the configuration you need, then check permissions and policy selections on the new device.
These GUI packages are for AMD64 / x86_64 distributions with a desktop environment. For Debian- and Ubuntu-based systems, choose DEB; for Fedora and other RPM-based distributions, choose RPM. Headless servers don’t need a desktop just to use a proxy: see the Mihomo core section and systemd deployment guide.
For managing configurations and proxy status on a Linux desktop. Install with your distribution’s package manager to handle dependencies. Desktop system proxy settings may not apply to terminal programs; configure environment variables or use TUN for command-line tools.
For Debian-based desktop users who prefer the FlClash workflow. If the app won’t start after installation, check the terminal output to distinguish missing desktop dependencies from a configuration loading error. Troubleshoot service permissions and desktop launch issues separately.
| Check | Before installing |
|---|---|
| Platform and architecture | The GUI packages here are for AMD64 / x86_64. For ARM servers, use the core section rather than trying to install an x64 desktop package. |
| Package format | Choose DEB or RPM for your distribution. The system package manager checks GUI dependencies. |
| Service and device permissions | TUN requires system support for a virtual network adapter and the necessary permissions. In containers, also check device access and network capabilities. |
Desktop proxy settings and shell environment variables are separate configuration methods. For server autostart, configuration paths, and logs, see the Linux Mihomo and systemd deployment guide.
Mihomo is a proxy core that handles protocols, rule matching, and DNS; it doesn’t include a graphical settings interface. The files below are for server and router users, or anyone managing services directly. For everyday desktop use, choose a GUI client above to manage the core, subscriptions, and traffic routing.
| System | Architecture and 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 AMD64 DEB |
| Linux | AMD64 · GZ | Download AMD64 GZ |
| Linux | ARM64 · GZ | Download ARM64 GZ |
| Linux | ARMv7 · GZ | Download ARMv7 GZ |
| Linux / Routers | MIPS softfloat · GZ | Download MIPS softfloat |
Extract ZIP or GZ files, then set the executable permission and configuration path for your target program. GZ compresses a single file; it shouldn’t automatically be treated as a TAR archive. Install DEB packages with your system package manager, then verify the service name, configuration path, and startup status.
Starting the core is only the first step. You’ll also need a valid configuration file, a writable data directory, and the required port bindings. Restrict access to the remote control interface. For LAN sharing, configure your firewall too; don’t expose a proxy listening port directly to the public internet.
Check protocol, core, and configuration compatibility →After downloading
The installer only deploys the program. Check configuration sources, proxy mode, and traffic routing separately. Working through them in order makes issues easier to isolate than changing several settings at once.
The client doesn’t include a subscription service. Prepare your own subscription link or local configuration, import it from the client’s configuration manager, and make sure it’s selected as the active configuration. If the list is empty after importing, check the response format and parsing messages before assuming installation failed.
How to import a subscription →Make sure the local listening port is available, then enable the system proxy and test your browser. Rule mode selects a policy based on rules; it doesn’t mean every request follows the same route. TUN handles traffic routing but doesn’t switch the routing mode to Global. These are separate settings.
Ports and system proxy settings →Before upgrading or switching clients, save your configuration files, subscription details, and local rule overrides. Quit the old client before testing the new one to avoid conflicts over ports, the system proxy, or the virtual network adapter. Once subscription updates, rule matching, and connections from your usual apps are working, remove the old setup.
Check rule-based routing →Installer FAQ
For your first setup, choose a GUI client. This page recommends Clash Plus for Windows, macOS, Android, and iOS, and Clash Verge Rev for Linux. GUI clients provide subscription import, proxy modes, and connection status. The Mihomo core is mainly for server and router users who manage configuration files and services themselves.
Check your device’s processor architecture in system settings, then verify the installer details. Windows x64 is for common 64-bit Intel and AMD processors. On Android, arm64-v8a is for most 64-bit ARM devices; armeabi-v7a is for 32-bit ARM. Choose the universal build if you’re unsure about your Android architecture. Some macOS architecture links on this page may currently resolve to the same x64 file. Apple Silicon users should confirm translation compatibility before installing.
Installing the client is only the first step. Import a working subscription or configuration file, select an active configuration and policy, then enable the system proxy or TUN if needed. Check that the configuration loaded and that no port is in use, then review the connection log. The installer does not include a subscription service.
Export your configuration and note your subscriptions, rule overrides, and port settings, then quit the running client. When upgrading the same client, follow the installer’s instructions. If switching clients, don’t assume their configuration directories are compatible. Once migration is complete, verify that connections work before removing the old app or configuration. Avoid letting two clients control the system proxy or virtual network adapter at the same time.
Save the full error message and confirm that the installer architecture matches your OS version. On Windows, check for required runtimes. On macOS, review the specific security alert in System Settings. On Android, check install permissions, storage space, and signature conflicts with existing apps. Don’t leave system security features disabled as a workaround. If only TUN fails after installation, check the service permissions separately.
Both clients are no longer maintained. Archive downloads are provided for migrating older setups and reproducing compatibility issues; choose a maintained client for a new installation. Features, protocols, and configuration fields in older versions may differ from current Mihomo. When migrating, recheck your rules, DNS settings, and subscription parsing results.