Clash downloads and platform selection

A good fit for desktop users who manage subscriptions, local overrides, and rules. When migrating, import your existing subscription first, then check proxy group names and rule references one by one. Don’t copy the entire data directory from another client. Grant any permissions required for service mode or TUN when prompted.

Consider FlClash if you want a similar workflow on your computer and phone. For everyday use, choose the installer. The archive must be extracted to a writable location, and you may need to provide its runtime environment. Either way, import your configuration separately; the extracted version won’t inherit data from another installation.

Another desktop GUI option for users familiar with subscriptions, proxy groups, and rules. After installation, test a connection with your existing configuration before changing the interface or adding overrides. If your configuration includes core-specific fields, check what the current client actually loads and review its logs.

This archived download is for restoring older setups or reference during migration, not for new devices. Older versions may not support configuration fields introduced by newer cores or keep up with system changes. If you must use one, save your original configuration first. When migrating, move your subscription and custom rules rather than overwriting the new client’s program files.

A good fit for users who manage configurations, subscriptions, and overrides on a desktop. First confirm that your configuration loads, then enable advanced features such as DNS and TUN one at a time. This makes it easier to undo changes and troubleshoot.

Both architecture links currently point to the same x64 distribution file; they are not separate native builds. If you’re using Apple Silicon, make sure your system supports Rosetta before choosing this package. For a native ARM64 installer, use Clash Plus above.

A good fit if you already use FlClash on another device and want a similar interface. Check proxy groups and rules in your configuration one by one. A similar interface doesn’t mean that permissions, background operation, or network routing work the same way on every platform.

Both macOS links in this download list point to AMD64 files. Intel Macs can use the package as provided. On Apple Silicon, confirm Rosetta compatibility before using it; the compatibility option is not a native ARM64 package.

Kept for users restoring an older setup or migrating configurations. For a new installation, consider a client that’s still maintained. Newer macOS permissions, core features, and configuration fields may not work in an older app. If you run into issues, check app compatibility separately from subscription validity.

Both architecture links in this list currently point to x86_64 files. On Apple Silicon, check compatibility requirements before using them. Archived packages may help with a transition, but aren’t recommended as a long-term starting point for a new device.

A good fit for Android users who prefer working with configuration lists, proxy groups, and connection logs. If you know your device’s architecture, download the matching package. If you’re unsure, choose the usually larger universal version. Activate the configuration before connecting; importing a file alone doesn’t make it the active configuration.

If an update reports a signature mismatch, don’t uninstall right away. Export your configuration and note your settings first. Check that the old and new downloads come from the expected sources and refer to the same app before deciding how to migrate, so you don’t lose local data.

Choose from ARM64, ARMv7, and x86_64 packages to match your device. Desktop and Android configurations can follow similar principles, but Android routes traffic through a VPN interface rather than a desktop system proxy. If an app can’t connect, check per-app settings and VPN status first.

A good fit for Android users with an existing Surfboard-compatible configuration. Its format differs from Clash YAML; changing the file extension won’t make it importable. Before downloading, confirm that your subscription provider offers the right format. When migrating, check proxy definitions, proxy groups, and rule syntax again.

This is a universal Android installer. The first connection still requires Android VPN permission. If the configuration fails to parse, fix its format or get a compatible configuration rather than repeatedly switching proxy modes.

This section provides an AMD64 deb package for Linux desktops with a compatible architecture and package management system. After installation, import a known-working configuration and check that proxy groups and logs look normal. Then enable startup or change system proxy settings as needed, so installation issues aren’t confused with network configuration problems.

When migrating from another platform, don’t copy overrides that contain absolute system paths. Recheck rule file locations, external controller addresses, and service permissions for your Linux environment.