CLIENT PACKAGES / SYSTEM & ARCHITECTURE
Choose your operating system, then confirm your processor architecture. For everyday use, choose a GUI client; for servers and routers, see the mihomo core downloads.
The app and subscription configuration are managed separately. After downloading, import your subscription URL or local YAML configuration.
DESKTOP / WINDOWS
For a new installation, start with Clash Plus. These desktop installers are primarily x64. Check your system type under Settings → System → About before downloading. Windows on ARM may be able to run x64 apps, depending on the OS; an x64 installer is not a native ARM64 build.
A good place to start if you’re building a daily workflow around imported profiles. After installing, open subscription management, load your configuration, select a policy, and then enable the system proxy. Check each setting during initial setup, and don’t enable proxy control in multiple clients at once.
For desktop users who want a GUI for configuration, policy switching, and log review. Before enabling TUN, check the service status and permission prompts. Importing a configuration doesn’t start the service; if something goes wrong, check the configuration and service logs separately.
For users who want a similar workflow across desktop and mobile. AMD64 and x64 refer to the same architecture; the processor doesn’t have to be made by AMD. You can reimport your subscription when switching, but check local rule overrides and app settings separately.
An alternative desktop interface for managing configurations. Keep using it if it already fits your workflow. After installing, check that the selected core supports your configuration syntax, especially subscriptions with rule sets, DNS overrides, or extended fields.
Use this archived download to reproduce a legacy environment or migrate an existing configuration. The client is no longer maintained; for new deployments, choose a maintained alternative above. Older cores may not support newer protocols or configuration fields. Export your configuration and note your ports, rules, and proxy mode before migrating.
| Check | Recommendations and limitations |
|---|---|
| Operating system | Use a Windows 10 or 11 release that is still supported by Microsoft. Check the installer’s requirements for its minimum supported version. |
| Processor architecture | The desktop downloads on this page are x64 / AMD64. 64-bit installers won’t run on 32-bit Windows. |
| Services and permissions | Installing service components or enabling TUN may require administrator approval. Save your configuration before proceeding with any prompts. |
| Existing clients | Quit old clients and disable their system proxy or TUN to avoid port conflicts or multiple apps taking control. |
DESKTOP / MACOS
Open Apple menu → About This Mac and check Chip or Processor. For Apple Silicon, choose an ARM64 download when available; for Intel, choose x64. Open the DMG and follow its instructions to move the app to Applications, then launch it from there.
Separate ARM64 and x64 downloads make it easy to choose the right package for your device. On first launch, import your configuration before enabling the system proxy. Follow system prompts to grant the permissions required for enhanced mode. If migrating from another client, check your ports and rule overrides.
For users who want desktop policy management and log views. Both links currently point to the same x64 package, so Apple Silicon users should check compatibility before installing. System proxy and TUN are different ways to route traffic; when troubleshooting, test with just one enabled.
The desktop and mobile versions have similar workflows, making this a good fit for existing FlClash users. The current download is AMD64; the link label does not guarantee native Apple Silicon support. After importing your subscription, recheck the mode, DNS, and system proxy settings.
An archived installer for users who rely on the legacy menu bar workflow. The client is no longer maintained, and both links currently point to an x86_64 file. New macOS permissions or subscription fields may not be compatible. For a new installation, start with a maintained client.
| Check | Instructions |
|---|---|
| macOS version | Use a supported macOS release. Minimum version requirements vary by client; check the installer or app documentation before installing. |
| Chip architecture | Apple Silicon uses ARM64; Intel uses x64. Some downloads currently provide x64 packages only. |
| Install location | Move the app to Applications before launching it. Don’t run it long-term from a mounted DMG. |
| System permissions | Grant network or service permissions as needed. Check the source if you see a security warning; don’t disable system security protections globally. |
MOBILE / ANDROID
Most recent phones use arm64-v8a. Older devices may use armeabi-v7a; if you’re unsure, choose the universal Clash Meta for Android package. After downloading the APK, grant install permission only to the source you’re using. Android will ask for VPN permission when you connect.
A good choice for everyday phone use. Import your subscription, select a policy group, and start the connection. Approve Android’s VPN prompt on first launch. If the connection drops when the screen is locked, adjust the app’s battery or background settings as needed.
Includes ABI-specific and universal packages for users who want explicit control over configuration and runtime mode. After updating a subscription, make sure the latest configuration is enabled. App-based routing and rule-based routing work differently; verify the target app after changing either one.
A good fit for users already running FlClash on other devices. Mobile connections use Android’s VPN service, which can be occupied by another VPN app. To troubleshoot, stop other VPNs first, then check your subscription nodes, routing mode, and DNS settings.
For users who already have a Surfboard-compatible configuration. Its configuration format differs from Clash YAML, so a Clash subscription can’t be imported as-is. Before downloading, check whether your provider offers the right format to avoid finding out after installation that the configuration isn’t supported.
| Check | Instructions |
|---|---|
| System and ABI | Choose a package for your device’s Android version and ABI. Check the installer for the minimum Android version. |
| Install permission | Follow Android’s prompt to allow installs from the current source. You can revoke that permission for the source after installation. |
| Connection permission | A VPN permission prompt appears the first time you connect. If another VPN is installed, check which app currently controls the connection. |
| Background operation | Check battery restrictions and auto-start settings only if Android interrupts the connection. You don’t need to change every permission at once. |
MOBILE / IOS
Find the app in the App Store and check its listing before installing. Refer to the listing for the current iOS requirements, compatible devices, and other details. After installation, add a configuration and follow the system prompt to allow a VPN connection.
After installing from the App Store, add a subscription or compatible configuration in the client. The first time you connect, iOS will ask to add a VPN configuration. Approve it, then return to the app and check the connection status. If another VPN is connected, disconnect it before testing.
If you can import a subscription but apps still can’t connect, check the selected policy and rule mode instead of reinstalling. Configuration updates, node selection, and system permissions are separate steps; checking them one at a time makes issues easier to pinpoint.
| Check | Instructions |
|---|---|
| macOS version | Check the app’s App Store listing for its current iOS version requirements and supported devices. |
| Install source | Open the app listing using the App Store link above, confirm the app name, and install. |
| VPN permission | Allow the app to add a VPN configuration when you connect for the first time. An existing VPN connection may affect your test. |
| Prepare a configuration | Have a valid subscription URL or compatible configuration ready. After importing it, check that the policy groups and nodes appear. |
DESKTOP / LINUX
If you have a desktop environment, start with a GUI client. Debian, Ubuntu, and similar distributions typically use DEB; RPM-based distributions use RPM. Run uname -m to check your architecture. Packages in this section are AMD64; for ARM servers, see the core downloads.
For managing subscriptions, policies, and logs on a Linux desktop. Install local packages with your distribution’s package manager to handle dependencies and keep an installation record. The desktop system proxy only affects apps that honor it; check proxy settings separately for terminals and containers.
A good fit for users on DEB-based desktop distributions who want a similar workflow across devices. Launch it in your user session after installation and import your configuration. If you need TUN, follow the client’s permission instructions; don’t run the entire desktop as root just to avoid granting the required permissions.
| Check | Instructions |
|---|---|
| Desktop environment | GUI clients need an available desktop session and the required runtime dependencies. For headless servers, use the core instead. |
| Architecture | If uname -m returns x86_64, choose an AMD64 package. aarch64 is ARM64; don’t use the x64 packages in this section. |
| Package manager | DEB and RPM packages aren’t interchangeable by changing the file extension. Choose the format that matches your distribution and dependencies. |
| Network permissions | TUN, policy routing, and services may require additional permissions. Record your existing DNS and routing settings before making changes. |
HEADLESS / SERVER / ROUTER
This section is for users who manage their own configurations on servers and routers. The core parses configurations, matches rules, and establishes connections; it doesn’t provide a complete desktop management workflow. For everyday use, choose a GUI client above to avoid managing services, permissions, and configuration directories manually.
| System | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · Run from the command line · x64 | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · Native ARM64 | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ · Extract and run | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ · Extract and run | Download Apple Silicon GZ |
| Linux | AMD64 | DEB · Install with a package manager | Download AMD64 DEB |
| Linux | AMD64 | GZ · Deploy the binary manually | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM devices | Download ARM64 GZ |
| Linux | ARMv7 | GZ · Compatible 32-bit ARM devices | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ · Soft-float environments | Download MIPS GZ |
| Check | Deployment requirements |
|---|---|
| Configuration directory | Prepare a readable configuration file and a writable working directory. Resolve relative paths from the working directory used when the process starts. |
| Permissions and services | Standard proxy listeners and TUN require different permissions. Run with the minimum permissions needed, and specify the configuration directory in the service startup options. |
| Ports and firewall | Check for port conflicts before starting. Allow LAN access only from trusted source subnets, and don’t expose the management interface directly. |
After extracting the archive, check the startup help and test your configuration before setting up a service. See Headless Linux and systemd deployment guide →
AFTER DOWNLOAD
A successful launch only confirms that installation is complete. Check the configuration first, then proxy routing, and finally the app or service you want to reach.
01 / CONFIGURATION
Open the Configuration, Profiles, or Subscription page and add a remote subscription or local file. After it downloads, confirm the profile is selected and its policy groups contain nodes. If YAML parsing fails, check the reported field and line number instead of repeatedly importing the same file.
02 / PROXY MODE
On desktop, test the system proxy with a browser first, then enable TUN if needed. On mobile, approve the VPN permission prompt. A common mixed-port setting is 7890, but check your current configuration and client overrides; the default value alone doesn’t confirm that the app is listening correctly.
03 / VERIFICATION
Select a policy and visit the target service, then check the connection or logs page for the matched rule and policy. Direct connections are expected when using rule mode. Change one setting at a time so you can identify the cause if something breaks.
PACKAGE QUESTIONS
Quick guidance on choosing an installer, updating, and making your first connection. For more detailed configuration help, visit the Help Center.
For Windows, macOS, Android, and iOS, start with Clash Plus; for Linux, start with Clash Verge Rev. If you already have a workflow, choose a familiar client that is still maintained. Installers include the app only—you’ll also need a compatible subscription or configuration file.
Check your processor and system architecture in system information. x64 and AMD64 refer to the same architecture; ARM64 is 64-bit ARM. On Android, arm64-v8a is usually the right choice for newer devices, while older 32-bit devices may need armeabi-v7a. Choose universal if you’re unsure. On macOS, check the downloaded package’s actual architecture rather than relying on your device’s name.
Some clients currently map both links to the same x64 file. The link label doesn’t mean the file is a native ARM build. Apple Silicon users should verify the file’s architecture and check whether Rosetta is needed. For a native ARM build, choose a client that provides one.
Open the client and add a remote profile from its Configuration, Profiles, or Subscription page. Paste your subscription URL and update it. Once the profile is loaded and a usable node appears in a policy group, enable the system proxy first, then configure TUN if needed. Subscription URLs are sensitive—don’t include them in public screenshots or support posts.
For the same client, you can usually quit the app and install the update over the existing version; follow the installer’s instructions. Back up your configuration, rule overrides, and local settings first. When switching clients, recheck subscription compatibility, the mixed port, and TUN settings. Disable the old client’s service components to prevent both apps from controlling the system proxy.
If a download fails, check your browser’s download history, available disk space, and network connection, then reload the page and try again. If the app installs but won’t connect, check separately that the profile loaded, a policy is selected, and the system proxy or TUN is active. Don’t disable certificate verification to troubleshoot connection issues. See the Help Center for more guidance.