Packages · Platforms & Architectures
Choose your device’s operating system, then select a package format. Use a graphical client on desktop or mobile; for servers and routers, see the Mihomo core.
Installers and subscription configurations are managed separately. Before switching clients, keep your existing configuration and local overrides so you can migrate them one at a time.
Start with an installer that includes a graphical interface. Desktop downloads here are primarily for x64 systems. If your device runs Windows on ARM, check system and app compatibility first; an ARM64 core is not a graphical client installer.
A good fit if you want one interface for importing configurations, choosing policies, and managing everyday connections. After installation, import your subscription, confirm the configuration is selected, then enable the system proxy. If you need to route traffic from more apps, learn about TUN permissions first.
Project website: clashplus.io. After installation, continue setup with the Getting Started guide.
A good fit if you want to manage configurations and rules with desktop integration. After installation, check the service and core status. The system proxy and TUN work differently; when prompted for permission, verify which feature is requesting access instead of toggling everything.
Follow the installer’s runtime requirements. If it reports a missing desktop component, resolve that first before troubleshooting your subscription.
A good fit if you want a similar workflow across desktop and mobile. After importing a configuration, check that its policy groups contain selectable options, then test access. A successful import only means the configuration was read—it doesn’t mean every app on your system is using the proxy.
Before upgrading, keep copies of your local rules and configuration. This helps keep interface preferences separate from subscription data during migration.
Another Windows graphical client option. When comparing clients, consider more than the interface: check how configurations are merged, what the core supports, and whether service permissions fit your workflow. Don’t overwrite the old client’s data directory; test with a configuration copy first.
Before switching clients, quit the old one and turn off the system proxy it configured to avoid port conflicts and overlapping traffic control.
This archived installer is mainly for recreating older environments and referencing configurations during migration. It’s not recommended for new installations: older cores may not support newer subscription fields or protocols. Being able to import a file doesn’t mean every setting in it will work.
Keep a copy of your old configuration before migrating. For help choosing a client, see Compare clients.
| Item | What to choose | Before installing |
|---|---|---|
| Processor architecture | This section mainly offers x64 installers | Check the system type in Settings. For ARM devices, verify compatibility separately. |
| System and dependencies | Follow the selected client installer’s requirements | Install system updates. If a runtime component is missing, resolve that dependency first. |
| Traffic permissions | Configure the system proxy and TUN separately | Grant permissions only when you need the service or virtual interface. Avoid having multiple clients manage traffic at once. |
Check your chip under About This Mac before choosing a download. Some current files are Intel builds, even when downloaded from the Apple Silicon option; verify Rosetta compatibility. The option label doesn’t guarantee a native ARM build.
Offers separate downloads for Apple Silicon and Intel, with a graphical interface for managing configurations and everyday connections. Open the disk image and follow the installation prompts, then launch the app from Applications. Import a configuration and confirm it works before deciding whether to enable launch at login.
Project website: clashplus.io. System permissions and client settings are configured separately.
A good fit if you want to manage desktop configurations and adjust rules. Both current chip options fall back to an x64 DMG. Apple Silicon users should check Rosetta and macOS compatibility; don’t rely on the chip label alone to determine the build architecture.
Check service permissions before enabling TUN. If the connection fails, review the logs before changing DNS or rules.
A good fit if you want a similar workflow across multiple devices. The current download is an amd64 build; the Apple Silicon option also requires checking compatibility. When migrating subscriptions, copy the subscription source first, then handle local overrides separately to identify incompatibilities.
Updating the client doesn’t update your subscription, and vice versa. After upgrading the app, check the selected configuration and policy groups.
Intended for existing installations and migration. The archived file is an x86_64 build, so Apple Silicon users should check compatibility. For new installations, consider a maintained client, especially if your configuration uses newer protocols or rule fields.
Before migrating, save your configuration and menu bar proxy settings. Avoid copying the entire old data directory over the new client.
| Item | What to choose | Before installing |
|---|---|---|
| Chip | Apple Silicon or Intel | Check About This Mac. Intel builds on Apple Silicon require Rosetta support. |
| macOS version | Follow the client’s installation and launch requirements | If the app won’t launch, check macOS compatibility before changing your subscription. |
| Network extensions and services | Grant permissions for the features you use | Review the system prompt the first time you use a feature, and confirm which app is requesting permission. |
For most recent phones, first check whether the ARM64 build is suitable; check ARMv7 for older devices. The first connection usually prompts for VPN permission, the system interface for routing local traffic. Typically, only one app can use this interface at a time.
Provides an ARM64 APK for importing configurations, choosing policies, and managing connections on your phone. Allow your browser or file manager to install the APK, then revoke that source permission if you like. VPN access is requested separately when the client connects.
Project website: clashplus.io. If the app frequently stops running in the background, check battery optimization and background restrictions in system settings.
A Clash Meta client option for Android, with ARM64, ARMv7, and universal APKs. Choose the matching build if you know your device’s architecture. Otherwise, try the universal build—but it may not work with every Android version.
Grant the VPN permission needed to connect, then adjust background activity and battery optimization settings for your device.
A good fit if you already use FlClash on desktop or prefer a similar configuration workflow. Choose ARM64 or ARMv7 based on your device’s support. If installation fails with a parsing error, check that the download is complete, the architecture matches, and your Android version meets the app’s requirements.
After migrating a configuration from desktop, check background activity and network permissions on mobile. Don’t just copy desktop system proxy settings.
A universal APK for users with a compatible Surfboard configuration. Its configuration syntax differs from Clash YAML, so changing the file extension won’t make it importable. Before downloading, confirm that your subscription uses the right format and that the protocols you need are supported.
If the configuration format doesn’t match, fix that first. Trying packages for different architectures won’t resolve configuration incompatibility.
| Item | What to choose | Before installing |
|---|---|---|
| Architecture | ARM64, ARMv7, or universal | Check which app ABIs your system supports; don’t judge by your phone’s age or model alone. |
| macOS version | Follow the installer’s compatibility guidance | If installation fails, check for an OS version issue, architecture mismatch, or conflict with an existing app signature. |
| App permissions | Install sources, VPN access, and background activity | These permissions serve different purposes. Configure each as needed, and avoid running multiple VPN apps at the same time. |
Check the app’s details and device compatibility in the App Store, then install it. The client reads configurations and manages connections; you’ll need to provide your own subscription. Confirm the system’s connection permission the first time you use the app.
Install from the App Store, then import a subscription you’re authorized to use or a local configuration. Check your selected policies before connecting. When iOS prompts you to add a VPN configuration for the first time, verify the app name and the source of the request. Check both your actual access and the client’s logs to confirm the connection works.
Project website: clashplus.io. Check the App Store listing for device requirements, app updates, and the latest store information.
| Item | What to choose | After installation |
|---|---|---|
| System and device | Check the App Store compatibility section | Confirm your iOS version meets the app’s requirements and that you have enough storage. |
| Configuration source | Prepare a valid subscription or local configuration | Confirm the imported configuration is selected, then check your policies and connection status. |
| Connection permission | Add the VPN configuration when prompted by iOS | If another VPN is already installed, check which app currently manages the connection. |
On a desktop Linux system, start with a graphical client. DEB and RPM are different package formats; a filename containing “Linux” doesn’t tell you which one to use. Check your distribution’s package system, processor architecture, and desktop dependencies. Downloads in this section are for AMD64.
A good fit for managing subscriptions, rules, and proxy status on a Linux desktop. Choose DEB for Debian, Ubuntu, and compatible distributions; choose RPM for Fedora and other RPM-based distributions. Start the interface after installation, check the core and service status, then enable TUN if needed.
ARM64 Linux devices can’t install the AMD64 packages in this section. Check what it does before granting service permissions or enabling TUN mode.
Provides an AMD64 DEB for desktop users on compatible package-based systems. Install it with your distribution’s package manager so dependencies are handled automatically. If the interface won’t launch, check the terminal output to determine whether the problem is a dependency or configuration issue.
Tray icon availability depends on your desktop environment. After closing the window, check whether the app is still running in the background and whether the system proxy remains enabled.
| Item | What to choose | How to check |
|---|---|---|
| System architecture | Graphical packages here are AMD64 / x86_64 | Run uname -m. If the result is aarch64, don’t install an AMD64 package. |
| Distribution | DEB or RPM package system | Check /etc/os-release, then choose a package based on your distribution’s package manager documentation. |
| Desktop and dependencies | Requires a compatible graphical environment | Let your package manager handle dependencies. For a headless server, consider the core below. |
| Network permissions | TUN and service installation may need extra permissions | First confirm the app starts in normal mode, then enable features that require permissions one at a time. |
Three checks before installing
These determine whether the app can install, launch, and connect. Check them in order to pinpoint problems more easily than by changing several settings at once.
AMD64 doesn’t mean it only works with AMD processors; it’s the x86 64-bit architecture used by common Intel PCs too. ARM64 is a different build target. Even with 64-bit hardware, your operating system may support only certain app architectures. Check your system information before downloading.
EXE, DMG, APK, DEB, and RPM each require a compatible environment. A compressed core is usually just an executable; it won’t create a graphical interface, desktop shortcut, or complete service for you. If your Linux package manager reports missing dependencies, resolve them before starting the client.
The client, subscription, and core are separate components. Updating the app won’t fix an expired subscription, and refreshing a subscription won’t update the app. First confirm the configuration loads, then check the policy groups and traffic routing mode. For protocol compatibility, see the core technical reference.
Command-line deployment
For servers, routers, and users who manage their own startup process. Desktop users should choose a graphical client above. The core package has no subscription management interface; you’ll need to manage configuration directories, listening ports, logs, and system services yourself.
| System | Architecture | Format and deployment notes | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP; extract, then run from a terminal | Download AMD64 ZIP |
| Windows | ARM64 | ZIP; for compatible ARM64 systems | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ; set executable permissions after extraction if needed | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ; native ARM64 core | Download Apple Silicon GZ |
| Linux | AMD64 | DEB; for compatible package management systems | Download AMD64 DEB |
| Linux | AMD64 | GZ; manual extraction and deployment | Download AMD64 GZ |
| Linux | ARM64 | GZ; for common aarch64 devices | Download ARM64 GZ |
| Linux | ARMv7 | GZ; for compatible 32-bit ARM environments | Download ARMv7 GZ |
| Linux | MIPS-softfloat | GZ; check byte order and software floating-point support | Download MIPS-softfloat GZ |
Prepare your own configuration file and make sure its ports aren’t already in use. Run the core in the foreground first to check that the configuration parses, then set up a background service. Enabling automatic restarts right away can turn a configuration error into a restart loop, making the original error harder to spot.
A standard proxy listener and a TUN interface have different permission requirements. Configure the relevant permissions only when you use those features; don’t grant the entire service broader privileges just to make it start. For rules, DNS, and protocol compatibility, see the protocol and core reference.
Set up the configuration after installation, then adjust advanced features once the connection works. These questions can help distinguish package issues from runtime settings.
For everyday desktop and mobile use, choose a graphical client. It provides options to import subscriptions, select policies, and review connection logs. The Mihomo core is for users who manage configuration, startup parameters, and system services themselves; downloading the core alone does not provide a graphical interface.
AMD64 is also called x64 or x86_64 and works with common 64-bit Intel and AMD processors. ARM64 is also known as aarch64 or arm64-v8a. ARMv7 is for some older 32-bit ARM devices. Choose an architecture supported by your operating system—not just one based on the processor brand.
Choose DEB for Debian, Ubuntu, and compatible systems; choose RPM for Fedora and other RPM-based distributions. Check the package architecture too. A graphical client is suited to everyday desktop use, while a core archive is for manual deployment—you’ll need to manage services, permissions, and configuration directories yourself.
Client installers don’t include a ready-to-use personal subscription. After installation, import a subscription you’re authorized to use or a local configuration, select the configuration and policies, then enable the system proxy or TUN if needed. Follow the Getting Started guide to establish a basic connection before adjusting rules.
Archived clients are mainly useful for recreating older environments, opening legacy configurations, and migration. For a new installation, choose a maintained client: older cores may not support newer protocols or configuration fields. Keep a copy of your original configuration during migration, and remove the old client only after confirming the new setup works.
Keep your subscription source, local configuration, rule overrides, and any essential connection settings. Note the status of the system proxy, TUN, and launch-at-startup options. Data directories and configuration merging vary between clients, so test an imported copy in the new client first. Don’t let two clients manage the same network settings at once.
Already installed but still having trouble? Search the FAQ by issue. For subscription format help, see Subscription guide.