CLIENT PACKAGES
Choose a graphical client by operating system, or a command-line core by architecture.
Check your operating system and processor, then choose a package below. Clash Plus is listed first where available; older clients are clearly marked as archived.
01 / GRAPHICAL CLIENTS
Each download button lists the package format. See the platform guide for installation steps.
This section offers x64 graphical clients for most Intel and AMD desktop devices. Windows on ARM users should first check the app’s compatibility requirements. The Mihomo ARM64 core below is not a graphical client installer.
A good starting point for setting up a subscription-based workflow. Install the desktop client, add a subscription or local configuration, then choose a proxy group. On your first connection, check the system proxy settings to avoid conflicts with an older client.
For desktop users who manage subscriptions, configuration overrides, and mihomo settings. Enabling TUN may require a service and additional permissions; test the subscription with the system proxy first, then enable virtual network capture step by step to make troubleshooting easier.
For users who want a similar workflow across desktop and mobile. Import a subscription after installation, then check the rule mode and proxy group. Compatible configurations can be reused across devices, but system proxy, startup, and network permissions must be set up separately on each device.
Desktop tools for configuration and proxy management. When importing an older subscription, first confirm that its fields are compatible with the selected core. Save custom rules using the client’s supported override feature to avoid losing local changes when the subscription updates.
The archived download is for recreating an older setup or exporting an existing configuration. Choose a maintained client for new installations. Older cores have limited support for newer protocols and rule fields; a successful import doesn’t guarantee the same connection behavior as a current client.
| Check | What to look for |
|---|---|
| Windows version | Use a supported Windows 10 or 11 setup where possible. Check each client’s release notes and installer for its minimum version. |
| Processor | Installers in this section are x64 / AMD64. Find your system type under Settings → System → About. |
| Runtime components | Some clients depend on components such as WebView2. If a window is blank or the app won’t start, check the installer prompts and app logs first. |
| Network permissions | System proxy and TUN services have different permission requirements. Follow the system prompts when installing a service or virtual network adapter. |
Check your chip under About This Mac. Apple Silicon uses ARM64; Intel uses x64. Some architecture links currently share an x64 package, so check the notes and actual filename before downloading.
Choose a DMG for your chip, open it, and move the app to Applications. Then launch it and import a subscription. Follow system prompts when enabling the system proxy or network extension for the first time. Product information is available at clashplus.io.
For managing subscriptions, configuration overrides, and rules in one place. Both chip links currently point to the same x64 DMG; Apple Silicon may require Rosetta. After importing your configuration, check that the system proxy or TUN is actually enabled.
Use alongside FlClash on other devices, but import the configuration separately on each one. Both links currently offer an AMD64 DMG; Apple Silicon users should check compatibility requirements. Quit the app before upgrading to avoid installation conflicts.
Kept for older menu bar workflows and configuration migration. Both architecture links share an x86_64 DMG; this is not a native ARM build. When moving to another client, restore rules and proxy settings separately rather than copying the entire app data directory.
| Check | What to look for |
|---|---|
| Windows version | Minimum macOS versions vary by client build. Check the release notes before installing; a mountable DMG does not guarantee compatibility. |
| Chip type | If About This Mac shows an Apple chip, choose a native ARM64 package where available. For an Intel processor, choose x64. |
| Compatibility | Apple Silicon may require Rosetta to run x64 / AMD64 packages. The cards above identify links that currently share a package. |
| System permissions | Network services, accessibility tools, and TUN each need different permissions. Follow the client’s prompts without disabling system security features. |
Most recent phones use ARM64. For older devices, check whether they support only 32-bit apps. When installing an APK, grant install permission only to the file manager or browser you’re using to open it. Approve VPN access when connecting.
ARM64 package available. After installation, add a subscription and select a configuration. Approve Android’s VPN request when connecting for the first time. If background connections keep dropping, check battery optimization, background activity limits, and the system’s app sleep settings.
Choose ARM64 or ARM based on your device’s ABI. If you’re unsure, the larger universal package may work, but check the installer’s compatibility prompt. After importing a subscription, select the configuration and start the connection; saving the subscription URL alone isn’t enough.
ARM64 and ARM APKs available. A good fit for users already running FlClash on desktop who want a similar configuration workflow. Mobile VPN routing differs from the desktop system proxy. If connections fail, check VPN status and app scope settings first.
For Android users with an existing compatible Surfboard configuration. This is not a substitute for a client that can read arbitrary Clash YAML files; check that your subscription provides the right format before downloading. If it only provides Clash configuration, choose a compatible client above.
| Check | What to look for |
|---|---|
| Windows version | Minimum Android versions vary by app build. The system installer checks version and package compatibility. |
| Processor ABI | arm64-v8a is 64-bit ARM; armeabi-v7a is 32-bit ARM. Universal packages are still limited by the system and app’s supported versions. |
| VPN permission | System approval is required for the first connection. Multiple VPN apps in the same user profile may replace one another, so run only one while testing. |
| Background activity | Long-running connections need appropriate background activity permissions. Strict battery restrictions can interrupt connections when the screen is locked. |
Install Clash Plus from the App Store. Check the store listing for current system compatibility. After installation, prepare a subscription URL or a supported configuration file, then import it and approve VPN access.
The App Store manages installation and updates. After importing a subscription, select a configuration before connecting via VPN. If another VPN is active on your device, disconnect it first. See clashplus.io for app details and product information.
| Check | What to look for |
|---|---|
| Compatibility | Check the App Store listing for the minimum iOS version and supported devices. There’s no need to choose a processor-specific installer. |
| Installation and updates | Get the app from the App Store, which also manages future updates. Keep your subscription URL and important local configuration before updating. |
| Connection permissions | Allow the VPN configuration the first time you connect. Organization-managed devices may restrict network extensions. |
| Configuration setup | Prepare a supported subscription or configuration format. Before sharing screenshots or logs, hide private parameters in your subscription URL. |
This section offers AMD64 graphical clients for desktop Linux. Choose DEB for Debian- and Ubuntu-based distributions, or RPM for RPM-based ones. For headless servers and routers, see the standalone core packages below.
AMD64 DEB and RPM packages available. Use your distribution’s package manager to handle dependencies. If the GUI won’t start, run the app from a terminal to inspect errors. TUN requires service and network-device permissions; don’t run the entire desktop app as root to work around authorization.
For Debian-based desktop users who want a consistent configuration workflow. This is an AMD64 DEB package. Whether the app can apply the desktop system proxy depends on its implementation; command-line tools may also need proxy environment variables configured separately.
| Check | What to look for |
|---|---|
| Distribution | DEB and RPM belong to different package management systems; changing the file extension won’t convert one to the other. Check installation output for distribution version and dependency details. |
| Architecture | The GUI packages here are AMD64 / x86_64. Run uname -m to check your system architecture. |
| Desktop dependencies | A working graphical session and the app’s dependencies are required. Wayland, X11, and tray support vary by desktop environment. |
| Permissions and networking | TUN requires the relevant device and network permissions. Containers, restricted hosts, and minimal kernel environments may not provide them. |
02 / COMMAND LINE AND SERVICE DEPLOYMENT
For server, router, and self-managed service deployments.
The core reads configuration, listens on proxy ports, and applies rules; it does not include a desktop subscription management interface. Most users should choose a GUI client above. Before deployment, check the operating system, CPU architecture, execution permissions, and configuration directory. GZ files usually need to be extracted first; install DEB packages with a package manager. For routers, also check firmware ABI, floating-point support, and available storage—not just the processor brand.
| System | Target architecture | File format | Download core |
|---|---|---|---|
| Windows | AMD64 / x64 | 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 |
03 / INSTALLATION AND MIGRATION
Installing the client is only the first step. Open the subscription or configuration page, paste a subscription URL you obtained and are authorized to use, and wait for it to finish loading. Then set that configuration as active. If import fails, check that the URL is complete and valid, and that its contents use a supported format. Don’t keep switching clients instead of checking the subscription itself; the same invalid URL is likely to fail everywhere.
Before migrating from an older client, back up local rules, subscription URLs, and overrides. Remote subscription updates may overwrite direct edits, so use the new client’s override or merge feature to preserve custom rules. Configuration directories, core files, and interface settings aren’t interchangeable; copying the entire data directory can bring over old ports, stale caches, and broken paths.
On desktop, start with the system proxy and test using a browser that follows system proxy settings. To route more apps, configure TUN using the platform guide. Mobile devices usually route traffic through the system VPN interface. Traffic capture and rule mode are separate settings: the former determines whether traffic enters the client; the latter determines how it’s routed. Rule mode is suited to everyday routing based on domains, addresses, and rule sets.
Run only one primary traffic-capture client while testing, and check for port conflicts. After quitting an old app, the system may still point to its stopped local proxy, leaving pages unable to load. Restore the system proxy settings before starting the new client. Avoid changing DNS, rules, ports, and TUN at the same time; changing several variables makes troubleshooting harder.
After connecting, check the client logs, selected proxy group, and actual app access. A running indicator only confirms that a process or service has started; it doesn’t prove the subscription is valid, DNS is working, or all apps are routed through the client. If something goes wrong, note the time and relevant error details, and remove private subscription parameters before sharing logs. Keep a restorable configuration backup before upgrading the client or core. Clean up the old setup only after confirming that basic access and custom rules work.
For platform-specific steps, see the installation guides for all platforms. For a focused walkthrough of import, connection, and testing, read the user guide. See the client comparison for differences in features and maintenance status.
04 / DOWNLOAD FAQ
For your first setup, choose a graphical client. It provides subscription import, proxy selection, logs, and system proxy settings. The Mihomo core parses configuration and routes traffic; it is better suited to server and router users who manage configuration files, services, and network permissions themselves.
Check your device’s processor or system type first. Intel and AMD desktop processors typically use x64, also known as AMD64; Apple Silicon and most recent Android devices use ARM64. Check both the processor architecture and operating system version before installing. Confirm the package against its actual filename and release notes.
The client installer and subscription service are separate. After installation, import a subscription or configuration file you obtained and are authorized to use, then choose a proxy group. An open app does not mean traffic is being routed through it. Check system proxy or VPN permissions, logs, and the actual connection.
Export or back up your subscription URL, local configuration, override rules, and app settings. Note the current port and traffic-capture mode, then quit the old client. When switching clients, don’t overwrite the entire data directory. Import your configuration first, then restore system proxy, TUN, and startup settings individually.
For some clients, both macOS architecture links currently point to the same x64 or amd64 package. A link label identifies the device choice; it does not guarantee a native ARM build. Apple Silicon may require Rosetta to run these packages. Check system prompts and the app’s release notes for compatibility details.
Archived packages are mainly for compatibility with older setups and configuration migration, and aren’t recommended for new installations. Unmaintained clients may not support newer protocols or configuration fields, and may be incompatible with newer systems. Back up your configuration before migrating, then test your subscription, rules, and traffic-capture setup in a maintained client.