CLIENTS / Choose a device
Choose your operating system, then the right architecture. Use a GUI client on phones and computers; see the Mihomo core downloads below for servers and routers.
Before downloading / 3 things to check
Choose a build for the OS you use, not for the source of your subscription.
ARM64 and x64 builds aren’t interchangeable. Check your device’s processor first.
Have a subscription link or config file ready. Installing the client won’t create nodes for you.
A good fit if you’re setting up a desktop proxy for the first time. Import and select your subscription, then choose an exit node from a proxy group. Turn on the system proxy for browsers; follow the TUN guide if you need to route more apps. Change one setting at a time so issues are easier to diagnose.
clashplus.io ↗
For desktop users who need to manage configs and rule overrides. After importing your subscription, test a basic connection before adding custom rules. Check that the service is running before enabling TUN. If the system proxy works but TUN doesn’t, check service permissions and other virtual adapters rather than downloading the subscription again.
A good option if you want a similar interface on your phone and computer. Extract the entire archive to a permanent folder before running it; don’t launch the app from within the archive. Quit the app before updating and keep its existing config directory. A portable ZIP doesn’t configure the system proxy or network permissions for you.
Another option for a desktop GUI client. When migrating, copy your subscription URL first. Once the new client loads the config correctly, move your rule overrides over one at a time. Clients store local settings differently, so copying the entire old config directory can bring over incompatible UI settings.
Kept for migrating older devices, reproducing existing configs, and compatibility testing. Not recommended as the default client on a new device. Older cores may not recognize newer protocols or config fields. Before migrating, note your subscription URL and proxy port. Once the new client works, disable the old app’s startup launch and system proxy.
A good place to start for a new installation. Move the app to Applications, launch it, import your subscription, and check the proxy groups before enabling the network mode you need. If you’ve used another client, turn off its system proxy first so both apps don’t keep changing the same network settings.
clashplus.io ↗
For users who need desktop config management and overrides. The Apple Silicon and Intel options currently link to the same x64 file, which requires Rosetta on M-series Macs. Test a regular proxy connection before enabling a service or TUN. Check the actual permission status in System Settings.
A good fit if you prefer a mobile-style interface. The available file is AMD64 and requires Rosetta on Apple Silicon. If proxy groups are empty after importing, check that the config is selected and the subscription parsed successfully. Don’t confuse an architecture issue with a subscription format issue.
Kept for compatibility with existing menu bar workflows and older configs. This archived build requires Rosetta on Apple Silicon. As the client is discontinued, compatibility with future system updates and config fields isn’t guaranteed. For new devices, choose one of the clients above, and back up local rules before migrating.
A good choice for a new Android phone. After installation, import the subscription from your provider, start the connection, and approve the VPN request. For the first test, keep rule mode enabled and check a site that should use the proxy. Adjust access controls only when you know which apps should bypass it, so you don’t accidentally exclude your browser.
clashplus.io ↗For users familiar with the Clash for Android configuration screen and network settings. Open Config, choose Import from URL or Import from File, save and select the config, then return to the home screen and start the service. If expected rules don’t appear after an update, check both the selected config and override settings—not just the subscription’s update time.
A good fit if you want a similar experience across devices. For most phones, check for ARM64 first; x86_64 is for compatible systems or emulators. After importing, make sure the config includes proxy groups before starting the service. A webpage or login prompt returned by a subscription URL isn’t a client config.
For users who already have a Surfboard-compatible config. This isn’t a way to import Clash YAML as-is, so check which config formats your subscription provider supports before downloading. If you only have a Clash config, use one of the clients above. When converting configs, check that rules, policy groups, and supported protocols are compatible.
After installing, import a compatible subscription and confirm that proxy groups and nodes appear before connecting. When the system shows a network permission prompt, check the app name and approve it. If the app says it’s connected but webpages won’t load, check the exit node, rule mode, and DNS in order instead of repeatedly toggling the VPN.
App Store usually handles app updates. Before switching devices, save your subscription source and any custom rules separately; an installed app isn’t a config backup. Subscription links may grant access to your account, so don’t post them in public forums or include them in screenshots.
clashplus.io ↗
For Linux desktop users who want a GUI for subscriptions, proxy groups, and rule overrides. After installation, test the config with a regular proxy before setting up a service or TUN. If terminal commands can’t connect, check whether they read system proxy settings; you may need to configure environment variables separately.
For desktop users familiar with the FlClash interface. Install the DEB, launch the app from the menu, import a config, and select a proxy group. If the window won’t start, check the terminal for dependency or display errors. If the app opens but the network doesn’t work, check the proxy port, desktop proxy settings, and routing permissions.
MIHOMO / CLI & SERVICE
For servers, routers, and self-managed environments. Most computer and phone users should choose a GUI client above and don’t need a separate core.
| Operating system | Architecture | File | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Windows AMD64 ↓ |
| Windows | ARM64 | ZIP | Windows ARM64 ↓ |
| macOS | Intel · AMD64 | GZ | macOS Intel ↓ |
| macOS | Apple Silicon · ARM64 | GZ | macOS Apple Silicon ↓ |
| Linux | AMD64 | DEB | Linux AMD64 DEB ↓ |
| Linux | AMD64 | GZ | Linux AMD64 GZ ↓ |
| Linux | ARM64 | GZ | Linux ARM64 ↓ |
| Linux | ARMv7 | GZ | Linux ARMv7 ↓ |
| Linux | MIPS · softfloat | GZ | Linux MIPS softfloat ↓ |
Extract GZ files before use, then set appropriate execute permissions on the binary. For routers, check the CPU model as well as byte order, floating-point ABI, and firmware support. MIPS softfloat does not work on every MIPS device. Install DEB files with a package manager that matches your distribution; they aren’t archives you can run directly.
Running the core on its own requires a config directory, listening ports, and a launch method. Transparent proxying also involves routing, firewall rules, and permissions. First confirm that the config loads locally, then integrate it with a system service. Don’t expose proxy ports or the control interface directly to the public internet. For LAN access, allow only devices you trust.
First make sure the app opens, then set up the config. Get a subscription URL or file from a trusted source and import it using the appropriate option in the client. If the link contains access credentials, paste it directly into the client; don’t submit it to a public website to troubleshoot. After a successful import, you should see proxy groups or nodes. An empty config entry alone doesn’t mean you have a working exit node.
Next, select the config, keep rule mode enabled, and start the service. On Android and iOS, approve the VPN permission prompt; on desktop, enable the system proxy if needed. Test a site that should use the proxy, then a site that should connect directly. Once both work, configure TUN, launch at startup, access controls, or DNS overrides one at a time so you can undo changes easily.
When moving from an older client, migrate the subscription URL and custom rules first rather than copying the entire app data directory. Clients store proxy ports, system services, auto-updates, and local overrides differently. Once the new client works, quit the old one and check that the system proxy no longer points to its port. Running both at once can cause port conflicts or intermittent connections.
Troubleshoot installation and connection failures separately. For installation issues, check the OS version, CPU architecture, signature conflicts, and whether the file downloaded completely. For connection issues, check subscription parsing, exit node status, proxy mode, DNS, and traffic routing. If the app opens, reinstalling it usually won’t fix an expired subscription or unreachable node.
DOWNLOAD / FAQs
No. The installer provides the client app; you’ll need to supply your own nodes and subscription. After installation, open the configuration page and import a compatible config from a URL or file. Select it and start the service, then approve the network permission prompt when it appears.
Most recent Android phones use ARM64. Choose ARM for older devices or systems that only support 32-bit apps. If you’re unsure, try the universal build of Clash Meta for Android. Installation issues can also stem from your Android version, a signature conflict with an existing app, or insufficient storage.
Open About This Mac from the Apple menu. If it lists an Apple M-series chip, choose the native ARM64 build; if it lists an Intel processor, choose x64. Some clients currently link both options to the same x64 file, as noted on the download card. Apple Silicon Macs need Rosetta to run these builds.
First check that the download completed, the architecture matches your device, and your system meets the client’s requirements. On Android, a signature mismatch can prevent installing over an app with the same name; export your config before uninstalling anything. If a desktop OS displays a security warning, verify the file’s source and read the prompt instead of disabling system-wide protections.
Usually not. GUI clients provide the configuration, proxy groups, and connection controls, and include or manage the core themselves. Standalone Mihomo builds are mainly for servers, routers, and command-line environments, where you’ll need to set up the config, launch method, and traffic routing rules yourself.
Not as the default choice for a new device. This page keeps archived downloads for Clash for Windows and ClashX Meta for migrating older setups or reproducing compatibility issues. For new devices, choose the featured or recommended client for your platform. Before migrating, back up your subscription URL, rule overrides, and access-control settings.