Choose your device’s operating system first, then check its CPU architecture. This page provides client software; to connect, you’ll also need a working configuration and system proxy or VPN permissions.
These desktop installers are for x64 systems. Open “Settings → System → About” and check your system type. For a first install, start with Clash Plus. If you already have a preferred configuration workflow, choose another client as needed.
A good fit if you want a similar workflow on your phone and computer. Import your configuration after installation, then choose a rule mode. Opening the app isn’t enough: start the service in the client and enable the system proxy.
For managing subscriptions, rules, and desktop proxy settings. The system proxy affects apps that follow system settings. If an app still bypasses the proxy, check its own network options before considering TUN mode.
Use it to import subscriptions, switch policy groups, and route traffic by rule. AMD64 and x64 refer to the same architecture here—not to AMD processors only. When migrating, import your configuration again and check the ports, DNS, and traffic-capture settings.
A desktop GUI for managing configurations. After switching clients, the old app’s auto-start or system proxy settings may still be active. Quit the old app before starting the new one to prevent both from competing for the same listening port.
Kept available for migrating legacy configurations and recreating older environments. The original client is discontinued and should not be relied on for support for newer protocols. For a fresh install, choose one of the current clients above. Before migrating, note your policy groups, custom rules, and local overrides.
| Check | Requirements or where to check |
|---|---|
| Processor and system | The installers above are for x64. On Windows ARM devices, first confirm x64 app compatibility; drivers and services may require separate checks. |
| Windows version | Use a supported Windows version and follow each installer’s compatibility guidance. Older systems may lack required runtime components. |
| Permissions | Standard system proxy settings and TUN have different permission requirements. Follow the prompts to approve administrator access when installing a service or virtual network adapter. |
| After installation | Make sure only one client in the system tray is capturing network traffic. If your browser loses connectivity after you quit the app, check whether the system proxy settings have been restored. |
Open the Apple menu in the top-left corner and choose “About This Mac.” A “Chip” entry usually means Apple Silicon; choose x64 for an Intel processor. Device architecture and the architecture of the available package are not always the same—the differences in this listing are noted below.
Separate ARM64 and x64 files are available. Open the DMG and follow the window prompts to install the app in Applications, then launch it from there. Import your subscription and check the selected policy group so you don’t end up with the app installed but no configuration selected.
For users who want desktop configuration management and rule controls. Both links in the current listing point to the same x64 file. Apple Silicon devices may need Rosetta; the link label does not mean a native ARM package is available.
A good fit if you prefer FlClash’s configuration workflow. Both links currently provide an AMD64 file, which is an x64 package. If macOS asks you to install Rosetta the first time you launch it, decide whether you’re comfortable running it through translation before continuing.
For recreating legacy environments or migrating from a menu bar client. This client is discontinued, and all files in the current listing are x86_64. Back up your configuration before switching; don’t assume the old core can handle newly added protocols or rule fields in a subscription.
| Check | Requirements or where to check |
|---|---|
| Processor | ARM64 is for Apple Silicon; x64, AMD64, and x86_64 refer to Intel architecture. Check each card for the architecture of the available file. |
| System compatibility | Check the minimum macOS version in the app’s compatibility prompt. Apple Silicon may need Rosetta to run x64 apps; verify network component compatibility separately. |
| Install location | Move the app to Applications. Before updating, quit the old running process, then replace the app files. |
| System permissions | If macOS prompts you about a network extension or background service, verify the app’s name in System Settings before approving it. Don’t disable global security protections just to get past a single prompt. |
Most newer phones can use ARM64, but some devices run a 32-bit operating system. Check your app’s ABI support before downloading. An APK is an Android app installer; once downloaded, open it from your browser’s downloads or a file manager.
A good fit if you’re importing a subscription and setting up rule mode on Android for the first time. The available file supports arm64-v8a. Add a configuration after installation, then start the connection. The first time you run it, Android will ask to create a VPN connection; verify the app name and allow it.
For users familiar with the Clash Android configuration workflow. Open the configuration page, import a subscription from its URL, and wait for the update to finish before selecting it. Choose the universal version if you’re unsure about the architecture; if you know it, use the matching single-architecture file.
The interface and workflow are similar across phones and desktops. After importing a configuration, test commonly used apps in rule mode. If the connection drops when the screen locks, check battery and background activity restrictions in the app settings instead of repeatedly reinstalling to work around system power management.
For Android users with a compatible configuration. Surfboard’s configuration format and feature support differ from Clash YAML; being a proxy client doesn’t make the two interchangeable. Confirm your subscription provider supports Surfboard, then import it and check that the rules load correctly.
| Check | Requirements or where to check |
|---|---|
| Architecture | ARM64 corresponds to arm64-v8a; ARM corresponds to armeabi-v7a. The ABI supported by your operating system is a better guide than the bitness advertised for the processor. |
| Windows version | Follow the compatibility requirements shown by the installer. If parsing fails, first check for an incomplete download, an architecture mismatch, or an outdated Android version. |
| Install-from-source permission | When prompted by Android, allow app installation only for the browser or file manager you’re using. You can revoke this permission afterwards if you wish. |
| VPN permission | The first time you connect, allow VpnService to create a local VPN interface. This captures device traffic; it does not mean the installer includes remote proxy nodes. |
| Background activity | Check background restrictions under “App info → Battery.” Wording such as “Unrestricted” or “Allow background activity” varies by device manufacturer. |
Open the store listing on your iPhone or iPad and check compatibility with your device before installing. The first time you add a VPN configuration, iOS will ask for confirmation. Installing the app and allowing its VPN configuration are separate steps.
Install and update through the App Store. After launching the app, import a working subscription and choose a policy and connection mode. When prompted to add a VPN configuration, verify the client name and approve it. Return to the app, check the connection status, then test an app that needs the proxy.
Official website: clashplus.io
| Check | Requirements or where to check |
|---|---|
| Windows version | Check the iOS and iPadOS requirements listed under “Compatibility” on the App Store page. |
| Connection permission | Follow the system prompt to add the VPN configuration. Your device may ask for your passcode or biometric authentication. |
| Configuration source | Prepare a subscription or connection details supported by the client. Don’t include links with access credentials in public screenshots or shared documents. |
| Updates | Update the app through the App Store. App updates and subscription updates are separate; updating the app does not update the subscription. |
These desktop packages are for AMD64. First check your distribution’s package format: Debian and Ubuntu-based systems generally use DEB, while Fedora and similar systems generally use RPM. For a headless server, see the core section below instead of installing a desktop app.
For managing configurations and proxy services on a Linux desktop. Install with your distribution’s package manager so it can handle dependencies. The desktop system proxy may not cover terminal apps; configure proxy environment variables separately or set up TUN if needed.
For Debian-based desktop users who prefer the FlClash interface. Make sure you have an active graphical desktop session before installing. If the app reports a missing shared library, check the package manager’s dependency information rather than replacing system libraries.
| Check | Requirements or where to check |
|---|---|
| Processor | Desktop packages are for AMD64 / x86_64; run uname -m to check your architecture. These installers won’t run directly on ARM devices. |
| Distribution | Choose DEB or RPM for your distribution. Follow the package manager’s output for dependencies and runtime requirements. |
| Desktop environment | The GUI client needs an active desktop session and the relevant graphical dependencies. For servers and routers, use the standalone core below. |
| Network permissions | TUN, routing, and firewall changes may require additional permissions. First confirm that a standard connection works, then enable traffic capture features step by step. |
For users running servers, routers, or self-managed services. The core reads configurations, listens on ports, and routes traffic; it does not include a desktop management interface. Most phone and desktop users should choose one of the GUI clients above.
| System | Architecture | File format | Download |
|---|---|---|---|
| Windows | AMD64 | 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 · softfloat | GZ | Download Linux MIPS softfloat |
| Check | Before deployment |
|---|---|
| Files and platforms | darwin means macOS; AMD64 means x86_64. For MIPS files, also check the device’s endianness and floating-point ABI; they are not universal packages for all MIPS devices. |
| Runtime configuration | Prepare a compatible YAML configuration, check that the ports are available, and make sure the working directory can access rule files and required data. |
| Service permissions | Expose only the required listening addresses and restrict access to the control interface. Grant permissions for TUN, routing changes, and system service registration as required by your platform. |
| Maintenance | Keep a rollback copy of the binary and configuration before updating. Test the configuration syntax before replacing the running service. |
For configuration fields, rule ordering, and day-to-day maintenance, see the beginner-to-advanced guide.
Get the basic connection working before adding rules or expanding the traffic capture scope. App upgrades, subscription updates, and system permissions are separate; check them independently when troubleshooting.
On the client’s configuration or subscription page, choose import from URL and paste a link from a trusted source. Save it and run an update to confirm the configuration isn’t empty and has no parsing errors. A successful update doesn’t enable it automatically—you still need to select the configuration.
For everyday use, start with Rule mode, which decides whether traffic connects directly or uses the proxy based on rules. On Android and iOS, allow VPN access when prompted; on desktop, check the system proxy. TUN captures traffic through a virtual network interface, so enable it only after understanding its impact.
Test both direct-connect websites and apps that need the proxy, then check the logs for configuration, DNS, or connection errors. Once everything works, export your local rules. Subscription updates may replace remote configuration; save custom content using the client’s supported override method.
Follow the steps to import a subscription and connect for the first time
If the installer won’t open, check your system and architecture first. If the app opens but can’t connect, check the configuration and connection permissions.
Check the supported ABI in your device or processor information. ABI is the binary interface an app needs to run. Choose ARM64 for devices supporting arm64-v8a, or ARM for devices that support only armeabi-v7a. If you’re unsure, choose the universal version of Clash Meta for Android. A 64-bit processor does not necessarily mean the operating system supports 64-bit apps.
You’ll need a working proxy configuration or connection details you’ve set up yourself. The client reads your configuration and handles traffic; the installer does not include a proxy service. Import a subscription URL from a trusted source on the configuration page. Once it updates successfully, select a policy group and start the connection.
No. In the current listing, both macOS links for Clash Verge Rev, FlClash, and ClashX Meta point to x64 files; Apple Silicon devices may need Rosetta. Clash Plus offers separate ARM64 and x64 files. Check the architecture notes on each card before downloading.
Close any other VPN app that’s running, then return to the client, start the service, and approve the system connection request. Android generally allows only one VpnService-based VPN to run per user at a time. Settings such as Always-on VPN may also affect switching.
Both projects are discontinued; their download links are kept for recreating legacy environments and migrating configurations. New configurations may use protocols or fields unsupported by their older cores. For a fresh install, choose a current client suited to your device. Before migrating, keep a copy of your existing configuration and check its rules, policy groups, and DNS settings.
For the same client, try installing over the existing version first and follow the installer’s guidance. Export your local configuration and custom rules before updating. Don’t overwrite one client’s program directory with another. On Android, a signature mismatch may prevent an in-place update; back up the app’s data before deciding whether to uninstall.
Already installed but having connection issues? See FAQs and troubleshooting. To learn about Rule, TUN, or VpnService, see the glossary.