Clash Plus
RecommendedWindows x64
For a new installation, start here. Complete the setup wizard, import your subscription, and then check the system proxy setting. Before enabling TUN, install or authorize the helper service as prompted by the app.
CLIENT PACKAGES / APPLE & DESKTOP
Clash Downloads and Architecture Guide
Clash Plus is recommended for Mac and iPhone. Check your operating system and CPU first, then choose an installer. On Apple Silicon, prefer a native arm64 build.
01 / SYSTEMCheck your operating system
Desktop installers and mobile apps are listed separately.
02 / ARCHCheck your CPU architecture
arm64 and x86_64 are different builds.
03 / CONFIGImport your configuration after installation
Downloading a client and setting up a subscription are separate steps.
PLATFORM SELECTOR
Choose an installer by platform
macOS is shown by default. Switch tabs to view downloads for other systems; use the format shown on each button. To compare interfaces and use cases, read the client comparison.
Windows Clients
The desktop installers below are for x64 systems. Open Settings > System > About to check your system type. On Windows on ARM, confirm x64 app compatibility separately; an x64 installer is not a native ARM64 build.
Clash Verge Rev
Windows x64
A desktop client for managing configurations, rules, and proxy groups. Before migrating an existing setup, export your overrides. Only let one client manage the system proxy at a time to avoid conflicting settings.
FlClash
Windows AMD64
A cross-platform interface for managing configurations and connections. AMD64 refers to the widely used x86_64 architecture and also works with compatible Intel processors; it is not limited to AMD devices.
Clash Nyanpasu
Windows x64
Another option for managing desktop configurations. After installation, check which core is in use and which fields it supports before importing your YAML. A different client name does not mean all UI settings can be migrated directly.
Clash for Windows
DiscontinuedArchived
Kept for migrating older setups and comparing configurations; not recommended for new devices. The older core has limited support for newer protocols and fields. When migrating, keep your subscription URL and rules rather than copying the entire old app folder over the new client.
Windows Installation Requirements
| Check | Requirements and guidance |
|---|---|
| System and architecture | Use a supported, up-to-date Windows x64 system where possible. Check each installer’s notes for its minimum Windows version. |
| Proxy routing | The system proxy works with apps that respect that setting. The TUN helper service may require administrator approval. |
| Install location | Choose a folder in the setup wizard. Quit the old process before updating, and keep your existing configuration in case you need to roll back. |
macOS: Apple Silicon and Intel
Open Apple menu > About This Mac. If your Mac has an Apple chip, choose arm64; if it has an Intel processor, choose x64. Architecture labels identify the download option, but the file itself must also match—don’t rely on button placement alone.
Clash Plus
RecommendedNative Apple Silicon build
Choose arm64 for an Apple Silicon Mac and x64 for an Intel Mac. Open the DMG and drag the app to Applications, then launch it from there. Follow macOS prompts to grant the required permissions the first time the app manages network traffic.
Clash Verge Rev
Current file: x64
For managing subscriptions and rules in one place. Both options currently download the x64 DMG, which may require Rosetta on Apple Silicon. For a native build, choose Clash Plus above—this file is not arm64.
FlClash
Current file: AMD64
For users who want a similar workflow across desktop operating systems. Both macOS options currently download the AMD64 DMG. AMD64 means x86_64; it is not the same as Apple Silicon arm64.
ClashX Meta
DiscontinuedArchived
For older menu bar workflows and comparing legacy configurations. Both options currently download x86_64 files. The older core may not support newer subscription fields; for a new installation, choose a client above and import your configuration again.
macOS Installation Requirements
| Check | Requirements and guidance |
|---|---|
| Processor | Prefer arm64 for Apple Silicon; use x64 / x86_64 for Intel. Check x64 app compatibility separately before running it on Apple Silicon. |
| macOS version | Minimum macOS versions vary by client; follow the app’s documentation and installer prompts. Matching the CPU architecture does not guarantee macOS version compatibility. |
| Permissions | System proxy and TUN are different ways to route traffic. Grant helper service, VPN, or network extension permissions as requested by the app. |
| Install location | Move the app to Applications before launching it. Avoid running it long-term directly from a mounted DMG. |
Android Clients
Recent phones typically use arm64-v8a, but check the ABI supported by your device. For older devices, see the armeabi-v7a option. If you’re unsure, Clash Meta for Android offers a universal package, which may vary in size and included architectures.
Clash Plus
Recommendedarm64-v8a
Android arm64 installer. The first time you connect, Android will ask to create a VPN connection; approve the request to route traffic. To keep the connection running in the background, adjust app permissions according to your device’s battery settings.
Clash Meta for Android
Multiple architectures
Choose an arm64, ARMv7, or universal installer for your device. If installation fails, check for an architecture mismatch, low storage, or a signature conflict with an existing app. Don’t delete unbacked configuration files just to try an in-place upgrade.
FlClash
arm64 / ARMv7
For mobile users who prefer an interface similar to the desktop client. Download the architecture that matches your device. After importing a configuration, test a foreground connection, then check whether system background restrictions affect it when the screen is locked.
Surfboard
Universal installer
Another Android option for rule-based proxying. Surfboard’s configuration format is not fully compatible with Clash YAML. Before installing, confirm that your subscription provides a compatible format; changing the file extension alone won’t make it importable.
Android Installation Requirements
| Check | Requirements and guidance |
|---|---|
| Architecture and version | Check whether your device uses arm64-v8a or armeabi-v7a. Refer to the installer’s compatibility details for the minimum Android version. |
| Install permissions | Grant permission only to the file manager or browser used to open the APK. Restore the previous setting when installation is complete, if needed. |
| VPN and background use | Allow the VPN request when connecting. Check whether another VPN is active, and add a battery optimization exception if needed. |
iOS and iPadOS Clients
Install Clash Plus from the App Store on iPhone or iPad. iOS manages network permissions; approve the VPN configuration the first time you connect. Don’t follow macOS installation steps or desktop helper service instructions.
Clash Plus
RecommendedApp Store
Open the App Store listing to check device compatibility, current app details, and installation requirements. After installation, add a subscription or import a compatible configuration, select a proxy group, and authorize the VPN connection.
iPhone and iPad Installation Requirements
| Check | Requirements and guidance |
|---|---|
| System compatibility | Check the App Store listing for the minimum iOS / iPadOS version and supported devices. |
| Network permissions | Follow the system prompt to add a VPN configuration on first connection, and check which app currently manages the connection. |
| Importing a configuration | Prepare a valid subscription or compatible file. Don’t copy desktop local paths or service settings directly to a mobile device. |
| Connection testing | Test over both Wi-Fi and cellular to avoid mistaking a limitation on one network for an installation problem. |
Linux Desktop Clients
The GUI installers below are for AMD64 desktops. Choose DEB for Debian- and Ubuntu-based systems, or RPM for distributions that use RPM packages. Servers and routers without a desktop environment are usually better suited to the Mihomo core below.
Clash Verge Rev
RecommendedAMD64
Choose DEB or RPM based on your distribution’s package manager; don’t mix installation commands. If the desktop app won’t start, check the terminal for missing dependencies or session errors before changing the runtime environment.
FlClash
DEB · AMD64
A Debian-family AMD64 installer. Whether the system proxy works depends on the app and desktop environment. Apps that ignore system proxy settings may need proxy environment variables or TUN instead.
Linux Installation Requirements
| Check | Requirements and guidance |
|---|---|
| Processor | The desktop package is for AMD64 / x86_64. Run uname -m to check your architecture; it won’t run directly on ARM devices. |
| Distribution | Choose the DEB or RPM package for your distribution. Let the package manager resolve library dependencies and check the app documentation for requirements. |
| Desktop and permissions | The GUI requires an active desktop session. TUN requires network permissions; don’t run the entire interface with elevated privileges just for convenience. |
Mihomo Core Downloads
For users managing servers, routers, or services themselves. The core has no desktop configuration interface; you’ll need to prepare a configuration directory, startup options, and service permissions. Most users should choose a GUI client for their platform.
| Operating system | Architecture | Package details | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP archive; extract and run from the command line | Download ZIP |
| Windows | ARM64 | Core binary for ARM64 systems | Download ZIP |
| macOS | Intel · AMD64 | GZ-compressed Darwin core binary | Download GZ |
| macOS | Apple Silicon · ARM64 | Native Apple Silicon core binary | Download GZ |
| Linux | AMD64 | Debian-family package | Download DEB |
| Linux | AMD64 | Standalone GZ-compressed core binary | Download GZ |
| Linux | ARM64 | 64-bit ARM servers and compatible devices | Download GZ |
| Linux | ARMv7 | Core binary for ARMv7 environments | Download GZ |
| Linux | MIPS softfloat | Binary for MIPS soft-float environments | Download GZ |
Core Runtime Requirements
| Check | Requirements and guidance |
|---|---|
| System and ABI | Match the operating system, instruction set, and runtime environment. Don’t choose a file based only on the CPU’s product name. |
| Configuration and directories | Prepare a compatible YAML configuration and a writable working directory. The service process must be able to read relative paths, rule files, and data files. |
| Network permissions | Configure listening addresses, firewall rules, and TUN permissions as needed. Bind the management interface to trusted networks only; don’t expose it directly to the public internet. |
INSTALLATION NOTES
From download to first connection
A completed download only means you have the program. Follow the steps below to check architecture, configuration, and network routing separately, so installation issues don’t get confused with subscription problems.
01 / PREPARE
Back up your working configuration before installing
If your current client works, note your subscription URL, configuration name, proxy group selections, and custom overrides first. Subscription links may contain access credentials, so store them somewhere private and controlled—not in public screenshots or shared documents. When switching apps, import the subscription again rather than copying the entire app data folder.
Quit the old client, then check the system proxy and VPN status. Some apps leave background processes or helper services running after you close the window. If two clients manage network traffic at once, you may see port conflicts, duplicate routes, or a system proxy still pointing to the old port. Keep to one active routing method before testing.
02 / IMPORT
Check the configuration format, not just the file extension
Clash clients typically read compatible YAML configurations, but a matching file extension doesn’t guarantee that the current core supports every field. If import fails, check whether the error concerns the subscription request, file parsing, or an unsupported protocol field. A link that returns a login page or error message may also have been saved as a file and mistaken for a configuration.
The installer does not include a usable subscription. Prepare a subscription or node configuration you’re authorized to use, add it in the app’s configuration manager, and wait for it to load. Then check that your proxy groups appear. For step-by-step instructions, read the quick-start guide. There’s no need to change DNS, TUN, and complex rules during initial setup.
03 / CONNECT
Test a basic connection before routing more traffic
On desktop, start with rule mode and the system proxy, then test a real page in your browser. On mobile, approve the VPN prompt from the system. Once connected, consider TUN if your apps require it. The system proxy does not cover every app automatically, and TUN does not make every rule global; they address traffic routing and the scope of interception in different ways.
If the client starts but can’t connect, check that the configuration is enabled, a proxy group is selected, and the system proxy points to the current listening port. Then review the connection log for matched rules and errors. Handle node timeouts, DNS resolution failures, and local port conflicts separately. See the troubleshooting guide for detailed steps.
04 / UPDATE
Distinguish app versions, core versions, and package architectures
The client interface and underlying core may update independently. Apps with the same name may not support exactly the same core features. If a configuration field fails after an update, check whether the current core supports it. If the installer reports an incompatible system, check your OS version and architecture before changing the subscription again.
Download links use the current manifest URL, and card version details appear only when data is available. A cross-platform app’s overall version number may differ from the version in a platform-specific filename; neither tells you the package architecture. Before installing, check the button label, actual filename, and installer prompts—especially the shared macOS x64 downloads noted on this page.
DOWNLOAD FAQ
Download and Installation FAQ
First check that the installer matches your device, then troubleshoot configuration and connectivity. These answers cover issues related to the downloads on this page.
Should I download arm64 or x64 for an Apple Silicon Mac?
Choose an installer explicitly labeled arm64 or Apple Silicon whenever possible. Clash Plus has a dedicated arm64 download. Some other clients on this page currently link to the same x64 file from both architecture buttons, as noted on their cards. These are not native arm64 builds and may require Rosetta on Apple Silicon Macs. Check each app's compatibility requirements.
Where can I install Clash Plus on iPhone or iPad?
Open the Clash Plus App Store listing from the iOS tab, check the app name, compatibility, and store details, then install it. Visit the official website at clashplus.io. After installation, follow the quick-start guide to import your configuration.
Can I connect as soon as the client is installed?
A client reads configurations, applies routing rules, and establishes connections; it does not include a subscription service. You’ll need a subscription link or configuration file you’re authorized to use. Import it, select a proxy group and rule mode, then enable the system proxy or VPN connection for your platform.
Why does macOS say the app can’t be opened?
Check the CPU architecture, the macOS versions supported by the app, and that the download completed. Move the app to Applications. If macOS blocks it, confirm the source is trusted and follow the prompts under System Settings > Privacy & Security. Don’t disable system-wide security. If macOS says the app is damaged, download it again and check compatibility.
What should I keep before updating or switching clients?
Keep your subscription URL, configuration files, overrides, proxy group selections, and custom DNS settings. Quit the old client and turn off its system proxy or TUN before installing another. Configuration folders and UI settings are not fully interchangeable between apps. Migrate using a subscription or YAML configuration rather than replacing the entire app folder.
Are Clash for Windows and ClashX Meta still good choices for new devices?
These clients are kept here as archived, discontinued projects, mainly for migrating older setups and comparing configurations. For a new device, start with a current client such as Clash Plus. Older cores may not recognize newer protocols or configuration fields, and keeping an old app does not mean it will continue to receive compatibility fixes.
DOCUMENTATION
Next steps after installation
For your first setup, follow this order: import a subscription → choose a rule mode → authorize the connection → test access. If an existing configuration stops working, troubleshoot by symptom rather than changing several network settings at once.