Client Installers · Choose a Platform and Architecture
Choose your operating system, then check your processor architecture. Graphical clients manage subscriptions and routing; the Mihomo core is for self-hosted network services.
CLIENT PACKAGES
Switch platforms to see the full list. For command-line deployments, go to the Mihomo Core.
Check System type under Settings > System > About. The desktop installers below are primarily x64. On Windows on ARM, check app emulation support and client compatibility; x64 is not the same as native ARM64.
A good place to start with your first setup. After installation, import a subscription, select its configuration, then choose a rule mode and outbound policy. Test your browser through the system proxy first. Once rules behave as expected, consider routing traffic from other apps. When switching clients, check the proxy port again instead of reusing the old system settings blindly.
clashplus.ioA good fit if you want a desktop interface for subscriptions, rules, connections, and logs. Import your existing configuration and confirm it's active, then check the system proxy status. To use TUN or service mode, follow the client's permission prompts. For ordinary web browsing, start with the system proxy—it makes installation issues easier to distinguish from configuration issues.
Choose FlClash if you want a similar workflow across different devices. The Windows download is an AMD64 installer; AMD64 and x64 refer to the same general architecture family. After launching it, check the configuration, mode, and which apps are routed. Importing a configuration doesn't automatically turn on the system proxy.
Another graphical client for managing configurations and proxy policies on Windows. Before migrating, keep your local overrides, rule-set references, and subscription update method in mind; different clients may store these settings in different places. After importing, check the connection details to verify your outbound route rather than relying only on the status toggle.
This archived installer is available for restoring older setups or migrating configurations, but isn't recommended for a first install. Its older core may not recognize newer protocols or configuration fields, and system updates can cause compatibility issues. When moving to a maintained client, export your configuration and review proxy groups, rules, and DNS one by one. Don't copy the entire program folder.
| Check | What to check | What to do |
|---|---|---|
| Windows version | Use a Windows version that is still supported by Microsoft. Check the installer for its specific minimum version. | A downloadable file isn't proof that it will work on an older system. |
| Processor | This page primarily offers x64 / AMD64 builds. | 32-bit Windows can't run x64 apps. For ARM devices, check app emulation compatibility separately. |
| Permissions | The system proxy and TUN have different permission requirements. | Grant service-installation or virtual network adapter permissions only if you need those features. |
Open About This Mac from the Apple menu to check whether your Mac has an Apple Silicon chip or an Intel processor. Once the DMG finishes downloading, install the app as prompted. If macOS displays a security warning on first launch, review the source and warning instead of disabling system protection outright.
Separate installers are available for Apple Silicon and Intel. Choose the file for your processor, then import an existing subscription. Quit other proxy apps before installing a new client, and make sure your system network settings don't contain an outdated proxy address. If your browser works but other apps aren't routed, check whether they use the system proxy before setting up TUN.
clashplus.ioManage desktop subscriptions, inspect rules, and troubleshoot connections. Both architecture links currently point to x64 DMGs. Apple Silicon users should check Rosetta and client compatibility first. After launching, confirm your configuration is active. If the client requests service permissions, follow its authorization steps; a permission error doesn't mean your subscription is invalid.
Manage subscriptions, policies, and connection modes. The current macOS file is labeled AMD64, meaning Intel x64—not native ARM64. Apple Silicon users should check translation support. When migrating a mobile configuration, also review desktop proxy ports, DNS, and app-routing settings; system-specific options won't automatically work on every device.
The archived build may help restore an existing menu bar workflow or migrate an older configuration. Since it's no longer maintained, don't assume it supports newer systems or protocols. Both links currently point to x86_64 files. For long-term use, consider a maintained client, then remove old login items, proxy settings, and background processes after migration.
| Check | What to check | What to do |
|---|---|---|
| Windows version | Minimum macOS versions vary by app. | Check the app's installation prompts and release requirements; matching the processor architecture doesn't guarantee system compatibility. |
| Chip type | Apple Silicon uses ARM64; Intel uses x64. | Check the actual filename before downloading. Intel apps generally need Rosetta on Apple Silicon. |
| Proxy permissions | System proxy, background services, and network extensions require separate permissions. | Enable only what you need, then test a regular browser connection after installation. |
Most recent phones use ARM64, but some devices still run apps in a 32-bit environment. If installation fails, check the system-supported ABI, Android version, and existing app signature instead of repeatedly downloading the same incompatible package.
ARM64 installer available. After installing, import a subscription and confirm the configuration is active. On the first connection, allow the VPN request when prompted. Android usually allows only one VPN app to use the VPN slot at a time. If the connection drops immediately, close other VPN apps and check background activity restrictions.
clashplus.ioChoose an ARM64, ARM, or universal build for your device. If your phone supports ARM64, use that build; if you're unsure, try the universal package, provided your system meets the client's requirements. After importing, select the configuration and start the connection. If it drops when the screen locks, check battery optimization and background permissions rather than changing rules.
ARM64 and 32-bit ARM APKs are available. Keep your existing configuration before installing. If an update fails, check that the signature and installation source match before uninstalling and risking data loss. After connecting, review app routing and rules to make sure the apps you want aren't excluded from the VPN.
A fit for users with an existing Surfboard-compatible configuration. Surfboard uses a different configuration format from Clash, so don't assume every Clash YAML subscription can be imported directly. Before downloading, confirm that your subscription provider supports this client and check its protocol and rule fields. If you only have a Clash configuration, use one of the clients above that can read it.
| Check | What to check | What to do |
|---|---|---|
| System and ABI | Check the install prompt for the minimum Android version and your system's supported app ABI for the architecture. | An ARM64 processor doesn't necessarily mean the device has a 64-bit app environment. |
| Installation permissions | Install the APK through your browser or file manager. | Allow installs only from the source you're using, then revoke permission if you no longer need it. |
| Background connections | The app needs system VPN permission and appropriate background activity permissions. | Check for conflicts with other VPN apps and battery restrictions when the screen is locked. |
Install Clash Plus from the App Store. Check the store listing for system compatibility, then import a subscription and add the VPN configuration when prompted. For your first connection, test a single destination. Once the configuration and rules work, adjust other options as needed.
Install and update through the App Store listing; check the store for system requirements. After installation, prepare a subscription or configuration file supported by the client, choose a policy and rule mode, then authorize the VPN connection. If your device already has other VPN configurations, check which one is active so you don't mistake another app's connection status for Clash Plus's.
clashplus.io| Check | What to check | What to do |
|---|---|---|
| System compatibility | Check the system requirements in the App Store listing. | Check your device's current iOS version before installing. |
| Connection permissions | The client needs permission to add and use a system VPN configuration. | Confirm the app name in the system prompt before granting permission. |
| Subscription configuration | You'll need a valid subscription with fields supported by the client. | After importing, check that the configuration is active and verify the selected policy and rule mode. |
Check your distribution's package format, then confirm the CPU architecture. The graphical clients below are for desktop environments. For servers or routers managed over SSH, use the command-line files in the core section.
AMD64 DEB and x86_64 RPM packages are available. Debian- and Ubuntu-based distributions typically use DEB; distributions with RPM package management use RPM. Let the package manager handle dependencies. After installation, launch the client from your desktop and check the subscription and system proxy. Terminal apps may not use the desktop proxy, so configure proxy environment variables separately.
This AMD64 DEB package is for Debian-based desktop environments that meet the app's dependencies. Don't install an AMD64 package directly on an ARM64 host or change the file extension to try to convert the package. Before enabling TUN, check virtual network adapter permissions, routing, and DNS. Get a standard proxy connection working first, then expand the apps you route.
| Check | What to check | What to do |
|---|---|---|
| System architecture | uname -m returns x86_64 for AMD64 packages. | Use a compatible core build on ARM devices; don't force-install a desktop AMD64 package. |
| Desktop and dependencies | Graphical clients require a working desktop session and the libraries provided by your distribution. | Install through your package manager and review any missing dependency warnings. |
| Routing traffic | The desktop proxy may not cover command-line apps or services. | Set proxy variables per process, or configure TUN after understanding its routing effects. |
MIHOMO CORE
For users managing servers, routers, or their own services. The core reads configurations and handles connections but doesn't include a full desktop interface for managing subscriptions. Most users should choose a graphical client above.
Check the architecture on the device that will actually run the core, not the computer you're using to download it. On Linux, x86_64 corresponds to AMD64, while aarch64 usually means ARM64. For ARMv7 and MIPS, also check the firmware, instruction set, and floating-point support. If your router has limited storage or permissions, read the firmware's package documentation first.
Extract ZIP files before use. GZ files are usually compressed single executables; after extracting, set execute permissions and configure the configuration directory. Install DEB packages with a package manager; check the package contents to see whether it registers a service. Don't treat GZ as a desktop installer or overwrite a core that's currently running.
| Target system | Processor architecture | File 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 |
AFTER INSTALLATION
Work through these steps in order to distinguish download, subscription, and connection issues.
Import a subscription that supports the Clash configuration format, wait for it to finish downloading, then select the configuration. A saved subscription that isn't activated may leave the core using old settings. If an update fails, check whether the issue is with the URL, server response, or configuration parsing. Don't post subscription links in public discussions or screenshots.
For everyday routing, start with rule mode. Make sure the proxy group has a working option, then enable the system proxy. Global mode only changes the outbound route for connections the client handles—it doesn't automatically send every app through the client. If your browser connects but other apps don't, check whether they use the system proxy before considering TUN. Change one setting at a time.
Back up your configuration and local overrides before updating, then quit the old client and install the new package. Check the system proxy, startup settings, background services, and virtual network adapter separately; uninstalling the app may not remove them. Delete the old directory only after verifying the new client works. If something goes wrong, use the logs to pinpoint whether the issue is configuration parsing, DNS resolution, or the destination connection.
DOWNLOAD QUESTIONS
Start with Clash Plus on Windows, macOS, Android, or iOS; try Clash Verge Rev on Linux. Choose a client to manage subscriptions and rules with a graphical interface—don't download only the Mihomo core. A client download doesn't include a subscription, so you'll need to provide a working configuration separately.
On Windows, check System type under Settings > System > About. On macOS, check the chip or processor in About This Mac. On Android, check the device processor and supported app architectures. On Linux, run uname -m. x86_64 corresponds to x64 or AMD64; aarch64 usually means ARM64. Don't choose based on the device brand alone.
For some clients in this list, both macOS architecture links currently point to the same x64 installer. Check the actual file architecture for Clash Verge Rev, FlClash, and archived ClashX Meta. Apple Silicon generally needs Rosetta to run Intel apps, but compatibility still depends on the client. For a native ARM64 build, choose a link explicitly labeled ARM64.
Archived installers are available for restoring older setups and comparing configurations. Since development has stopped, don't assume support for newer protocols, system changes, or core features. For a fresh install, choose a maintained client. Back up your configuration before migrating, then review proxy groups, rules, and DNS settings.
First, make sure your internet connection works with the proxy disabled. Then import a valid subscription, select its configuration, choose rule mode and a working policy, and enable the system proxy. Set up TUN only if needed. Subscription failures, node timeouts, and DNS errors occur at different stages; use the logs to troubleshoot each one.
Keep your subscription source, configuration files, local override rules, and any essential settings. Quit the old client before installing a new build for the same architecture. Don't enable the system proxy or TUN in two clients at once. After confirming the new client imports your configuration and routes traffic correctly, remove the old setup. Remove subscription URLs, tokens, and other personal information before sharing logs.