CLIENT / PACKAGE / ARCHITECTURE
Choose an operating system, then check the architecture. Client installers and the Mihomo core are listed separately.
New to Clash? Start with Clash Plus for Windows, macOS, Android, or iOS; Linux users can choose Clash Verge Rev. For command-line deployments, choose a core instead.
Installation and subscription setup →01 / Client installers
Compare multiple clients for each platform. Installers provide the app; you’ll need to supply your own subscription or configuration to connect.
The GUI client installers below are for x64 systems. Check your system type under Settings → System → About. On ARM devices, confirm that your system can run x64 apps; these files are not native ARM64 builds.
A good starting point for a first Windows install. Import a configuration and choose a proxy group in the GUI, then enable the system proxy for your use case. Get a standard proxy connection working before trying network interception features that require additional permissions.
EXE installer · x64
Manage subscriptions, configurations, and routing rules. If you’re switching from another client, back up your overrides and local rules first, then migrate your subscription. The client’s generated configuration may differ from the original subscription file; if a reference fails, check the merged configuration.
EXE installer · x64
A good fit if you want a similar configuration workflow across devices. After installation, set up the system proxy on this device separately. Copying a configuration doesn’t transfer system permissions; check startup behavior and network interception settings again on the new device.
EXE installer · AMD64
Another option for managing desktop configurations. When importing an existing YAML file, make sure proxy group names match their rule targets. If the old client used custom overrides, distinguish standard core fields from options saved by the client interface.
EXE installer · x64
This archived client is provided for compatibility checks in existing setups. Its older core may not recognize newer configuration fields or protocols. For a new installation, choose one of the clients above. Keep a copy of your configuration before migrating; don’t overwrite your only copy.
Archived Windows installer
| Check | Requirement or selection | After installation |
|---|---|---|
| Processor architecture | GUI installers in this section are x64 / AMD64. On ARM devices, check compatibility before installing. | The app starts, and the core reports no architecture mismatch. |
| System environment | Check the selected client’s release notes for supported operating systems and runtime requirements. | If a runtime component is missing, install it as prompted by Windows, then restart the client. |
| Permissions and ports | Configure standard proxy mode separately from service modes that require elevated permissions. | Allow only one client to control the system proxy, and check for listening port conflicts. |
Open Apple menu → About This Mac to check your chip. Apple silicon uses ARM64; Intel Macs use x64. Quit any existing client before installing, keep your subscriptions and local configurations, then move the new app to Applications.
Separate DMG files are available for Apple Silicon and Intel. Choose the one that matches your chip, then follow macOS prompts to authorize the app on first launch. After importing a configuration, check the rule mode and proxy group before enabling the system proxy.
DMG · Separate ARM64 / x64 files
Manage desktop subscriptions and routing rules. Both chip links currently serve the same x64 file, so Apple Silicon users should check compatibility first. For a clean migration, import the original subscription before moving overrides over one at a time.
DMG · Current file is x64
A good fit if you want a similar configuration workflow on desktop and mobile. The Mac file on this page is AMD64, and both architecture links use the same file. After installation, check network permissions and proxy settings again; don’t reuse listening addresses from another device.
DMG · Current file is AMD64
Archived for reference on legacy Mac setups. The current download is x86_64, and this older client may not support newer configuration features. For a new setup, choose one of the clients above. When migrating an existing setup, note your current proxy port and configuration source.
Archived DMG · Current file is x86_64
| Check | Requirement or selection | After installation |
|---|---|---|
| Chip type | Use native ARM64 for Apple Silicon when available; choose x64 for Intel. | The downloaded file architecture matches your runtime environment. |
| macOS version | Check the app’s release notes and installer prompts for the minimum supported version. | macOS allows the app to open, and required permissions are granted. |
| Network settings | Quit the old proxy client before enabling the new system proxy. | After switching networks, check the proxy toggle and DNS instead of reinstalling the app. |
Check your device’s processor architecture before choosing an APK. Most newer ARM phones use ARM64; older 32-bit systems may need ARMv7. A 64-bit-capable processor doesn’t guarantee that the installed OS is 64-bit. If you’re unsure, consider the universal package.
This page provides an ARM64 APK. After installing and importing your configuration, approve the VPN connection when prompted. If battery management restricts background activity, check the app’s background permissions instead of repeatedly switching subscriptions.
APK · arm64-v8a
Choose from ARM64, ARM, and universal builds to match your device. After importing a configuration, enable the correct profile and check your proxy group. A VPN icon in the status bar means the tunnel is active; it doesn’t guarantee that every destination is reachable.
APK · Single-architecture and universal builds
Choose between ARM64 and ARMv7 builds. You can use similar configuration structures on phones and desktops, but local paths, listening addresses, and system-level controls must be set up separately. Multiple VPN apps usually can’t control the same connection at once.
APK · arm64-v8a / armeabi-v7a
Another Android configuration option. Before using it, check that your subscription provider supports its configuration format. Renaming a Clash YAML file to a Surfboard extension won’t convert it. Identify the format before migrating to avoid mistaking a parse error for a node issue.
APK · Universal build · Check configuration format
| Check | Requirement or selection | After installation |
|---|---|---|
| System architecture | Use arm64-v8a for ARM64; choose an ARM build for 32-bit ARM systems. Universal builds are an alternative. | The installer reports no architecture compatibility error. |
| Install permissions | In system settings, allow installs from the source you used to download the APK. | After installation, revoke source permission if you no longer need it. |
| Connection and background activity | Check each app’s OS requirements and approve the VPN permission prompt. | Check for conflicts with other VPN apps, background activity permissions, and battery settings. |
Check Clash Plus device compatibility, app details, and current pricing on the App Store. After installing, use a subscription or configuration you’re authorized to access, add the VPN configuration when prompted, then check your rules and proxy group selection.
Install and update the iOS app through the App Store. After importing a configuration for the first time, check that it’s enabled and that the proxy group points to a working target, then approve the connection. App installation, VPN connection, and access to a particular website are separate steps; check each one.
App Store · Check store listing for compatibility
| Check | Requirement or selection | After installation |
|---|---|---|
| Device and OS | Check the App Store listing for compatible devices and the minimum OS version. | The app opens normally; updates are managed through the App Store. |
| Network permission | Allow the VPN configuration when prompted by iOS. | Make sure the active VPN configuration matches the client you selected. |
| Configuration source | Have a working subscription or local configuration, and confirm the client supports its protocols. | Enable the subscription, choose a valid proxy group target, then test access. |
For desktop environments, choose a GUI client. For server or router deployments, use the core downloads. Run uname -m to check your architecture: this section provides AMD64 / x86_64 packages. Choose DEB or RPM according to your distribution’s package manager.
Manage subscriptions and routing rules on a Linux desktop. Choose DEB for Debian- and Ubuntu-based systems; choose RPM for distributions that use RPM package management. Installing through your system package manager can also resolve dependencies. Check the distribution and app requirements for compatibility.
AMD64 · DEB / RPM
This section provides an AMD64 DEB package. After installation, check the system proxy in your desktop session, then configure terminal apps as needed. The desktop proxy toggle usually won’t set proxy environment variables for every shell, so check command-line tools separately.
AMD64 · DEB
| Check | Requirement or selection | After installation |
|---|---|---|
| Desktop and architecture | GUI clients require a compatible desktop environment; packages in this section are AMD64. | For an ARM server, use the core section instead of installing an AMD64 desktop package. |
| Package format | Choose DEB or RPM for your distribution and let the package manager handle dependencies. | Resolve missing dependencies first; don’t mix base libraries from other distributions. |
| Processes and proxy settings | Manage desktop sessions, terminal environment variables, and background services separately. | Confirm that the core is listening before checking whether an app is using the proxy. |
For users managing their own server, router, or service deployment. The core reads configuration and handles traffic, but does not include a full GUI client. For everyday desktop or mobile use, choose a GUI client above. Operating system labels in this section identify the core files only.
| Operating system | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · x64 command line | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · ARM64 command line | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ · Intel Mac | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ · Apple silicon | Download ARM64 GZ |
| Linux | AMD64 | DEB · Debian-based package | Download AMD64 DEB |
| Linux | AMD64 | GZ · Standalone binary | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM | Download ARM64 GZ |
| Linux | ARMv7 | GZ · 32-bit ARM | Download ARMv7 GZ |
| Linux | MIPS soft-float | GZ · Check firmware and endianness | Download MIPS GZ |
Keep the configuration directory separate from the executable, and prepare a valid config.yaml first. Once the configuration passes validation, start the core in the foreground and review the logs. Confirm the listening address and port before handing it over to a service manager. If the configuration references external rule files, make sure the runtime user can read them.
On a server, start with an explicitly defined local listening address. If other devices need access, plan access controls and firewall rules as well. TUN and routing settings require different permissions from a standard HTTP proxy; don’t grant elevated permissions to every process just to bypass an error. See the configuration reference for field details.
02 / After-download checks
Troubleshoot installation, configuration, and network issues separately instead of repeatedly switching clients.
AMD64 and x64 usually mean the same 64-bit x86 architecture, regardless of processor brand. ARM64 uses a different instruction set; don’t treat the two as interchangeable just because both are 64-bit. Check your system architecture, then read the file details beside the download button.
If the installer says your system isn’t supported, check the OS version and file architecture first. If the app opens but the core won’t run, check core logs and runtime dependencies. This page doesn’t give one minimum OS version for every client; refer to the selected app’s release notes.
Back up your local configuration, subscription source, and overrides before updating. Numbers in installer filenames and app release information are separate details; don’t use a single number on this page to judge which platform builds are newer. The release notes and in-app version information are better sources for what changed.
When switching clients, quit the old process first, then import your subscription and enable the configuration. Check the system proxy, proxy group, DNS, and listening port before testing access. If only one app can’t connect, check whether it uses the system proxy instead of deleting all your configuration. See the Getting Started guide for detailed steps.
03 / Download FAQs
Select a question to expand it. For more connectivity troubleshooting, see Troubleshooting.
For everyday desktop and mobile use, start with a GUI client to manage subscriptions, proxy groups, and system proxy settings. The Mihomo core is for servers and routers where you provide your own configuration files, startup commands, and service management. Downloading the core alone does not give you a full graphical interface.
AMD64 and x64 usually refer to the same 64-bit x86 architecture; ARM64 is for 64-bit ARM processors. Check your processor in system information, then match it to the package architecture. If you’re unsure, an Android universal package is an option, though it’s usually larger than a single-architecture build. Check the app’s release notes for supported OS versions.
In the current download list, some clients’ Apple Silicon and Intel links point to the same x64 file. Separate links don’t mean separate native installers are available. Apple Silicon users should first check whether the file runs under Rosetta. For a native ARM64 installer, choose the Clash Plus download explicitly labeled ARM64 on this page.
Keep your subscription URL, local YAML configuration, overrides, and any proxy group selections you need to recreate. Subscription URLs may contain credentials, so don’t share them publicly. Before migrating, quit the old client, then import your setup into the new one and check proxy mode, listening ports, and DNS settings. Two clients controlling the system proxy at once can cause conflicts.
The installer provides the client app, not a proxy service. You’ll also need to import a subscription you’re authorized to use or a local configuration, enable it, and select a working proxy group. Then enable the system proxy or grant VPN permission as needed. If you still can’t connect, check the logs, port conflicts, and DNS first, then follow the setup guide and troubleshooting steps.