Clash Plus
Top pickA good starting point for managing subscriptions and proxies in one GUI. Choose the x64 installer, import your configuration after setup, then check the proxy mode and system proxy settings.
Choose a platform, check the architecture, then download and install. For a first-time Windows setup, start with Clash Plus or Clash Verge Rev.
Check your operating system and processor architecture.
Choose a GUI client that’s actively maintained.
Get a subscription link and import the configuration after installation.
Most desktop downloads below are x64. Check your system type under Settings → System → About first.
A good starting point for managing subscriptions and proxies in one GUI. Choose the x64 installer, import your configuration after setup, then check the proxy mode and system proxy settings.
For Windows users who need subscription management, rule-based routing, and TUN settings. This site’s guides follow its common workflows. Before enabling TUN, make sure Service Mode is installed and running.
For users who want a similar workflow across desktop and mobile. The installer is convenient for everyday use; choose the ZIP if you prefer to manage the extracted folder yourself. Check the app’s settings for the data location.
An alternative desktop interface for managing configurations. Before migrating a subscription, confirm that the core supports its protocols and fields. Restore rules, ports, and proxy groups one at a time to avoid carrying over outdated overrides.
An archived download for recreating older environments and comparing settings before migration. Choose a maintained client for new devices. Back up Profiles, subscription URLs, and custom rules, then migrate them to the new client instead of overwriting the entire old data directory.
| Check | What to do |
|---|---|
| System | Use a Windows version that still receives security updates. Check the selected client’s release notes and installer for its minimum supported version. |
| Processor architecture | Downloads here are primarily x64 / AMD64. On ARM devices, check system compatibility first; an x64 package is not a native ARM64 build. |
| Installation permissions | Installing to some directories, setting up system services, or adding a virtual network adapter may require administrator approval. Importing a regular subscription should never require giving a third party your system password. |
| Proxy conflicts | Quit any old client before installing. For testing, use only one system proxy and one TUN traffic-routing setup at a time. |
Installation alone doesn’t establish a connection. Import a subscription, enable its configuration, and choose a proxy group. If a browser works but other apps don’t, check whether those apps follow the system proxy. Set up the required service only if you need TUN; don’t enable several traffic-routing options at once.
Open Apple menu → About This Mac to check whether your Mac has an Intel processor or Apple silicon.
Download the DMG for your Mac’s chip. Open the disk image and follow the instructions to move the app to Applications, then launch it. On the first connection, watch for system network permission prompts and make sure the imported subscription is selected as the active configuration.
For users who want familiar desktop subscription and rule management. Both fallback downloads are x64 DMGs. Apple silicon users should check the actual package architecture and Rosetta compatibility; this is not a promise of a native ARM build.
For users who want a consistent workflow across devices. Both fallback downloads are AMD64 DMGs; check compatibility requirements on Apple silicon. After migrating your configuration, recheck system proxy and DNS settings.
An archived download for users comparing an older menu bar workflow. The fallback build is x86_64; Apple silicon users should check compatibility requirements. If an OS upgrade causes permission or proxy issues, consider switching to a maintained client.
| Check | What to do |
|---|---|
| macOS version | Check the client’s current release notes for its minimum macOS version. Don’t assume an older system is compatible just because it can open the DMG. |
| Chip | On Apple silicon, choose a package explicitly labeled ARM64. x64 / AMD64 packages may require Rosetta. |
| App permissions | Follow system prompts for app launch, network extensions, or service permissions. Check System Settings → Privacy & Security for the specific reason. |
| Configuration migration | Back up subscriptions and rules. Don’t copy Windows service paths or shortcuts directly to macOS. |
Downloads are grouped by platform, but the label alone doesn’t tell you the file’s architecture. Check both the filename and app documentation. If it won’t launch, first distinguish between an OS version limit, processor architecture, and a security prompt. Don’t run commands from unknown sources to remove all system protections.
Most recent phones use ARM64. Older devices may need ARMv7; check your device information or choose the universal build if you’re unsure.
A good starting point for ARM64 phones and tablets. Install the APK, import a subscription, and allow the VPN connection when prompted. For long-running background use, check battery optimization and background activity permissions.
For users who want to manage Clash configurations and policies on Android. ARM64 is for most newer devices; the ARM build is for compatible older devices. The universal build is a convenient choice if you’re unsure of your architecture, but it’s usually larger.
For users familiar with FlClash on desktop who want to use it on Android. Choose a package that matches your phone’s processor; ARMv7 is for compatible older devices. After restoring your configuration, check which apps are routed and review permissions rather than assuming they match another device.
For Android users with an existing Surfboard-compatible configuration. Its format differs from Clash YAML, so changing the file extension won’t make it importable. Before downloading, check whether your subscription provider supports the required format.
| Check | What to do |
|---|---|
| OS and architecture | Check the app’s current minimum Android version. A 64-bit processor may still run a 32-bit OS, so the device’s system determines which packages it can install. |
| Install source | Grant install permission only to the browser or file manager you’re using, and revoke it afterward if you wish. |
| VPN permission | The first connection requires system approval. Another VPN app may already be using the VPN connection. |
| Background activity | Check app restrictions in system battery settings. The names for background locking and auto-start vary by device manufacturer. |
If you see “App not installed,” check OS compatibility, available storage, and whether the installed app has the same signature. Builds with different signatures usually can’t be installed over each other; export your configuration before uninstalling. If the connection drops when the screen turns off, check background restrictions instead of repeatedly switching APKs.
Install Clash Plus from the App Store and check the store listing for compatibility with your device and iOS version.
Open the app’s App Store page and check the developer and compatibility details before installing. Get a working subscription, import its configuration in the app, and choose a policy. On the first connection, follow the iOS prompt to add a VPN configuration.
| Check | What to do |
|---|---|
| Device and OS | Check the minimum OS version and compatible devices listed on the current App Store page, and make sure you have enough free storage before installing. |
| Network permission | The first connection requires approval to add a VPN configuration. You can check its status in Settings. |
| Subscription configuration | Make sure the link is valid and its format is supported. After importing, select the configuration and test the connection. |
| Connection conflicts | Disconnect other VPNs while testing so you don’t mistake another app’s connection status for this client’s. |
Installing the app and subscribing to a service are separate steps. The app reads your configuration and handles connections; the subscription provider supplies nodes and manages your account. If an update fails, check the link’s expiry and your account status. If a connection fails, check the app logs and selected policy instead of assuming installation is the problem.
For desktop Linux, start with a GUI client. Choose DEB or RPM for your distribution and confirm you have AMD64.
Manage subscriptions, rules, and proxy groups on a Linux desktop. Debian- and Ubuntu-based systems typically use DEB; Fedora and other RPM-based distributions use RPM. Install any additional desktop dependencies required by your distribution.
For Debian-based desktops and users who want a familiar workflow across devices. This download is an AMD64 DEB package. If installation succeeds but the app won’t launch, save the terminal output and check runtime libraries and your desktop session first.
| Check | What to do |
|---|---|
| Processor | Check your architecture with uname -m; desktop packages here target x86_64 / AMD64 and are not for ARM routers. |
| Package format | Choose DEB or RPM for your distribution. Renaming a package extension does not convert it. |
| Desktop dependencies | GUI clients need a compatible desktop environment and runtime libraries. Check your distribution and the client’s documentation for required versions. |
| Network permissions | TUN and system services may need additional permissions. If working remotely, keep a way to restore your connection. |
Servers accessed only over SSH are usually better suited to the standalone Mihomo core. Enabling the system proxy on a desktop doesn’t necessarily configure terminal apps too. Check the desktop proxy, environment variables, and TUN routing separately; a successful browser test doesn’t mean every process is routed.
For users who manage YAML configuration, startup arguments, and system services themselves. Most desktop users should choose one of the GUI clients above.
| Operating system | Architecture | Package format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP, 64-bit x86 devices | Download AMD64 · .zip |
| Windows | ARM64 | ZIP, compatible ARM64 systems | Download ARM64 · .zip |
| macOS | Intel AMD64 | GZ, Intel Mac command-line environments | Download Intel · .gz |
| macOS | Apple Silicon ARM64 | GZ, Apple silicon command-line environments | Download ARM64 · .gz |
| Linux | AMD64 | DEB, compatible Debian-based systems | Download AMD64 · .deb |
| Linux | AMD64 | GZ, standalone executable for manual deployment | Download AMD64 · .gz |
| Linux | ARM64 | GZ, 64-bit ARM servers or devices | Download ARM64 · .gz |
| Linux | ARMv7 | GZ, compatible 32-bit ARM devices | Download ARMv7 · .gz |
| Linux | MIPS softfloat | GZ, check endianness and device ABI | Download MIPS · .gz |
Similar processor names don’t guarantee binary compatibility. On Linux, check uname -m, then verify system bitness, runtime libraries, and device firmware requirements. For MIPS devices, also check endianness and floating-point ABI. If you see “Exec format error,” verify the architecture rather than repeatedly changing the startup script.
Set appropriate read and write permissions for the configuration directory, and check for port conflicts before starting. Restrict access to the management interface and use separate credentials; don’t expose it directly to the public internet. Before changing routes or enabling TUN on a remote server, keep console access or another recovery path available.
GUI clients often manage the core path and startup arguments; replacing them manually can cause interface mismatches. If you only need to update the desktop app, use its built-in updater. To understand how the core, configuration, and interface fit together, read the user guide.
Open the configuration page, paste a working subscription link, and import it. Wait for the update to finish, then enable the configuration. Subscription links grant access to your account; don’t include them in public screenshots or shared documents. If import fails, save the exact request error.
Start by testing common websites in Rule mode. Global mode changes how policies are selected; it doesn’t automatically route traffic from every app. System proxy settings, VPN permission, and TUN are separate routing mechanisms, so check each one individually.
During testing, watch both the connection view and the logs. Confirm that requests reach the client, match the expected rules, and use an available policy. If something fails, change one setting at a time and test again; changing DNS, ports, and mode together makes troubleshooting harder.
Choose your device platform, then start with the first Clash Plus card for that platform. Windows users following this site’s guides to Service Mode and TUN Mode can also choose Clash Verge Rev. After installing a client, you’ll still need to import a working configuration; the installer does not include a subscription service.
x64 and AMD64 usually refer to the same 64-bit x86 architecture; they are not limited to AMD processors. In Windows, check System type under Settings → System → About. On a Mac, check the chip under About This Mac. For Apple silicon downloads, verify the actual package architecture: some available builds are x64 and require a compatibility layer.
The page retains an archived Clash for Windows installer, mainly for recreating older environments and migrating configurations. Discontinued does not mean existing features stop working immediately, but don’t expect new protocol support, ongoing compatibility fixes, or future maintenance. Choose a maintained client for new devices, and back up subscriptions, rules, and settings before migrating.
First check your OS version, processor architecture, and file type, then confirm the download completed and you have enough disk space. On Windows, quit any existing instance before installing. On macOS, review the specific message under Privacy & Security. On Android, check install permissions and whether the app’s signature conflicts with an existing installation. Keep the exact error message; don’t disable system security protections.
Import a working subscription on the configuration page and enable it, then select a policy in the proxy group and test in Rule mode. On desktop, check the system proxy. On Android and iOS, approve the system VPN prompt. If the issue persists, check the logs to distinguish subscription request failures, authentication errors, DNS resolution problems, and connection timeouts.
Usually not. GUI clients generally bundle or manage their own compatible core, so use the client’s built-in updater. Standalone Mihomo packages are for server or router users who manage configuration, startup arguments, and system services themselves. Before replacing a GUI client’s core, check configuration format, interfaces, and version compatibility.