CLASH / CLIENT PACKAGES
Choose your operating system, then check the architecture. Use a graphical client for everyday setup; use the Mihomo core to run your own service.
Each card button downloads the corresponding file. Version details appear only when valid release information is available. After switching platforms, copy the address-bar URL to return to the same set of downloads.
For a first install, start with Clash Plus. The desktop clients below offer x64 installers. Windows on ARM users should confirm x64 app compatibility; an x64 download is not a native ARM64 build.
A good fit for desktop users getting started by importing a subscription. After installation, add a configuration and confirm it loads before enabling the system proxy. Virtual network adapter features may require administrator permission. Test the standard proxy first, then try TUN separately.
For users who want subscription management, rule inspection, and desktop traffic control. Back up custom overrides before upgrading, and check the service status after installation. If the standard proxy works but TUN won’t start, check service permissions and logs instead of repeatedly changing subscriptions.
For users who want a similar workflow across devices. Import your configuration on first launch, then check the selected policy group. Interface settings are separate from subscription contents. When migrating, back up both configuration files and any app preferences you want to keep.
Another graphical client for desktop. After importing an existing configuration, check the active core and configuration parsing logs, then verify the system proxy port. Avoid letting multiple clients manage the system proxy at once; one may undo the other’s settings as soon as they’re enabled.
Archived for reference and migration from older setups. The client may not support newer protocols or configuration fields. For a new install, choose a maintained option above. Before migrating, save your subscription URL and custom rules, then restore them one at a time. Don’t copy the old runtime directory over the new application.
| Check | How to choose |
|---|---|
| System and architecture | Check System type under Settings → System → About. The desktop downloads here are x64; see the relevant release notes for the minimum supported Windows version. |
| Installation permissions | Test the system proxy on its own first. Installing services and enabling TUN usually require administrator approval. |
| After-install checks | Exit other proxy clients, import a subscription, enable the system proxy, then check the actual outbound in the connection log. |
Check your chip under Apple menu → About This Mac. Apple Silicon users should choose a native ARM64 build when available. Some download links currently serve x64 compatibility builds, labeled below; check the actual filename before downloading.
Separate DMG downloads are available for each architecture, making this a good option for Mac users setting things up for the first time. Move the app to Applications before launching it, rather than running it from the disk image. Once your configuration loads, enable the system proxy first. If you need TUN, approve the network component when prompted.
For users who want desktop subscription management and traffic control. Both architecture links currently fall back to the same file. Apple Silicon may require Rosetta, and app compatibility should be confirmed. If macOS blocks the app on first launch, read the system prompt rather than running an untrusted command to bypass it.
For users already familiar with FlClash. The Apple Silicon link currently serves an amd64 build, not a native ARM64 version. After importing your configuration, check DNS and proxy mode. If other network filtering tools are running, disable overlapping traffic controls before testing.
For users who need to check an older menu bar setup; both links currently point to the same x86_64 file. Permissions, protocol support, and compatibility may be limited on newer systems. We recommend migrating subscriptions and custom rules to a maintained client instead of relying on this archived build for ongoing updates.
| Check | How to choose |
|---|---|
| Chip | Apple M-series chips are Apple Silicon. Intel Macs use x64, amd64, or x86_64; these labels generally refer to the same architecture. |
| System compatibility | See the client’s release notes for its minimum macOS version. Rosetta can help with some architecture compatibility issues, but it doesn’t guarantee that every component will run. |
| Network permissions | Grant system proxy or network extension permissions when needed on first use. If traffic control fails, check the permission status and logs first. |
Most recent phones use arm64-v8a, but a 64-bit processor doesn’t guarantee that the operating system supports 64-bit apps. If Android says the app is incompatible, check the system ABI and choose an ARM or universal build accordingly.
For Android devices compatible with arm64-v8a. On first connection, the app will ask to set up a VPN connection; confirm the app name before granting permission. Importing a subscription doesn’t connect you automatically: check the active configuration and policy group, then look for actual requests in the connection log.
For Android users with Clash Meta configurations. If you’re unsure which architecture to choose, try the universal build, provided your device meets the app’s system requirements. If connections drop in the background, check battery restrictions and background permissions. Frequent automatic speed tests aren’t a reliable way to check whether the app stays connected.
Offers 64-bit and 32-bit ARM builds; choose the one that matches your device’s actual runtime environment. If switching between VPN apps, disconnect the existing VPN before starting this client. In most standard Android user environments, two VPN services can’t both control traffic at the same time.
Check configuration compatibility before using it. Surfboard isn’t a Clash-style interface backed by a core that directly reads full Clash YAML, so don’t assume a Clash subscription URL can be imported as a Surfboard configuration. Use a format your service provider explicitly supports, then check the rules and policies after importing.
| Check | How to choose |
|---|---|
| Architecture and version | Check the system ABI and Android version. See the client’s installation prompt and release notes for specific minimum requirements. |
| Install source | Allow installation only for the browser or file manager used to download the APK. If there’s a signature conflict, back up the existing app’s configuration first. |
| Background operation and traffic control | A VPN permission is required to connect. Change battery settings only if you’ve confirmed the system is restricting background operation; avoid unnecessary always-on settings. |
Install Clash Plus from the App Store. Check the store listing for device compatibility and current availability. Once installed, add your own subscription or configuration.
When connecting for the first time, allow the VPN configuration when prompted by iOS. After importing, make sure the configuration is enabled and check the selected policy group. If your device already has another VPN or a device management profile, find out what it does before switching to avoid disrupting your work network.
Official site: clashplus.io. Updates are managed through the App Store. Consider saving important subscription URLs and custom settings before upgrading. The client and network service are separate; connection quality still depends on the service and routes you use.
| Check | How to choose |
|---|---|
| Device compatibility | Check the App Store listing’s Compatibility section for the required iOS version and supported devices. |
| Network permissions | Confirm the iOS VPN permission on first connection. Traffic control won’t work until the configuration is authorized. |
| Connection strategy | Test availability with the default connection method first. Adjust on-demand connection settings only as needed, and avoid repeated speed tests or unnecessary updates. |
For desktop use, start with a graphical client. Check your distribution’s package format and CPU architecture first. The downloads below are for amd64 / x86_64; for server or router deployments, see the core section.
DEB is usually the right choice for Debian, Ubuntu, and similar systems; choose RPM for Fedora and other RPM-based distributions. Check the release notes for desktop dependencies. Being able to install a package doesn’t mean every runtime dependency is present. If launch fails, run it from a terminal and keep the error output; that’s more useful than reinstalling repeatedly.
For amd64 desktop systems compatible with this DEB package. After installation, check whether desktop apps can use the system proxy. Command-line programs may ignore desktop proxy settings, so you may need to configure environment variables or use TUN. Don’t rely on a “connected” status in the GUI as proof; test an actual request.
| Check | How to choose |
|---|---|
| Distribution and architecture | Run uname -m to check your architecture, then consult your distribution’s documentation. DEB and RPM packages aren’t interchangeable by changing the file extension. |
| Graphical dependencies | Check compatibility with desktop libraries, the system tray, and your display environment. Minimal server installations aren’t suitable for running a desktop GUI directly. |
| TUN permissions | You need an available TUN device and the required permissions. In a container or restricted environment, also check which capabilities the host has enabled. |
For users running their own services on servers or routers. The core parses configurations and handles traffic, but doesn’t include a full desktop interface. Most users should choose one of the graphical clients listed above.
| Platform | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · 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 softfloat GZ |
ZIP and GZ files are compressed; extract them before running. On Linux and macOS, make sure the file is executable. Create a dedicated configuration directory and place config.yaml and any required rule resources somewhere the core can access. Run it in the foreground first and check the parsing output before configuring it as a service.
If the core needs to listen on an external address, distinguish clearly between the proxy port and the control interface. Never expose the management interface directly to the public internet. TUN, DNS listeners, and route changes each require appropriate permissions. Resolve permission errors from the specific logs rather than granting every process the highest privileges from the outset.
The core is licensed under GPL-3.0; each project maintains its own client interface and packaging. When checking configuration fields, make sure the documentation matches the core you’re running—don’t infer capabilities from the client name alone. For deployment steps, see the full documentation.
Check architecture and permissions, and back up your configuration before connecting. This helps narrow down troubleshooting if something goes wrong after installation.
The architecture in the filename is a more reliable guide than your device’s brand. Check System type on Windows, chip details on Mac, the system ABI on Android, or uname -m on Linux. Each identifies whether a program can run on your system. Even with a matching CPU architecture, older systems may lack dependencies required by newer apps, so check the client’s minimum OS version too.
If the download is unusually small, has an incomplete extension, or the browser still shows it in progress, wait for it to finish before running it. If the system reports incompatibility, don’t try every package in turn. Save the full error message and determine whether the cause is the architecture, OS version, permissions, or a missing dependency.
Before migrating from an older client, back up your subscription URL, local YAML, custom rules, and overrides. Subscription updates often regenerate the remote configuration, so edits to generated files may be overwritten next time. Put any changes you need to keep in the override or merge mechanism supported by the new client.
For your first test, use just one traffic-control method. On desktop, try the system proxy first; on mobile, confirm VPN permission. Enable TUN only if you need it. Visit a site and check the connection log for its domain, matched rule, and outbound policy. That’s a better way to confirm the configuration works than relying on the color of a toggle.
Answers to common questions about choosing an installer, archived clients, and your first connection. For subscription updates and node latency, see the FAQs.
Desktop and mobile users should start with a graphical client. This page recommends Clash Plus for Windows, macOS, Android, and iOS, and Clash Verge Rev for Linux. The Mihomo core is for server and router users who manage configuration, services, and logs themselves; it is not a full graphical client.
x64 and amd64 usually refer to 64-bit Intel and AMD architectures; ARM64 and arm64-v8a refer to 64-bit ARM. On Android, armeabi-v7a is for compatible 32-bit ARM devices, while universal builds include multiple architectures. Check your device’s system information and the actual filename—don’t choose based on the device brand alone.
For some clients, the Apple Silicon and Intel links currently point to the same x64 file; compatible downloads are labeled on this page. Apple Silicon devices may need Rosetta to run these builds, and compatibility depends on the app. For a native ARM64 build, choose a Clash Plus download explicitly labeled arm64.
First, make sure the download completed and that the file extension and CPU architecture match your device. Then check the client’s release notes for system requirements. On Android, check permission to install from that source and look for a signature conflict with an existing app. On Linux, make sure you have the right package format: deb or rpm. Don’t disable system security protections; keep the exact error message and use it to investigate.
Both remain available as archived downloads for reference and migration from older setups; neither is maintained. For a new installation, choose a maintained client that supports your system and protocols. Before migrating, back up your subscription URL, custom rules, and overrides. Don’t overwrite your only copy of an old configuration.
Import a valid subscription or local YAML file and make sure it loads, then select a rule mode and an available policy. On desktop, enable the system proxy, make a request in your browser, and check the connection log for the matched rule and outbound. Enable TUN by following the guide only if you need to proxy apps that don’t respect the system proxy.