Clash Plus
Top PickManage subscriptions, choose proxy groups, and control connections from a graphical interface. For your first run, confirm the config is enabled before turning on the system proxy.
Choose your operating system, then check the processor architecture. Use a desktop client on laptops and phones; for servers and routers, see the standalone core builds.
Platform tabs can be shared as links. When switching devices, check the package format and architecture again.
The desktop client downloads here are mainly x64. In Windows, go to “Settings → System → About” and check System type. On ARM devices, first confirm x64 app compatibility; desktop app compatibility and TUN driver support are separate considerations.
Manage subscriptions, choose proxy groups, and control connections from a graphical interface. For your first run, confirm the config is enabled before turning on the system proxy.
Includes config management, rule inspection, and mihomo-related settings. To use TUN, install the service as prompted and grant the required permissions.
A good fit if you want a similar experience across desktop and mobile. Choose EXE for a standard install. If you choose ZIP, extract all files before launching the app.
A good fit if you prefer desktop config management. When switching clients, import your config again and check the proxy port to avoid conflicts with an old client still running in the background.
Kept as an archived download for reference when checking older setups or migrating configs. For a new device, choose one of the clients above; the older core may not read newer subscription fields.
| Check | Before You Install | Tip |
|---|---|---|
| Operating system | Use a supported Windows 10 or 11 release. Check the selected client’s release notes for its exact minimum requirements. | On older systems, check compatibility with required runtimes and UI components first. |
| Processor | Installers in this section are primarily x64 / AMD64. | A 32-bit system cannot run an x64 installer. |
| Network permissions | System proxy usually works without elevated permissions; service mode or TUN may require administrator approval. | Test the system proxy first, then enable TUN if your apps require it. |
After installation, quit any old proxy client before opening the new one. If your browser still reports a proxy connection error, check whether the system proxy points to an old port. Don’t let two clients control the system proxy at once. See the first-time setup guide for steps.
Open Apple menu → About This Mac. A device listed with an Apple chip is Apple Silicon; choose x64 for a device with an Intel processor. Check the actual package name after downloading: some channels currently link to the same x64 file for both architectures.
Choose the DMG for your chip. Open the disk image and follow the installer, then launch the app from Applications, import your subscription, and approve any network permissions.
A good fit if you need config editing, rule management, and core settings. Both current downloads are x64 DMGs; Apple Silicon users should check translation-layer compatibility.
A cross-platform graphical client. The current Mac download is AMD64; after importing a config, check system proxy, launch-at-login, and background settings again.
The archived download is for reference with older setups and config migration. The current file is x86_64; use a maintained client to address permissions and compatibility issues on newer systems.
| Check | Before You Install | Tip |
|---|---|---|
| macOS version | Check your macOS version in About This Mac and compare it with the client’s current release requirements. | Being able to open a DMG doesn’t mean the app supports your version of macOS. |
| Chip architecture | Apple Silicon uses ARM64; Intel uses x64 / x86_64. | Choose a native build that matches your processor when available. |
| Network permissions | Helper services, network extensions, or VPN features may require system approval. | Grant only the permissions needed for the features you use. |
If the app won’t launch, read the system alert and check the download source, macOS version, and architecture. Don’t disable system security features as a first step. Quit any old menu bar proxy app before installing a new client to prevent both apps from changing the same network proxy settings.
Most recent Android phones use ARM64. Older devices may still use 32-bit ARM. If you’re unsure, check your device details or choose the universal Clash Meta for Android build. Installation and connecting are separate steps; connecting also requires system VPN approval.
Import subscriptions, choose proxy groups, and manage connections on your phone. This is the ARM64 APK; add a config after installation, then start the connection.
Available in ARM64, 32-bit ARM, and universal builds. Match the package to your device architecture when possible; the universal build includes more architectures and is useful if you can’t identify your device type.
A good fit if you use FlClash on both phone and desktop. ARM64 and ARM builds are available here; don’t choose ARM64 on a 32-bit device.
For users with an existing compatible config. Its syntax differs from Clash YAML, so check that your service provider supports Surfboard’s config format before importing.
| Check | Before You Install | Tip |
|---|---|---|
| OS and architecture | Check the Android versions supported by the client and whether your device uses ARM64 or ARM. | If installation fails with a parsing error, first check the Android version and package architecture. |
| Install permissions | When installing through a browser or file manager, Android may ask you to allow app installs from that source. | Grant install permission only to the source you’re actually using. |
| Connection permissions | The first time you start the proxy, approve the VPN connection request. | Another VPN app may replace or interrupt the current connection. |
If the connection drops when the screen locks, check whether the system restricts background activity, then adjust battery settings if needed. If the connection acts up after switching between Wi-Fi and mobile data, stop and reconnect first. Check the logs if it keeps failing instead of repeatedly reinstalling the app.
Get Clash Plus from the App Store on iPhone or iPad. Check device compatibility in the store listing. After installation, open the client and import a valid subscription; when connecting for the first time, follow the system prompt to allow a VPN configuration.
Install and update through the App Store. Import a config, choose a proxy group, and start the connection. Check the current App Store listing for compatibility details.
Client website: clashplus.io
| Check | Before You Install | Tip |
|---|---|---|
| macOS version | Check the Compatibility section of the App Store listing for the required iOS / iPadOS version. | Make sure the store lists your device as compatible before installing. |
| Config source | Prepare a subscription URL or local config file supported by the client. | After importing, confirm the intended config is selected. |
| VPN permission | The first connection requires permission to add a VPN configuration and may require device authentication. | After switching VPN apps, confirm which app currently controls the connection. |
A VPN Connected status only means the local proxy tunnel is active; it doesn’t guarantee that every route in your subscription works. If a website won’t load, check in order that the config is up to date, the proxy group has an available option, and the connection matches the expected rule. See the Troubleshooting Guide for the full process.
For desktop Linux, start with a graphical client. Debian and Ubuntu-based distributions generally use DEB; Fedora and other RPM-based distributions use RPM. Check dependency compatibility. The desktop client packages here are AMD64 and won’t work on ARM routers.
DEB and RPM packages are available for AMD64 devices with a desktop environment. Let your distribution’s package manager handle dependencies, then launch the app from the application menu.
The AMD64 DEB package here is for Debian-based desktop systems. Installing the client doesn’t automatically configure proxy access for terminal tools; each tool may need its own proxy settings.
| Check | Before You Install | Tip |
|---|---|---|
| Distribution | Check whether your system uses DEB or RPM packages and review the client’s dependencies. | A matching package format doesn’t guarantee compatibility with every older distribution. |
| Processor | Run uname -m; x86_64 corresponds to the AMD64 packages listed here. | aarch64 devices need software built for the matching architecture. |
| Runtime environment | Desktop clients need a compatible desktop environment and graphics libraries. | For headless servers, use the standalone Mihomo core. |
Command-line apps don’t always use the desktop system proxy. If your browser works but terminal tools don’t, check those tools’ proxy options or environment variables; this alone doesn’t mean the installation failed. If you need system-wide traffic routing, assess TUN permissions and routing configuration.
For servers, routers, and command-line use. The standalone core has no desktop config editor, so you’ll need to prepare a YAML config, working directory, service startup, and network permissions yourself. Laptop users should start with one of the GUI clients above.
| System | Processor architecture | Package format | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP | Download Windows AMD64 |
| Windows | ARM64 | ZIP | Download Windows ARM64 |
| macOS | Intel / AMD64 | GZ | Download macOS Intel |
| macOS | Apple Silicon / ARM64 | GZ | Download macOS ARM64 |
| Linux | AMD64 | DEB | Download Linux AMD64 DEB |
| Linux | AMD64 | GZ | Download Linux AMD64 GZ |
| Linux | ARM64 | GZ | Download Linux ARM64 |
| Linux | ARMv7 | GZ | Download Linux ARMv7 |
| Linux | MIPS soft-float | GZ | Download Linux MIPS |
| Check | Before Deployment | Tip |
|---|---|---|
| Architecture | Check the CPU architecture, operating system, and router firmware details. | For MIPS, check byte order and floating-point ABI as well as the device model. |
| Config and directories | Prepare a readable config file and a writable working directory. | Test the config in the foreground before setting up a background service. |
| Network and permissions | Check that the listening port is available; TUN and routing changes may require extra permissions. | Expose the management interface only to trusted addresses and set up access controls. |
GZ files are compressed executables: extract them and set the execute permission. ZIP files must also be fully extracted. On first run, check the config parsing results and verify the listen address, DNS, and rules. For LAN sharing, check the firewall too; don’t expose proxy ports directly to the public internet.
Start with a working config before adding TUN, LAN sharing, or launch-at-login. Change one setting at a time to make issues easier to diagnose and undo.
The client and proxy service are separate. After installation, get a valid subscription URL or local YAML file, add it on the config page, and enable it. Subscription URLs may contain private access credentials: copy the full URL, and don’t share it in screenshots or support requests.
Once the config loads, choose a rule mode and check that the proxy group has an available option. Turn on the system proxy on desktop, or approve VPN access on mobile. Don’t change DNS, TUN, and rules all at once. If the connection fails, changing one thing at a time helps pinpoint whether the issue is installation, configuration, or the route.
See the subscription import and first-connection guide →Before migrating, note your subscription URL, manually added rules, ports, and custom DNS settings. Locally edited settings may not be included when you export a subscription, so save the original config. After importing successfully into the new client, quit the old app and let the new one take over the system proxy.
If both clients use mixed-port: 7890, running them at the same time may cause a port conflict. Make sure the old app has fully quit before testing the new one. To roll back, restore the original config; don’t overwrite one client’s app settings directory with another’s.
Test an actual connection, not just the toggle: Open a site you use, then check the client’s connection list or logs for the matched rule. If one app fails, check whether it uses the system proxy. If all apps fail, check the config, proxy group, DNS, and route one by one. The full process is in the Troubleshooting Guide.
Start with package selection and installation. For connection issues, see the FAQ.
Start with Clash Plus on Windows, macOS, Android, or iOS; on Linux, try Clash Verge Rev. Check your operating system and processor architecture before downloading a desktop client. You’ll still need to import a valid subscription or config file after installation.
AMD64 and x64 usually refer to the same 64-bit x86 architecture, common on Intel and AMD PCs. ARM64 is used by most newer Android devices and Apple Silicon Macs. Check your device’s processor details and verify the package architecture before downloading. If you can’t identify your Android device’s architecture, choose the universal build.
The client reads your config and handles connections; the installer does not include a proxy service. Import a valid subscription or YAML config, make sure it’s enabled, select a proxy group, and turn on the system proxy. On mobile, you’ll also need to approve the system VPN permission.
Back up your subscription URL and local config, then import them into the new client. Configs that use mihomo-specific fields need a compatible core; Surfboard requires a config format it supports. System proxy, launch-at-login, and permission settings usually need to be checked again—they aren’t migrated with the subscription.
Clash for Windows and ClashX Meta are kept here as archived downloads for checking older setups or migrating configs. For a new device, choose a client that’s still maintained. Older clients may not support current system permissions, subscription fields, or protocols.
Usually not. Desktop clients generally include a core and provide config management and proxy controls. Standalone Mihomo builds are mainly for servers, routers, and command-line deployments, where you’ll need to prepare the config, service startup, and network permissions yourself.