Client Downloads · Choose Your System Architecture
Choose your operating system, then check the processor architecture.
After installation, continue with subscription setup and system proxy settings.
Browse the options for your platform in order. The recommended card offers a common starting point, but you can choose another client if you prefer. Enable the system proxy or TUN in only one client at a time to avoid conflicting settings.
Check your system type under “Settings → System → About.” Desktop downloads in this section are primarily x64; x64 does not mean native ARM64 support. Windows on ARM users should first confirm application compatibility and client component requirements, then test the installation.
Standard system proxy and TUN have different permission requirements. Import a subscription and test the system proxy first. Explore TUN and service mode only if apps ignore the system proxy or you need to route more connections. Quit any running client before installing, upgrading, or uninstalling.
| Item | Requirements and steps |
|---|---|
| System | Use Windows 10 or 11 while it continues to receive security updates. Check the installer for the client’s specific minimum requirements. |
| Processor | This section mainly offers x64 installers. Confirm that your system is 64-bit before running the installer. |
| Network permissions | Installing a service, virtual network adapter, or firewall rule may require administrator approval. Make sure the system proxy uses the correct listening port. |
A good starting point for importing a subscription, choosing a proxy group, and setting up the system proxy. After installation, open the configuration screen, import and enable a valid subscription, then check the connection and logs. If migrating an old setup, keep a copy of your custom rules instead of overwriting the new client’s settings folder.
clashplus.io ↗
For users who want to manage configurations, rules, and core settings from a desktop interface. Check installation permissions before enabling service mode. After refreshing a subscription, make sure the selected configuration is still the one you expect. Put custom changes in an override or merge section so a subscription refresh doesn’t erase them.
For users who want a similar experience across desktop and mobile. If this is your first install, choose the installer. Extract the ZIP archive fully and launch the app from a fixed folder—don’t run it from within the archive utility. After quitting, check that the system proxy has been restored.
Another option for Windows desktop users. After importing a configuration, confirm that the core starts correctly before setting the proxy mode. Clients differ in UI preferences, override methods, and data locations; when migrating, import subscriptions and local rules separately.
Kept for migrating existing setups and referencing older configurations. Archived software should not be expected to support new protocols, operating systems, or configuration fields. For a first install, choose a client listed above. Before continuing with a legacy setup, consider system compatibility and maintenance risks.
Open the Apple menu and select “About This Mac” to check whether your device has an Apple chip or an Intel processor. Clash Plus offers separate arm64 and x64 packages. Some other clients currently link both architecture options to the same x64 file; Apple silicon devices need Rosetta to run it.
Open the downloaded DMG, then drag the app into Applications and launch it from there. Review prompts for network extensions, helper tools, or Keychain access in the context of the action the client is performing. Authorization steps vary by client, so you may not see every prompt during each installation.
| Item | Requirements and steps |
|---|---|
| macOS version | Check your macOS version against the app’s requirements. If the installer reports that your OS is too old, don’t keep retrying the same file. |
| Chip architecture | On Apple silicon, choose a native arm64 package when available. x64 packages typically need Rosetta on Apple silicon. |
| Permissions | Follow the prompts in “System Settings → Privacy & Security” and any network-related settings. Approve requests only from apps whose source you’ve verified. |
Choose arm64 for Apple silicon and x64 for Intel Macs. After installation, import a subscription, make sure the configuration loads, then enable the system proxy. Quit the app before updating, and keep your local rules and subscription source so you can restore settings if compatibility issues arise.
clashplus.io ↗
For desktop users who want a GUI for managing subscriptions and overrides. Both download links currently point to an x64 DMG. The Apple silicon link is not a native ARM build; check that Rosetta and the app are compatible. Follow the system prompts to authorize service components during installation.
For users already familiar with FlClash. The Apple silicon and Intel links currently use the same amd64 file; Apple silicon devices must run it in x64 compatibility mode. After launching, test the configuration before setting up the system proxy and background operation.
Kept for reference and migration from older setups. The current download is x86_64, so Apple silicon devices need compatibility mode. Support for newer systems and core configuration fields may be limited; for a first install, choose a maintained client.
Most recent Android phones use arm64, but a 64-bit processor doesn’t guarantee a 64-bit app environment. Check your device’s system information before choosing a package. If Android reports that the app is incompatible, check the architecture and OS version instead of repeatedly trying same-named apps from different sources.
After installation, you’ll usually need to approve the system VPN connection request. Android generally allows only one active VPN service, so other VPNs or network-filtering apps may conflict. Allowing background activity can help prevent interruptions during subscription updates or network changes; adjust battery restrictions as needed.
| Item | Requirements and steps |
|---|---|
| App architecture | arm64-v8a is for 64-bit ARM; armeabi-v7a is for 32-bit ARM. If you’re unsure, try the universal package. |
| Install source | Temporarily allow installs from the browser or file manager you’re using. You can revoke this permission after installation. |
| Connection permissions | Approve the VPN request on first connection. Also check background restrictions, Private DNS, and other VPN services. |
For phones and tablets running a 64-bit ARM system. After installation, import a subscription, select the configuration, approve the VPN request, and test a browser connection. Subscription URLs often contain personal access credentials; hide sensitive parameters when sharing screenshots or logs.
clashplus.io ↗Offers packages for multiple architectures, useful when you need to match the app to your device. Choose the universal build if you’re unsure of the architecture; it’s usually larger. After importing a subscription, confirm that the configuration is selected—a configuration name alone doesn’t mean the proxy is running.
For users who want an interface similar to the desktop client. After installation, check the configuration format and update URL before connecting. If the connection drops when the screen locks, check background activity, battery optimization, and auto-start restrictions, changing one setting at a time.
For users with an existing Surfboard-compatible configuration. Surfboard doesn’t use Clash YAML as its native configuration format, so arbitrary Clash subscriptions aren’t necessarily compatible. Check the subscription format and supported protocols before downloading.
Get Clash Plus for iPhone or iPad from the App Store. Check the app name, device compatibility, and system requirements on the store page before installing. Requirements may change; check the current listing rather than relying on your device model alone.
For your first session, import a compatible subscription and approve the system VPN configuration request. A saved configuration isn’t the same as an active connection; check both the client and system status after connecting. Treat configuration URLs as personal data and use a trusted method when transferring them to another device.
| Item | Requirements and steps |
|---|---|
| Device requirements | Check the iOS / iPadOS version and device compatibility shown on the App Store listing. |
| Download | Use the App Store button below to open the app listing. The official site is clashplus.io. |
| First connection | Get a valid subscription, import and select a configuration, then follow the system prompt to add a VPN configuration. |
The App Store handles installation and app updates. After opening the app, confirm that the subscription imported and the configuration is selected, then connect. App updates and subscription updates are managed separately; updating the app won’t replace your subscription service or extend its validity.
clashplus.io ↗Choose a package format that matches your distribution. Debian, Ubuntu, and their derivatives typically use DEB; Fedora and similar distributions commonly use RPM. These are different package formats, not alternatives based on file size. Desktop packages in this section target amd64 / x86_64.
GUI clients need a compatible desktop session and runtime dependencies. For headless servers, routers, or devices with a different processor architecture, see the Mihomo core section. If the tray icon doesn’t appear after installation, check desktop tray support; its absence doesn’t necessarily mean the core failed to start.
| Item | Requirements and steps |
|---|---|
| Package format | Use DEB with Debian-based distributions and RPM with compatible RPM-based distributions. Use your system package manager to handle dependencies. |
| Processor | This section provides amd64 / x86_64 desktop packages. Check your machine’s architecture with uname -m. |
| Network routing | A desktop system proxy doesn’t cover every app. TUN requires additional permissions and correctly configured routes and DNS. |
For managing subscriptions and proxy settings on a desktop. Choose the package format for your distribution and let the package manager report missing dependencies. If the app won’t start, launch it from a terminal to see errors; don’t try to work around dependency issues by repeatedly installing different package formats.
For Debian-based desktop systems and users already familiar with FlClash. After installation, import a configuration and check the logs before choosing the desktop system proxy or TUN. If another proxy service is running, stop it first and check for port conflicts.
For servers, routers, and self-managed proxy services. The core loads configurations, matches rules, and establishes connections; it doesn’t include a full desktop setup wizard. Most desktop and mobile users should choose a GUI client above and won’t need to download the core separately.
Before downloading, check your OS, CPU architecture, and runtime environment. ARMv7, ARM64, and MIPS are not interchangeable. MIPS also depends on byte order and floating-point ABI, so use the softfloat files below only when they match your device. Don’t guess the architecture based on a router’s appearance or brand.
| System | Architecture | Format | Package |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 |
| Windows | ARM64 | ZIP | Download ARM64 |
| macOS | Intel / AMD64 | GZ | Download Intel |
| macOS | Apple Silicon / ARM64 | GZ | Download Apple Silicon |
| Linux | AMD64 | DEB | Download AMD64 DEB |
| Linux | AMD64 | GZ | Download AMD64 GZ |
| Linux | ARM64 | GZ | Download ARM64 |
| Linux | ARMv7 | GZ | Download ARMv7 |
| Linux | MIPS softfloat | GZ | Download MIPS softfloat |
Keep the core executable and configuration path clearly identified. Run mihomo -t -f config.yaml to check that the configuration loads before starting the service. Passing validation doesn’t guarantee that subscription outbounds work or that system routes and DNS are configured correctly.
In production, use a restricted account, traceable logs, and a clear service restart procedure. Keep the original configuration and a rollback copy before replacing the core. Test protocol compatibility and rule parsing before switching the persistent service. For platform-specific installation and permissions, see the user documentation.
Use the subscription manager to add the full URL, or import a local YAML file. The sample URL https://example.com/sub?token=xxxx is for format illustration only. A web page URL, login page, or Base64-encoded node list may not be importable as a Clash configuration; check the format provided by the source first.
After the subscription downloads, select the configuration and check the outbound selected in its proxy group. Rule mode is a good starting point for everyday routing. Global mode changes outbound selection; it can’t fix an invalid subscription. If something goes wrong, keep the original configuration and change one setting at a time to pinpoint the cause.
On desktop, enable the system proxy; on mobile, confirm the VPN is connected. Test a regular website and the service you want to reach, then check the connection list to see which rules matched. If only one app is affected, look into its proxy settings or TUN rather than changing all your network settings at once.
First determine whether the issue is choosing a package, installing it, or connecting. A successful download only means the file was saved; loading a configuration and routing network traffic are separate steps.
For Windows, macOS, Android, and iOS, start with Clash Plus; for Linux, consider Clash Verge Rev. Check your OS and processor architecture before downloading. Clients do not include a usable subscription, so prepare a compatible configuration before connecting.
arm64 is for 64-bit ARM processors; x64 or amd64 is for 64-bit Intel and AMD processors. Android’s armeabi-v7a targets 32-bit ARM devices. Universal packages typically include multiple architectures and are larger. Some Apple silicon download links for macOS currently point to x64 compatibility packages that require Rosetta—not native ARM builds, despite the link label.
The installer only provides the client. Import a valid subscription or local configuration, enable it, and select an available outbound in the proxy group. Then turn on the system proxy or enable TUN if needed. If you still can’t connect, check the subscription download, port conflicts, system permissions, and application logs.
Check the download source, file type, and system architecture, and read the warning carefully. On macOS, review blocked apps in Privacy & Security; on Android, temporarily allow installs from the current source; on Windows, open the security warning details. Don’t leave system security features disabled just to install an app.
Keep your subscription URL, local YAML files, custom rules, overrides, and any proxy settings you may need to restore. Quit the old client normally before installing the new one. When switching clients, reimport the original subscription instead of overwriting the entire configuration folder; databases and UI settings may not be compatible.
Usually not. GUI clients generally bundle the core or include a core manager. Standalone Mihomo packages are mainly for servers, routers, and self-managed services, where you’ll also need to prepare the configuration, permissions, and startup method. If you already use a GUI client, update the core through its built-in tools.
Troubleshoot Subscription Updates, Connection Issues, and Logs →