CLIENT PACKAGES / DOWNLOADS
Choose your operating system, then check your processor architecture. Desktop clients handle subscriptions and rules; the standalone Mihomo core is for self-managed deployments.
Browse by platform
Start with the featured pick if this is your first installation. Choose another client based on its interface, configuration features, and fit with your existing workflow. The architecture listed in the package name matters more than the device brand.
Most desktop packages below are x64. Go to Settings → System → About to check your system type. A Windows device with an ARM processor isn’t necessarily able to run x64 apps natively.
A good fit if you’re getting started with subscriptions and node selection. Install the desktop app, then add your configuration. System proxy routes traffic from apps that follow your system proxy settings; enable TUN only if your use case calls for it.
A good fit for desktop users who need subscription management, rule inspection, and connection troubleshooting. Powered by the mihomo core, it lets you manage subscriptions in Configuration, choose policies in Proxy, and check errors in Logs. TUN mode may also require service permissions as prompted by the client.
A good fit if you use both desktop and Android and prefer a similar interface on each. After importing your configuration, check your proxy groups and routing mode. When switching devices, copy the configuration; don’t overwrite the application data directory across platforms.
An alternative desktop experience. Before choosing it, check that the current release supports your core features and configuration fields. When switching clients, quit the old one before importing your configuration to prevent both apps from changing system proxy settings or listening on the same port.
Archived installers are for recreating legacy setups and migrating configurations. Older cores may handle newer protocols, fields, and rule sets differently; importing a subscription doesn’t guarantee every node will work. For a new installation, choose a currently maintained client above.
| Check | Before you install |
|---|---|
| Operating system | Use a version of Windows 10 or 11 that is still supported by Microsoft. Check the installer for the minimum requirements of each release. |
| Processor | Most packages here are x64 / AMD64. On ARM devices, check compatibility and whether the client’s services support your system. |
| Permissions | The installer or client services may ask for administrator approval. System proxy usually doesn’t require an admin service; check TUN permissions separately. |
| First launch | Import your configuration before enabling the proxy. If the installer reports a missing dependency such as WebView2, follow the prompts to install it. |
Check your chip under Apple menu → About This Mac. Apple Silicon uses ARM64; Intel Macs use x64. For compatibility builds, check the filename and whether Rosetta is required.
Choose the DMG that matches your Mac’s chip. Open the disk image and drag the app into Applications, then launch it from there. Import your subscription and select a node before enabling the proxy. If you need the client to route traffic in the background, follow the system prompts to grant the required permissions.
A good fit for managing multiple configurations and checking rule matches on Mac. Both current downloads fall back to x64 builds. Apple Silicon users should confirm Rosetta compatibility; the download label does not guarantee a native ARM build.
A good fit if you want a consistent experience across devices. The current macOS fallback is an AMD64 build; Apple Silicon users should check compatibility first. After installation, verify that your configuration parsed correctly instead of relying only on the connection toggle.
Archived builds can help migrate from an older menu bar workflow or recreate a legacy setup. The current fallback is an x86_64 build; Apple Silicon users should check compatibility. Export and keep your old configuration, then test it in a new client rather than editing the original directly.
| Check | Before you install |
|---|---|
| macOS version | Minimum macOS versions vary by client. Check the requirements for the release you download; opening a DMG doesn’t mean the app is compatible with an older system. |
| Chip | On Apple Silicon, choose a native ARM64 build when available. The x64 compatibility builds labeled on this page may require Rosetta. |
| Install location | Move the app to Applications, eject the disk image, and launch it from there to avoid issues with updates and service paths. |
| System permissions | Follow system prompts to approve app and network permissions. If you see a security warning, check its specific cause rather than disabling system-wide protections. |
Most newer phones use ARM64, but processor capabilities and the ABIs supported by the operating system can differ. Check your device information, or choose a clearly labeled universal package if you’re unsure.
An ARM64 installer is available. Grant installation permission only to the browser or file manager you use. On first connection, approve Android’s VPN request. If the connection drops when the screen locks, check battery management settings instead of reinstalling the app.
A good fit if you already have Clash configurations and want to keep using rules and proxy groups on Android. ARM64 is for compatible 64-bit systems; ARM supports compatible devices. The universal build is convenient if you can’t identify your architecture, but it’s usually larger.
A good fit if you already use FlClash on desktop. Android routes traffic through its VPN service, which works differently from a desktop system proxy. Before connecting, quit other apps using the VPN connection, then check your active configuration and node.
A good fit if you already have a compatible configuration. Surfboard uses a different syntax from Clash YAML, so changing the file extension won’t make a configuration importable. Check which formats and protocols your subscription provider supports before choosing this client.
| Check | Before you install |
|---|---|
| macOS version | Minimum Android versions vary by release. If the installer reports an incompatibility, check your Android version and ABI first. |
| Package architecture | arm64-v8a is ARM64; armeabi-v7a is 32-bit ARM. These labels indicate architecture, not how recent the release is. |
| Connection permissions | You’ll need to approve the VPN request the first time you start the proxy. Usually, only one active VPN service can run in the same user profile. |
| Background operation | For a persistent connection, check background activity and battery restrictions. Adjust settings only for apps that need it, then check whether the connection holds when the screen locks. |
Install Clash Plus from the App Store. Check the store listing for supported iOS versions and devices.
Import your own subscription or configuration after installing. Check your nodes and rules, then follow the system prompts to add a VPN configuration. Test access in an app you use regularly after connecting. If only some apps have issues, check your rules and DNS before reinstalling.
| Check | Before you install |
|---|---|
| System and device | Check the App Store compatibility section for the app’s supported iOS versions and devices. Don’t assume requirements are the same as on other platforms. |
| Installation | Use the App Store link above. The App Store handles installation and updates. |
| Network permissions | Allow the VPN configuration when prompted. If you already use another VPN service, check for conflicts before connecting. |
| Configuration | Prepare a valid subscription or compatible configuration. Buying a device or installing a client doesn’t provide working nodes. |
Choose the package format for your distribution, then check the architecture. DEB and RPM refer to package formats, not processor types; AMD64 and x86_64 usually refer to the same 64-bit x86 architecture.
AMD64 DEB and x86_64 RPM packages are available for desktop configuration management. Install them with your distribution’s package manager and resolve any dependencies. Check TUN service permissions separately from desktop proxy settings; terminal apps may not follow the desktop system proxy automatically.
An AMD64 DEB package is available for desktop users on Debian, Ubuntu, and compatible distributions. If the app won’t start, check its dependencies and desktop session first. If nodes won’t connect, investigate your configuration and core logs instead; these are separate issues.
| Check | Before you install |
|---|---|
| Distribution and package format | Debian- and Ubuntu-based systems typically use DEB; Fedora and other RPM-based systems use RPM. Compatibility also depends on dependency versions. |
| Processor | Desktop packages here target AMD64 / x86_64. Run uname -m to check your architecture. For ARM servers, see the core downloads section. |
| Desktop environment | Graphical clients need a working desktop session and the required runtime libraries. Avoid installing a full desktop environment on a minimal server just to run a proxy client. |
| Proxy coverage | The desktop system proxy, terminal environment variables, and TUN mode route traffic differently. Test each app you need after installation. |
For servers, routers, and users who manage services themselves. Desktop users should choose a graphical client instead; a separate core usually isn’t needed.
| Operating system | Processor architecture | Format | Core package |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download Windows AMD64 |
| Windows | ARM64 | ZIP | Download Windows ARM64 |
| macOS | Intel / AMD64 | GZ | Download macOS Intel |
| macOS | Apple Silicon / ARM64 | GZ | Download macOS ARM64 |
| Linux | AMD64 | DEB | Download Linux AMD64 DEB |
| Linux | AMD64 | GZ | Download Linux AMD64 GZ |
| Linux | ARM64 | GZ | Download Linux ARM64 |
| Linux | ARMv7 | GZ | Download Linux ARMv7 |
| Linux | MIPS softfloat | GZ | Download Linux MIPS softfloat |
| Check | Before deployment |
|---|---|
| Target architecture | Match the architecture of the device that will run the core, not the computer you download it on. For routers, also check endianness and floating-point support. |
| Configuration and data | Prepare a compatible YAML configuration, rules, and geodata files. Make sure the user running the core has the required permissions for its working directory. |
| Service management | An archive isn’t a service installer. Choose a service manager for your system and plan logging, restart behavior, and startup order. |
| Ports and permissions | Check for port conflicts and confirm the listening address first. Configure the required permissions if you need TUN, and don’t expose the controller API directly to the public internet. |
Installation and migration
Check installation, configuration, and connectivity separately. This helps you tell whether the app failed to start or the configuration didn’t take effect.
01 / Installation
Installer errors, missing runtime libraries, outdated system versions, and node timeouts are different problems. First check that the package architecture matches your device and that the app opens and reads your local configuration. Then troubleshoot the network connection. Don’t disable system-wide security to get past an installer warning; identify the specific dependency, permission, or source issue instead.
02 / Configuration migration
Before updating, back up your local configuration, overrides, and custom rules. Note your active proxy groups and ports. A subscription importing successfully in multiple clients doesn’t guarantee that every client supports the same extension fields. Test one configuration in the new client before migrating anything else. For clients with different formats, such as Surfboard, check the subscription format rather than copying YAML directly.
03 / Connection test
After importing your subscription, select the configuration, choose a proxy group and node on the Proxy page, then enable system proxy or TUN as needed. Open the target app and check the matched rule, destination address, and selected policy on the connection page. An enabled toggle only confirms that traffic interception is on; it doesn’t verify access. If you can’t connect, check the subscription, DNS, and node status in the logs.
Download FAQs
This section covers download choices. For DNS, port, and system proxy issues, see the FAQs.
Start by choosing your platform. For Windows, macOS, Android, and iOS, Clash Plus is a good first choice. Choose Clash Verge Rev for desktop configuration management, rule inspection, and log troubleshooting. Linux users can choose between Clash Verge Rev and FlClash. Clients do not include subscriptions, so import your own configuration after installation.
ARM64 and x64 refer to different processor instruction sets, not different software tiers. Check your processor in system settings first. If you can’t identify your Android device’s architecture, choose a universal build if available. An x64-compatible package may require Rosetta on Apple Silicon, so check the package name and client requirements before installing.
Installation only sets up the client. You’ll also need to import a valid subscription or configuration, select it, choose a node in the proxy group, and enable system proxy or TUN mode if needed. Check rule matches on the connection page. Troubleshoot an expired subscription, unreachable node, and local port conflict separately.
Back up your local configuration, subscription URL, custom rules, and override settings. Note the active configuration and proxy ports. Quit the old client before installing the update to prevent two cores from competing for the same ports. When switching clients, test a small part of your configuration first rather than copying the entire application data directory.
Archived builds of Clash for Windows and ClashX Meta can help recreate a legacy setup, migrate configurations, or support an existing workflow. Archived does not mean actively updated, and older clients may not support newer protocols or configuration fields. For a new installation, choose a currently maintained client.
Usually not. Desktop clients typically bundle the required core and manage configuration and startup for you. Standalone Mihomo packages are mainly for servers, routers, and users who manage services themselves; you’ll need to provide a configuration file and handle permissions and service management.