Client downloads / System architectures / Mihomo core
Choose your operating system, then confirm your processor architecture. For everyday use, choose a GUI client; for server or router deployments, choose the Mihomo core.
Installers do not include a proxy service. Before getting started, prepare a subscription you’re authorized to use or a local configuration. See the setup guide for the recommended steps.
Clients are listed in a consistent order for each platform, with the recommended option first and archived clients clearly marked.
The GUI clients below provide x64 installers. Check Settings → System → About in Windows to confirm your system type. Don’t mistake an x64 package for a native ARM64 build on an ARM device. For a new installation, start with Clash Plus, then choose another client if its interface or configuration options better suit your needs.
A good fit for a straightforward desktop setup: install the app, then add a subscription or import YAML. Select the configuration, check the policy group and outbound selection, and then enable the system proxy.
Product details: clashplus.io
A good fit for managing configurations, rule overrides, and runtime settings through a desktop interface. When migrating an existing setup, import and verify the original subscription first, then restore local overrides one at a time. Don’t assume the old client’s GUI settings will transfer completely.
A good fit if you want a similar workflow across desktop and mobile. This page provides the Windows installer. After importing a subscription, check rule mode and your policy group selection. When updating the subscription later, take care to keep any local settings you need.
Another Windows desktop client to try if its interface suits your workflow. On first launch, verify the connection with a known-good configuration before changing the proxy port, startup behavior, or other settings. This makes troubleshooting easier.
This archived download is for compatibility with older setups and configuration migration. For new devices, choose a client that is still updated. Older configurations may differ in core fields, rule sets, and network routing behavior; back up your configuration and note the current listening ports before migrating.
| Check | What to do |
|---|---|
| System | Use a supported version of Windows 10 or 11 where possible. Check the selected client’s current release notes for its minimum version and runtime requirements. |
| Processor architecture | The GUI installers here are x64 / AMD64. Compatibility with Windows on ARM depends on the operating system and client components; these are not native ARM packages. |
| Network permissions | The system proxy generally works with apps that follow system proxy settings. TUN or service mode may require administrator privileges and the relevant driver components. |
| Verify after installation | Close any old client, import your configuration, and select rule mode before checking connection history. If a port is already in use, resolve the conflict instead of reinstalling repeatedly. |
Open the Apple menu and choose About This Mac to see whether it lists a chip name or an Intel processor. Choose a package based on its actual architecture; the DMG extension alone does not mean the files are interchangeable.
Download the DMG for your Mac’s chip, open it, and move the app to Applications. On first launch, import your configuration, then follow the client’s prompts for system proxy or network permissions. Quit any running older instance before updating the app.
Product details: clashplus.io
A good fit for managing multiple configurations and local overrides on desktop. After downloading, confirm the app launches before setting up the system proxy and service components. Verify basic rule mode before changing cores or enabling TUN, so permission and configuration issues don’t compound.
Offers a similar configuration management workflow across platforms. The Mac file currently listed is AMD64, which is in the same architecture family as x64. Apple Silicon users should confirm compatibility before configuring system network routing.
For compatibility with existing menu bar workflows and migration. This archived client is not recommended for new systems. If permissions or runtime issues appear after a macOS upgrade, back up your subscription and local rules, then migrate to a client that is still updated.
| Check | What to do |
|---|---|
| macOS version | Use a supported version of macOS. Minimum requirements vary by client build; check the release notes before installing. |
| Chip type | On Apple Silicon, choose a file explicitly labeled ARM64; on Intel, choose x64. An app running through compatibility support does not guarantee that its helper services or network components are compatible. |
| Install location | Move the app to Applications before launching it. Running it from the disk image can interfere with updates and prevent helper components from being found. |
| Permissions | Grant permissions only for actions you expect. If prompted to allow a network extension or access the keychain, verify the app name and the source of the request. See the setup guide for details. |
Recent devices typically use ARM64, but a 64-bit-capable processor doesn’t guarantee that the system runs 64-bit apps. Check which app architectures your device supports. If you’re unsure, consider a client with a universal build. The first connection requires system approval for VPN access.
This download is an ARM64 APK. After installing, add a subscription, select the configuration, and check the policy group before connecting. Approve the VPN prompt for the current app. If the connection drops in the background, adjust its background permissions in your device’s battery settings.
Product details: clashplus.io
A good fit for Android users with Clash configurations. Available builds include ARM64, 32-bit ARM, and universal. The universal build can help if you’re unsure of the architecture, but your Android version must still meet the app’s requirements. Back up your setup before migrating from another variant.
Provides Android builds for ARM64 and ARM. If you also use FlClash on desktop, you’ll find a similar configuration workflow, but device permissions and network routing must be configured separately. Don’t assume desktop listening port or TUN settings are suitable defaults for a phone.
A good fit for users with a compatible Surge-style configuration. Surfboard is not a drop-in replacement for clients that read all Clash YAML fields. Before downloading, check which format your subscription provider offers and whether it supports your proxy protocols and rules, so format issues aren’t mistaken for network problems.
| Check | What to do |
|---|---|
| System and architecture | Check your Android version and app ABI: ARM64 corresponds to arm64-v8a, and ARM to armeabi-v7a. See the installer and release notes for the minimum system version. |
| Install permissions | In system settings, grant the app used to open the APK permission to install apps. You can revoke that permission after installation if you wish. |
| VPN slot | A regular personal VPN connection typically can’t be controlled by multiple apps at once. Disconnect other proxy or VPN apps before connecting; handle work profiles according to your device’s policies. |
| Installation failed | Check the Android version, CPU architecture, available storage, and any signing conflict with an installed app, in that order. Export your configuration before switching variants; don’t clear app data as a first step. |
Install on iPhone or iPad through the App Store. Check the store listing for compatibility and app details, then import your configuration after installation. On first connection, follow the system prompt to add a VPN configuration and verify which app is requesting permission.
Get the client from the App Store. After installation, open configuration management and add a usable subscription or import a compatible configuration. Select a configuration and policy group before connecting. Subscription URLs often contain access credentials, so be mindful of who can see them when copying, taking screenshots, or syncing to other devices.
Website: clashplus.io
| Check | What to do |
|---|---|
| System compatibility | Check the current App Store compatibility list for the minimum iOS or iPadOS version and supported devices. Expand Compatibility in the store listing before installing. |
| Prepare your configuration | Have a subscription you’re authorized to use or a compatible configuration ready. Installing a client and getting proxy service are separate steps. |
| First-time authorization | Allow the expected VPN configuration when connecting. Once iOS shows the VPN status, check the client’s connection history to confirm requests use the expected outbound route. |
| Regular updates | The App Store updates the client, while subscriptions are refreshed inside the app. These are separate update processes. |
Check your distribution’s package manager and processor architecture first. DEB packages are for Debian, Ubuntu, and related distributions; RPM packages are for distributions that use the RPM package system. The desktop packages here are AMD64 / x86_64. For server or router deployments, see the Mihomo core tab.
A good fit for managing subscriptions and rule configurations on a Linux desktop. Choose DEB or RPM for your distribution and use its package manager to resolve dependencies. After installation, verify that a basic configuration loads before setting up the system proxy or network features that require extra permissions.
This section provides an AMD64 DEB package for desktop distributions that support this architecture and package format. Launching the app window doesn’t mean it handles all network traffic. Choose system proxy or TUN based on whether your apps follow proxy settings.
| Check | What to do |
|---|---|
| Processor | Run uname -m to check the architecture. x86_64 matches the AMD64 packages here; aarch64 devices cannot run these native desktop packages. |
| Desktop and dependencies | GUI clients require a desktop session and the relevant graphical libraries. Check the current build notes and package manager output for minimum distribution, glibc, and runtime requirements. |
| Installation method | Install with your distribution’s package manager and use it to resolve dependencies. Don’t rename a DEB as an RPM or mix software sources from different distributions to resolve dependencies. |
| Service permissions | TUN, routing, and DNS interception may require elevated permissions. For server deployments, use a dedicated service account and a clearly defined configuration directory rather than running the entire GUI as a privileged process long-term. |
Mihomo is a core that loads configurations, matches rules, and handles proxy connections; it is not a GUI client. This section is for server and router deployments and users who manage services themselves. Desktop and mobile users should generally choose a GUI client above to manage configuration and runtime status.
| System | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · 64-bit x86 | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · 64-bit ARM | Download ARM64 ZIP |
| macOS | Intel AMD64 | GZ · Command-line core | Download Intel GZ |
| macOS | Apple Silicon ARM64 | GZ · Command-line core | Download ARM64 GZ |
| Linux | AMD64 | DEB · Package installation | Download AMD64 DEB |
| Linux | AMD64 | GZ · Binary deployment | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM | Download ARM64 GZ |
| Linux | ARMv7 | GZ · Compatible 32-bit ARM environments | Download ARMv7 GZ |
| Linux | MIPS-softfloat | GZ · MIPS soft-float environments | Download MIPS GZ |
ZIP is an archive and GZ is a compressed file; neither is a double-click installer. After extracting, place the core and configuration in a clearly defined directory. On macOS or Linux, grant execute permission if needed. Test the configuration from the command line before registering a system service, so repeated service restarts don’t mask configuration errors.
The commands below use a Unix-like environment and assume the current directory contains an executable named mihomo and a config.yaml file. A successful test only confirms that the configuration can be read; it doesn’t guarantee that subscriptions, DNS, or outbound connections work. Check the logs to verify actual requests.
./mihomo -t -f ./config.yaml
./mihomo -d . -f ./config.yamlFor server deployments, restrict the control interface and proxy listening addresses, and configure authentication and firewall rules as needed. Never expose the local control interface directly to the public internet. For how rules, policy groups, and listening ports fit together, see port settings and the policy groups section.
The installer provides the client and its bundled components; the subscription provides available proxies, policy groups, and rules. Updating the client won’t fix an expired subscription, and refreshing a subscription won’t update the client. Download buttons retain their full file links and use links from the download manifest when it’s available on the page. Client version details appear only when the manifest contains valid data. Check the platform and architecture you selected to confirm the package name.
For a first installation, import one configuration from a trusted source, select rule mode, choose a proxy policy group, then test with the system proxy or your mobile device’s VPN connection. Once basic requests work, configure TUN, DNS overrides, and per-app routing as needed. Changing ports, DNS, policy groups, and routes all at once makes problems harder to isolate. See the setup guide for full instructions and proxy modes for the differences between modes.
Before switching clients, note your subscription source and record any manually added rules and local overrides you need. Screenshots alone usually aren’t enough to restore a complete configuration. Turn off the old client’s system proxy and TUN before starting the new one. Once connections, DNS resolution, and rule matching work, clean up the old setup. Subscription links and configurations may contain access credentials; keep backups somewhere secure and share only the necessary, sanitized details when troubleshooting.
For installation issues, check architecture and permissions first; for connection issues, check your configuration and network. Find more steps in Troubleshooting.
Desktop and mobile users should usually start with a GUI client to import configurations, switch modes, and view logs. The Mihomo core is for server and router users who manage configuration, startup options, and system services themselves; it is not a standard desktop installer.
x64 and AMD64 usually refer to the 64-bit x86 architecture; ARM64 refers to 64-bit ARM. Check your processor and operating system in system information before choosing a download. On macOS, distinguish Intel from Apple Silicon. Some current Mac downloads are x64, so check the card details to see whether Rosetta is needed.
The installer provides the client only; it does not include a proxy service. After installation, import a subscription you’re authorized to use or a local configuration, choose a policy group, and enable the system proxy or TUN if needed. For your first connection, use rule mode and check connection history and logs to confirm the actual outbound route.
Multiple clients may change system proxy settings, compete for listening ports, or create virtual network interfaces at the same time. Before switching clients, turn off the old client’s system proxy and TUN, then exit the old process. Check the new client’s ports and permissions before reconnecting, and avoid running multiple network interception instances at once.
Before updating, note your subscription source and export your local configuration, rule overrides, and any settings you want to keep. Configuration directories and GUI data are not fully interchangeable between clients, so use the subscription URL or standard YAML configuration when migrating. Verify the new client before retiring the old one, and never share backups containing subscription credentials publicly.
Clash for Windows and ClashX Meta are listed for compatibility with older setups and migration of existing configurations, not as first choices for new devices. Unmaintained clients may not support newer system permissions or configuration fields. For a fresh install, choose a client that is still updated; back up older setups before migrating.