Choose your operating system, then select the right architecture. Use a GUI client on desktops and phones; choose the Mihomo core for servers and routers as needed.
Desktop client / EXE
The desktop installers below are for x64 devices. For a first installation, start with Clash Plus. If you already have a CFW setup, back it up first, then restore subscriptions and overrides individually in the new client.
A good choice for first-time installs and anyone who wants to use a similar configuration across desktop and mobile. After installation, import a subscription or local configuration and confirm you can select a policy group before enabling the system proxy. To route traffic from apps that ignore the system proxy, follow the guide to configure TUN and grant the required permissions.
clashplus.io
A good fit for users who need desktop subscription management, rule configuration, and service mode. Before migrating, check your existing scripts, override fields, and core differences. Don’t copy the old client’s entire data directory. Follow the system prompts to authorize service-related features the first time you enable them.
A cross-platform GUI client option. After importing your configuration, start in rule mode and check your proxy groups and default route before deciding whether to enable startup on login. If another proxy app is already running, turn off its system proxy first to avoid conflicting settings.
Another option for managing desktop configurations. Before choosing it, confirm that the included core supports your existing subscription. After installation, keep a minimal working configuration: verify basic proxying first, then migrate custom DNS, rule sets, and overrides gradually to make issues easier to diagnose.
Keep this build for restoring existing setups, migrating configurations, and troubleshooting compatibility. Clash for Windows is discontinued, so newer protocols, system changes, and configuration fields may not be supported. For new devices, choose one of the alternatives above. To recover old settings, back up Profiles, Mixin, and local rules first.
| Check | Recommendation |
|---|---|
| Operating system | Use a supported version of Windows 10 or 11. Check the installer for each client’s minimum requirements. |
| Processor | This section provides x64 installers. Check your system type under Settings > System > About. Confirm compatibility separately for ARM devices. |
| Permissions and ports | Installing a service and using TUN may require administrator approval. Listening ports must be available, but clients don’t all need to use the same port. |
You’ll still need to import a configuration after installation. See the Windows setup guide for steps.
Desktop client / DMG
Check About This Mac for your chip: Apple M-series chips use Apple Silicon builds, while Intel processors use x64. Some download links currently point to the same x64 file, so check the architecture of the actual download.
Separate installers are available for both Mac architectures. Open the disk image and follow the prompts, then launch the app from Applications. If prompted to grant network-related permissions, verify the app’s name before allowing access. Importing a configuration doesn’t enable the system proxy; check the connection settings separately.
clashplus.io
A good fit for users who need subscription management and desktop system integration. Both links currently point to the same x64 file; they are not separate native builds. Apple Silicon devices may require Rosetta, and you should check compatibility with your macOS version. For a native ARM64 build, see Clash Plus above.
A good fit if you already use FlClash on another platform and want a familiar workflow. AMD64 in the filename refers to the same architecture as x64; this is not a native Apple Silicon build. After installation, check that your configuration loads before enabling the proxy. Don’t let two clients manage the system proxy at the same time.
This archived download is kept to help migrate older setups. Both architecture links currently provide an x86_64 file; the button labels don’t indicate native ARM64 builds. Compatibility issues may not be fixed now that development has stopped. For new installations, choose a maintained client.
| Check | Recommendation |
|---|---|
| macOS version | Minimum macOS versions vary by client. Check each app’s requirements and installer prompts; don’t assume one client’s requirements apply to another. |
| Processor architecture | Use native ARM64 builds on Apple M-series Macs and x64 builds on Intel Macs. x64 apps on Apple Silicon may require Rosetta. |
| Network permissions | System proxy, service, and network extension permissions work differently. Enable only the features you need, and verify which app is requesting access. |
If you have trouble launching the app or granting network permissions, see the macOS setup guide. Don’t bypass prompts by disabling system-wide protections.
Phones and tablets / APK
Most recent Android phones use ARM64. Check your device’s supported architecture before downloading. The first time you connect, Android will ask you to authorize the VPN connection.
A good starting point for configuring Clash on your phone. After downloading, allow your browser or file manager to install apps when prompted; you can revoke that permission afterward. Import a subscription and choose a policy before connecting. If the connection keeps dropping in the background, check the app’s battery and background-use restrictions.
clashplus.ioChoose an installer for your device’s architecture, or use the universal build. If you know your device’s architecture, use the matching package; if not, try the universal one. System requirements still apply. If an update reports a signature mismatch, back up your configuration and check the download source before uninstalling the app and risking your local settings.
Choose the installer that matches your phone’s architecture. The ARMv7 build is for devices that still support that architecture. Confirm the system VPN prompt the first time you connect; disconnect any other VPN app first. Installing the app doesn’t configure a subscription, and system proxy settings from your desktop won’t sync to your phone.
A good fit if you already have a configuration compatible with Surfboard. Surfboard isn’t a drop-in replacement that can read every Clash YAML file; check its subscription format and protocol support separately. If you only have a Clash-format subscription, ask your provider whether a compatible format is available. Simply changing the file extension won’t make it importable.
| Check | Recommendation |
|---|---|
| macOS version | Minimum Android versions vary by client and release. Check the app’s documentation and the installer’s result; a matching architecture doesn’t guarantee that your Android version is supported. |
| CPU architecture | ARM64 corresponds to arm64-v8a, and ARMv7 to armeabi-v7a. Universal builds are for devices with an unknown architecture that still meet the system requirements. |
| Connection permissions | Android requires VpnService permission. If background activity is restricted, check battery optimization, auto-start, and background permissions. Don’t run multiple VPN connections at once. |
See the Android setup guide for installation and background settings. Work profiles and device management policies may also restrict VPN use.
iPhone and iPad / App Store
Install Clash Plus from the App Store. Check the store listing for current OS compatibility, app permissions, and update information.
Open the app after installation and import a subscription or configuration you’re authorized to use. Follow the app’s steps to add a VPN configuration. When iOS asks for permission, check the app name and prompt before allowing the connection. Once connected, review your policy groups and rules; you don’t need to stay in global mode for everyday use.
clashplus.io| Check | Recommendation |
|---|---|
| System and device | Check the App Store compatibility section for supported iOS or iPadOS versions and devices. |
| Installation and updates | Install and update through the App Store. If installation fails, check your OS version, available storage, and the specific message shown in the store. |
| Network configuration | The first time you connect, allow the app to add a VPN configuration. Before using it alongside other network extensions or VPN tools, check the connection status and any management policies. |
Desktop distributions / DEB and RPM
This section provides AMD64 GUI clients. Choose DEB for Debian, Ubuntu, and compatible distributions; choose the matching RPM for Fedora and other RPM-based distributions. For servers and routers, see the Mihomo core tab.
A good choice if you have a desktop environment and want a GUI for managing subscriptions and policies. Install through your distribution’s package manager when possible so it can check dependencies. The desktop system proxy only affects apps that follow that setting. Terminal programs may need proxy environment variables configured separately, so a tray icon alone doesn’t confirm that all traffic is routed.
An installer for AMD64 desktop environments that support DEB packages. If the installer reports missing dependencies, check your distribution version and software sources instead of forcing the installation. Before enabling TUN, check permissions and local routing. If you’re connected remotely, make sure you have a way to recover before changing the default route.
| Check | Recommendation |
|---|---|
| CPU architecture | This section provides AMD64 / x86_64 packages. Check your architecture with uname -m; ARM64 devices can’t install AMD64 packages directly. |
| Package format | DEB and RPM packages aren’t interchangeable just by changing the file extension. Use your distribution’s native package manager and read any dependency errors. |
| Runtime environment | GUI clients require a desktop environment and the relevant runtime libraries. Services and TUN also need appropriate permissions. If you don’t have a desktop environment, use the core instead. |
See the Linux setup guide to understand the differences between desktop proxy settings, terminal environments, and system services.
Servers and routers / command line
Mihomo is a proxy core, not a desktop installer with subscription management. Most users should choose one of the GUI clients above. Choose the core for your device architecture if you need to manage configuration, services, and routing yourself.
| System | Architecture | Package type | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | 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 |
| Check | Deployment notes |
|---|---|
| Architecture and format | Choose a build that matches your device. GZ files are compressed; extract them before setting executable permissions. Install DEB files with a compatible package manager. |
| Configuration and directories | You need a readable YAML configuration and a writable data directory. Make sure rule sets and geodata paths match the configuration, and start the core from the right directory. |
| Permissions and access | TUN, routing, and DNS listeners may need additional permissions. Restrict the control interface to trusted access; don’t expose it directly to the public internet. |
Run the core in the foreground and check its error output before deployment. Once you’ve confirmed the configuration loads, set up a background service and automatic startup. See the Linux and service deployment guide.
From installer to working connection
Verify a basic connection first, then add custom rules. Installation, configuration, and routing traffic are separate steps; checking them in order makes issues easier to pinpoint than repeatedly changing installers.
Use a subscription URL you’re authorized to access, or select a local YAML configuration. A webpage URL isn’t the same as a subscription link. If importing fails, check the format, access status, and error details. Subscription URLs may contain credentials, so don’t post them publicly.
Start with rule mode for everyday use, then choose an outbound in the relevant policy group. Global mode is for cases where you specifically need all traffic routed the same way; it won’t fix an unavailable node. Direct mode doesn’t turn off the client, so check the core status separately from proxy routing.
Check the local listening port before enabling the system proxy. Use TUN only if you need to route more traffic. Test with the apps you actually use and check the logs to confirm rules are being applied. If something goes wrong, turn off the new setting and return to the last working state.
Installer FAQs
Check your operating system, architecture, and configuration source first. These answers cover choosing an installer and getting started; follow each client’s prompts for app-specific instructions.
Start with the platform for your device. Check Clash Plus first for Windows, macOS, Android, and iOS; for Linux, start with Clash Verge Rev. If you already have a configuration file, make sure the client’s core supports its protocols and fields before importing it.
On Windows, check System type under Settings > System > About. On macOS, check the chip under About This Mac. Most Intel- or AMD-based desktop computers use x64; Apple Silicon uses ARM64. Most recent Android phones use ARM64, while older devices may need ARM. If you’re unsure, try the available universal build. Always check the architecture of the actual installer.
The installer provides the client, not a working subscription or proxy nodes. Import a configuration you’re authorized to use, choose a policy group, then enable the system proxy or TUN as needed. The system proxy only affects apps that follow that setting; TUN usually requires service or network-extension permissions.
Archived builds are intended for migrating existing setups and troubleshooting compatibility. Since the project is no longer maintained, it won’t receive regular fixes, and newer operating systems, protocols, or configuration fields may not be supported. For new installations, choose a maintained alternative and keep your existing configuration before migrating.
Keep your subscription URL, local configuration, custom rules, overrides, and any port settings you need. Configuration directories and override mechanisms vary between clients, so don’t replace the entire data directory. Import a configuration into the new client and verify that it connects before disabling the old client’s proxy and startup settings.
The Mihomo core reads configuration and handles proxying, DNS, and rules. It’s typically managed through the command line, a service, or an external control interface. A GUI client adds subscription import, policy switching, and system integration. Most desktop and mobile users should choose a GUI client; server and router users can select the core for their device architecture.