Client installers / processor architectures / installation guides
Choose an operating system, then select a client and processor architecture. FlClash is available for desktop and Android; for iOS, see the Clash Plus App Store listing.
Desktop clients · x64 installers
Clash Plus is a good starting point for a first-time install. Choose FlClash if you prefer a Flutter-based interface. If you already use another client, back up your configuration and compare how each handles subscriptions and system proxy settings. Don’t run multiple clients that control the system proxy at the same time.
A good fit for first-time Windows proxy setup. Install the desktop client, import an existing subscription, select the active configuration, and check the outbound policy. Before enabling the system proxy, quit any other proxy clients to prevent them from overwriting each other’s settings.
EXE installer · x64
A desktop client for managing subscriptions, rules, and proxy settings in one place. When you first enable TUN or service-related features, follow the prompts to grant permissions. For regular browser use, test the system proxy first; there’s no need to enable every network-control option at once.
EXE installer · x64
Built with Flutter and powered by the mihomo core. A good fit if you use Windows and Android and want a similar workflow on both. After importing a configuration, you can adjust rule mode, system proxy, and TUN settings. When switching devices, check each one’s ports and permissions separately.
EXE installer · AMD64
Another desktop interface to consider if you want to compare configuration management and workflows. Before switching clients, export your subscriptions and local rules, then check policy group names. Interface settings from one client generally can’t be imported as a universal configuration.
EXE installer · x64
Archived download for legacy environments and migrating existing configurations. For a new installation, choose a maintained client above. Older cores may not recognize newer configuration fields; if parsing fails, check field compatibility before reinstalling.
Archived Windows installer
| Check | Guidance |
|---|---|
| Operating system | Use a supported version of Windows 10 or 11. Check the installer for the exact minimum requirements. |
| Processor | Desktop downloads in this section are primarily x64. Windows on ARM users should confirm that their system supports x64 apps. |
| Network control | The system proxy affects only apps that follow proxy settings. TUN and service installation may require administrator permission. |
| Installation order | Quit older clients, install the app, import your configuration, then enable network features one at a time. The default mixed port is often 7890; check your current settings. |
Desktop clients · DMG images
Check your chip under About This Mac. Clash Plus provides separate downloads for Apple Silicon and Intel; some other options currently offer x64 files only, as noted on their buttons. Don’t assume a download is native ARM just because of its listing name.
Choose the DMG for your chip, open it, and move the app to Applications. On first launch, import a subscription before enabling the proxy. Apple Silicon and Intel require different architecture builds; use the matching build when updating, too.
DMG · separate native ARM64 and x64 downloads
A good fit for users who want desktop configuration management. Both chip options on this page currently point to the same x64 DMG; Apple Silicon users should check Rosetta compatibility. For a native ARM build, see the Clash Plus ARM64 download in this section.
Current file: x64 · Apple Silicon requires compatibility support
A good fit if you want a similar workflow across FlClash on desktop and mobile. The current DMG is labeled AMD64, and both download options point to the same file. Apple Silicon users should confirm compatibility before installing or migrating settings.
Current file: AMD64 · not a native ARM64 build
For reference with older macOS workflows and configuration migration. The current download is x86_64; the Apple Silicon option is also a compatibility build. This archived client isn’t recommended for new setups, particularly because of permissions and configuration compatibility on newer systems.
Archived DMG · x86_64
| Check | Guidance |
|---|---|
| Chip architecture | Apple M-series chips use ARM64; Intel Macs use x64. A compatibility build is not the same as a native ARM64 build. |
| System requirements | Use a macOS version that’s still supported. Check the app’s prompts for its minimum version. |
| Compatibility | Running x64 apps on Apple Silicon usually requires Rosetta. Before installing, check that your device’s policies allow the required components. |
| Permissions | Grant network permissions as prompted. If macOS blocks the app, check the specific reason rather than disabling system security features. |
Phones and tablets · APKs
Most newer Android phones use ARM64, but a device’s appearance or OS bitness doesn’t always reveal its processor architecture. Check your device’s processor information first. If you’re unsure, see the universal package for Clash Meta for Android. On first connection, approve the system VPN request.
ARM64 installer. A good fit if you want to import a subscription first and then use rule mode. Allow installation only for the browser or file manager you used to download the APK. You can revoke that permission after installation if you prefer.
APK · arm64-v8a
Downloads include ARM64, ARM, and universal builds. An architecture-specific package is the best match for your device; the universal package is useful if you can’t identify its architecture yet. After importing a configuration, select it before starting the VPN so the app uses the active configuration.
APK · ARM64 / ARMv7 / Universal
Built with Flutter, with a setup workflow similar to the desktop app. On mobile, network traffic is routed through Android’s system VPN, not the desktop system proxy. If the connection drops when the screen locks, check battery optimization and background activity permissions.
APK · arm64-v8a / armeabi-v7a
A good fit for Android users who already have a compatible configuration. Its format differs from Clash YAML, so changing the file extension alone won’t make it importable. Confirm format support with your configuration provider before downloading, and check syntax and policy references when migrating rules.
APK · universal Android build
| Check | Guidance |
|---|---|
| System compatibility | Minimum Android versions vary by app. If the installer reports incompatibility, check your OS version and CPU architecture first. |
| Choose an architecture | ARM64 corresponds to arm64-v8a; 32-bit ARM usually corresponds to armeabi-v7a. Universal packages support multiple architectures, as specified by the app. |
| VPN permission | Approve the system VPN request on first launch. Other VPN apps may not run at the same time as the current connection. |
| Background activity | Once the connection is stable, adjust battery optimization if needed. Change one power-saving setting at a time to identify what affects the connection. |
iPhone and iPad · App Store
Use a client made for iPhone or iPad. The FlClash Android installer won’t work on iOS. This section links to Clash Plus in the App Store; check the current listing for compatibility, in-app features, and pricing.
Install and update through the App Store. On first launch, import a configuration you’re authorized to use, select the active policy, then follow the system prompts to add a VPN configuration. Desktop setup instructions on this site don’t replace the iOS permission flow; follow the app and system prompts.
If your subscription URL contains access credentials, don’t include the full URL in public screenshots. After moving to another device, check policy groups and DNS settings again, and confirm the current client supports the configuration’s features.
App Store · Check the listing for iPhone and iPad compatibility
| Check | Guidance |
|---|---|
| System version | Check the Compatibility section of the App Store listing for minimum iOS and iPadOS requirements. |
| Installation | Use the App Store link above to view app details and update history. |
| Network permissions | Follow the prompts to add a VPN configuration. Managed devices must also follow their device management policies. |
| Configuration source | Have a working subscription or compatible configuration ready. Installing the client and subscribing to a service are separate steps. |
Linux distributions · DEB / RPM
Check your distribution’s package management system before choosing an installer. The GUI clients in this section provide AMD64 / x86_64 packages. For servers, routers, and other architectures, see the Mihomo core section; desktop installers aren’t general-purpose service binaries.
Available as DEB and RPM packages. Debian and Ubuntu-based distributions generally use DEB; Fedora and other RPM-based distributions use RPM. Install with your distribution’s package manager to handle dependencies. If a library is missing, check the specific dependency rather than installing a package for another distribution.
DEB / RPM · AMD64 / x86_64
Provides a Linux AMD64 DEB package. A good fit for Debian-based desktops where you want to use FlClash for configuration management. Tray support and whether apps follow the system proxy depend on your desktop environment and apps; successful installation doesn’t mean all apps are using the proxy.
DEB · AMD64
| Check | Guidance |
|---|---|
| Distribution | Choose the DEB or RPM package to match your package manager. Check the package dependencies for minimum system library requirements. |
| Processor | GUI packages in this section are AMD64 / x86_64 and won’t run on ARM64 or MIPS routers. |
| Desktop environment | Requires a working graphical session and the app’s dependencies. For headless servers, use the core instead. |
| Permissions and routing | TUN requires network device and routing permissions. Keep a recovery method available before enabling it, especially when managing a remote system, to avoid losing access. |
Command-line and service deployment · servers / routers
Mihomo is a network processing core, not a GUI client with subscription management. It’s intended for users who can manage configuration files, startup options, and service permissions themselves. Most desktop and mobile users should choose a GUI client above instead of taking on service deployment and routing maintenance.
AMD64 and x86_64 refer to the same common 64-bit desktop architecture. ARM64, ARMv7, and MIPS are not interchangeable. For routers, also check firmware ABI, endianness, and floating-point requirements; seeing ARM or MIPS alone isn’t enough to confirm compatibility.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Download ARM64 ZIP |
| macOS | Intel AMD64 · GZ | Download Intel GZ |
| macOS | Apple Silicon ARM64 · GZ | Download ARM64 GZ |
| Linux | AMD64 · DEB | Download AMD64 DEB |
| Linux | AMD64 · GZ | Download AMD64 GZ |
| Linux | ARM64 · GZ | Download ARM64 GZ |
| Linux | ARMv7 · GZ | Download ARMv7 GZ |
| Linux | MIPS softfloat · GZ | Download MIPS GZ |
| Check | Before deployment |
|---|---|
| System and ABI | Confirm the operating system, CPU architecture, and firmware compatibility. MIPS softfloat doesn’t mean the binary will run on every MIPS device. |
| Compressed files | Extract ZIP and GZ archives first. On Unix-like systems, you may also need to set execute permissions. A file extension alone doesn’t mean installation is complete. |
| Configuration file | Prepare a valid YAML file. Check policy group references, rule order, DNS, and listening ports before starting the service. |
| Service permissions | Standard proxy ports and TUN have different permission requirements. Use the least privileges possible and restrict access to the control interface. |
After downloading
Start with the smallest working connection, then add features one at a time. That makes it easier to tell whether an issue comes from installation, your subscription, rules, or system network settings.
After the download finishes, make sure the file matches your operating system and processor architecture. If the installer reports incompatibility, note the full message instead of trying multiple clients in a row. Back up your configuration before upgrading, so uninstalling doesn’t also remove app data.
The client doesn’t include a subscription service. After importing a subscription URL or local configuration, select it as the active configuration. If an update fails, check that the URL is valid and your system clock is correct. Don’t post the full subscription URL in public.
Choose rule mode and a working policy, then visit a familiar site in your browser. If the browser works but an app doesn’t, check whether that app follows the system proxy. Enable TUN only if needed, then retest DNS and direct connections.
Installers and updates
For Windows, macOS, Android, and iOS, start with the recommended Clash Plus. For Linux, start with Clash Verge Rev. Choose FlClash if you want a similar experience on desktop and Android. If you already have a working configuration, check that the client supports its format before switching.
Check your processor architecture in your system’s About or System Information settings. Most Intel and AMD desktop PCs use x64 or AMD64. Recent Android devices commonly use ARM64; older 32-bit ARM devices need ARMv7. Apple Silicon is ARM64, but some macOS downloads on this page are currently x64 files. Check each download card for compatibility details.
The client and subscription service are provided separately. After installation, import a subscription URL or configuration file you’re authorized to use, select it as the active configuration, choose an outbound policy, and start the connection. First, test browser access in rule mode; enable the system proxy or TUN only if your apps need it. See the getting started guide for detailed steps.
Make sure the download completed and the file extension matches your operating system, then check the processor architecture and any installer prompts. On Windows, review your system’s security history; on macOS, check the specific message under Privacy & Security. On Android, grant installation permission only to the source you actually used to download the APK. Don’t leave system protections disabled just to install an app.
An in-place upgrade of the same client usually keeps its existing data directory, but this depends on the installation method and app version. Before upgrading, export your configuration and note your ports, DNS settings, and rule overrides. Don’t assume data will migrate automatically when switching clients or moving from an installed app to a portable archive. Check your settings again after importing.
The Mihomo core parses configurations, matches rules, and handles proxy connections, usually running from the command line or as a service. A GUI client adds subscription management, settings screens, and system integration. Server and router users can choose a core binary; most desktop and mobile users should choose a GUI client for their platform.