# packages · Clients & Core
Choose a GUI client for desktop and mobile; use the Mihomo core for servers and routers.
Check your operating system first, then your processor architecture. A client manages configuration and proxy controls; the mihomo core handles protocol connections and rule-based routing. They are different types of downloads.
# platform: windows
For a first installation, start with Clash Plus. If you're already familiar with another client, choose one based on how you prefer to manage configurations. The desktop installers below target x64 systems. Windows on ARM users should check app compatibility first; an x64 installer is not a native ARM64 build.
A good fit if you want to import subscriptions, choose policies, and toggle the proxy from one interface. After installation, add a compatible Clash configuration and make sure it's selected and enabled. Then choose rule mode and enable the system proxy. If you need to route traffic from apps that ignore system proxy settings, check the permissions required for TUN.
Official site: clashplus.io ↗
A good fit for desktop users who want to inspect connections, manage configurations, and edit rule overrides. After installation, verify that the core starts before enabling the system proxy. If you use service mode or TUN, pay attention to permission prompts during setup. Keep your subscriptions and overrides when updating; don't use an auto-updated subscription file as a permanent editing workspace.
A good fit if you want a similar configuration workflow across devices. AMD64 and x64 are labels for the same processor architecture; you don't need an AMD processor. When migrating from another client, reimport your subscription and check policy group selections and DNS settings individually. Don't copy the entire application data directory.
An alternative desktop interface for managing configurations. Before installing, quit any other proxy client to prevent conflicts between local listening ports and system proxy settings. After enabling a configuration, visit a familiar site and check the connection log for the matching rule. If the connection fails, check node availability and routing separately rather than relying on the UI toggle alone.
Kept for recreating legacy setups and migrating configurations, not recommended for new installations. Older cores may have limited support for newer protocols and configuration fields; a configuration that won't start doesn't necessarily mean the subscription URL is invalid. Before moving to a maintained client, back up your configuration, reimport the subscription, and check rules, DNS, and the system proxy port.
| Check | Requirements and steps |
|---|---|
| System | Use a version of Windows that still receives security updates. Check the selected client's installer for its minimum OS version. |
| Processor | The GUI packages on this page are x64 / AMD64. Check your system type under Settings → System → About. |
| Permissions and runtimes | Installing services or a virtual network adapter may require administrator approval. If a runtime such as WebView2 is missing, follow the installer prompts to install it. |
| First launch | Import a configuration and verify that the core is running before enabling the system proxy. During testing, let only one proxy client control system traffic. |
# platform: macos
Check your chip under About This Mac. Don't rely on the button labels alone to identify Apple Silicon and Intel builds: in the current list, both Clash Verge Rev and FlClash entries, as well as both ClashX Meta entries, point to x64 builds. Apple Silicon may need Rosetta to run them; Clash Plus offers a separate ARM64 build.
Choose the disk image for your chip, copy the app to Applications, and launch it from there rather than running it from the mounted image. Import a subscription and check the policy groups, then test browser access with the system proxy. If you later need TUN, grant the permissions requested by the client. Keep your existing network settings available for troubleshooting.
Official site: clashplus.io ↗
Manage subscriptions, policies, and desktop traffic routing. Both buttons currently point to the same x64 disk image, so Apple Silicon users should check compatibility before running it. Quit the old process before updating. If the system proxy doesn't work after launch, check the proxy settings for the active network service and confirm they match the port shown by the core.
A good fit if you already use FlClash on other devices and want a familiar workflow. The current download is an AMD64 build; Apple Silicon users should check compatibility requirements. You can reuse a compatible subscription across devices, but you'll need to configure system proxy settings, TUN permissions, and local file paths again on this Mac.
For keeping an existing menu bar workflow or recreating a legacy setup. The archived download is x86_64, not a native ARM64 build. For new installations, consider a maintained client. Before migrating, note your configuration file location, subscription source, and custom rules, then recheck traffic routing and DNS in the new client.
| Check | Requirements and steps |
|---|---|
| macOS version | Minimum macOS versions vary by client build; check the installer requirements. Don't install over an older system without checking compatibility. |
| Chip and build | Use an ARM64 build on Apple Silicon and x64 / AMD64 on Intel. Check the package notes before using a compatibility option. |
| Install location | Copy the app from the DMG to Applications. Quit any temporary instance running from the mounted image before launching the installed app. |
| System permissions | Changing system proxy settings or running a TUN service may require approval. If you see a security warning, verify the app's source instead of disabling system-wide protections. |
# platform: android
Most recent phones use ARM64, but check the app ABI supported by your device. After downloading the APK, allow the browser or file manager you used to install apps. You can revoke that permission once installation is complete. When you connect, Android will ask for VPN permission so the client can route device traffic.
A good starting point if you're importing a Clash subscription on your phone for the first time. Add a configuration, update the subscription, and select a policy group. Then start the connection and approve Android's VPN prompt. If the connection drops in the background, check battery optimization and background activity restrictions; reimporting the same subscription won't fix the system stopping the app.
Official site: clashplus.io ↗For Android users who need mihomo configuration features, including configuration file and subscription management. Choose the build that matches your device ABI; if you're unsure, try the universal build. After importing a configuration, set it as active before connecting. A subscription appearing in the list doesn't mean the core has loaded it.
Carry over your FlClash subscription and policy workflow from desktop to Android. Before connecting, close other apps using the VPN slot to avoid conflicts between traffic-routing apps. If the status bar shows a connection but apps can't reach the internet, check the node and DNS in the connection log, then make sure per-app proxy settings haven't excluded the app.
For users who already have a compatible configuration. Surfboard's configuration format is not the same as Clash YAML, so you can't assume an arbitrary Clash subscription will import with all rules intact. Check that your subscription provider offers a compatible format before downloading. If conversion is needed, verify protocol fields, policy groups, and rule semantics. Don't submit subscriptions containing credentials to untrusted online tools.
| Check | Requirements and steps |
|---|---|
| System and ABI | Check the APK installer for the minimum Android version. ARM64 uses arm64-v8a; ARMv7 uses armeabi-v7a. |
| Install permission | Allow app installs only for the app you use to open the APK. If Android reports an incompatible architecture, download a matching build. |
| VPN connection | Approve the VpnService connection request and stop any other VPN app that may be using the same slot. |
| Background activity | Allow background activity, autostart if needed, and notifications in your device settings to prevent the system from stopping the connection when the screen locks. |
If the connection drops when the screen locks, see Android VpnService and battery optimization guidance.
# platform: ios
Get Clash Plus from the App Store. Check the store listing for device compatibility and current app details before installing. After installation, prepare your own subscription or configuration file and follow the system prompts to add a VPN configuration.
After installing from the store, add a subscription link or import a compatible file in the client. When connecting for the first time, allow iOS to add a VPN configuration, then check that a policy group has an available node. The connection toggle only indicates that routing has started; the rules and policy groups determine the actual route. Verify it by testing access.
Official site: clashplus.io ↗| Check | Requirements and steps |
|---|---|
| Device and OS | Check the App Store listing for compatible devices and the minimum iOS version. |
| Configuration source | Prepare a supported subscription or configuration, and make sure its protocols and fields are within the app's supported range. |
| Connection permission | When prompted during the first connection, allow the system to add a VPN configuration. You may need to confirm with your device passcode. |
| How to verify | Select a node and visit the site you need. If you see problems after switching between Wi-Fi and cellular, check the app's connection status and logs. |
For the full walkthrough, see Get an iOS client and import a configuration. If a subscription update fails, first check that the original URL is reachable. Don't post the link in screenshots or public discussions.
# platform: linux
These GUI installers target AMD64 desktops. Choose DEB for Debian, Ubuntu, and compatible distributions; choose RPM for distributions that use RPM packages. For headless servers, see the core downloads instead—you don't need to install a desktop environment just to run a proxy.
A good fit for Linux desktop users who want GUI-based subscription management, connection details, and rule debugging. Install dependencies with your distribution's package manager; don't mix packages from different distributions. Whether the system proxy covers a target app depends on the desktop environment and the app itself. Terminal programs may also need proxy environment variables set separately.
A good fit if you use a DEB-based distribution and want a familiar workflow across devices. Before installing, check that your desktop environment and runtime dependencies meet the app's requirements. TUN requires virtual network interfaces and routing permissions. First verify the subscription and node with the system proxy, then test TUN separately to avoid confusing permission issues with configuration problems.
| Check | Requirements and steps |
|---|---|
| Architecture | The GUI packages are AMD64 / x86_64. Run uname -m in a terminal to check the architecture reported by the kernel. |
| Package format | DEB and RPM belong to different package systems; changing a file extension won't make a package installable. |
| Runtime dependencies | Requires a graphical desktop and the libraries needed by the client. Your package manager will identify any missing dependencies. |
| Traffic routing | The desktop system proxy, terminal environment variables, and TUN are separate ways to route traffic. Choose what your apps need; don't assume every process is covered. |
# binary: mihomo
For users running their own services on servers or routers. Core packages don't include a desktop settings interface and won't configure subscriptions or the system proxy for you. Most desktop and mobile users should use a GUI client above to manage core startup and permissions.
| System | Processor / package format | Core downloads |
|---|---|---|
| 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 softfloat GZ |
Extract ZIP files first. GZ files usually contain a single compressed binary; on Unix-like systems, make it executable after extraction. Install DEB files with a package manager. Prepare a configuration directory and compatible YAML file, then start the core in the foreground and check its output before setting up a service. This helps prevent repeated background restarts from hiding configuration errors.
If you already have an executable and configuration, run a configuration test first. The paths below are local examples; make sure the files exist before running the command. Passing a syntax test only confirms that the configuration can be read—it doesn't confirm node reachability, working DNS, or that system traffic is routed through the core.
mihomo -t -f ./config.yamlBind the listener to localhost by default. If you need LAN access, explicitly configure allowed addresses, authentication, and firewall rules. Restrict access to the external controller API as well. Before replacing the binary, keep the old file and configuration, then verify that the new build starts before updating the running service.
| Check | Requirements and steps |
|---|---|
| System and ABI | Match the operating system, bitness, CPU instruction set, and firmware ABI. On low-power devices, also check the instruction set used to build the binary. |
| Configuration and resources | Prepare a readable configuration file and ensure the resources required by rule providers and DNS can be updated. |
| TUN permissions | The OS must provide a virtual network device and the required permissions. Containers also need explicit device and network capabilities. |
| Running as a service | Use the system service manager to control the process, logs, and restart behavior. Test configuration changes before reloading. |
# after-install
Your configuration is active. The installer includes the app, not a personal proxy service. After importing a subscription, confirm that it updated successfully, select the configuration, and check for usable policy groups. Direct edits to generated subscription files may be overwritten on the next update; use the client's supported override or separate configuration mechanism for custom rules. See how to import a Clash subscription link.
Traffic is reaching the core. Rule mode determines where traffic goes after it enters the core; the system proxy and TUN determine how it gets there. They aren't interchangeable. Start by enabling the system proxy and testing in a browser. Use TUN only if the target app doesn't follow proxy settings. See how to configure the Clash system proxy.
Nodes and rules are behaving as expected. Latency tests can help compare nodes, but they don't guarantee that every site or protocol will work. After choosing a node, visit the service you need and check the connection panel for the matched rule, policy group, and exit route. If something fails, note the symptoms and change one setting at a time. Avoid changing DNS, mode, and node selection simultaneously. See node testing and connection checks.
# download-faq
Start with a GUI client. It brings subscription imports, proxy selection, and system proxy controls together. The Mihomo core is better suited to server and router users who want to manage configuration, startup flags, and services themselves.
Check your system's processor and app runtime requirements first. x64 and AMD64 refer to the same architecture; ARM64 is not ARMv7. On Android, choose the universal build if you're unsure which ABI your device supports. On macOS, verify the installer’s actual architecture; Apple Silicon may need Rosetta to run an Intel build.
You'll need your own compatible configuration or subscription; installing a client does not provide proxy nodes. After importing it, check the policy groups and select a node. Test the connection in rule mode with the system proxy first, then configure TUN if needed. Subscription links may contain access credentials, so don't share them publicly.
Note your subscription source, rule overrides, ports, and TUN settings, and use the client's export feature to back up your configuration. Quit the old client before installing the update. On first launch, check the configuration directory, subscription, and system proxy status. When switching clients, reimport the original subscription rather than overwriting the entire data directory.
Disable other proxies or VPNs first, confirm the subscription updated successfully, and select an available node. Check rule mode, the system proxy port, and connection logs. If you need TUN, test its service permissions and virtual network interface separately. If connectivity still fails after quitting the client, check for stale system proxy settings pointing to a local port.
Archived clients are mainly useful for reproducing legacy setups or migrating configurations, not for new installations. Older cores and configuration fields in Clash for Windows and ClashX Meta may differ from those in current subscriptions. Back up your configuration before migrating, then recheck rules, DNS, and traffic routing in a maintained client.