Client installation / architecture selection / core setup
Choose an installer for your platform.
Use a graphical client for everyday connections or deploy the Mihomo core on its own.
Choose your device platform, then check the processor architecture. Clash Plus is our top pick for Windows, macOS, Android, and iOS; Linux users can start with Clash Verge Rev. Installers don’t include proxy servers. On first launch, import an existing subscription or local YAML configuration.
Setup after installation →Choose an operating system
Desktop installers
The graphical clients below provide x64 installers. Check Settings under System → About for your system type. On ARM devices, also confirm that your version of Windows supports running the app.
A good starting point for desktop users setting up a subscription, choosing a proxy group, and using rule mode. After installation, add a configuration, select a node, and enable the system proxy. If you need to capture traffic from apps that ignore system proxy settings, test a basic connection first, then configure TUN. Avoid changing several network settings at once.
For users who want to manage mihomo configurations from a desktop interface. You can reimport an existing subscription, but client-specific overrides and scripts need to be migrated separately. Before enabling a service or TUN, review the permission prompts and make sure the new client is running—not a leftover background process from an older app.
A good fit if you use both desktop and mobile devices and want a consistent experience. You’ll still need to import configurations and grant permissions on each device. After installing the desktop app, check the listening ports and system proxy status. When switching clients, don’t assume your settings will carry over automatically.
Another option for managing configurations on desktop. If you already use this client, import a configuration and check compatibility before moving your everyday setup. If parsing fails, check the specific fields and whether the core supports them. A subscription working in another app doesn’t guarantee compatibility here.
This archived download is for reproducing older setups and reference during configuration migrations. Its older core has limited support for newer protocols and configuration fields, so it’s not recommended for a first install. Before switching, back up your local configuration, custom rules, and port settings, then disable the old client’s system proxy.
| Check | What to look for |
|---|---|
| Operating system and architecture | The desktop downloads on this page are primarily x64. Check the selected client’s release notes and installer prompts for the minimum supported Windows version. |
| Installation permissions | Writing to the installation directory, running background services, and installing a virtual network adapter may require administrator approval. Importing a configuration and capturing network traffic are separate actions. |
| Proxy conflicts | Before switching clients, disable the old app’s system proxy. Also check for browser proxy extensions and other VPNs that may be handling your connections. |
Apple Silicon / Intel
Check About This Mac for your chip. Clash Plus offers separate ARM64 and x64 downloads. Some clients below currently point both architecture options to the same x64 package, which is not a native ARM64 build.
Choose ARM64 for Apple Silicon and x64 for Intel Macs. Open the disk image and follow the installation instructions, then launch the app from Applications. After importing a subscription, check the rule mode first. Grant permissions for the system proxy, network extension, or TUN only as needed.
Manage subscriptions, rules, and proxy groups on macOS. The Apple Silicon option in the current release list still provides an x64 file, which requires system translation to run. For a native ARM64 build, choose the Clash Plus download above that’s clearly labeled ARM64.
A good fit if you want a similar interface across devices. The current macOS listing provides an AMD64 image, and both architecture options point to the same file. Check the file’s actual architecture before installing. After migrating a subscription between clients, review DNS, ports, and network capture settings.
For users who still need an older workflow. The archived package is x86_64; confirm translation compatibility before running it on Apple Silicon. For a new installation, choose a client that’s still maintained. When migrating, back up subscriptions, custom rules, and local configuration—not just the app itself.
| Check | What to look for |
|---|---|
| Chip architecture | Apple M-series chips use ARM64; Intel Macs use x64. If the architecture listed for a download differs from the actual file, follow the card details and check the file itself. |
| macOS compatibility | The minimum supported macOS version depends on the client release. If the app won’t start on an older system, check the release notes rather than changing macOS security settings. |
| Network permissions | You may see a permission prompt the first time the app captures traffic. Before replacing an older client, quit its background processes and restore the system proxy settings. |
ARM64 / ARM / universal builds
Most recent phones use ARM64. For older devices, check the supported system ABI rather than relying on the processor model alone. Android VPN permission is usually required to connect.
ARM64 download available. After installation, import a compatible subscription, make sure the configuration loads, then select a node and connect. Android asks you to approve the VPN connection the first time. If the connection stops when the app is in the background, check battery optimization and background activity limits instead of repeatedly reinstalling.
Choose an ARM64, ARM, or universal build to match your device. A universal build is useful if you’re unsure of the architecture, but it can’t bypass Android version requirements. After importing, check that a proxy group has selectable nodes before starting the service. Check app-level and rule-based routing separately so you know which apps are being handled.
ARM64 and ARM downloads available. Android VPN permission is separate from a desktop system proxy toggle, so follow the connection steps shown in the mobile app. If another VPN is running, disconnect it first. When checking for subscription updates, make sure the update request itself has network access.
For Android users with a compatible Surfboard configuration. Surfboard and Clash use different configuration formats, so you can’t assume any Clash subscription will work as-is. Before downloading, check the format and protocol support offered by your service. If converting a configuration, handle sensitive subscription URLs carefully.
| Check | What to look for |
|---|---|
| System and ABI | Choose arm64-v8a or armeabi-v7a based on your device’s supported ABI. Check the installer’s package details for the minimum Android version. |
| Install permissions | Allow your browser or file manager to install apps from this source. If Android reports that the package is incompatible, check the architecture, system version, and whether an existing app has a different signing key. |
| Connection permissions | Approve the VPN request the first time you connect. Background restrictions, app-level routing, and other VPNs can affect which traffic is handled and how long the connection stays active. |
Install from the App Store
Check device compatibility on the App Store product page, then install the app. Before connecting for the first time, prepare a compatible subscription. After installation, follow the app’s prompts to add a VPN configuration.
On iOS, install from the App Store. Open the app, add a subscription or import a compatible configuration, check the proxy groups, and approve the VPN prompt. Nodes, rules, and app settings are separate parts of the setup. If a connection fails, check the import and active policy first—you don’t need to rebuild the entire configuration right away.
| Check | What to look for |
|---|---|
| Device and iOS version | Check the current App Store listing for the minimum iOS version, device compatibility, and app updates. |
| Network configuration | The app needs to add a VPN configuration when you connect for the first time. Management policies on work or school devices may restrict this permission. |
| Subscription setup | Prepare a compatible configuration or subscription URL. After importing, check the nodes and proxy groups so you don’t switch on the connection without selecting a route. |
Desktop distributions / AMD64
Use a graphical client on desktop Linux. Choose deb for Debian, Ubuntu, and similar distributions; choose rpm for distributions that use RPM packages. For headless servers, see the Mihomo core section.
For Linux desktop users who want a graphical interface for managing mihomo configurations. Install with your distribution’s package manager to resolve dependencies. TUN and service modes also affect permissions and routing. First verify the proxy using a local port, then enable network capture step by step.
This section provides an AMD64 package for Debian-based desktop distributions. A successful installation doesn’t mean every app is using the proxy: desktop system proxy settings, terminal environment variables, and TUN capture work differently. Choose the method that fits the app and check the connection logs to confirm.
| Check | What to look for |
|---|---|
| Processor and package format | Run uname -m to check your architecture. The graphical packages above are AMD64 / x86_64; deb and rpm packages are not interchangeable. |
| Desktop and dependencies | Graphical clients need a working desktop session and the required runtime libraries. Check your package manager’s output for specific dependencies. |
| Services and permissions | A local proxy and TUN require different permissions. If you need the client to run continuously, verify the configuration before setting up a service. Keep recovery access available before changing routes, especially on remote systems. |
For the differences between desktop and server setups, see Deploying Clash on Linux: Desktop and Command-Line Setups.
Servers / routers / standalone use
This section provides the standalone core, without a graphical interface. It’s for users who manage configuration directories, startup options, and system services themselves. Desktop and mobile users are usually better off with a graphical client above.
Check the device that will run the core—not the device downloading the file. AMD64 and x86_64 refer to the same architecture family; ARM64, ARMv7, and MIPS are not interchangeable. For routers, also check endianness, floating-point ABI, firmware limits, and available storage. Don’t choose based on the product name alone.
| System | Architecture | Format | Direct download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download Windows AMD64 |
| Windows | ARM64 | ZIP | Download Windows ARM64 |
| macOS | Intel AMD64 | GZ | Download macOS Intel |
| macOS | Apple Silicon ARM64 | GZ | Download macOS ARM64 |
| Linux | AMD64 | DEB | Download Linux DEB |
| Linux | AMD64 | GZ | Download Linux AMD64 |
| Linux | ARM64 | GZ | Download Linux ARM64 |
| Linux | ARMv7 | GZ | Download Linux ARMv7 |
| Linux | MIPS softfloat | GZ | Download Linux MIPS softfloat |
| Item | What you’ll need |
|---|---|
| Configuration and permissions | Prepare a compatible YAML configuration and make sure the user running Mihomo can read its configuration directory. On Unix-like systems, grant the extracted binary execute permission. |
| Ports and firewall | Check whether the listening ports are already in use. Restrict access to proxy ports and the control interface to trusted devices; don’t expose them directly to the public internet. |
| Service management | Test startup and the configuration in the foreground before adding a system service. Keep a recovery plan before changing routes or DNS. |
After installation
Complete these three setup steps in order. A successful install doesn’t mean your proxy is already working.
01 / Configuration source
First, make sure the subscription provides a format your client can read. A complete YAML configuration can include proxy groups and rules; a list of nodes alone usually can’t replace a full configuration. After importing, check the configuration name, update time, and proxy groups to make sure you didn’t load an older file by mistake.
See how to import a subscription →02 / Traffic routing
For everyday use, start with rule mode and then enable the system proxy. System proxy settings only affect apps that follow them; TUN can capture a wider range of traffic. Verify that a basic route works before troubleshooting specific apps, games, or terminal traffic. This makes it easier to pinpoint the cause.
See how to configure the system proxy →03 / Verify the result
Open the site you want to reach and review the connection log to see the matched rule, proxy group, and node in use. A latency test only measures a particular test request; it doesn’t prove that a site is reachable. If something fails, save the error details and narrow down whether the issue is the subscription, DNS, route, or network routing.
See the connection troubleshooting steps →Updates and migration
App updates affect the interface, system integration, and bundled core. Subscription updates change remote configuration content. Version details appear on the cards once the release manifest loads. Filenames and app version labels may differ across platforms, so check the actual installer and the client’s release notes.
Keep a restorable copy of your configuration before upgrading. If you use overrides, scripts, or local rules, note where they take effect. A remote subscription update may overwrite the original configuration; putting long-term rules directly in a subscription file can cause them to disappear on the next refresh.
Before moving to a new client, disable the old client’s system proxy, auto-start, and related background services. Closing its window may not quit the app. After importing your subscription into the new client, test one route first. Then re-enable TUN, LAN sharing, or complex routing as needed to avoid changing several variables at once.
Subscription URLs, exported configurations, and connection logs may contain sensitive information. Store backups securely. When asking for help, remove subscription credentials, node authentication fields, and unnecessary personal browsing records. For definitions of configuration terms, see the Clash terminology guide.
Download questions
Start with Clash Plus on Windows, macOS, Android, or iOS; Linux users can start with Clash Verge Rev. Check your operating system and processor architecture before downloading. A client is not a proxy service: you’ll still need to import an existing compatible subscription or local configuration.
AMD64 and x64 refer to the common 64-bit Intel and AMD architecture; ARM64 is for ARM-based devices. On Android, choose a build that matches your device ABI, or use the available universal build if you’re unsure. On Apple Silicon, choose a native ARM64 build when available. An x64 build requires system translation support.
The installer provides a client and configuration management tools, but no proxy servers. Get a compatible subscription from a service you already use, or import your own YAML configuration. Then choose a node from a proxy group and enable the system proxy or the network capture mode you need. Subscription URLs contain access credentials—don’t share them publicly.
Before upgrading the same client, export your configuration and note any overrides, proxy group selections, and ports. Different forks with similar names may use separate configuration directories. When switching clients, reimport your subscription and check your rules. Before uninstalling the old app, disable its system proxy and background services to prevent both clients from handling traffic at once.
Mihomo is the core that handles protocol connections, rule matching, and traffic forwarding. A graphical client adds an interface for importing configurations, selecting nodes, and integrating with the operating system. Server and router users can run the core and manage configuration, permissions, and services themselves; desktop and mobile users are usually better off with a graphical client.
First make sure the installer matches your platform, processor architecture, and operating system. Then check available disk space and installation permissions. On Linux, confirm whether you need a deb or rpm package and check for missing libraries. On Android, allow installs from the source you’re using. Read any system warnings before taking action, and don’t disable device-wide security protections just to proceed.