CLIENT / PLATFORM / ARCHITECTURE
Choose your operating system, then your processor architecture. Graphical clients import configurations and manage proxy groups; use the Mihomo core to deploy a service yourself.
# config.yaml · Configuration example
mixed-port: 7890
allow-lan: false
mode: rule
log-level: infoThe installer runs the client; subscriptions and rules come from a configuration file.
PACKAGE INDEX
Available clients are listed separately for each platform. If this is your first install, start with the top recommendation. Before switching clients, back up your subscription URL, local YAML files, and overrides.
The graphical client installers below are for x64 systems. Go to Settings → System → About and check your system type before choosing an installer. Windows on ARM compatibility depends on the OS and client; the system name alone isn’t enough to determine support.
A good starting point for a first Windows install. After installation, add a subscription or import a local configuration, then check your proxy groups and operating mode. System proxy and TUN route traffic differently. For your first connection, test the system proxy before changing other settings.
A good fit if you want to manage configurations and rules in a desktop interface. Subscription updates may replace the subscription file, so put custom DNS, ports, and rules in the override locations supported by the client. Before enabling service mode or TUN, finish the installation and grant any permissions requested by Windows.
A cross-platform graphical client for a consistent configuration workflow across desktop and mobile devices. Here, AMD64 means x86-64; it does not mean the processor must be made by AMD. When migrating, check the system proxy listening port so other apps don’t keep pointing to the old client.
Another option for managing configurations on desktop. After importing an existing configuration, confirm that it is selected, then check that the names referenced by your proxy groups exist. Avoid enabling the system proxy or TUN in two clients at once; they can conflict over routing, DNS, and listening ports, making issues harder to diagnose.
This archived download is provided for reproducing legacy setups and reference during migration. It does not guarantee compatibility with current operating systems or support for new protocols. For a new installation, choose a client listed above. Back up your original configuration and overrides before migrating, then check rules, DNS, and proxy groups one by one. Never overwrite your only backup.
| Check | What to look for | After installation |
|---|---|---|
| System and architecture | Use a supported Windows 10 or 11 x64 system where possible. Check the installer’s requirements for the exact minimum version. | In System Information, check whether the processor is x64-based. |
| Permissions and ports | Running the desktop app and installing a service require different permissions. TUN or service mode may require administrator access. | Make sure the mixed port is available. Exit any older client before testing. |
| Configuration source | Have a subscription URL you’re authorized to use or a local YAML file ready. | Enable the configuration before turning on the system proxy, then check the logs to confirm rules are matching. |
Check your chip under About This Mac: Apple M-series chips are Apple Silicon; Intel Macs use x64. Check both the channel name and the file architecture—some channels listed here currently download the same x64 file.
Separate ARM64 and x64 installers are available. Choose the one that matches your chip. Open the DMG and move the app to Applications, then launch it from there. After importing a configuration, check the system proxy status. Set up TUN using the client’s instructions if you need to route traffic from more apps.
Manage subscriptions, proxy groups, and rules. Both macOS channels currently point to the same x64 DMG; Apple Silicon needs Rosetta 2 to run it. After installation, test the original subscription with minimal changes before adding custom overrides. This makes it easier to tell subscription issues apart from local conflicts.
A good fit if you want a consistent workflow across platforms. Both macOS channels currently point to an AMD64 file, which requires a compatibility layer on Apple Silicon. If the system proxy is on but an app still connects directly, check whether that app respects the system proxy before trying a different installer.
Kept for migrating legacy configurations and existing setups. Both channels currently download an x86_64 file; neither is a dedicated ARM64 build. For new installations, use a maintained client. During migration, save your menu bar proxy settings and local configuration, then remove the old app only after confirming the new client works.
| System | Installer choice | Notes |
|---|---|---|
| Apple Silicon | Choose a native build explicitly labeled ARM64 where available. | Some macOS channels on this page currently provide x64 builds, which require Rosetta 2 to run. |
| Intel | Choose an x64, AMD64, or x86_64 build. | These labels refer to the same processor architecture on this page. They cannot run native ARM64 builds. |
| System permissions | Your macOS version must meet the app’s installation requirements. | Follow system prompts to authorize network services. If macOS blocks an app, verify its source instead of disabling system security protections altogether. |
First check which app architectures your device supports. Most newer phones can use ARM64; older devices may need 32-bit ARM. A 64-bit-capable processor doesn’t necessarily mean the operating system can install every 64-bit app, so check your device’s system environment.
A good starting point for installing on an ARM64 Android device. After importing a configuration, start the connection and allow the system VPN request. This permission routes device traffic; it does not confirm that your subscription works. Check the active configuration, proxy group, and rule mode too. If the connection drops in the background, check battery and background activity restrictions.
Choose from ARM64, ARM, and Universal builds to match your device. If you’re unsure which architecture you need, try Universal; it usually includes more architectures. After importing a configuration, select it before starting the service. Saving a subscription URL to the list alone won’t route any traffic.
Offers a configuration workflow similar to the desktop version. After granting VPN access, check that no other VPN app is running—Android usually allows only one app to use the system VPN interface at a time. To proxy traffic from selected apps, review the client’s per-app settings and note that they work differently from YAML domain rules.
Surfboard uses its own supported configuration format; it is not a drop-in replacement for loading arbitrary Clash YAML files. Before migrating, confirm that your provider offers a compatible format and check whether protocols, policies, and rules are supported. Renaming a file extension does not convert its format.
| Check | Requirement | What to check |
|---|---|---|
| Architecture | ARM64 corresponds to arm64-v8a; 32-bit ARM corresponds to armeabi-v7a. | If Android says the app isn’t compatible, check the architecture, OS version, and signature of any existing app. |
| Install permissions | Grant permission only to the browser or file manager you’re using to install the app. | After installation, revoke permission to install apps from that source if you no longer need it. |
| VPN and background activity | Approve the system VPN request the first time you connect. | Don’t run multiple VPN apps at once. If the connection drops in the background, check battery optimization and auto-start restrictions. |
Install Clash Plus from the App Store. Check the app’s product page for installation requirements, supported devices, and current store information. After installation, import a configuration you’re authorized to use to route connections according to its policies and rules.
Install the app from its App Store page, then add a subscription or import a configuration. When you connect for the first time, follow the iOS prompt to allow a VPN configuration. Return to the app to check the connection and proxy group. If a configuration update fails, first verify that the subscription URL is complete, then check for request or format errors.
Clients on different platforms may use different configuration workflows, so don’t rely on desktop screenshots to find identically named buttons. If you have a YAML file, check the import result and supported fields before connecting. Never post screenshots of a full configuration containing private subscription details in public forums.
| Check | Requirement | Where to check |
|---|---|---|
| Device and OS | Meet the compatibility requirements listed on the App Store product page. | Check compatibility in the App Store and your current iOS version in Settings. |
| Network permission | Allow the client to add a VPN configuration through the iOS system flow. | After granting permission, return to the client, start the connection, and confirm which configuration is active. |
| Subscription setup | Use a complete, active subscription URL or a compatible local configuration. | After importing, check proxy groups and rule targets. Troubleshoot update issues separately from connection issues. |
For desktop use, start with a graphical client. The Linux GUI packages on this page are for AMD64. When choosing DEB or RPM, check your distribution’s package manager, desktop dependencies, and processor architecture. For server or router deployments, see the core section.
A good fit for Linux desktop users who want a graphical interface to manage subscriptions and the system proxy. Debian- and Ubuntu-based systems usually use DEB; Fedora and other RPM-based distributions use RPM. Installing through your distribution’s package manager can help resolve missing dependencies. Don’t force installation by ignoring dependency errors.
For AMD64 desktop systems that use DEB packages. After installation, import your configuration and confirm that the local port is listening, then check that the desktop system proxy is working. Command-line tools may not use desktop proxy settings; configure a proxy or environment variable separately according to each tool’s documentation.
| System | How to check | What to look for |
|---|---|---|
| Processor | uname -m | x86_64 matches the AMD64 graphical installers on this page. These packages won’t run directly on ARM devices. |
| Distribution | cat /etc/os-release | Choose DEB or RPM for your distribution and make sure its desktop dependencies are met. |
| Service permissions | Check the client logs and service status. | TUN requires the appropriate device and network permissions. The system proxy affects only apps that follow that setting. |
For servers, routers, and users who manage service processes themselves. The core has no desktop configuration interface; you’ll need to provide config.yaml, a working directory, a startup method, and network permissions. For everyday desktop or mobile use, choose one of the graphical clients above.
| System | Processor architecture | File type and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · x86-64 command-line core | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · ARM64 command-line core | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ · extract before running the binary | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ · native ARM64 core | Download ARM64 GZ |
| Linux | AMD64 | DEB · for compatible package managers | Download AMD64 DEB |
| Linux | AMD64 | GZ · manage the binary yourself | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM devices | Download ARM64 GZ |
| Linux | ARMv7 | GZ · compatible 32-bit ARM systems | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ · verify endianness and ABI | Download MIPS GZ |
| Item | Requirement |
|---|---|
| Files and directories | Extract GZ files first. On Unix-like systems, make the binary executable. Keep configuration and runtime directories clearly separated so the core doesn’t load a different configuration when started from another location. |
| Network access | Local HTTP/SOCKS proxies, TUN, and transparent proxying each require different network setup. Starting the core successfully does not automatically route router traffic through the proxy. |
| Configuration and permissions | Make sure the configuration is readable, ports can be bound, and the required network permissions are available for TUN. Run the service with the least privileges needed. |
Before deployment, run mihomo -t -f config.yaml to check that the configuration parses, then choose your service startup options. See config.yaml reference for field details and rule order. For router deployment, see Run the mihomo core as an OpenWrt side router.
AFTER INSTALLATION
01 / IMPORT
After installation, prepare your configuration source. Copy the full subscription URL without leading or trailing spaces. Preserve YAML indentation in local files. After importing, check the configuration name and any errors, then set it as the active configuration. Installing a client and successfully fetching a subscription are separate steps.
02 / SELECT
For everyday rule-based routing, start with mode: rule. Make sure every proxy group referenced by your rules exists, then select an available outbound in each group. Global and rule modes work differently; being able to connect in global mode doesn’t prove your routing rules are correct.
03 / VERIFY
On desktop, start by enabling the system proxy; on mobile, approve the VPN permission prompt. Check connection logs for the matched rule, outbound target, and any errors. If something goes wrong, isolate the cause: check configuration updates, DNS resolution, proxy connectivity, and app routing separately instead of changing multiple settings at once.
DOWNLOAD NOTES
For Windows, macOS, Android, and iOS, start with Clash Plus, the first option listed for each platform. On Linux, try Clash Verge Rev. Graphical clients make it easy to import subscriptions, switch proxy groups, and view logs. Choose the Mihomo core if you need to manage the service process yourself.
AMD64 and x64 usually refer to the x86-64 architecture; ARM64 uses a different instruction set. Check your processor type in system information first. The Android Universal build includes multiple architectures, which can help when you’re unsure what your device supports, but the download is usually larger.
Clash Plus offers a dedicated ARM64 installer; choose the Apple Silicon option. Both macOS channels currently listed here for Clash Verge Rev, FlClash, and ClashX Meta point to x64 files. Apple Silicon requires Rosetta 2 to run these builds, so the channel name alone does not mean the download is a native ARM64 build.
Installing a client does not provide a proxy configuration. After installation, import a subscription you’re authorized to use or a YAML file, enable that configuration, choose an available outbound in a proxy group referenced by your rules, then turn on the system proxy or enable TUN if needed. If the connection fails, check the client logs first.
Back up your original configuration and client overrides before importing them into the new client. Common YAML fields can often be reused, but protocol support, TUN settings, DNS behavior, and client-specific fields may differ. After importing, check the logs, proxy group names, and rule targets—not just whether the file was saved.
Clash for Windows and ClashX Meta remain available as archived downloads for reproducing legacy setups and migrating configurations. Their archived status does not guarantee ongoing OS compatibility or bug fixes. For a new installation, choose a current client listed near the top for your platform, and remove the old client only after confirming the new setup works.