CLIENT PACKAGES / YAML CONFIG
Choose your OS, then your CPU architecture. Use a GUI client on desktop or mobile; consider a standalone core for servers and routers.
Clash Picks brings together client comparisons and setup guides. The software listed below belongs to its respective projects; download links don’t mean this site develops the apps or provides proxy service. If you already have a subscription, keep its original source and import it after installation using the guide.
For your first install, start with the featured pick. Download buttons are on each card, with alternative architectures listed alongside. If you’re unsure which chip you have, check your system information rather than relying on the filename extension.
For a new install, start with Clash Plus. The desktop installer here is for x64 systems. Check System type under Settings → System → About. After installation, import your configuration before enabling the system proxy; there’s no need to turn on TUN right away.
A good first choice for Windows. Install and open the client, then import your existing source from the subscription or configuration settings. Test your browser connection in Rule mode. If you need to route apps that ignore the system proxy, check the permissions required for TUN.
clashplus.io
For users who want to manage subscriptions, overrides, and desktop proxy settings. When migrating an old configuration, import the original subscription first, then restore local rules one by one. TUN and service mode require system permissions. If startup fails, check the logs rather than reinstalling over your existing configuration.
If you use both desktop and mobile, choosing the same client family can make switching between interfaces easier. The Windows AMD64 package also works on common Intel x64 processors. After importing, check the active proxy group. Mobile app-routing settings don’t automatically configure the desktop system proxy.
For users who want to compare different desktop management interfaces. Before installing, quit any running proxy clients to avoid port conflicts or virtual network adapter clashes. Start by importing one working configuration. Once subscription updates and rule matching are confirmed, restore more complex overrides.
This archived download is for reproducing older setups or planning a migration. For everyday use, choose one of the clients above. Older overrides, scripts, and core fields may not migrate directly. Back up your subscriptions and configuration files, then verify each item in the new client before removing the old setup to avoid losing local rules.
| Check | What to check before installing |
|---|---|
| Processor | This section offers x64 / AMD64 packages. ARM devices must meet the system compatibility requirements; these are not native ARM installers. |
| Windows version | Minimum requirements vary by client; check the installer and the project’s current documentation. An x64 label alone doesn’t guarantee compatibility with older Windows versions. |
| Permissions and ports | Installing a service or enabling TUN may require administrator privileges. Make sure the mixed port doesn’t conflict with another instance. |
Turn off the system proxy before quitting the client. If your browser still can’t connect after the app exits, check whether Windows proxy settings still point to a local listening address, then continue troubleshooting.
Check your chip in About This Mac: choose the corresponding ARM package for Apple Silicon or the x64 package for Intel. Some current download links still point to x64 files, as noted on their cards. The link label doesn’t replace checking the architecture of the actual binary.
Choose the DMG for your chip, open it, and follow the installer prompts. On first launch, import your subscription before allowing the client to change system proxy settings. When switching clients, turn off the old app’s proxy settings so traffic isn’t still sent to a process that has exited.
clashplus.io
For desktop users who need subscription management and local overrides. Both fallback links currently point to x64 files, so don’t assume they’re native Apple Silicon builds. On an ARM-based Mac, check installer and OS compatibility before using this build.
For users already familiar with FlClash. Both fallback links currently point to AMD64 files; Apple Silicon users should check compatibility first. When migrating, keep the original subscription source. Desktop system proxy settings and mobile VPN permissions must be configured separately.
For reference when migrating older configurations or recreating a menu bar workflow; not recommended for a first install. The current fallback is an x86_64 build, so Apple Silicon users should check compatibility. When upgrading, review DNS, rule sets, and local port settings in the original configuration.
| Check | What to check before installing |
|---|---|
| Chip type | Choose ARM64 or x64 for Apple Silicon or Intel, respectively. Check the architecture of the actual file linked here. |
| Windows version | Check the installer’s minimum macOS requirement; there is no single minimum version that applies to every client. |
| Compatibility and permissions | Running an Intel build on Apple Silicon may require Rosetta 2, and compatibility isn’t guaranteed for every feature. Grant permissions for TUN or helper services when prompted by macOS. |
If macOS shows a security alert, confirm the file source and app name before following the relevant security settings. Don’t disable system-wide security just to launch a client. Test the system proxy and TUN separately.
Most newer phones use ARM64, but a device’s age isn’t a reliable way to tell. Check the processor and system architecture before choosing an APK. On first connection, you’ll usually need to grant VPN permission. This allows the app to route traffic; it doesn’t mean your subscription is ready.
Start here for your first Android install. Once the download finishes, allow installs from the current source when prompted, then open the client and import your subscription. Make sure the configuration is selected before connecting. Approve the VPN permission prompt, then test access in a browser.
clashplus.ioPackages are available for different processor architectures, making this a good fit for users who want to manage configuration files directly. If you can’t identify your architecture, consider the universal package, provided your system meets the app’s requirements. After updating the configuration, make sure it’s enabled, then choose a proxy group and mode.
A good fit if you also use FlClash on desktop. The ARMv7 package is for compatible 32-bit ARM devices; it isn’t a performance variant of the ARM64 build. If the connection drops when the screen locks, first check background activity and battery settings before investigating subscription or network issues.
For users with a compatible Surfboard configuration. Its configuration syntax differs from Clash YAML, so arbitrary Clash subscriptions won’t necessarily work. Check which formats your subscription provider supports, then import it and verify that proxies, groups, and rules are recognized correctly.
| Check | What to check before installing |
|---|---|
| Architecture and OS | ARM64 corresponds to arm64-v8a, while ARMv7 is usually labeled armeabi-v7a. Check the current installer’s minimum Android version. |
| Install permissions | Allow installs from the browser or file manager you’re using. Once installation is complete, you can restore the setting to match your security preferences. |
| VPN and background activity | Approve the system VPN prompt and avoid connecting another VPN at the same time. Check background activity and battery optimization restrictions as needed. |
“App not installed” doesn’t always mean the download failed. Installation may be blocked by an architecture mismatch, an outdated OS, or a different signature on an existing app. Note the error before deciding whether to uninstall the old version; save local configurations first.
On iPhone or iPad, open the App Store listing for Clash Plus. Check the device compatibility details shown there before installing. You’ll still need to import your own subscription or configuration before connecting.
Install and update through the App Store listing. On first launch, add your subscription and confirm the configuration has loaded before adding a VPN configuration when prompted. Rules copied from a desktop may need compatibility checks against the mobile core; sharing a subscription URL doesn’t guarantee every setting can be reused as-is.
clashplus.io| Check | What to check before installing |
|---|---|
| Device and OS | Check the Compatibility section of the App Store listing to make sure your iOS or iPadOS version meets the requirements. |
| Connection permissions | Approve the VPN configuration when prompted. Device management policies may prevent network configurations from being added. |
| Configuration source | Prepare a supported subscription or local configuration. Installing the app doesn’t create a proxy service. |
When a connection fails, first identify whether the issue is with installation, subscription import, or network access. If the App Store install worked but subscription updates fail, check that the source is valid. If the subscription loaded but connections fail, check the selected proxy group and logs.
If you use a desktop environment, start with a GUI client. Choose DEB for Debian- or Ubuntu-based distributions, or RPM for distributions that use RPM package management, and check dependencies. The GUI packages here target AMD64 / x86_64; for other architectures, see the Mihomo core section below.
A good first choice for Linux desktops. Match the package format to your distribution; the system package manager will handle dependencies. Whether the system proxy covers a particular app depends on how that app handles proxy settings. Command-line tools and container networking may need separate configuration, so don’t assume the desktop toggle routes all traffic.
For AMD64 Linux desktop environments that meet the dependency requirements. Import your configuration and test with the regular system proxy before considering TUN routing. For a headless server, don’t install a desktop just to run a management window; the standalone Mihomo core is a better fit.
| Check | What to check before installing |
|---|---|
| Architecture | Run uname -m to check your system architecture. The GUI packages here target x86_64 / AMD64. |
| Distribution and dependencies | DEB and RPM packages aren’t interchangeable. Check installer output for desktop libraries, runtimes, and version requirements. |
| Network permissions | TUN requires the right permissions and routing setup. Before changing a remote server’s default route, make sure you have a fallback and can still access the server. |
If installation succeeds but the interface won’t start, check desktop dependencies and application logs first. If there’s no network access, investigate listening ports, system proxy settings, and DNS separately. Don’t conflate GUI startup issues with core connection problems.
Downloading the app doesn’t finish the setup. Get the simplest connection working first, then restore custom rules. Change one setting at a time so it’s easier to roll back if something breaks.
Open subscription or configuration management, then paste a valid URL or import a local YAML file. Confirm the update completed and set the new configuration as active. Subscription URLs may contain credentials, so don’t share screenshots or post them in public forums.
Rule mode uses your configuration to decide whether traffic connects directly or through a proxy. Check that every policy group referenced by a rule is defined and has an available option. Global mode can help with troubleshooting, but it isn’t a substitute for a correct rule configuration.
On desktop, enable the system proxy and test in a browser. On mobile, approve the VPN prompt. If the browser works but other apps don’t, consider TUN or app-specific proxy settings. Check rule matches in the logs; latency figures don’t replace testing real access.
For users managing servers, routers, or their own service processes. Desktop and mobile users can use one of the GUI clients above; there’s no need to install the standalone core as well.
With a standalone core, you’ll need to provide the configuration, launch method, listening ports, and service permissions. ARMv7, ARM64, and MIPS aren’t interchangeable. MIPS softfloat also depends on the floating-point ABI, so router users should choose based on the firmware environment rather than guessing from the device brand or model.
| Platform | Architecture | File type | Download |
|---|---|---|---|
| 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 |
Extract ZIP and GZ downloads before use. GZ files are usually compressed single executables, not graphical installers. Unix-like systems may also require execute permission. Start the core in the foreground and review the logs first; once the configuration parses correctly, add it to a service workflow you manage.
Install DEB packages with your package manager, but don’t assume the service is fully configured just because the package installed. Confirm the install path, launch arguments, and configuration directory before setting up startup on boot.
The core needs a complete configuration, including proxy sources, policy groups, and rules. Don’t use a snippet with only a few example lines as a complete, working configuration. Before changing DNS, TUN, or routing, save a verified working copy so you can restore it.
Restrict the external control interface to localhost or a trusted network, and protect access. On public servers, check the firewall and listening address too. See Clash configuration deep dive for parameter details.
Start with Clash Plus on Windows, macOS, Android, or iOS, and Clash Verge Rev on Linux. Check your OS and CPU architecture first. If you already have a preferred client, compare alternatives such as FlClash. A client is not a proxy service; after installation, you’ll still need to import a valid subscription or configuration file.
x64 and AMD64 usually refer to the same 64-bit x86 architecture. ARM64 is a different architecture, so the two are not interchangeable. On Windows, check System type in System Information; on macOS, check the chip in About This Mac; on Android, choose ARM64 or ARMv7 based on your device’s processor. If you can’t confirm your Android architecture, consider the universal package listed on the card. A download label doesn’t guarantee a native ARM build, so check the architecture of the actual installer.
Installation is only the first step. Import a valid subscription or local YAML file, make sure the configuration is enabled, choose Rule mode, and turn on the system proxy. Once your browser connects, consider TUN only if your apps need it. If connection still fails, check the subscription update status, application logs, and port conflicts in that order. Change one setting at a time.
Keep your subscription source, local YAML files, custom rules, overrides, and any required port settings. Import and verify everything in the new client before removing the old one. Don’t run two system proxies or TUN services at once. Scripts and override formats can differ between clients, so check each item during migration. Backups may contain subscription credentials; store them somewhere you control.
Clash for Windows and ClashX Meta are listed here as archived downloads for reproducing older setups or planning a migration. For everyday use, choose a client that is actively maintained and compatible with your current OS. After importing an old configuration into a new core, check its rules, DNS, and overrides before enabling the system proxy.
Mihomo handles configuration parsing, rule matching, and proxy connections. A standalone core package usually doesn’t include a subscription manager, tray menu, or interface for setting the system proxy. Choose the core package if you manage a server, router, or service process yourself. Desktop and mobile users should use one of the GUI clients above; there’s no need to download the core separately.