Client installers · Architecture options · Core downloads
Choose a client for your operating system, then check your processor architecture. GUI clients are best for everyday desktop and mobile use; see the mihomo core for server and router deployments.
mixed-port: 7890
mode: rule
log-level: info
rules:
- MATCH,DIRECTIn Settings, go to “System → About” to check your system type. The desktop installers below are primarily x64 builds.
A good fit for Windows users who want to start by importing a subscription. Download the x64 installer, then choose a configuration and outbound policy after installation.
On your first launch, import a configuration before enabling the system proxy. TUN requires additional system permissions, so enable it only after basic access works. This makes it easier to tell subscription issues apart from virtual network adapter problems.
A good fit for users who need subscription management, overrides, and service mode. Check the active configuration after installation, then decide whether to enable TUN based on your apps’ needs.
This link provides an x64 installer. Windows on ARM users should check compatibility-layer and driver support first; a working interface doesn’t guarantee that virtual network adapter features are supported.
A good fit for users who want a similar experience across devices. Choose the installer for a standard setup, or the archive if you prefer to manage the files yourself.
Extract the archive fully before use; don’t launch the app from inside the archive utility. Before updating, quit the old process and keep your existing data directory and custom configuration.
Another option for a Windows GUI client. Before migrating, export your subscriptions and local rules, then import them into the new client one by one.
Settings directories and override behavior can vary between clients. Keep the old client as a fallback, but run only one proxy service while testing the new app to avoid local port conflicts.
Archived build for legacy migrations and configuration comparisons. For a new installation, choose a client above that’s still maintained.
Older cores may have limited support for newer protocols and configuration fields. Before migrating, note your proxy ports, subscription URL, and custom rules. If a field causes a parsing error, don’t simply delete every reported field to force the app to run.
| Check | Requirements and guidance |
|---|---|
| Operating system | Use a supported 64-bit version of Windows 10 or 11. Check the selected client’s installer for its specific minimum requirements. |
| Processor | The packages on this page are mainly x64 / AMD64; these terms refer to the same architecture here and don’t mean the package is limited to AMD processors. |
| Installation permissions | Configure standard settings and the system proxy as prompted by the client. Installing services, virtual network adapters, and TUN may require administrator approval. |
If your browser works but Store apps don’t, first check whether the app follows the system proxy, then see the Clash UWP loopback guide. Avoid changing the port, DNS, and TUN all at once, or it’ll be difficult to tell what made a difference.
Open “About This Mac”: choose arm64 for an Apple chip or x64 for an Intel processor.
Choose the native installer for your chip. After downloading, open the disk image, move the app to Applications, and launch it from there.
Follow the system prompts to authorize the app on first launch. After importing a configuration, check the proxy group and system proxy status. If you need TUN, follow the client’s prompts for its service or network extension.
A good fit for managing rules and subscription overrides. Both macOS links in the current manifest provide x64 disk images.
This package may require translation on Apple Silicon. If macOS reports an architecture incompatibility, choose a native arm64 client instead; repeatedly changing the file extension won’t help.
A graphical client for macOS. Both current links point to amd64 packages for Intel; Apple Silicon users should check translation support.
When setting up, import a subscription and select a proxy group first. If another proxy tool is running in the background, quit it before checking whether the system proxy points to this client’s listening port.
Archived client for comparing existing setups. Both architecture links currently point to x86_64 packages; for a new installation, see the clients above.
After a macOS upgrade, older client service components may no longer be compatible. When migrating, keep your YAML files and subscription sources; don’t copy the old client’s entire settings directory into the new app.
| Check | Requirements and guidance |
|---|---|
| Operating system version | Use a supported version of macOS. Check the installer and app documentation for each client’s minimum version. |
| Chip architecture | Apple Silicon uses arm64; Intel uses x64 / x86_64. Check the architecture of the actual download. |
| Network permissions | System proxy, background service, and TUN permissions work differently. Review each system prompt carefully. |
If macOS displays a security warning, verify the download source and review the system guidance; disabling security protections globally isn’t recommended. If the app hasn’t launched successfully, troubleshoot installation and architecture first rather than changing your subscription.
Most recent phones use ARM64. For older devices, check the supported app ABIs before choosing ARMv7 or a universal build.
ARM64 installer for importing subscriptions, choosing proxy groups, and managing connections on your phone. Grant VPN connection permission when prompted after installation.
When Android asks for VPN permission, confirm which app is requesting it before allowing access. If the connection drops when the screen turns off, check the app’s background and battery restrictions; reinstalling or repeatedly changing configurations usually isn’t necessary.
Choose ARM64 or ARMv7 to match your device. If you’re unsure, use the universal build, which is typically larger.
After adding a remote configuration, wait for it to download successfully, then set it as active. Subscription download failures and VPN permission issues are separate; check network access and system permissions independently.
Phone installers are available for ARM64 and ARMv7. Choose the one your device supports; ARMv7 refers to the processor architecture, not the Android version.
When switching from another client, disconnect its VPN first. Android typically allows only one active VPN, so the previous VPN disconnecting when the new app starts is expected behavior.
For Android users with configurations in its compatible format. This isn’t a way to import arbitrary Clash YAML as-is, so confirm your subscription format before downloading.
Protocol and rule syntax support depends on the app. If your provider only offers Clash-format configurations, ask whether a compatible option is available; changing the file extension alone won’t convert the format.
| Check | Requirements and guidance |
|---|---|
| Operating system version | Minimum Android versions vary by client. If the installer reports incompatibility, check your Android version and ABI first. |
| Install source | Allow installation permissions only for the app you’re using to open the package, and revoke them in Settings afterward if you wish. |
| App permissions | A system VPN permission is required to connect. For continuous operation, check background restrictions and battery settings. |
If Android says the app wasn’t installed, check the architecture, available storage, and whether its signature conflicts with an existing app. Uninstalling an older app may erase local configurations, so export anything important first.
Check the App Store listing for app details, device compatibility, and updates.
Open the Clash Plus listing in the App Store and check that your device meets the current system requirements before installing. The official website provides product information; follow the in-app guidance to complete initial setup.
After installation, import your own configuration or subscription, then approve the VPN configuration when prompted by iOS. Check the active proxy group before connecting. If importing a subscription fails, make sure the URL is complete; don’t share links containing access credentials publicly.
| Check | Requirements and guidance |
|---|---|
| Device and system | Check the Compatibility section of the App Store listing and confirm your device and iOS version before installing. |
| Install source | Open the app listing through the store link on this page, then let iOS handle installation and future updates. |
| Connection permission | On first use, follow the prompts to add a VPN configuration and check whether another VPN app is already connected. |
The VPN indicator at the top of the screen means a tunnel is active; it doesn’t mean every domain is routed through the proxy. In rule mode, the configuration still determines whether traffic goes direct or through the proxy. When testing, check the target website and which rule matched rather than relying on the status icon alone.
Choose a GUI client for a desktop environment. For remote servers, containers, and routers, see the Mihomo Core tab.
Choose DEB for Debian- and Ubuntu-based systems, or RPM for Fedora and other RPM-based distributions. AMD64 / x86_64 packages are available on this page.
Install using your distribution’s package manager to handle dependencies. If the window won’t launch, check the terminal output for graphics library or WebView errors before troubleshooting proxy settings.
Linux AMD64 DEB installer for users of Debian-based desktop distributions. Check compatibility with your distribution and its dependencies before installing.
The desktop system proxy doesn’t cover every terminal app. Command-line tools may use their own proxy settings, environment variables, or TUN routing. After installation, test browser and terminal access separately.
| Check | Requirements and guidance |
|---|---|
| Distribution | Choose DEB or RPM for your distribution; don’t rename another package format and try to install it. |
| Processor | The GUI packages above are for AMD64. Run uname -m to check your architecture; aarch64 devices can’t run these packages natively. |
| Desktop and permissions | GUI packages require compatible desktop dependencies. TUN also involves a virtual network adapter, routing, and the required permissions. |
If dependencies are missing, follow the error guidance from your distribution’s package manager. Before enabling TUN on a remotely managed machine, keep a fallback connection available and check the routing rules to avoid sending management traffic through an untested proxy.
For users running servers, routers, or self-managed background services. Most users should choose a GUI client.
| System | Processor and format | Core package |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Download ARM64 ZIP |
| macOS | Intel · GZ | Download Intel GZ |
| macOS | Apple Silicon · GZ | Download Apple Silicon 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 |
| Check | Requirements and guidance |
|---|---|
| Target architecture | Check the instruction set, bitness, and router endianness. MIPS isn’t compatible with every MIPS device, so don’t choose based on the processor brand alone. |
| Configuration directory | Set up a readable and writable directory for configuration and runtime data. The account running the core should have only the permissions it needs. |
| Network capabilities | Listening ports, DNS, and TUN have different requirements. Test a standard proxy listener before configuring traffic routing. |
Name the extracted program mihomo and test the configuration from its directory. These commands assume config.yaml is in the current directory; on Windows, use the corresponding executable name.
./mihomo -t -f ./config.yaml
./mihomo -f ./config.yamlThe first command checks the configuration; the second starts the core in the foreground so you can see errors directly. After confirming basic connectivity, configure service management and startup. Don’t expose the external control interface to the public internet; for remote management, configure authentication and restrict access first.
Start with a basic connection you can verify, then expand traffic coverage one step at a time.
Add your subscription URL on the configuration page, wait for the content to download, then set it as the active configuration. Don’t include URLs with access credentials in public screenshots. Keep a recoverable copy before editing local files.
Start in rule mode and check that the proxy group points to a working outbound. Global mode changes how rules are selected; it doesn’t mean every app’s traffic is intercepted. Coverage also depends on the system proxy or TUN.
Open the target website in a browser, then check the connection log for its domain, matched rule, and outbound policy. If it fails, troubleshoot in this order: configuration loading, DNS, rules, and connection errors. Don’t change every setting at once.
Choosing a client, checking your architecture, and preparing to update.
For Windows, macOS, Android, and iOS, start with Clash Plus; for Linux, try Clash Verge Rev. Check your OS and processor architecture before downloading. You’ll still need to import a valid configuration or subscription after installing the client.
ARM64 and x64 use different processor instruction sets, so don’t choose based on the operating system name alone. The Android universal build includes multiple architectures and is usually larger. Some macOS download links currently point to x64 builds. Apple Silicon users should check Rosetta compatibility and choose a build explicitly labeled arm64 whenever available.
The installer provides the client, not a proxy service. Import your own subscription or configuration, select a proxy group, then enable the system proxy or TUN if needed. Test browser access in rule mode first, then adjust other settings as needed.
Keep your subscription URL, local configuration, override rules, and client settings. Quit the old app and related background services before installing. When switching clients, export your configuration first; don’t overwrite the entire data directory. If your subscription contains access credentials, don’t share the exported file publicly.
Both clients are listed here as discontinued archival options, mainly for migrating legacy setups and comparing existing configurations. For a new installation, choose a client that’s still maintained. Older clients may not recognize fields in configurations designed for newer cores.
mihomo is the core that runs configurations, processes rules, and forwards connections. The command-line package doesn’t include a graphical configuration interface, making it suitable for servers, routers, and self-managed services. For everyday desktop or mobile use, a GUI client above is usually more convenient.
Installed but having connection issues? Visit the Help Center. To learn about DNS and virtual network adapter settings, see DNS Configuration and TUN Configuration.