Clients / Packages / CPU Architecture
FlClash, Clash Plus, and other clients in the Clash ecosystem. Choose your operating system first, then confirm the package architecture.
Find a client by device
The first card for each platform is the recommended option. Other clients have their own interface and configuration workflows. Choose based on OS compatibility, your existing setup, and how you plan to use the client.
The GUI installers in this section are for x64. Check your system type under Settings → System → About. After installation, import your subscription and enable system proxy or TUN if needed. Before switching clients, quit any other proxy app so you can tell which one is handling your connections.
A good starting point for a first installation: install the client, then add your existing subscription. After importing it, check that the configuration is selected and choose a rule mode and suitable proxy group. When enabling system proxy or a virtual network adapter for the first time, follow any permission prompts. Confirm installation and connectivity separately.
For users who want desktop configuration management and rule-based routing. When migrating an existing setup, note your local overrides, proxy group selections, and DNS settings as well as the subscription URL. Service mode and TUN require different permissions from a standard system proxy. Install the service as prompted, then check which traffic it handles.
FlClash includes subscription management, proxy selection, and network mode settings. It's a good fit if you want a similar workflow on desktop and mobile. After installing, add your subscription on the configuration page, update it, and select the configuration. If you use the ZIP package, keep the extracted folder intact rather than moving only the main executable.
Another desktop GUI option. When switching clients, test the basic connection with the same subscription first, then migrate custom rules and local preferences one at a time. Clients may organize configuration enhancements and core settings differently. Copying the entire data directory can carry over outdated paths and service state.
Kept for reproducing legacy environments and migrating existing workflows. Archived versions no longer gain core features, protocol support, or OS compatibility; they may not recognize protocols or fields in newer subscriptions. For new installations, choose a maintained client. If you need to keep using a legacy setup, back up its configuration and test connectivity and proxy restoration after quitting.
| Check | What to do |
|---|---|
| Windows version | Use a Windows version that still receives security updates. Check each client's installer for its specific minimum version. |
| Processor | Packages here are x64 / AMD64. On Windows ARM devices, check compatibility with the app and network drivers first. |
| Network permissions | System proxy works with apps that follow Windows proxy settings. TUN or background services may require administrator approval. |
| After installation | Import and select a configuration, then test the connection. Turn off system proxy and TUN in the old client before uninstalling or switching. |
Open About This Mac from the Apple menu to check whether your Mac has Apple silicon or an Intel processor. Check the architecture label against the actual package file. Some clients currently link both architecture options to the same x64 file; details are noted on their cards.
Choose the DMG for your chip and follow the instructions in the mounted disk image. Approve the required system permissions on first launch, then import your subscription and select an outbound policy. Before updating, quit the app and keep your existing configuration. After replacing it, test the basic connection before restoring custom network settings.
For users who want desktop rule management and enhanced configuration options. Both the Apple silicon and Intel links currently point to an x64 DMG. On Apple silicon, check Rosetta and component compatibility; follow the installer and launch prompts. If you need a native ARM64 package, look for a client in this section that explicitly offers one.
Configuration and proxy workflows are similar to those on other platforms. Both macOS links currently provide the AMD64 DMG; here, AMD64 means x64, not native ARM64. Apple silicon users should check compatibility first. You can import a subscription into another client, but local interface preferences, permissions, and TUN state must be set up again.
Kept for users with existing ClashX Meta configurations and menu bar workflows. Both architecture links currently provide an x86_64 file. On Apple silicon, check translation support and compatibility with legacy components. Archived software may not support newer protocols or configuration fields. Before migrating, keep a copy of the original configuration and test the same subscription in a maintained client.
| Check | What to do |
|---|---|
| Windows version | Minimum macOS versions vary by client and build. Check the app's compatibility notes before installing. |
| Chip architecture | Apple silicon uses ARM64; Intel uses x64 / x86_64. Some download links currently share the same x64 file. |
| Installing the app | Open the DMG and follow the prompts to install the app in Applications. On first launch, check for system prompts under Privacy & Security. |
| Network permissions | Grant network extension or service permissions as needed, and avoid having multiple clients change system proxy settings at once. |
Most recent Android phones use ARM64, but check which app architectures your device supports. Install the APK with the system installer and approve VPN access the first time you connect. Running multiple apps that use a VPN interface at once may cause them to replace one another's connection.
ARM64 APK available. When installing, allow installs from the source you used to download the file, as prompted by Android. You can revoke this permission afterward if you prefer. On first launch, add your subscription and confirm it updates successfully before connecting. If Android pauses the connection in the background, check battery and background activity settings instead of reinstalling the client.
Packages are available for specific architectures, plus a universal package if you're unsure which one you need. Universal packages are usually larger; choosing the correct architecture-specific package can reduce the download size. After importing your configuration, select it and check the proxy group. Connection reliability also depends on Android's background restrictions and the status of other VPN apps.
Use a similar configuration interface on mobile and desktop to manage subscriptions from the same source. The ARM64 package is for compatible phones, the ARM package is for devices that support 32-bit apps, and x86_64 is for matching devices or environments. After importing, select the configuration. Rule mode, proxy group, and VPN connection status all determine how traffic is routed.
For Android users whose configurations use Surfboard's supported syntax and protocols. Surfboard uses a different configuration format from Clash YAML, so import a compatible configuration rather than simply changing a file extension. If you have a Clash subscription, check whether your provider offers a matching format. Verify protocol, rule, and DNS fields separately.
| Check | What to do |
|---|---|
| OS compatibility | Check the minimum OS version and architecture shown by the APK installer. If installation fails, check your Android version, available storage, and package architecture. |
| Package architecture | arm64-v8a is ARM64; armeabi-v7a is 32-bit ARM; x86_64 is for matching architecture environments. |
| Connection permissions | Approve the system VPN prompt the first time you connect. If another VPN is active, disconnect it before testing this client. |
| Background activity | Check battery optimization, background activity, and auto-start permissions in your device settings to keep the app running when needed. |
Install Clash Plus on iPhone or iPad through the App Store. Check device compatibility, features, and pricing on the store page before installing. Desktop installers and Android APKs do not work on iOS; use the App Store link in this section.
After installation, import an existing subscription or configuration, then add a VPN configuration and approve the connection when prompted by iOS. Subscription availability, protocol compatibility, and App Store installation are separate steps. Once the app opens, confirm that the configuration loaded and a proxy group is selected. Check the App Store listing for current pricing and supported iOS versions.
| Check | What to do |
|---|---|
| Device and OS | Check the App Store listing for compatibility with your iPhone or iPad and current iOS version. |
| Install from the App Store | Open the Clash Plus App Store link in this section and install the app. |
| Network permissions | On first connection, follow the system prompts to add a VPN configuration. Approve it, then return to the client and check its status. |
| Configuration | Have a working subscription or configuration ready. Test the connection on Wi-Fi and cellular data separately. |
For desktop Linux, choose DEB or RPM according to your distribution's package manager. The GUI packages here are AMD64 / x86_64. Servers and routers are usually better suited to a direct core deployment. GUI clients also require a desktop session and supporting runtime libraries, so the package extension alone does not guarantee compatibility.
Available as DEB and RPM packages. Debian- and Ubuntu-based distributions generally use DEB; Fedora and other RPM-based distributions use RPM. Install dependencies through your distribution's package manager. Launch the app in a desktop session, import a configuration, and test the system proxy. Follow the client's instructions for TUN permissions and service setup.
The FlClash Linux desktop version includes subscription, proxy, and configuration controls. Choose DEB or RPM for your distribution, or use the AppImage build. AppImage may still require runtime dependencies and executable permission. When changing installation formats, keep your user configuration, quit the old process, and then launch the newly installed app.
| Check | What to do |
|---|---|
| Processor | GUI packages in this section are AMD64 / x86_64. Run uname -m to check the machine architecture reported by the kernel. |
| Distribution | DEB and RPM use different package management systems. Compatibility also depends on runtime libraries and the desktop environment. |
| Dependencies | Use your distribution's package manager to install the downloaded package and follow its output to resolve missing dependencies. |
| No desktop environment | Server and router users can switch to the Mihomo core section and manage service startup and network permissions themselves. |
The Mihomo core is for users managing proxy services on servers, routers, and other self-managed systems. It handles protocols, rules, DNS, and connections; a GUI is provided by a client layered on top. Most desktop and mobile users should choose a GUI client above. Direct core deployments require you to manage the configuration file, working directory, service permissions, and logs.
| Operating system | Architecture | File and download |
|---|---|---|
| Windows | AMD64 | Download AMD64 ZIP |
| Windows | ARM64 | Download ARM64 ZIP |
| macOS | Intel AMD64 | Download Intel GZ |
| macOS | Apple Silicon ARM64 | Download Apple silicon GZ |
| Linux | AMD64 | Download AMD64 DEB |
| Linux | AMD64 | Download AMD64 GZ |
| Linux | ARM64 | Download ARM64 GZ |
| Linux | ARMv7 | Download ARMv7 GZ |
| Linux | MIPS-softfloat | Download MIPS-softfloat GZ |
| Check | Deployment checklist |
|---|---|
| OS and instruction set | Check that the operating system, CPU architecture, and target binary are compatible. ARMv7, ARM64, and MIPS are not interchangeable. |
| Configuration file | Prepare a valid mihomo configuration and verify rules, proxy groups, listening ports, and data file paths. |
| Execution permissions | On Unix-like systems, ensure the binary is executable. Set permissions required for TUN and port listening based on the features you use. |
| Service management | Manage startup, shutdown, logs, and updates yourself. Back up the configuration and stop the old process before replacing the binary. |
For differences in core features and configuration formats, see the Protocol and Core Technical Reference. For a core bundled with a client, use the client's built-in update method to avoid mismatched paths or service state after a manual replacement.
Test the basic configuration before adding custom settings. Change one network option at a time to make issues easier to diagnose.
Before updating, save your subscription URL, local rules, and configuration overrides. When quitting the old client, turn off system proxy or TUN first so two apps don't handle network traffic at the same time. If the installer reports that a file is in use, check the tray app and background services before continuing.
Add your existing link on the configuration or subscription page, update it, and confirm that the configuration loaded successfully. Subscription links usually contain personal access credentials, so store them securely. Seeing a subscription name does not mean it's active; select the configuration and check its proxy group.
For everyday use, start with rule mode and enable system proxy or TUN as needed by your apps. If the connection fails, check your local network and subscription first, then review the client logs. Updating the app and updating a subscription are separate actions; doing one does not update the other.
Download FAQs
Find answers about system requirements, subscription sources, and update preparation below.
Choose your device's operating system, then start with the recommended Clash Plus. To use FlClash, find its card under Windows, macOS, Android, or Linux. For a new installation, choose a client that is still maintained. Before migrating an existing setup, back up your subscription, rules, and local settings.
Clients organize their interfaces and settings differently. Start with the default configuration to test the connection, then adjust DNS, per-app routing, and other advanced options one at a time. For protocol support and core compatibility, see the protocol guide.
Check your processor architecture in system information. x64 and AMD64 usually refer to the same 64-bit architecture; ARM64 is a different architecture. If you're unsure which Android architecture you need, choose the universal Clash Meta for Android package. Some macOS architecture links currently point to the same x64 package, so check the card's compatibility notes before downloading.
64-bit systems can use different instruction sets, so “64-bit” alone doesn't tell you whether a package will work. Check the actual runtime environment, especially for emulators, virtual machines, and remote devices. If you download a file on a PC for a router, choose the package for the router's architecture.
Add your existing subscription link on the client's configuration or subscription page, save it, update it, and then select the configuration. Downloading a client and getting proxy service are separate steps; the installer does not create a usable subscription. Treat subscription links as sensitive information and never share a complete link containing access credentials.
If an update fails, check that the link is complete, the service is active, and the configuration format is supported. See the subscription import guide for where to enter it, or the subscription sources guide for information about sources and usage limits.
Open the Clash Plus App Store page in the iOS section. Check compatibility with your device, features, and current pricing, then install through the App Store. The official client website is clashplus.io. After installation, import an existing configuration and approve the VPN connection when prompted by iOS.
Test the connection on Wi-Fi and cellular data separately. If you use one subscription across multiple devices, check your provider's device and simultaneous connection limits to avoid mistaking service restrictions for an installation problem.
Back up your subscription URL, local rules, configuration files, and overrides, then disconnect and quit the old client. After updating, check that your configuration is selected, proxy groups are intact, and system proxy or TUN is enabled as expected. When switching clients, verify configuration compatibility and local settings separately; copying only the application files is not enough.
Clash for Windows and ClashX Meta are marked as archived clients on this page. If a legacy version cannot recognize configuration fields, check protocol and core support instead of repeatedly reinstalling the same version. Once migration is complete and the connection is verified, decide whether to remove the old data.
Mihomo is a core that handles proxy protocols, rules, and network connections; it does not include a full desktop interface. Core packages are mainly for users managing their own services on servers or routers. Most desktop and mobile users should start with a GUI client. Running the core directly means managing the configuration, permissions, startup, and logs yourself.
GUI clients handle some core management for you and may use their own data directories and service mechanisms. If you already use a client, check its built-in core management options first. Before replacing core files manually, confirm how the client supports core updates.