Client / Architecture / Package
Choose your operating system, then check your CPU architecture.
Clash Plus is our top pick for Windows, macOS, Android, and iOS; for Linux, start with Clash Verge Rev. If you already have a configuration, check protocol and core compatibility before switching clients.
Choose by device
Check the architecture label on the download button—not just the file size. Features and release schedules can vary by platform, even for the same client.
All desktop clients in this section are x64 builds. Most 64-bit Intel and AMD PCs use this architecture. Windows on ARM may require compatibility support; a core’s ARM64 package is not a substitute for a GUI client.
A good starting point if you’re new to the Clash ecosystem and want to import a configuration through a graphical interface. Import your subscription after installation, then choose a proxy group and mode. The system proxy toggle does not tell you whether a node is working.
Official site: clashplus.io · EXE installer
For desktop users who want to inspect connections, manage rules, and adjust overrides. Before enabling TUN, check service mode and permission requirements. If you only need browser access, verify the system proxy first for a simpler troubleshooting path.
x64 build · No standalone Windows ARM64 GUI installer
A good fit if you already use FlClash on your phone and want a similar workflow on desktop. A portable configuration does not mean you can copy the entire app settings folder. Reimport your subscription, then restore rules and DNS settings individually.
AMD64 is another name for x64; it does not mean you need an AMD processor.
An alternative desktop interface. Before migrating, check which protocols, rule providers, and core features your configuration requires. A YAML file appearing in the app does not mean every field is supported.
Import your configuration and check the logs before routing system traffic
Kept for reproducing legacy environments, comparing interfaces, and planning migrations—not recommended for new installations. Since development has ended, future OS changes and new protocol support are not guaranteed. Menu names in older guides may also differ from those in current clients.
For legacy use · Save subscription URLs and custom rules before migrating
| Check | Recommendation |
|---|---|
| System | Use a supported version of Windows 10 or 11. Check each app’s release notes and installer for its minimum version. |
| Processor | These are x64 installers. Find your system type under Settings → System → About. |
| Permissions and runtime | The standard interface and TUN service may require different permissions. If a runtime component is missing, follow the installer’s instructions instead of repeatedly installing older versions. |
Check About This Mac for your chip: Apple M-series models use Apple Silicon; Intel models need x64. The Apple Silicon link below is currently labeled x64, so check Rosetta and app compatibility before using it. It is not a native ARM64 package.
Choose the build that matches your chip. Open the DMG and follow the installer window to move the app into Applications, then launch it from there. For your first setup, import a subscription and select a node before enabling a proxy mode.
Official site: clashplus.io
For desktop users who need rule management and connection troubleshooting. Both links currently point to the same x64 build. Check compatibility before using it on Apple Silicon, then review service mode and system proxy permissions after installation.
The Apple Silicon link is not a native ARM64 installer
A good choice if you want a similar workflow on desktop and mobile. Both downloads listed here are AMD64 builds. Check Rosetta compatibility on Apple Silicon, and review DNS and proxy mode again after importing your configuration.
AMD64 and x64 refer to the same architecture class
For users who need to reproduce an older menu bar workflow. Both links currently serve x86_64 packages; that does not indicate native Apple Silicon support. For new installations, choose a maintained client. When migrating an old configuration, check its core fields again.
For legacy use · Check compatibility with newer macOS versions
| Check | Recommendation |
|---|---|
| macOS version | Use a supported macOS release. Check each app’s release notes and installer for its minimum system requirements. |
| Chip | Choose native ARM64 for Apple M-series Macs and x64 for Intel Macs. An x64 compatibility build is not a native package. |
| Compatibility and permissions | Running x64 apps on Apple Silicon may require Rosetta. Installing services or routing network traffic may require additional permissions. |
ARM64 is the best place to start for most newer phones. Older devices may run a 32-bit ARM system, so don’t rely on the processor’s marketing name alone. If you’re unsure, choose the universal Clash Meta for Android package and check the installer’s compatibility notice.
For managing subscriptions and everyday rule-based routing on your phone. The first connection requires Android VPN permission. If another app is already using the VPN interface, check whether both can run at the same time.
Official site: clashplus.io · ARM64 APK
For users familiar with Clash configuration who need to choose a specific device architecture. The universal package includes multiple architectures and is usually larger. After importing a subscription, confirm the configuration is selected before connecting, then check the logs.
ARM64 recommended; choose the universal build if you’re unsure about your device architecture
For users who switch between desktop and phone and want a consistent interface. If the connection drops when the screen locks, check background activity and battery optimization settings before changing network options.
The APK architecture must match your device
For users with an existing configuration compatible with Surfboard. Its configuration format differs from Clash YAML, so don’t assume your existing subscription can be imported as-is. Check that your provider’s output format and the protocols you use are supported.
Universal APK · Check the configuration format before importing
| Check | Recommendation |
|---|---|
| Android version | Minimum Android versions vary by client release. Check the installer and app details; newer builds may not support older systems. |
| Architecture | ARM64 uses arm64-v8a; 32-bit ARM uses armeabi-v7a. Use the universal package if you’re unsure which architecture your device supports. |
| Permissions | When installing an APK from a browser, grant install permission only to the source you’re using. Approve VPN access when prompted to connect. |
Check device compatibility and app details in the App Store. Desktop system proxy instructions do not apply directly to iOS. When connecting for the first time, follow the system prompt to add a VPN configuration.
Check the system requirements on the App Store listing before installing. Open the app, import a valid configuration, and choose a policy before connecting. Adding a VPN configuration is a system permission step; it does not verify that your subscription or proxy service works.
Official site: clashplus.io
| Check | Recommendation |
|---|---|
| System and device | Check the App Store listing for compatibility and confirm your device’s iOS version before installing. |
| Install and update | Install and update through the App Store. Refer to the store listing for the latest release information. |
| Configuration and permissions | Prepare a valid subscription or configuration, then follow the system prompt to authorize a VPN configuration. |
This section offers AMD64 desktop installers with a GUI. Choose DEB for Debian and Ubuntu-based systems, or RPM for Fedora and other RPM-based distributions. Package format is only the first check; distro version, desktop environment, and library dependencies also matter.
For Linux desktop users who want a GUI to manage configurations and connections. Use your distribution’s package manager to handle dependencies where possible. If TUN fails to start, check service permissions, routing, and DNS separately instead of only changing the desktop proxy setting.
AMD64 desktop builds only; see the core section for ARM servers
For users who want a similar cross-platform interface on Debian-based desktops. Don’t install a GUI on a remote server without a desktop session. For background services, startup tasks, or router deployments, a standalone core is easier to manage.
DEB package · Check distribution dependencies before installing
| Check | Recommendation |
|---|---|
| Distribution and package format | DEB and RPM are not interchangeable. Check the app documentation and package manager for minimum distro versions and shared library requirements. |
| Architecture and session | Desktop packages are AMD64 / x86_64 and require a working graphical session. Use uname -m to help confirm your architecture. |
| Permissions and networking | TUN requires the appropriate system capabilities and permissions. First confirm that the configuration loads, then set up services, startup, and traffic routing. |
For servers, routers, and users who manage processes themselves. Mihomo is a core, not a complete GUI. For everyday desktop and mobile use, choose one of the GUI clients above. ZIP and GZ files below are program archives; DEB is a package. You’ll still need to prepare a configuration after extracting or installing.
| System | Architecture | Format and download |
|---|---|---|
| Windows | AMD64 / x64 | Download ZIP |
| Windows | ARM64 | Download ZIP |
| macOS | Intel / AMD64 | Download GZ |
| macOS | Apple Silicon / ARM64 | Download GZ |
| Linux | AMD64 | Download DEB |
| Linux | AMD64 | Download GZ |
| Linux | ARM64 | Download GZ |
| Linux | ARMv7 | Download GZ |
| Linux | MIPS-softfloat | Download GZ |
| Check | Before deployment |
|---|---|
| System and CPU | The runtime must match the operating system, architecture, and required instruction set. Check compatibility carefully on older processors, custom firmware, and minimal systems. |
| Configuration and directories | Prepare a readable configuration file, any required rule resources, and a writable data directory. Check startup output in the foreground before configuring background execution. |
| Services and permissions | You’ll need to configure process supervision, startup, listening ports, and TUN permissions yourself. Restrict access to the management interface and set authentication securely. |
Read about protocol support, core compatibility, and configuration fields
After downloading
Before upgrading the same client, save your subscription URL, custom rules, and overrides. When switching clients, avoid copying the entire application data folder: configuration files may be portable, but interface preferences, ports, service state, and internal databases may not be compatible.
Quit the old client before running the new installer. On first launch, import one known-good configuration and check the load result and logs. Confirm the rule mode and proxy group before enabling the system proxy or TUN. Change one traffic-routing method at a time to narrow down problems.
A client loads configurations, applies routing rules, and establishes proxy connections; installing it does not provide a service. An expired subscription, incompatible format, missing node parameters, or conflicting DNS settings can all result in a connection that starts but cannot reach the internet. Use the logs to investigate each possibility.
For certificate errors, check the system clock, destination website, and connection path. Don’t fix them by disabling certificate verification. Before sharing logs, screenshots, or configurations, remove subscription URLs, credentials, and identifiable device information. For step-by-step help, follow the guide in order: import, choose a mode, connect, and verify.
Download FAQ
Check your operating system, architecture, and configuration format first; then troubleshoot permissions and networking. These answers go with the download links on this page.
Start with Clash Plus on Windows, macOS, Android, or iOS; on Linux, consider Clash Verge Rev. Check your device architecture and configuration format before comparing interfaces and features. Clients do not include a proxy service—you’ll need to import a valid configuration after installation.
If your current setup works, there’s no need to switch just for a different interface. Check the client comparison to see whether the target app supports your protocols and rules.
x64 and AMD64 usually refer to the same 64-bit x86 architecture; ARM64 is different. Check your processor type in system information. If you’re unsure about your Android device, choose the universal build. If an Apple Silicon download is labeled x64, check Rosetta compatibility first—it is not proof of a native build.
Check the architecture label in the filename too. If your system says the app isn’t compatible with your device, choose the correct architecture instead of changing the file extension.
Back up your subscription URL, custom rules, overrides, and client settings. Note the core and proxy mode you currently use, then quit the old client before running the installer. When switching clients, reimport your configuration rather than replacing the entire application data folder. Remove subscription URLs and credentials before sharing logs.
If your subscription manages your rules, distinguish remote updates from local edits so the next refresh doesn’t overwrite temporary changes. See the configuration import guide for details.
First identify whether the download failed, the package format is wrong, or the system blocked the app from launching. For download issues, note the browser error and check available disk space. For installation issues, verify the operating system, CPU architecture, and file extension. If you see a security warning, check the publisher and system requirements—don’t disable system protections outright.
Missing Linux dependencies, macOS compatibility issues, and Windows runtime errors are different problems. Keep the exact error message—it’s more useful than simply saying the app won’t open.
Both are listed here as discontinued clients for reproducing legacy environments and comparing migration paths. This does not guarantee support for newer protocols, rule fields, or operating systems. For a new installation, choose a maintained client; for an older configuration, check that its fields are supported by the current core.
An app with Clash in its name does not necessarily support all the same core features. For protocols such as VLESS and Hysteria2, check the protocol and core guide instead of relying only on screenshots from older tutorials.
Mihomo is the core program that handles proxy protocols, rule matching, DNS, and related functions; it is not a complete desktop app. Running the core directly means managing configuration, processes, and permissions yourself, which suits servers and routers. For everyday desktop or mobile use, choose a graphical client.
GUI clients usually also manage configuration imports, the system tray, startup, and system proxy settings. Extracting the core to your desktop won’t provide those features automatically.