Clash downloads by platform

Clash Verge Rev

Desktop client

A good fit for desktop users managing multiple configs, policy groups, and rules. After installation, select a config and check the logs to confirm it loaded before enabling the system proxy. Editing a config and updating a subscription are separate actions; a subscription update may replace remote config contents.

For service mode or TUN, follow the app’s prompts to grant the required permissions. If the service fails to start, check its status and any security software alerts. Don’t enable every network option in the config at once.

FlClash

Installer / ZIP archive

The installer is the straightforward choice for most desktop users; the ZIP archive suits those who want to manage the app directory themselves. Extract the archive fully before launching the app—don’t run it from the archive preview. The app directory and config storage location may be different.

Save a working copy of your config before upgrading, then quit the old process before replacing app files. When switching clients, check your policy selections and system proxy port again; similar interface labels don’t guarantee that settings carry over.

Clash Nyanpasu

Windows desktop client

Provides a graphical interface for managing desktop configs and checking runtime status. After importing a config, confirm which core the client is using, then check for fields or protocols that core doesn’t support.

The system proxy only affects apps that honor system proxy settings. Some apps need a proxy configured separately; other traffic may require TUN. Identify how traffic enters the proxy before deciding whether to route more of it.

Kept for migrating older configs, referencing the legacy interface, and reproducing existing setups. Archived means maintenance has ended; support for new protocols, rule types, and system versions is not guaranteed. For a first installation, consider one of the maintained clients above.

Before migrating, export your local config and note your ports and policy group selections. Review each setting in the new client rather than copying the old app’s entire data directory; interface state and config storage formats may differ.

Clash Verge Rev

Current listing: x64 build

A good fit for managing subscription configs, rules, and desktop proxy status. Both architecture links in the current listing point to the same x64-labeled file; the second link is not a native ARM package. Apple Silicon users should check whether Rosetta is supported.

After installation, check that the helper service is running. If the system proxy is on but your browser still connects directly, first confirm that the local listening port matches the system proxy port, then check the connection logs.

FlClash

Current listing: AMD64 build

A good fit for desktop users who prefer FlClash’s config workflow. Both links currently point to an AMD64 file. Apple Silicon users should check compatibility first; for a native build, choose an installer explicitly labeled ARM64 above.

Before upgrading, quit the old process and replace the app in Applications. Keep your subscription URL and local overrides, then check your policy group selections after upgrading. Reinstalling repeatedly won’t fix a config issue.

ClashX Meta

Discontinued

For reference when migrating an existing setup or config. Both architecture links point to the same x86_64 file; check compatibility before using it on Apple Silicon. A discontinued version is not a good default for new systems or protocols.

When switching to another client, turn off the old app’s system proxy before enabling the new one. Keep the original YAML for reference, but adjust fields to match the new core instead of carrying over every old setting.

For Android users who need to choose an architecture, manage Clash configs, and check proxy status. ARM64 and 32-bit ARM are different builds. If you’re unsure which architecture your device uses, check its system information before considering the universal build.

After importing a subscription, wait for the config to finish downloading, then select it and start the service. VPN permission only allows Android to establish a local traffic tunnel; it doesn’t mean the remote proxy is working. Check your policy groups and connection logs too.

FlClash

Choose a build for your device

Packages are available for ARM64, 32-bit ARM, and x86_64. Don’t choose x86_64 just because your ARM phone reports a 64-bit system; x86_64 is mainly for devices or emulators using that architecture.

When switching from another client, stop its VPN connection first. Android typically allows only one app to use the VPN tunnel at a time. If permission prompts keep appearing or the connection is replaced, check whether another VPN app is running.

Surfboard

Separate config format

Uses a config format different from Clash YAML, and suits users with a compatible subscription or familiarity with its syntax. You can’t import any Clash config as a Surfboard config; first check which format your subscription provider supplies.

When converting configs, check for differences in rule types, policy groups, and protocol support. Successful import doesn’t guarantee every field carries over correctly; verify important rules and app behavior after connecting.

FlClash

DEB package

This section provides a DEB package for AMD64 desktops. Before installing, confirm that your distribution uses the corresponding package system, and use its package manager to handle dependencies. This AMD64 package won’t run directly on ARM64 devices.

For startup at boot, distinguish between launching after desktop login and running as a system service. The former depends on a graphical session; the latter needs separate permissions and a runtime directory. For server use, deploying the core directly is often a better fit.