Client downloads / Choose by platform
Clash Plus, Clash Verge Rev, and other Clash clients. Choose your operating system first, then check the processor architecture.
This page lists options by platform; not every app is Clash Verge Rev. Verge Rev is for desktop, while phones use their own clients. You’ll still need to import a valid subscription or local configuration after installation; the app itself does not include a proxy service. For your first setup, open the Getting Started guide and follow the steps to import a configuration, choose a mode, and test the connection.
Desktop / Windows
The downloads below are x64 installers. Clash Plus is a good starting point for new users; choose Clash Verge Rev for Mihomo settings and override management. Quit any running proxy apps before installing to prevent multiple clients from changing the system proxy or competing for the same ports.
A good fit for Windows users who want to start by importing a subscription. After installation, make sure the configuration parses correctly before enabling the system proxy. If you need to route traffic from apps that ignore the system proxy, review TUN settings and permission requirements separately.
Includes subscription, policy group, connection, and settings interfaces for desktop users who need to manage rules and overrides. System proxy and TUN are different ways to route traffic. Test one first, then decide whether to enable additional settings such as service mode.
A good fit if you want a similar workflow on desktop and mobile. This is the Windows AMD64 installer. When migrating, re-import your subscription and check your policy groups; copying an entire data folder from another client is not recommended.
Another desktop management interface in the Clash ecosystem. If you already have a configuration, check that its fields are compatible with the selected core before importing it. The interface can manage configurations, but it can’t make an older core support protocols or rules that it doesn’t recognize.
This legacy client is listed for compatibility testing, configuration export, and migration reference in existing setups. Because it’s no longer maintained, don’t expect ongoing OS compatibility updates or bug fixes; older cores may also fail to recognize new subscription fields. For new installations, choose a client above that’s still maintained.
| Check | Requirements and notes |
|---|---|
| Processor | The Windows graphical clients listed here are x64 / AMD64 builds. On ARM devices, first check emulation support and client compatibility. |
| OS and dependencies | Use a supported version of Windows 10 or 11. Check the selected client’s release notes for its minimum OS version. If prompted to install dependencies such as WebView2, follow the app’s instructions. |
| Permissions | System proxy and TUN have different permission requirements. Installing services, creating virtual network adapters, and adding firewall rules may require administrator access. |
| Before migrating | Back up subscriptions and overrides, then quit the old app. After installation, check listening ports, startup settings, and system proxy status. |
Desktop / macOS
Check About This Mac for your chip type: Apple silicon uses ARM64, while Intel processors use x64. Downloads are labeled by architecture, but some links in this list currently point to the same Intel build. Read the notes on each card before choosing.
Choose the disk image for your chip. Open the DMG and follow the installer to move the app into Applications, then launch it from there. If it asks to create a network configuration, review the system permission prompt and make sure it refers to the client you just installed.
A good fit for users who need desktop subscription management and rule overrides. Both the Apple silicon and Intel links currently point to an x64 image. Apple Silicon users should check Rosetta compatibility; this is not a separate native ARM build.
Offers a configuration workflow similar to the versions on other platforms. Both architecture links currently point to an AMD64 image, so Apple silicon users should check translation support. After switching clients, check the system proxy and avoid letting two apps manage it automatically at the same time.
Listed as a migration reference for existing menu bar client setups. Both architecture links currently provide an x86_64 image, which requires compatibility support on Apple silicon. The old version number doesn’t guarantee compatibility with newer systems; choose a client above for a new installation.
| Check | Requirements and notes |
|---|---|
| Chip and package type | On Apple silicon, prefer a native ARM64 build. x64 / AMD64 / x86_64 builds are for Intel and require Rosetta support on Apple silicon. |
| OS version | Minimum macOS versions and signing requirements vary by client. Check the installer prompts and the app’s release notes. |
| Network permissions | System proxy settings, network extensions, and helper services may each request permission. On managed devices, follow your organization’s administrator settings. |
| Install location | After installation, launch the app from Applications. Quit older processes before upgrading to avoid running separate copies from the mounted image and local folder. |
Mobile / Android
Most recent phones use ARM64, but a 64-bit-capable processor doesn’t guarantee that the OS provides a 64-bit runtime. Check the app ABI in your system information or device specs before choosing a build. On first connection, Android will ask for VPN permission; this allows traffic routing but does not confirm that your subscription is working.
For 64-bit ARM Android devices. After installation, add a subscription and enable the configuration before connecting. Start with the default background settings; adjust battery optimization for this client only if it actually disconnects when the screen is locked. Avoid broadly disabling background restrictions.
Supports configuration import and Android VPN routing. Choose the matching build if you know your architecture; otherwise, use the universal version. It usually includes components for more architectures, but it still requires a supported Android version.
A good fit if you want a similar workflow on mobile and desktop. ARM64 corresponds to arm64-v8a; 32-bit ARM corresponds to armeabi-v7a. When switching from another VPN app, disconnect it before starting the new client to avoid conflicts over Android’s VPN slot.
Its configuration syntax differs from Clash YAML, so it’s best for users who already have a compatible configuration. Don’t assume a Clash subscription link will work. Before importing, check that your provider supports the format, policy groups, and rules to avoid a setup that installs successfully but never parses.
| Check | Requirements and notes |
|---|---|
| App architecture | ARM64 builds require system support for arm64-v8a. Check for a 32-bit ARM build on older devices; don’t determine an emulator’s architecture from its host computer alone. |
| OS version | Check the minimum Android version shown by the app installer. A universal build supports more architectures but does not lower the OS version requirement. |
| Install permission | Allow installation for the download app or file manager you’re using. You can restore the permission afterward based on your device’s security settings. |
| Connection and background activity | Allow the system VPN request. If Android stops the app in the background, check battery settings, persistent notifications, and other VPN apps before reinstalling the configuration. |
Mobile / iOS
Install Clash Plus on iPhone or iPad through the App Store. Check the store listing for device compatibility, available features, and download availability. After installing, add a compatible subscription and approve the system network configuration prompt when you connect for the first time.
Check the app name and device requirements on the App Store listing before installing. After importing a subscription, make sure the configuration is enabled before connecting. If you use another VPN or a device management profile, check how it affects the system network connection.
Official website: clashplus.io
| Check | Requirements and notes |
|---|---|
| Device and OS | Check the App Store listing for the required iOS or iPadOS version and compatible devices. The store shows whether the app is available for your device. |
| Network permissions | Approve the system network configuration request to connect for the first time. Organization-managed devices may also be restricted by administrator policies. |
| Configuration source | Have a subscription or configuration supported by the client, and check that it’s active and the service is available. Installing an app and purchasing network service are separate things. |
| Test the connection | Even after iOS shows a VPN status, test the app you want to use. If only certain apps fail, check their rules and DNS resolution rather than relying on the connection icon. |
Desktop / Linux
Graphical clients are intended for Linux distributions with a desktop environment. Check your package format and processor architecture: DEB is generally for Debian and Ubuntu-based distributions, while RPM is commonly used by Fedora and others. This section offers AMD64 desktop builds; for routers and headless servers, see Mihomo below.
For Linux desktop users who need subscription, rule, and Mihomo settings. Choose the package format for your distribution and let its package manager handle dependencies. Before enabling TUN, check service permissions and virtual network adapter support; there’s no need to test system proxy and TUN at the same time.
This is an AMD64 package for Debian-based desktops. On other distributions, changing the file extension does not convert the package format; check dependency and desktop library compatibility first. If an app doesn’t use the proxy after installation, check whether it follows the desktop system proxy settings.
| Check | Requirements and notes |
|---|---|
| Architecture | The graphical installers here are for AMD64 / x86_64. Run uname -m to check your machine’s architecture. ARM devices can’t install AMD64 packages directly. |
| Distribution and dependencies | Match DEB or RPM to your package manager. Check the client’s release notes for desktop library, WebView, and system library requirements. |
| Runtime environment | Graphical clients require a desktop session. For SSH, containers, or routers, consider the standalone core instead of trying to install a desktop interface. |
| TUN requirements | You need an available TUN device and the necessary network permissions. Containers, virtual machines, and hosted servers may be restricted by the host’s policies. |
Core / Server & Router
For server, router, and command-line users who manage their own configurations. The core handles proxying, DNS, and rule execution; it is not a full graphical client. Most desktop users should choose a GUI app above. If a client already manages the core, you don’t need a separate core download to connect for the first time.
| Operating system | Processor architecture | File type | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 ZIP |
| Windows | ARM64 | ZIP | Download ARM64 ZIP |
| macOS | Intel · AMD64 | GZ | Download Intel GZ |
| macOS | Apple Silicon · ARM64 | GZ | Download ARM64 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 |
ZIP and GZ are archive formats; they don’t register a system service. After extracting, first check that the binary runs as a regular user, then set the configuration directory and handle logging, startup, and permissions. Install DEB packages with a package manager. Installation alone does not provide a valid subscription or correct routing configuration.
For MIPS devices, also check endianness, floating-point ABI, and firmware support; “router” alone isn’t enough to choose a file. TUN, transparent proxying, and LAN forwarding require additional network permissions and firewall settings. Before changing routes on a remote server, keep a recovery path to your admin connection. See the Configuration Reference for field structure and rule syntax.
Before installation
Test installation, configuration import, and traffic routing separately to find issues faster. Avoid changing the client, subscription, DNS, and proxy mode all at once on first launch.
01 / Package
Check your system information before looking at the file extension. x64, AMD64, and x86_64 generally refer to the same desktop architecture; ARM64 is a different instruction set. These are not performance tiers. If your file manager hides extensions, check the file properties to confirm the actual type.
If the installer says “This app can’t run on your device,” check the architecture and OS version first instead of repeatedly downloading the same file. Company- or school-managed devices may also restrict network tools; follow your organization’s device management process.
02 / Configuration
Before upgrading, note your subscription URL, configuration name, custom rules, and overrides. Subscription links may contain account identifiers; don’t post them publicly or include them in screenshots. When troubleshooting, share only the fields relevant to the error and remove sensitive parameters.
When switching clients, use each app’s import interface to add the subscription again. Caches, databases, and window settings may not be compatible, so copying the entire configuration folder is not a reliable migration method. Quit the old client before launching the new one.
03 / Verification
First make sure the configuration parses successfully, then choose a policy group and proxy mode, and finally enable the system proxy or VPN / TUN. A successful launch only confirms that the app installed. A VPN icon doesn’t prove the target app is matching the expected rules.
If something goes wrong, test a regular webpage, the target app, and DNS resolution separately, then use the client logs to narrow down the cause. If internet access still fails after quitting the app, check whether the system proxy still points to a local port. See Getting Started for the full setup flow.
Download notes
This section covers choosing a package, upgrading, and post-install checks. See the configuration docs for details on routing rules and DNS fields.
Choose your platform, then start with the recommended Clash Plus. For a desktop interface to configure Mihomo, try Clash Verge Rev. Linux users can also start with the recommended Clash Verge Rev. Installers contain the client only; you’ll need a valid subscription or configuration file to connect.
Check your processor architecture in your system information. x64, AMD64, and x86_64 generally refer to the same 64-bit desktop architecture; ARM64 and arm64-v8a refer to 64-bit ARM. On Android, choose the universal build if you’re unsure. Some macOS architecture links currently point to the same Intel installer; Apple Silicon users should check Rosetta compatibility.
Save your subscription URL, export or back up custom rules, override scripts, and client settings, and keep a copy of your current working configuration. Quit the old client before installing the new one. When switching clients, re-import your subscription rather than replacing the entire app data folder. Restore auto-start only after checking proxy mode, listening ports, and DNS behavior.
If the app won’t launch, check the OS version, processor architecture, and runtime dependencies, then review the specific error reported by the system. If it launches but can’t connect, make sure a subscription is imported and the configuration is enabled, then check for conflicts involving the system proxy, listening ports, or other proxy apps. Disabling security protections or ignoring certificate warnings is not a general fix.
Archived clients are older graphical apps that are no longer maintained. They’re listed mainly for compatibility testing and migration reference. Mihomo is a standalone proxy core without a full desktop interface or subscription management, making it suited to server and router users who manage their own configuration and services. Most desktop users should choose a graphical client that’s still maintained.