Choose a GUI client for your operating system, then check your processor architecture. Set up subscription imports, automatic updates, and rules after installation.
Clash Resource Hub brings together downloads and guides for Clash ecosystem clients. Features, licensing, and system support vary by project; check each project’s documentation.
Choose your operating system first. The main button on each card links to the standard installer; secondary buttons offer other architectures or package formats.
The GUI clients here offer common x64 installers. For first-time use, install one client and import your configuration; there’s no need to run multiple proxy apps at once. Multiple clients can conflict when they compete to control the system proxy or use the same listening port. If you already use another client, export your configuration and overrides before trying a new setup.
For importing configurations and managing proxies on desktop. Start with the x64 installer, then import your subscription in the configuration settings and make sure it’s selected. Updating subscriptions and updating the client app are separate actions.
clashplus.io
For desktop users who work with subscriptions, rules, and service mode. After installing, check that your configuration loaded before setting the system proxy. If you need TUN, install or enable the service as prompted by the client; elevated permissions aren’t a universal fix for every issue.
A cross-platform GUI client for a consistent experience on desktop and mobile. Use the installer for a standard setup, or choose the archive if you prefer to manage the app directory yourself. Extract the archive fully before running the app; it isn’t installed just because it’s inside a ZIP file.
A Clash ecosystem client for desktop. Before importing an existing YAML file, check which fields the core supports and how the client handles overrides. UI settings may not be stored in the subscription file, so review your ports, system proxy, and DNS options after migration.
An archived client for reproducing legacy setups and migrating configurations. For new installations, consider one of the maintained clients above. The older core may not recognize newer protocols or configuration fields; this download’s availability doesn’t mean its capabilities will expand with subscription updates.
| Check | What to look for |
|---|---|
| OS support | Check your Windows version under Settings > System > About. Refer to the selected client’s release notes for its minimum version requirement. |
| Processor | Installers in this section are primarily for x64. On Windows ARM devices, check app emulation compatibility; an x64 package is not a native ARM64 build. |
| Permissions | Standard proxy settings and virtual network adapters have different permission requirements. Read the client’s prompts before enabling a service or TUN. |
Open About This Mac from the Apple menu to check your chip, then choose the Apple Silicon or Intel download. After downloading the DMG, open it, drag the app to Applications, and launch it from there. Follow system prompts to review any system extensions, network permissions, or background services.
Downloads are listed for Apple Silicon and Intel. After installation, import your configuration and check the system proxy status. When switching clients, disable the old app’s system proxy and background services first to prevent both apps from changing your network settings.
clashplus.io
Manage desktop configurations, rules, and subscription updates. Both architecture options currently link to the x64 DMG in the download listing, so Apple Silicon users should check compatibility. Opening the client doesn’t mean the configuration is active; select it and check the proxy mode.
For users who want a similar experience across desktop and mobile. The current Mac download is labeled AMD64; Apple Silicon users should check the requirements for running it through translation. After importing a mobile configuration, review the desktop system proxy, listening ports, and launch-at-login settings.
An archived download for legacy configurations and workflows. The current file is x86_64, not a native ARM build. Before migrating to another client, back up your local configuration and check how the new core handles DNS, rule resources, and override fields.
| Check | What to look for |
|---|---|
| Chip | Apple M-series chips use Apple Silicon; Intel chips use x64. Check the architecture of the actual download. |
| macOS version | Minimum macOS requirements vary by client and release. Check the project documentation before installing. |
| Install location | Copy the app to Applications before running it. Follow system prompts to grant network permissions and authorize services. |
Most recent phones use ARM64, but check the ABIs supported by your device. 32-bit systems and some older devices need the ARMv7 package; if you’re unsure, use the client’s universal package. On first launch, you’ll typically be asked to approve a VPN connection. This allows the app to handle system traffic; it doesn’t import a subscription.
ARM64 Android download. After installing, import and select your subscription, then connect. If the app stops working when the screen locks, check background activity and battery settings first rather than repeatedly reinstalling it.
clashplus.ioAvailable packages include ARM64, ARMv7, and universal builds. The universal package supports multiple ABIs and is typically larger; if you know your device’s architecture, download the matching build. A local YAML file and a remote subscription are maintained differently: local files don’t receive remote updates automatically.
The mobile and desktop apps offer similar GUI workflows. ARM64 is the usual choice; check ARMv7 support on older systems, and confirm whether an emulator uses x86_64. Android allows only limited VPN concurrency, so disconnect other apps that handle network traffic before testing.
An Android proxy client with a universal installer. Its configuration format isn’t interchangeable with Clash YAML. Before importing, check whether your subscription provider offers a format supported by Surfboard, then review its rules and policy settings. Changing the file extension alone won’t convert the configuration.
| Check | What to look for |
|---|---|
| OS and ABI | Check each client’s documentation for its minimum Android version. An ARM64 processor doesn’t guarantee that the system provides a 64-bit runtime. |
| Installation permissions | Follow the system prompt to allow installs from your download source. You can tighten the permission again after installation. |
| Background activity | If the system stops the connection, check background restrictions, battery optimization, and other VPN apps—not just the subscription URL. |
Open the app’s store listing on your device to check system compatibility, app details, and current availability. After installation, import a supported configuration, then follow the system prompts to add a VPN configuration. If you use another app to route network traffic, disconnect it before testing.
Install the app and manage updates through the App Store. On first use, check your configuration source, import format, and connection permissions. Automatic subscription updates depend on the client’s settings; an App Store app update doesn’t set them up for you.
clashplus.io| Check | What to look for |
|---|---|
| Compatibility | Check the system requirements and supported devices listed on the App Store page. |
| Connection permissions | Follow the system prompts to add a VPN configuration. After connecting, test rules and DNS behavior with real requests. |
| Configuration source | Use a compatible configuration you’re authorized to access. App updates and subscription updates are separate. |
Check your distribution’s package manager, then confirm your CPU architecture. GUI packages in this section are primarily for AMD64 and require a desktop session. For remote servers, containers, and routers, don’t choose a desktop installer based on its file extension alone; see the core downloads below for packages by architecture.
Available in DEB and RPM formats. Let your system package manager handle dependencies during installation. After launch, check the desktop tray, configuration loading, and system proxy settings. A GUI launch failure is different from a proxy connection failure, so first confirm the app is running correctly.
This section offers an AMD64 DEB for compatible Debian-based desktop systems. Desktop proxy settings may not apply to terminal apps, which may need proxy environment variables of their own. For system-wide traffic routing, check TUN permissions and routing configuration.
| Check | What to look for |
|---|---|
| Distribution | Debian, Ubuntu, and similar distributions generally use DEB; distributions with RPM package management use the corresponding RPM package. |
| Architecture and dependencies | Run uname -m to check your architecture. Packages here are for AMD64; see the project documentation for GUI dependencies and system library requirements. |
| Traffic routing | System proxy settings, terminal environment variables, and TUN are separate options. After setup, check that each target app uses the expected configuration. |
x64, x86_64, and AMD64 usually refer to the same class of 64-bit desktop architecture; they aren’t limited to AMD processors. ARM64 uses a different instruction set, while ARMv7 is common on older 32-bit devices. Match the architecture first, then choose the package format—EXE, DMG, APK, DEB, or RPM. Don’t choose based on the OS name alone.
Some download options may share the same installer, so an architecture option on a card doesn’t guarantee native support. Before installing, check the actual filename, app documentation, and system compatibility. If the app won’t run, check the architecture and OS version first; don’t change your proxy settings as a first step.
A client installer updates the GUI, runtime components, and app features. A subscription update fetches configuration, proxy resources, or rules. Reinstalling the app doesn’t replace importing a subscription, and may not fix an expired subscription URL, an incompatible format, or a remote access issue.
Before upgrading, save your subscription source, local YAML, overrides, and rule resource settings. Note your ports, DNS, and TUN options. Test with a copy before switching clients, and move over only after confirming that the configuration loads and the rules work as expected. See the subscription import guide for setup steps and the full guide for configuration fields and maintenance.
For users managing their own server, router, or runtime environment. Most users should start with a GUI client above.
The core reads configuration, applies rules, and handles connections; it doesn’t include a full desktop interface for managing settings. Before deployment, prepare your own configuration directory, startup method, logging, and permissions. On routers, also check the firmware architecture, runtime libraries, and transparent proxy setup. Downloading the right architecture is just the first step—it doesn’t configure DNS interception or LAN routing for you.
| System | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP, x64 command-line environment | Download AMD64 ZIP |
| Windows | ARM64 | ZIP, Windows ARM64 environment | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ，Intel Mac | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ, Apple M-series chips | Download ARM64 GZ |
| Linux | AMD64 | DEB, Debian-based package management | Download AMD64 DEB |
| Linux | AMD64 | GZ, executable for custom deployments | Download AMD64 GZ |
| Linux | ARM64 | GZ, 64-bit ARM environment | Download ARM64 GZ |
| Linux | ARMv7 | GZ, compatible 32-bit ARM environment | Download ARMv7 GZ |
| Linux | MIPS soft-float | GZ, check endianness and firmware ABI | Download MIPS GZ |
What to know about installers, app updates, and importing configurations.
For everyday desktop and mobile use, start with a GUI client. Import your subscription in its configuration settings and manage updates there. The Mihomo core is for users who want to configure startup options, manage services, and handle network traffic themselves—typically on servers, routers, or custom setups.
Check your processor architecture in your system information. Most Intel and AMD desktop CPUs use x64 or AMD64; Apple Silicon uses ARM64. On Android, also check which ABIs your system supports. ARMv7 is a different architecture from ARM64, so don’t choose between them based on the similar names.
Save your subscription source, local configuration, overrides, and rule resource settings. Note your system proxy, TUN, DNS, and port options. Use the client’s export or backup feature when available. Before switching clients, import your configuration and check each setting.
The installer provides the client app, not a ready-to-use proxy configuration. In the configuration settings, import a Clash YAML file you’re authorized to use or a compatible subscription URL. Select the configuration, then check the rule mode and system proxy. Subscription URLs may contain access credentials, so don’t share them publicly.
Debian- and Ubuntu-based distributions generally use DEB packages; distributions that use RPM package management generally use RPM packages. Desktop users should start with a GUI client. For headless systems or custom services, choose a Mihomo core archive that matches your architecture.
Archived downloads are provided for reproducing legacy setups and migrating configurations; they don’t receive ongoing feature or compatibility updates. For a new installation, choose a maintained client. When migrating, check that the new core supports your protocols, rules, and DNS fields, and keep a copy of your original configuration.