CLIENTS / PACKAGES / ARCHITECTURES
Client downloads, system architectures, and config options.
Choose your operating system first, then check your CPU architecture. GUI clients are suited to everyday desktop and mobile use. Mihomo core builds are for users who manage processes, services, and config directories themselves.
PLATFORM INDEX
Download buttons specify the package format or architecture. Version details come from the download manifest; check the selected app’s installation prompts for system requirements.
These downloads are for x64 desktops. Check System type under Settings > System > About. Don’t assume an ARM device is compatible based on its OS name alone; check its app emulation support separately.
A good fit for a desktop workflow that covers config import, proxy selection, and everyday connection management. On first launch, import an existing subscription or local file, select the config, and then enable the system proxy. If you need to route traffic from more apps, set up TUN using the guide. Avoid enabling multiple traffic-routing methods at once, which can make issues harder to diagnose.
A good fit if you want to manage subscriptions, rules, and desktop proxy settings. Before using service mode or a virtual network adapter, make sure the relevant components are installed and have the required permissions. When migrating an old config, check the results of its overrides and rule merging. A setting in the GUI may take precedence over a field with the same name in a subscription.
A cross-platform client for users who want a similar workflow across devices. Permissions and traffic-routing options still vary by OS. After installing, check for port conflicts with older clients. Once you’ve imported a config, use the connection view to confirm rules are matching instead of relying on toggle states alone.
Another option for managing desktop configs. If you’re switching from an existing client, back up your config files and client settings separately; don’t overwrite the new app’s entire data directory. After importing, check proxy group names, rule references, and core-specific fields. A subscription parsing successfully doesn’t mean every extension field will work the same way.
This archived download is for reproducing legacy environments and comparing old configs. The project is no longer maintained; its core’s protocol and field support may differ from current Mihomo. For a new install, consider one of the clients listed above. If you need to keep an old setup, store its config separately and don’t let the old app and a new client change system proxy settings at the same time.
| Check | Requirements and steps |
|---|---|
| Processor | These downloads are x64 / AMD64. They don’t support 32-bit systems; on ARM devices, check app emulation compatibility. |
| System | Use a Windows version that still receives system updates. Check the installer prompts for the minimum OS version and runtime requirements. |
| Permissions and connectivity | Installing services or TUN components may require administrator approval. The system proxy only affects apps that honor system proxy settings. |
Check your chip in Apple menu > About This Mac. Apple Silicon uses ARM64; Intel uses x64. After downloading, open the DMG, move the app to Applications, and launch it from there.
Separate installers are available for Apple Silicon and Intel, so you can choose based on your Mac’s chip. After launching the app, import a config and check the ports before enabling a connection method. If macOS asks for network permissions, review what the feature needs: standard system proxy settings and virtual network adapter routing have different permission scopes.
A good fit for managing desktop subscriptions, rules, and traffic-routing settings. The Apple Silicon option currently isn’t a separate native ARM build, so check compatibility with the actual x64 package. After installing, make sure your config parses correctly before deciding whether to install the service component. Don’t disable macOS security protections just to dismiss a launch warning.
Worth considering if you already use FlClash on mobile or another desktop OS. A cross-platform interface doesn’t mean permissions work the same way on every OS; check network permissions and background activity separately on macOS. Both options currently point to the same AMD64 file. Check your chip before installing—config compatibility doesn’t imply binary architecture compatibility.
For users who need the legacy menu bar workflow or want to reproduce an old config. The project is no longer maintained, and macOS updates may introduce new compatibility issues. Before switching clients, back up your local rules and config, turn off the old app’s system proxy, then import everything into the new client. This helps prevent stale port settings from breaking connections.
| Check | Requirements and steps |
|---|---|
| Chip | On Apple Silicon, choose a file explicitly labeled ARM64. On Intel, choose x64 / AMD64 / x86_64. |
| macOS version | Minimum macOS requirements vary by app. Check the installer prompts, especially on older systems. |
| Install location | Move the app to Applications before launching. Follow macOS prompts for network permissions and keep system security protections enabled. |
Most recent phones use ARM64, but check the app ABI supported by your device. After installing the APK, the first connection will usually trigger a system VPN permission prompt. Confirm the app name before allowing the connection.
This download is the arm64-v8a package. After installing, add a subscription or import a local config, then wait for proxies and proxy groups to load before connecting. If the connection drops when you switch apps or lock your phone, check battery optimization and background restrictions. First confirm the app is still running, then troubleshoot proxies or DNS settings.
For Android users who want to use Clash Meta configs. If you know your device’s architecture, choose the matching file. The universal package can help if you can’t identify the ABI, but it’s still subject to OS and hardware requirements. If you enable per-app proxying, check the app list and default behavior so your test traffic comes from an app that’s actually routed through the proxy.
Available for ARM64 and ARMv7 devices; choose based on your device’s ABI. A desktop config can be a starting point, but check mobile-specific app routing and background settings again. Before connecting, make sure no other VPN service is active. Seeing the system VPN indicator doesn’t mean every request is routed through a proxy.
Surfboard is another Android proxy client, but it uses its own config syntax. Clash YAML isn’t a drop-in replacement. If you already have a Clash subscription, check whether your provider offers a compatible format before installing. Review converted proxy groups, rules, and DNS behavior individually.
| Check | Requirements and steps |
|---|---|
| App ABI | ARM64 usually corresponds to arm64-v8a, and ARM to armeabi-v7a. The ABI supported by your system is a better guide than the chip’s marketing name. |
| Install permission | Follow the system prompts to allow the browser or file manager you’re using to install apps. You can revoke this permission afterward if you like. |
| Runtime requirements | Check the installer for the minimum Android version. Review VPN permission, battery optimization, and the manufacturer’s background activity policies separately. |
Install Clash Plus from the App Store. Before downloading, check the listing for current system requirements, features, and device compatibility. Import a compatible config after installation.
iPhone and iPad users can start from the App Store listing. After opening the app, import a subscription or config and confirm that proxy groups and proxies have loaded. Follow the system prompt to add a VPN configuration. For your first connection, test with a single config before changing rules. Don’t post private subscription links in public forums when updating the source or sync settings.
| Check | Requirements and steps |
|---|---|
| OS compatibility | Check the iOS / iPadOS requirements and compatible devices listed on the App Store page. |
| Network permissions | The first connection requires adding a VPN configuration. Check the app name and purpose before granting permission. |
| Config preparation | Prepare a subscription or config you’re authorized to use. Installing the client and configuring a proxy service are separate steps. |
GUI clients are for Linux systems with a desktop session. DEB and RPM are different package formats, so choose the one that matches your distribution. Servers, containers, and routers are usually better suited to the Mihomo core downloads.
A good fit for desktop users who want to manage subscriptions and proxy rules through a GUI. DEB is for distributions such as Debian and Ubuntu that use the corresponding package management system; RPM is for distributions using the RPM ecosystem. Let your system’s package manager handle dependencies. If the app won’t start, check the terminal output first, then look into desktop environment and runtime library compatibility.
This section provides an AMD64 DEB package. After installing, check that your config loads and the listening ports are available, then decide whether to use desktop proxy settings or TUN. System proxy support varies across desktop environments, and command-line apps may only read environment variables. A working browser connection doesn’t prove that every command-line tool uses the same proxy.
| Check | Requirements and steps |
|---|---|
| Architecture and package format | These packages are AMD64 / x86_64. Match the DEB or RPM format to your distribution’s package management system. |
| Runtime environment | Requires a desktop session and compatible system libraries. For headless systems, see the core downloads. |
| Traffic routing | TUN requires device permissions and route settings. Verify system proxy settings, environment variables, and transparent routing separately. |
CORE / SERVICE / ROUTER
These builds are for servers, routers, and users who manage services themselves. The core doesn’t include a complete GUI setup flow; you’ll need to manage the config directory, permissions, service startup, and logs. For everyday desktop and mobile use, start with one of the GUI clients above.
| System | Architecture | File 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 | Requirements and steps |
|---|---|
| Handling downloads | Extract ZIP files. GZ files usually extract to a single executable. Install DEB packages with the relevant package manager. |
| Config and permissions | Prepare a valid YAML file, a writable working directory, and the required execution permissions. Assess permissions separately when using TUN or privileged ports. |
| Service management | Set up startup, shutdown, and log rotation yourself. Limit the control interface’s listening scope and configure access authentication as needed. |
Before starting, use the core’s config test to check that the YAML parses, then verify the ports and rule-provider paths. A running core only means the program has started; traffic still depends on system proxy, routing, or transparent proxy settings. See the YAML handbook for field details.
BEFORE THE FIRST CONNECTION
Verify installation, config import, and traffic routing separately.
01 / PROFILE
Use a subscription link or local config you’re authorized to access. After importing, confirm that proxies and proxy groups are visible, then check that subscription updates work. Don’t submit private subscription URLs to unfamiliar online converters or show the full address in screenshots.
02 / ROUTING
Start by testing rule mode with one routing method enabled. System proxy, VPN, and TUN have different scopes; avoid running multiple proxy clients at once. If only one app doesn’t work, check its proxy settings instead of repeatedly reinstalling the client.
03 / VERIFICATION
Check the connection view or logs to see whether requests reach the core, which rule matched, and which proxy was selected. A proxy speed test is only one test, not a substitute for checking real apps. If you have name resolution issues, check the DNS mode and rule order.
DOWNLOAD NOTES
Find answers here about choosing packages, architectures, and migrating clients. For connection troubleshooting, see the Help Center.
Start with Clash Plus for Windows, macOS, Android, or iOS, and Clash Verge Rev for Linux. Check your OS, CPU architecture, and package format before choosing. If you rely on specific override scripts, tray behavior, or mobile config management, verify those features before switching.
The installer provides a client, not a configured proxy connection. Import a subscription you’re authorized to use or a YAML file, then confirm that proxies and proxy groups load before enabling the system proxy or TUN as needed. Subscription URLs may contain credentials, so don’t share them publicly.
On Windows, check System type in Settings > System > About. On macOS, check the chip or processor under About This Mac. On Android, check your device specs or use a system information app. On Linux, run uname -m. x86_64 usually means x64 or AMD64; aarch64 usually means ARM64. Check the actual filename too—the download group alone may not identify the architecture correctly.
In the current list, both macOS architecture options for Clash Verge Rev, FlClash, and ClashX Meta point to x64 files. The option label doesn’t guarantee a native ARM build. Before using these on Apple Silicon, check Rosetta and app compatibility. For a clearly labeled ARM64 installer, choose Clash Plus.
Save your subscription source, local YAML files, overrides, rule-provider settings, and any port details you need. Keep backups somewhere secure on your device. Client data directories and script interfaces may not be compatible, so migrate with the import feature. Confirm rules and proxy routing in the new client before disabling the old setup.
First, confirm that the config is selected, the core is running, and a proxy is available. Then check the system proxy or VPN, the TUN toggle, and the app’s own proxy settings. Avoid running multiple traffic-routing tools at once. Use the connection view and logs to see whether requests reach the core; a speed test alone doesn’t prove that every app is using the proxy.