Clash Plus
A good fit if you want to import configurations and manage proxies in a graphical interface. Product details: clashplus.io.
CLIENTS / PACKAGES
Choose your platform, then check your processor architecture. Use a GUI client on desktop or mobile; choose the Mihomo core for servers and routers as needed.
New here? Prepare a valid subscription or local YAML configuration. The installer does not include a proxy service.
01 / GUI Clients
Clash clients differ in interface, configuration management, and system integration. Choose the tab for your device, then check the architecture listed on each card. You don’t need to install every client for the same platform. Keep a backup of your existing configuration, import your subscription on first launch, and only then enable network routing.
This section offers x64 desktop installers for compatible Intel and AMD PCs. Check your system type in Settings → System → About. On Windows on ARM, verify compatibility for both the client and its drivers; an installer that runs does not guarantee that TUN will work.
A good fit if you want to import configurations and manage proxies in a graphical interface. Product details: clashplus.io.
Before using service mode or TUN, check the service components and permission prompts. If the system asks for additional runtime components, install them as prompted, then restart the client.
Before migrating, make sure your subscription parses correctly, then choose a proxy mode. Don’t overwrite the old client’s data directory; settings may not carry over between clients.
If you rely on custom rules, back up any local changes outside your subscription. Client updates and subscription updates are separate; check each one independently.
Older cores may not recognize fields in newer configurations. If parsing fails, don’t reinstall repeatedly. Check the reported field first, then migrate the configuration to a compatible client.
| Check | Requirements and steps |
|---|---|
| Processor | Desktop builds here are x64 / AMD64. Check System Information; these builds don’t support 32-bit Windows. |
| System | Use a Windows version that still receives security updates. Check the selected client’s installer for its minimum version and runtime requirements. |
| Permissions and routing | For regular browsing, test System Proxy first. TUN or service installation may require administrator approval. Quit other proxy clients before you begin. |
Open About This Mac from the Apple menu. If it lists an Apple chip, choose Apple Silicon; if it lists an Intel processor, choose Intel. Both download options are listed below. Some channels may currently point to the same package, so verify the app’s actual architecture and compatibility after installation.
Import your subscription after installation, then check System Proxy permissions. Product details: clashplus.io.
Running an Intel app on Apple Silicon may require Rosetta. Check driver and service compatibility separately; a successful launch doesn’t confirm they’ll work.
Quit the app before updating. If macOS says it’s still in use, stop network routing and background processes before replacing the app files.
A macOS upgrade may affect system integration in older clients. For new devices, use a maintained option and back up your rules and DNS settings before migrating.
| Check | Requirements and steps |
|---|---|
| Chip | Check About This Mac to identify Apple Silicon or Intel, then verify the architecture of the file offered by your download channel. |
| macOS version | Minimum macOS requirements can change between client releases. Follow the app’s compatibility notice. Switching to a different chip build won’t fix an unsupported macOS version. |
| First launch | Launch the app from Applications and grant any permissions requested by macOS. If you see a security warning, note the reason; don’t bypass protections with commands from untrusted sources. |
Most recent phones use ARM64, but the processor model alone doesn’t confirm which ABIs the system supports. Check your device’s system information first. Older devices may use ARMv7; if you’re unsure, choose a universal build if the client offers one. Make sure the download completes before installing, then grant VPN permission when you connect.
After connecting, adjust background battery settings if needed to keep Android from stopping network services when the screen is locked. Product details: clashplus.io.
After importing your configuration, activate it before connecting. If it conflicts with another VPN app, disconnect the other VPN first rather than repeatedly reimporting your subscription.
Back up your subscription and custom settings before upgrading. If Android reports a signature mismatch, check whether the new build comes from a different release channel before backing up and migrating.
Changing a file extension won’t convert a configuration. If your link only provides a Clash configuration, ask the provider whether a compatible subscription link is available.
| Check | Requirements and steps |
|---|---|
| Architecture and version | Check the ABIs your system supports and the Android version required by the APK. Follow the installer’s compatibility notice. |
| Install permissions | Allow app installs only for the downloader or file manager you’re using. Revoke that permission afterward if you no longer need it. |
| Connection and background activity | Approve the VPN prompt on first connection. If the connection drops when the screen locks, check battery optimization, background restrictions, and VPN conflicts. |
For step-by-step instructions, see how to import a configuration and connect on Android. Installation failures are usually related to the device or installer. Connection failures call for checks of your subscription, nodes, DNS, and app routing. Troubleshoot these separately.
Open the App Store listing on your iPhone or iPad and check device compatibility before installing. Have an existing subscription or configuration ready. The first time you connect, approve the system prompt to add a VPN configuration.
Official site: clashplus.io. After importing, make sure the configuration is enabled, then choose a proxy group and connect.
| Check | Requirements and steps |
|---|---|
| Compatibility | Check the App Store listing for current iOS / iPadOS requirements and supported devices. |
| Installation and updates | Install through the App Store and manage app updates there. Refresh subscription content inside the client. |
| First connection | Prepare a valid configuration and approve the system VPN prompt. Check whether another VPN or device management policy could affect the connection. |
Desktop users should first check their distribution’s package format and CPU architecture. The GUI installers below are for AMD64: choose DEB for Debian- and Ubuntu-based distributions, or RPM for Fedora and other RPM-based distributions. Converting package formats doesn’t guarantee compatible system dependencies.
Desktop sessions, tray support, and service permissions can affect how the app works. If the interface is running but traffic isn’t routed, check system proxy settings and core logs.
Command-line tools don’t always follow the desktop system proxy. If terminal apps still can’t connect, check their proxy settings or configure TUN if permissions allow.
| Check | Requirements and steps |
|---|---|
| Architecture | Run uname -m to check. GUI packages here are for x86_64 / AMD64; for other architectures, see the core downloads below. |
| Distribution | Check the DEB / RPM format, desktop environment, and runtime dependencies. Refer to the package’s dependency declarations for supported systems. |
| Service permissions | System Proxy and TUN have different permission requirements. Before enabling TUN, check system network device support and service permissions. |
02 / Command-line core
Mihomo is a proxy core, not a desktop client with a settings window. After downloading a build, you’ll need to provide a YAML configuration, runtime directory, and process management. For everyday desktop or mobile use, choose a GUI client above; the extracted core file is not a standard installer.
Before deploying to a server or router, make sure the OS, CPU architecture, and runtime environment match. ARMv7 and ARM64 aren’t interchangeable, and MIPS softfloat is not a universal router build. On Linux, uname -m can help identify the architecture, but check your device firmware documentation to confirm compatibility.
| Operating system | Processor architecture | File format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP archive | Download Windows AMD64 |
| Windows | ARM64 | ZIP archive | Download Windows ARM64 |
| macOS | Intel / AMD64 | GZ archive | Download macOS Intel |
| macOS | Apple Silicon / ARM64 | GZ archive | Download macOS ARM64 |
| Linux | AMD64 | DEB package | Download Linux AMD64 DEB |
| Linux | AMD64 | GZ archive | Download Linux AMD64 GZ |
| Linux | ARM64 | GZ archive | Download Linux ARM64 |
| Linux | ARMv7 | GZ archive | Download Linux ARMv7 |
| Linux | MIPS softfloat | GZ archive | Download Linux MIPS softfloat |
03 / Post-install checks
Open the configuration or subscription page, paste your subscription link, and wait for the client to parse it. Make sure the new configuration is enabled, not just listed. Subscription links contain access credentials, so hide the full URL in screenshots and support requests.
View subscription import steps →Start with Rule mode and enable System Proxy for the apps that need a proxy. Use TUN only if an app ignores the system proxy and you need broader routing, following the guide. Don’t run multiple clients that take over network traffic at the same time.
View System Proxy settings →Test both direct and proxied destinations, and check whether the connection log shows the expected rules. If the client is running but you still can’t connect, check System Proxy, proxy groups, DNS, and rules in that order. Keep any reproducible error messages.
Troubleshoot connection issues →Client updates provide app and core improvements; subscription updates refresh service configuration. If old nodes remain after an app update, refresh your subscription. If parsing fails, check that the link is valid and the configuration format is supported; you don’t need to uninstall the client first. Back up local rules before migrating, then recheck System Proxy, TUN, and launch-at-startup settings after upgrading.
For Windows, macOS, Android, and iOS, start with Clash Plus. Linux users can start with Clash Verge Rev. Check your device architecture before downloading the right installer. If you already have a setup that works, you can keep using a familiar client that remains compatible with your system.
These labels indicate the processor architecture an installer is built for. Most Intel and AMD desktop PCs use x64, also called AMD64. Apple Silicon uses ARM64. On Android, check which ABIs your device supports. Universal builds include multiple architectures and are usually larger; choose one only if the client offers it.
Installing the app only sets up the client. You’ll still need to import a valid subscription or local configuration, choose an available proxy group, and enable System Proxy or TUN if needed. The installer does not include a subscription service. Follow the Getting Started guide to import your configuration, choose a mode, and verify the connection.
Clash for Windows and ClashX Meta are no longer maintained. Their download links remain available mainly for migrating older setups and comparing configurations. For new devices, choose a maintained client. Back up your configuration before migrating, check that the new core supports your rules, DNS settings, and proxy groups, and avoid letting two clients manage your network at once.
Check your OS version, processor architecture, installer format, and available disk space first. Note the full error message from the system or installer. On Windows, check required runtime components; on macOS, check app compatibility and security settings; on Android, check install permissions and package conflicts. Don’t disable system security protections.
For everyday desktop and mobile use, choose a client with a graphical interface to import subscriptions, switch proxy groups, and view logs. The Mihomo core is for server, router, and command-line users who manage their own configuration, startup options, and service processes. The core itself does not include a desktop settings interface.
Still having configuration or connection issues? Browse the Help Center by topic, or go straight to the relevant section of the Troubleshooting guide for a specific error.