Choose your operating system first, then verify the processor architecture and package format. For desktops and mobile devices, prefer a graphical client; consider the standalone Mihomo core for servers, routers and automated environments.
Tabs sync with the address-bar anchor, so you can save or share the entry point for the current platform. Client cards are ordered by recommendation; discontinued software remains with archival notes.
Windows 10 and Windows 11 users should start with Clash Plus. Compare Clash Verge Rev, FlClash and Clash Nyanpasu when you need detailed rule editing, core switching or a cross-platform interface. For a first installation, use the EXE installer. On managed devices or restricted accounts, also verify permission to write to the program folder and modify system proxy settings.
A solid starting point for a new Windows installation. The interface centralizes subscriptions, proxy groups, system proxy settings and connection status, reducing manual core and configuration-folder maintenance. Run the installer wizard, then import a subscription and choose a rule mode.
For desktop users who want detailed control over configurations, rules, logs and core options. After installation, check whether the configuration uses Mihomo-specific fields before importing the subscription. Only the Windows x64 installer currently available in the remote manifest is provided here.
For users who work across Windows, macOS, Linux or Android and want a consistent workflow. The installer is convenient for routine updates, while the ZIP package suits users who manage the program folder themselves. Both use the same type of configuration; choose one.
A desktop management interface for subscriptions, proxy groups, rules and connection details. When migrating an existing setup, copy the original configuration first, then verify that script, proxy-provider and rule-provider paths still work.
Kept for existing installations and migration checks. It is not recommended for new long-term use because future system changes, protocol extensions and rule formats will not receive ongoing compatibility updates. Before migrating, export the configuration, record the port and proxy mode, then verify each item in the new client.
| Check | Recommendation | Details |
|---|---|---|
| System | Windows 10 / 11 | Older systems may lack client dependencies or support for modern network interfaces. |
| Processor | x64 / AMD64 | The Windows GUI packages on this page primarily target common 64-bit desktop architectures. |
| Installation format | EXE preferred | ZIP is best for users familiar with folder permissions, shortcuts and upgrade management. |
| First launch | Confirm system proxy permissions | Managed devices may restrict proxy changes, service installation or firewall access. |
Check the chip type in About This Mac first. M1, M2, M3, M4 and other M-series Macs use Apple Silicon and should select ARM64; Intel Macs should select x64. Choosing the wrong architecture may prevent the app from starting or force it to run through a compatibility layer. After downloading the DMG, move the app to Applications and approve network and proxy-related permissions when prompted.
For macOS users who want to quickly import subscriptions, choose proxy groups and configure the system proxy. Download the Apple Silicon or Intel package that matches the chip; do not determine architecture from the macOS version alone.
For users who need Mihomo configuration fields, rule providers and detailed connection logs. The two macOS download keys in the current manifest use the same fallback file; the download script updates the actual URL from the remote manifest.
For users who want a similar workflow across desktop and Android devices. The macOS architecture entries in the current remote manifest use the same fallback file; the deployment URL is updated after the download script reads the manifest.
Kept for existing macOS installations and configuration migration. Since the client is no longer maintained, new installations should prioritize actively updated graphical clients. Before continuing, confirm that the current system version, configuration fields and proxy mode still work as expected.
| Mac information | Select | How to identify it |
|---|---|---|
| Apple M-series chip | ARM64 / Apple Silicon | The Chip field in About This Mac shows an Apple M-series model. |
| Intel processor | x64 / Intel | The Processor field in About This Mac shows an Intel model. |
| Installation file | DMG | Open the disk image and move the app to Applications. |
| First run | Check system permissions | Follow macOS prompts to approve app execution, network extensions and proxy settings. |
Recent mainstream Android phones and tablets usually use ARM64. Older 32-bit devices may need an ARM package; choose Universal when unsure. After installation, Android will request permission to establish a VPN connection on first connect, which is the standard way Android routes traffic through a local proxy. Battery usage also depends on rule size, DNS settings, protocol type and background restrictions.
For common 64-bit Android phones and tablets. Import a subscription after installation, confirm that a usable option is selected in each proxy group, then start the connection. If background activity is tightly restricted, review the client’s background permission in battery settings.
For Android users who need Mihomo configuration features, with ARM64, ARM and Universal packages available. Choose the matching package when the architecture is known; use Universal when unsure to avoid architecture mismatches.
For users already using FlClash on desktop who want the same workflow on mobile. ARM64 and ARM packages are provided; most recent devices should use ARM64, while older 32-bit devices may need ARM.
For users who need an Android rule-based proxy client and prefer a universal package. Before importing a configuration, confirm that its format is supported; if it relies on Mihomo-specific fields, check compatibility first.
| Package label | Compatible devices | Selection rule |
|---|---|---|
| arm64-v8a | Recent 64-bit phones and tablets | If the architecture is unknown but the device is relatively new, try ARM64 first. |
| armeabi-v7a | Older 32-bit ARM devices | Choose this only when the device is confirmed to be 32-bit. |
| Universal | Devices with unknown architecture | It supports more devices, but the file is usually larger. |
| System permissions | Android VPN connection | Follow the system prompt to approve local VPN access on the first connection. |
Install Clash Plus on iPhone and iPad through the App Store. After installation, import a subscription, choose a proxy group and follow the system prompts to add a VPN configuration. If the subscription uses specific protocols or extended fields, review the import result to confirm that all entries and rule groups appear.
A graphical client for iPhone and iPad. View the app details and install it from the App Store; product information and usage instructions are also available at clashplus.io. When starting the first connection, iOS will request permission to add a VPN configuration. Approve it, then return to the client and choose a proxy.
| Step | Action | Result |
|---|---|---|
| Install | Open the app page in the App Store | Confirm that the device meets the requirements listed on the store page. |
| Import | Add a subscription or configuration | Confirm that proxy entries, rules and proxy groups are recognized. |
| Authorize | Add a VPN configuration | Follow the iOS prompts to complete authorization. |
| Verify | Choose a proxy and start the connection | Check the client status and the target app’s network access. |
Desktop Linux users can choose Clash Verge Rev or FlClash. Debian, Ubuntu and derivatives typically use DEB; Fedora, RHEL, Rocky Linux, openSUSE and similar systems typically use RPM. Before installing, confirm the distribution’s package system and desktop environment. Remote servers and routers are better suited to the Mihomo core section below.
For AMD64 Linux desktops, with DEB and RPM packages available. After installation, confirm that the desktop environment allows the app to change proxy settings. If using TUN, also check system permissions, network interfaces and firewall rules.
For Linux desktop users already using FlClash on another platform. This page provides an AMD64 DEB download from the fixed manifest. For other package formats or architectures, check the remote manifest first to avoid mixing packages from different distributions.
| Distribution family | Package | Pre-install checks |
|---|---|---|
| Debian / Ubuntu family | DEB | Confirm the system is AMD64 and review package dependency messages. |
| Fedora / RHEL family | RPM | Confirm that the package manager and distribution version can handle the package. |
| Desktop environment | GUI client | Confirm that the tray, system proxy and notification features work correctly. |
| Server or router | Mihomo Core | A GUI client is usually unnecessary without a desktop environment. |
The Mihomo core is intended for servers, routers, containers, automated deployments and users who maintain configuration files themselves. Regular Windows, macOS, Android and Linux desktop users should generally choose a GUI client above, which handles core startup, configuration import, system proxy settings, logs and updates. The standalone core does not replace those management interfaces.
| System | Architecture | Format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 core |
| Windows | ARM64 | ZIP | Download ARM64 core |
| System | Architecture | Format | Download |
|---|---|---|---|
| macOS | Intel / AMD64 | GZ | Download Intel core |
| macOS | Apple Silicon / ARM64 | GZ | Download Apple Silicon core |
| System | Architecture | Format | Download |
|---|---|---|---|
| Linux | AMD64 | DEB | Download AMD64 DEB |
| Linux | AMD64 | GZ | Download AMD64 archive |
| Linux | ARM64 | GZ | Download ARM64 archive |
| Linux | ARMv7 | GZ | Download ARMv7 archive |
| Linux | MIPS soft-float | GZ | Download MIPS archive |
| Check | What to verify | Common boundary |
|---|---|---|
| CPU architecture | AMD64, ARM64, ARMv7 or MIPS soft-float | The program will not run correctly if the architecture does not match. |
| Configuration file | Protocols, proxy groups, rule sets, DNS and listening ports | Extended fields must correspond to features supported by the current core. |
| Runtime permissions | Directory read/write, port binding and network-interface permissions | TUN and system services typically require additional permission settings. |
| Operations | Process supervision, startup order, logs and updates | Server environments should have a clear stop and rollback procedure. |
For a computer, phone or tablet used every day, start with a GUI client. Clash Plus is the first choice across the main platforms for importing subscriptions, switching rule modes, choosing proxy groups and checking connection status. Compare Clash Verge Rev, FlClash or Clash Nyanpasu when you need more configuration views.
Do not judge compatibility by the client name alone. Core capabilities, configuration fields and protocol support determine whether a subscription imports completely. The same subscription may have fields ignored, rule providers fail to load or protocols go unrecognized under different cores, so review parsing messages after import.
When migrating from Clash for Windows or ClashX Meta, save the original subscription URL, configuration file, proxy port, bypass list and mode selection first. Import the same subscription into the new client, confirm that proxy entries, proxy-group structure and rule providers load correctly, then switch the system proxy.
Migration does not mean overwriting the old folder. Clients may handle configuration paths, script fields, overrides and core parameters differently. Keeping the old environment makes it easier to compare a failed parse instead of losing both the working configuration and the evidence needed to troubleshoot.
When there is no desktop environment, the software must run as a system service, or multiple instances should be managed from configuration files, standalone Mihomo is a better fit. This requires the operator to identify the CPU architecture, set file permissions, plan listening ports and manage process supervision, logs and upgrades.
For home routers, verify the firmware architecture carefully. ARM64, ARMv7 and MIPS cannot be identified by the device’s appearance; check system information or package-manager output. Devices with limited storage may also need tighter control of rule databases, logs and temporary files.
Android and iOS typically use the system VPN interface to pass traffic to the client. Connection stability depends not only on the client but also on background restrictions, DNS settings, rule size and the selected protocol. If the connection drops after the screen locks, check background and battery policies first.
When mobile networks switch frequently, recovery speed depends on the protocol implementation. Start with rule mode and conventional DNS settings, confirm basic stability, then add complex overrides gradually so the source of any problem remains identifiable.
Complete the system installation flow on desktop platforms and grant the required connection permissions on mobile. After the first launch, do not enable several proxy clients at once; they may compete for the system proxy, VPN interface or the same listening port.
After adding a subscription, confirm that proxy entries, proxy groups and rules appear. If the client reports a parsing failure, check the subscription content and core compatibility first instead of repeatedly importing the same invalid configuration.
For a first run, start with rule mode and select an available option in the main proxy groups. Global mode sends more connections through the selected proxy and is useful for short diagnostics, but should not be the default long-term mode without understanding its scope.
After starting the connection, review the client logs first, then test the browser and target app. If the browser works but another app fails, check whether that app follows the system proxy. If all apps fail, inspect the port, DNS, proxy group and firewall.
These questions cover package formats, processor architectures, migration from older clients and standalone core selection. For configuration imports, rule modes and connection troubleshooting, continue to the guide and FAQ pages.
Most desktop users should choose the EXE installer. It deploys program files and creates common shortcuts, making subsequent use more straightforward. ZIP is for users who want to choose the program directory, understand file permissions and manage upgrades manually. The two formats generally do not indicate different feature levels; the main difference is deployment and maintenance.
Open About This Mac and check the Chip or Processor field. If it shows an Apple M-series chip, choose Apple Silicon or ARM64; if it shows Intel, choose Intel or x64. Do not rely only on the purchase year, since models from nearby years may use different architectures.
ARM64 is for mainstream 64-bit Android devices, ARM is generally for older 32-bit devices, and Universal supports a broader range of architectures. When device information is clear, matching the architecture reduces file size; when unsure, Universal is safer. If installation fails with an architecture error, switch to the matching package instead of repeatedly installing the same file.
Existing installations may still run, so this page keeps an archived download entry, but the client is no longer maintained. New installations should favor actively updated clients. During migration, save the subscription, configuration, port and bypass settings, then verify rules and proxy groups one by one in the new client instead of overwriting the old folder.
Usually not. Graphical clients such as Clash Plus, Clash Verge Rev and FlClash already handle core execution, subscription management, system proxy settings and logs. Direct Mihomo deployment is better suited to servers, routers, containers and environments where processes must be orchestrated manually.
First confirm that the subscription URL is reachable and has not expired, then review the client’s configuration-parsing message. Check whether the current core supports the protocol type, rule providers, proxy providers, scripts or override fields. If the cause remains unclear, test a simpler configuration to determine whether the client itself can load configurations normally.