CLIENT PACKAGES / MIHOMO CORE
Choose your operating system first, then your architecture. Use a GUI client on desktops; deploy the mihomo core on servers and routers as needed.
Use only one client to manage the system proxy. Before switching clients, turn off the system proxy and TUN in the old one.
Start with Clash Plus for everyday use. Compare other clients if you need configuration overrides or a different desktop workflow. All GUI packages below are x64; x64 does not mean native Windows ARM support.
A GUI client for Windows desktops. Manage configurations, check connection status, and switch proxy policies from the app.
Download the x64 installer and follow the setup wizard, then import an existing subscription. For your first test, use the system proxy. Once the configuration connects, set up TUN permissions and launch-at-startup options if needed.
For desktop users who need to manage mihomo configurations, subscriptions, and overrides. After importing a configuration, check which profile is active before enabling the system proxy.
TUN and service actions may require administrator privileges. If prompted, check the installation location and service status. Don’t run another proxy service at the same time.
A cross-platform GUI client. On Windows, choose the installer or zip archive; the installer is recommended for most setups.
Extract the archive fully to a permanent folder before launching the app. Don’t run it from the archive preview. Before upgrading, note where your configuration is stored so you can find it if the app folder moves.
An alternative desktop interface for managing Clash. For users who prefer a different way to organize configurations and navigate the app. Windows x64 installer available here.
When switching from another client, export the configuration file rather than copying the entire app folder. After importing it, check proxy group references, listening ports, and override rules.
Archived client kept for migrating existing setups and comparing legacy configurations. For new installations, choose a maintained client listed above.
Older cores may not support newer configuration fields or protocols. If you encounter configuration errors, consider switching clients. Don’t remove security-related settings or weaken system protections just to keep an old app running.
| Check | Requirement | How to check |
|---|---|---|
| Operating system | Use a supported version of Windows 10 or 11; check the installer for its exact minimum requirements | Settings → System → About |
| CPU architecture | Desktop packages here are x64 and won’t work on 32-bit systems | Check system type and processor type |
| Permissions and ports | Standard proxy and TUN have different permission requirements; listening ports must be available | Check the logs after launch, then test the system proxy |
Check your chip in About This Mac. Apple Silicon uses arm64; Intel uses x64. Channel names don’t guarantee the file architecture, so the buttons below clearly label channels that currently point to x64 files.
Separate disk images are available for Apple Silicon and Intel. Download the build for your chip, open the DMG, move the app to Applications, and launch it from there.
Import a configuration first and confirm that its proxy policies work. System proxy settings affect apps that respect them. For broader traffic routing, review the TUN permissions and routing requirements.
For Mac users who need subscription management and configuration overrides. Both Mac channels currently point to x64 images; Apple Silicon users should confirm that system translation support is available.
After migrating a configuration, check what’s actually active, then verify the ports and system proxy. App settings and the original subscription are separate layers; save custom overrides before updating the subscription.
For users who want a similar workflow across devices. The current Mac installer is amd64 (x64); the Apple Silicon channel points to the same file.
After installation, make sure the proxy address in macOS network settings matches the client’s listening address. Before quitting the app, turn off the system proxy to avoid leaving a local port with no app listening on it.
Kept for existing menu bar workflows and migrating legacy configurations. This archived client isn’t recommended for new setups, and may not support newer mihomo fields.
The current listing is an x86_64 image, and both chip channels point to the same file. Apple Silicon users need a working translation environment; this is not a native arm64 build.
| Check | Requirement | How to check |
|---|---|---|
| Chip | Choose arm64 for Apple Silicon and x64 for Intel | Apple menu → About This Mac |
| Operating system version | Use a macOS version supported by the current client build; check compatibility before installing | About This Mac → macOS version |
| x64 translation | Apple Silicon needs translation support to run x64 files | Check the actual file architecture and any system launch warnings |
Most recent phones use arm64. Older devices may need armv7. If you’re unsure, check your system and processor information or choose a universal package. You’ll also need to grant VPN permission after installation.
Our recommended Android GUI client, with an arm64-v8a package. Import subscriptions and choose proxy policies from the app.
After installing, import a configuration, start a connection, and approve the system VPN prompt. If the connection drops when the screen locks, check background app restrictions before increasing health-check frequency.
Available in arm64, 32-bit ARM, and universal packages. Choose the package that matches your device when you know its architecture; the universal package is for broader device compatibility.
After importing a configuration, check the active profile and proxy group selection. VPN mode changes how traffic flows on your device. If another VPN app is running, disconnect it before testing this setup.
Available for arm64-v8a and armeabi-v7a. These packages target different processor environments. A 32-bit system may still need the 32-bit package, even if the chip supports 64-bit.
Check the configuration and DNS settings before connecting. For long-running background use, allow the app to keep running in your phone’s system settings. To troubleshoot battery drain, check the log level and check interval before changing traffic routing.
An Android universal package for users with a compatible configuration. Surfboard uses a different configuration format from Clash YAML, so don’t assume the same subscription URL will work in both.
Before installing, check which format your subscription service provides. If you already have a Clash configuration, use one of the clients above. If migrating, check how each rule and policy maps across formats.
| Check | Requirement | Notes |
|---|---|---|
| Architecture and version | Choose by device ABI; check the package manager’s prompt for the minimum Android version | If installation fails, check the architecture and Android version first |
| Install permission | Allow the browser or file manager you’re using to install apps | You can revoke this permission in system settings afterward |
| Runtime permissions | Approve VPN access when connecting; check background restrictions for continuous use | Enable only the VPN connection you need |
Install Clash Plus from the App Store. Check system compatibility on the store page first. After installation, import your own configuration and follow the system prompts to add a VPN configuration.
Check the App Store listing for supported iPhone and iPad models, system requirements, and app details. Installing the app and configuring a proxy are separate steps; installation alone doesn’t provide a working proxy connection.
Add a subscription or configuration you’re authorized to use, then check the selected policies. Approve the system prompt when connecting. If access fails, check that the configuration loaded before troubleshooting nodes and DNS—reinstalling the app repeatedly won’t help.
Client website: clashplus.io. Visit the website for product information; use the App Store button below to install the app.
| Check | Requirement | How to check |
|---|---|---|
| Supported devices | Check the iPhone and iPad compatibility listed on the App Store page | App Store → Compatibility |
| Operating system version | Meet the minimum system requirements shown in the App Store | Settings → General → About |
| Connection setup | Prepare a compatible configuration and allow the app to add a VPN configuration | After importing, check the selected policy and connection status |
Use deb packages on Debian and Ubuntu; use rpm on Fedora and RHEL-based distributions. The desktop packages below are for amd64 / x86_64. For ARM servers and routers, see the Mihomo Core tab.
Recommended for Linux desktops. Manage configurations, subscriptions, and proxy modes in the GUI. Choose deb or rpm for your distribution, and let the package manager handle dependencies instead of copying installed files by hand.
After installation, launch the app from your desktop menu, import a configuration, and check the core logs. Verify the local listener and system proxy before enabling TUN. Check service permissions, routing, and DNS separately to narrow down issues.
Linux amd64 deb package for Debian-based desktops. A good fit if you want one GUI for managing subscriptions and proxy policies.
Download the package, then install it with your package manager from the directory where it’s saved. If dependencies are missing, start by reading the error message. When switching from another client, check that it’s no longer listening in the background and that your desktop proxy settings don’t retain an old address.
| Check | Requirement | How to check |
|---|---|---|
| Distribution | deb packages are for Debian-based systems; rpm packages are for compatible RPM-based distributions | cat /etc/os-release |
| Architecture | Packages in this section target amd64 / x86_64 | uname -m |
| Desktop environment | Requires a graphical session and the runtime dependencies declared by the package; tray behavior varies by desktop environment | Check package dependencies and the application startup log |
| TUN | Requires an available TUN device, suitable network permissions, and routing configuration | ls -l /dev/net/tun |
For servers, routers, and users who manage services themselves. The core has no desktop configuration GUI; desktop users should choose a GUI client. Before downloading, check the operating system, CPU architecture, and package format.
| System | Architecture and format | Deployment notes | Download |
|---|---|---|---|
| Windows | AMD64 · zip | For 64-bit x86 systems; extract and launch from a terminal | Download AMD64 zip |
| Windows | ARM64 · zip | Native Windows ARM core | Download ARM64 zip |
| macOS | Intel / amd64 · gz | For Darwin x86_64 systems | Download Intel gz |
| macOS | Apple Silicon / arm64 · gz | Native Darwin ARM64 core | Download Apple Silicon gz |
| Linux | AMD64 · deb | For Debian-based x86_64 systems; install with a package manager | Download AMD64 deb |
| Linux | AMD64 · gz | Place the binary and configure the service yourself | Download AMD64 gz |
| Linux | ARM64 · gz | For 64-bit ARM servers and compatible devices | Download ARM64 gz |
| Linux | ARMv7 · gz | For 32-bit ARMv7 systems; check the system ABI | Download ARMv7 gz |
| Linux | MIPS softfloat · gz | Only for devices with a matching architecture, byte order, and ABI | Download MIPS softfloat gz |
Prepare a configuration before starting the service. The usual Linux configuration directory is ~/.config/mihomo/; put config.yaml there. Use -d to specify the directory explicitly and avoid path issues when the working directory changes.
mkdir -p ~/.config/mihomo
mihomo -v
mihomo -t -d ~/.config/mihomoThese commands assume the executable is in PATH and the configuration file is in place. Passing a syntax check only means the configuration can be parsed; it doesn’t confirm that nodes, DNS, or routing work.
A compressed file isn’t a system service. After extracting the gz file, set execute permissions, choose where to keep the binary, and configure its startup arguments. systemd user services and system services have different file paths, permissions, and lifecycles—don’t mix their commands.
TUN requires additional network permissions and device support. First verify port listening with a standard proxy, then configure transparent proxying and startup at boot. Keep the control interface bound to loopback where possible; exposing it to your LAN without access controls is unsafe.
View core configuration and field referenceInstall the app first, import a configuration next, and route traffic last. A successful installer launch only shows that the app is basically compatible with your system. Proxy access also depends on configuration format, subscription validity, policy selection, and your network. Don’t change ports, DNS, routing, and operation mode all at once on first launch; change one thing at a time to make issues easier to isolate.
mixed-port value and listening address. On Linux, run ss -lntp to check the port. Make sure your browser’s proxy settings match the listener. Command-line tools may need their own proxy options or environment variables.Before upgrading, keep your subscription source, custom rules, and overrides. Backups may contain credentials, so store them in a secure location and remove sensitive details before sharing logs. Once the new client works, remove the old app and startup entries to prevent background services from occupying ports.
Check your operating system, architecture, and package format before troubleshooting runtime settings.
For desktops and phones, choose a GUI client to import configurations, select proxy groups, and view logs. On Linux desktops, try Clash Verge Rev or FlClash. Choose the mihomo core for servers, routers, or devices where you manage systemd services yourself; the core requires a configuration file and a startup method.
amd64 and x64 usually refer to the same 64-bit x86 architecture, not just AMD processors. arm64 is 64-bit ARM; armv7 is usually 32-bit ARM. On Linux, run uname -m to check the architecture. For routers, also check the firmware ABI and floating-point support—don’t choose a package based only on the processor brand.
Debian, Ubuntu, and their derivatives typically use deb packages; Fedora and RHEL-based distributions typically use rpm. Check the CPU architecture and desktop dependencies too. The Linux GUI packages on this page are for amd64 or x86_64. Don’t install them on ARM devices; see the Mihomo Core tab for deployment options.
Check the architecture of the actual file. Both Mac channels listed here for Clash Verge Rev, FlClash, and ClashX Meta currently point to x64 files, which require system-supported translation on Apple Silicon. Clash Plus has a separate arm64 build. The mihomo core section also distinguishes Darwin arm64 from amd64.
The client installer doesn’t include a working proxy subscription. Import a configuration you’re authorized to use, select an available policy, then enable the system proxy or TUN if needed. Make sure mixed-port matches the port set in your app. If access still fails, check the core logs, DNS, and rule matches in that order.
Export your current configuration first, and note the subscription source, override rules, and actual configuration directory. Store backups securely because they may contain sensitive information. Quit the old client before installing the update to avoid multiple processes competing for the same listening port. After updating, check configuration parsing, system proxy settings, and TUN permissions before restoring background operation.