CLIENT PACKAGES / MIHOMO CORE
Choose your operating system first, then check your processor architecture. Use a graphical client on desktop and mobile; choose the Mihomo core for servers and routers.
Installers do not include proxy nodes or service. After installation, import a valid subscription or local configuration.
BEFORE INSTALL
Use the current filename to identify the package architecture. Client version labels and installer versions may be maintained separately upstream, so don’t rely on the version number alone to determine compatibility.
PLATFORM SHELF
Use the arrow keys to switch tabs. Share a link to a system section to open that category directly. Read the architecture notes for your platform before downloading.
This section offers x64 graphical clients. Check your system type under Settings → System → About. Most Intel and AMD desktop PCs use the x64 package. On ARM devices, first confirm that your system supports x64 apps; these installers are not native ARM64 packages.
A good choice for first-time setup and everyday use. After installing, import a subscription or configuration file, then confirm it’s enabled and select a proxy group. Test browser traffic through the system proxy before setting up network interception features that require administrator access.
clashplus.ioFor desktop users who need to manage multiple configurations, rule overrides, and system integration. Check the service status after installation. Before enabling TUN, confirm service permissions and test traffic routing. Review old configuration syntax one item at a time, and don’t run another proxy client at the same time.
A graphical interface for configuring mihomo, with a central view of proxies, connections, and logs. AMD64 is another name for the 64-bit x86 architecture and works on common Intel x64 systems too; it isn’t limited to AMD processors.
An alternative desktop client for configuration management and proxy policy changes. After installation, check compatibility between the current core and your subscription. Support for newer protocols or configuration fields depends on the core; a successful import in the interface doesn’t guarantee the configuration will work fully.
An archived download for legacy setups, migration, and compatibility checks. For a new installation, use a maintained client listed above. Core settings, service options, and scripts from older configurations may not carry over as-is. Save the original files before migrating, then test the new setup separately.
| Check | Requirements and guidance |
|---|---|
| System and architecture | Packages in this section are x64 / AMD64. Check the current client release notes and installer prompts for the minimum supported Windows version. |
| Permissions | For standard configuration and system proxy setup, follow the usual user workflow. Installing a service or enabling TUN may require administrator approval. |
| Existing setup | Quit the old client and make sure its proxy port is free. Save your configuration before uninstalling, then check that the system proxy points to the new app after installation. |
Installing the app doesn’t mean it’s routing your traffic. First confirm that the core starts successfully, then enable the system proxy and check browser requests in the connection list. Verify separately whether your terminal uses the system proxy.
Check About This Mac to see whether your device has an Apple Silicon chip or an Intel processor. After downloading a DMG, open the disk image and move the app to your Applications folder. When migrating an existing setup, quit the old process first to prevent menu bar controls and system proxy settings from conflicting.
For a first installation, choose the native architecture for your chip. After importing a configuration, check the selected proxy group and enable the system proxy if needed. Before routing more traffic, grant the required system permissions and confirm that local network, work network, and development services remain accessible.
clashplus.ioFor users who need desktop configuration management, rule overrides, and service integration. Move the app to a permanent location before opening it; don’t run it from the disk image. After enabling the service, check permissions and core logs. If something goes wrong, disable TUN and test with the system proxy alone.
A graphical way to manage mihomo configurations and proxy policies. AMD64 and x64 refer to the same architecture here. After updating, confirm the configuration path and selection, then check DNS and connection logs so you don’t mistake a disabled configuration for an unavailable node.
For compatibility and migration from existing menu bar workflows. This client is no longer maintained, so it’s not recommended for new setups. Save your configuration, switch to a maintained client, and recheck configuration support, proxy ports, and startup settings.
| Check | Requirements and guidance |
|---|---|
| Chip architecture | Native Apple Silicon packages are labeled ARM64; Intel packages are labeled x64, AMD64, or x86_64. Compatibility mode is not a substitute for checking the native architecture. |
| System compatibility | Minimum macOS versions vary by client; check the current release notes. If you use an x64 package on Apple Silicon, confirm Rosetta compatibility. |
| App and permissions | Move the app to your Applications folder before opening it. Grant permissions for the requested features when prompted; don’t disable system security globally just to get past a launch warning. |
Most recent phones use ARM64, but a 64-bit-capable processor doesn’t guarantee the system runs a 64-bit app environment. Check your device and system architecture first; older devices may need the ARMv7 package. If VPN access is requested, make sure the prompt comes from the client you just installed before continuing.
Manage configurations and proxy policies on your phone. After installing the APK, import a subscription and grant VPN access, then check the connection status. Confirm it works with the screen on before changing background settings, so battery restrictions aren’t mistaken for node timeouts.
clashplus.ioFor users who want to manage Clash Meta configurations on Android. Choose the package for your architecture, or consider the universal package if you’re unsure. After importing, confirm the configuration is selected and check the proxy mode, proxy groups, and per-app routing. Seeing the subscription name alone isn’t enough.
Manage configurations, proxies, and logs on your phone. Before updating, save your subscription source and local overrides; afterward, confirm the active configuration. If the connection drops in the background, check battery optimization and background permissions before running repeated speed tests or reinstalling the client.
An alternative for Android. Surfboard uses its own supported configuration format; don’t assume it can import every Clash YAML file unchanged. Check whether your subscription service offers a compatible format, review any import errors, and use the appropriate configuration if needed.
| Check | Requirements and guidance |
|---|---|
| App architecture | ARM64 corresponds to arm64-v8a, and ARMv7 to armeabi-v7a. Check the installer and release notes to confirm whether the universal package supports your device. |
| System and installation | Make sure your system version meets the selected client’s requirements. Grant permission to install apps only for the source you’re using. |
| VPN and background activity | Grant VPN access and make sure another VPN service isn’t competing for the connection. Adjust background limits in your device manufacturer’s settings. |
The VPN icon only shows that the system has established a local traffic tunnel; it doesn’t mean every destination is reachable. Check your subscription, selected proxy group, and rule matches too. When troubleshooting battery drain, consider background activity, speed test frequency, and subscription update frequency.
Install Clash Plus from the App Store. Import a valid configuration after installation, then add the VPN configuration when prompted. Verify the connection with the default routing settings before adjusting rules and proxy groups for your needs.
Check the App Store listing for current system compatibility and release details. After installation, import a subscription and confirm the configuration parses correctly, then select a proxy policy. If the app shows as connected but access fails, check node availability and rule routing separately; don’t rely on the status icon alone.
After switching between Wi-Fi and cellular data, check whether the connection recovers. Updating a subscription changes the configuration, not the client app. Save the working configuration before editing rules so you can restore it quickly if something breaks.
clashplus.io| Check | Requirements and guidance |
|---|---|
| System compatibility | Check the current App Store listing for the minimum iOS version and supported devices. |
| Configuration source | Use a valid subscription or supported local configuration. Installing a client doesn’t create usable proxy nodes. |
| Network permissions | Add the VPN configuration when prompted by iOS. If you use another VPN app, check for service conflicts first. |
Use a graphical client on desktop. These packages are for AMD64 / x86_64: choose DEB for Ubuntu, Debian, and related distributions; choose RPM for distributions that use RPM package management. For headless servers, use the Mihomo core and manage the service yourself.
Manage configurations, proxy groups, and proxy settings on a Linux desktop. Install with your distribution’s package manager to handle dependencies. TUN also depends on device permissions, service configuration, and routing; a successful installation doesn’t mean system traffic is being routed.
A graphical alternative for Linux desktops, with configuration and log views. Before installation, confirm your distribution supports DEB packages and meets the runtime dependencies. Browsers, desktop apps, and terminals may use different proxy settings, so test them separately rather than treating one app’s result as the system-wide status.
| Check | Requirements and guidance |
|---|---|
| Architecture | Run uname -m to check. The output x86_64 usually matches the AMD64 packages in this section; don’t use an AMD64 package on aarch64. |
| Package format | DEB and RPM are for different package management systems; they aren’t interchangeable file extensions. |
| Dependencies and permissions | A supported desktop environment and the client’s runtime dependencies are required. Configure permissions for services and TUN separately, as needed. |
Terminal apps often require proxy environment variables to be configured separately. On a headless server, test the configuration in the foreground before setting up systemd. If the service fails to start, avoid repeatedly changing graphical client settings.
HEADLESS / SERVER / ROUTER
Mihomo handles protocols, rule matching, and network forwarding; it isn’t a client with a configuration management interface. This section is for server and router deployments and users who want to run it as a standalone process. Most desktop and mobile users should choose one of the graphical clients above.
| System | Architecture | Format and use | Package |
|---|---|---|---|
| Windows | AMD64 | ZIP · x64 command-line | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · ARM64 command-line | Download ARM64 ZIP |
| macOS | Intel AMD64 | GZ · Intel processors | Download Intel GZ |
| macOS | Apple Silicon ARM64 | GZ · Apple Silicon | Download ARM64 GZ |
| Linux | AMD64 | DEB · Debian-based package management | Download AMD64 DEB |
| Linux | AMD64 | GZ · Standalone executable | Download AMD64 GZ |
| Linux | ARM64 | GZ · aarch64 systems | Download ARM64 GZ |
| Linux | ARMv7 | GZ · ARMv7 systems | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ · Soft-float devices | Download MIPS GZ |
| Check | Deployment requirements |
|---|---|
| Hardware compatibility | Check the processor architecture, endianness, and supported instructions. For MIPS devices, verify the floating-point ABI too; don’t choose a package based on the device model alone. |
| File format | ZIP is a compressed archive; GZ usually compresses a single executable, which may need to be made executable after extraction. Install DEB packages with a package manager. |
| Networking | TUN requires system support for virtual network interfaces and the necessary permissions. On routers, also check existing firewall rules, DNS services, and network interface settings. |
If startup fails, check the logs for configuration parsing errors, port conflicts, and permission issues. Don’t change DNS, routing, and proxy groups all at once. Keep a working baseline and adjust one setting at a time.
INSTALL → IMPORT → VERIFY
The installer only makes the client runnable. To connect, you also need a valid configuration, working nodes, and the right proxy settings. After importing a subscription, check for parsing errors and make sure the newly imported configuration is active—not an old test file.
Next, select a proxy group and test a specific request through the system proxy or mobile VPN. Once it works, configure TUN, per-app routing, and automatic updates if needed. If something goes wrong, note your system, client name, package architecture, and exact error, then follow the relevant steps on the Troubleshooting page.
This is a checklist, not a report of your device’s current connection status.
PACKAGE QUESTIONS
Check the package format and runtime environment first, then troubleshoot the connection. Expand a question below to see the answer.
Start with a graphical client. It provides configuration import, proxy group selection, logs, and system integration. The Mihomo core is better suited to server or router users who can manage configuration files, processes, and network permissions themselves.
The core doesn’t replace a graphical client’s configuration workflow. For desktop users who just need to import a subscription and choose a proxy, a client makes it easier to confirm that each step is complete.
Check your processor architecture in system information first. Intel and AMD desktop systems typically use x64 or AMD64; choose an ARM64 package for devices that support ARM64 apps. If you can’t confirm your Android architecture, consider the client’s universal package. Some macOS Apple Silicon download links currently point to x64 files; check Rosetta compatibility before using them.
Architecture labels describe the target system, not a performance tier. Check both the button description and filename before downloading. If your system says the app is incompatible, check the architecture and system version before troubleshooting your subscription.
The installer contains only the client. After installation, import a valid configuration or subscription, enable it, and select a proxy group. Then configure the system proxy or TUN. Check node availability, whether requests reach the core, and which rules match.
Seeing nodes in a list doesn’t mean they’re usable, and a successful speed test doesn’t mean every site will be routed as expected. Test one request and check the connection logs. If your browser works but your terminal connects directly, check the terminal’s proxy settings first.
Save your subscription source, local configuration, rule overrides, and proxy group selections. Stop the old client before updating to prevent two processes from competing for proxy ports or a virtual network interface. After updating, make sure the configuration is still enabled and test the proxy and DNS separately.
Remote subscription updates may overwrite changes. Save custom rules using the client’s supported override feature. When switching clients, check whether their override methods are compatible. Don’t delete the old setup after copying just one configuration file.
If a download is interrupted, download the complete installer again instead of running an incomplete file. For an architecture mismatch, check your system type, processor, and filename. On Apple Silicon, macOS x64 packages also require Rosetta compatibility. Note the system error, then follow the steps for that symptom on the Troubleshooting page.
Installation can also fail because of low disk space, missing system dependencies, or a process left running. Keep the exact error message and distinguish between “installer won’t run,” “app won’t start,” and “core failed to start”—each requires different troubleshooting steps.
Archived downloads for Clash for Windows and ClashX Meta are available mainly for migrating existing setups and checking compatibility. For a new installation, choose a maintained client. During migration, recheck core support, configuration syntax, and system proxy settings.
An archived package can help you reproduce an old setup, but it won’t gain the capabilities of a newer core. If your subscription uses protocols or fields that the old core doesn’t support, switch to a compatible client instead of repeatedly importing the same configuration.