Choose your operating system, then check the architecture. Use a GUI client on desktops and phones; choose the Mihomo core for servers and routers.
Installers don’t include a subscription service. Have a subscription link you’re authorized to use ready, then follow the subscription import guide after installation.
For a first install, start with Clash Plus. The desktop installers below are for x64. Check your system type under “Settings → System → About” before installing. On ARM devices, first confirm that your system supports x64 apps.
For Windows users who want to start by importing a subscription. Install the app and select your subscription first, then enable the system proxy. If an app ignores system proxy settings, check TUN and permission settings.
Official website: clashplus.io
A good fit for desktop workflows that need subscription management, rule-based routing and service mode. After installation, check that the app launches normally before enabling service mode. Troubleshoot startup, configuration import and TUN permissions separately.
For users who want a similar experience across desktop and mobile. When switching, import your subscription again and check custom rules, ports and DNS individually. Settings files from different clients aren’t necessarily interchangeable backups.
For users who want a different way to manage desktop configurations. Quit any other proxy app before switching to avoid port conflicts. After importing your configuration, test access in rule mode before restoring your custom settings.
Archived installer, mainly for reproducing legacy environments and checking existing configurations. For new deployments, choose a maintained client. Older cores may not support newer protocols, rule fields or configuration syntax, so a successful launch alone doesn’t guarantee compatibility.
| Check | What to choose or do |
|---|---|
| Operating system | Use a supported 64-bit version of Windows 10 or 11. Check the installer for the exact minimum version. |
| Processor | These downloads are for x64 / AMD64. They don’t work on 32-bit Windows; on ARM devices, confirm compatibility first. |
| Runtime | Clash Verge Rev uses a WebView2 runtime. If it’s missing, install it as directed by Windows or the installer. |
| Permissions | First verify the standard app interface and system proxy. Administrator approval may be required to install a service or virtual network adapter, or to enable TUN. |
After installation, launch the client from the Start menu. If the window is blank, check the runtime; if a port is already in use, quit other proxy apps and try again. Enabling the system proxy doesn’t make every terminal app use it automatically. See the troubleshooting guide for details.
Check your chip under Apple menu → “About This Mac.” Choose Apple Silicon for an Apple M-series chip, or Intel for an Intel processor. Some alternative clients currently point both options to the same x64 file; check each card’s compatibility notes before downloading.
Separate installers are available for Apple Silicon and Intel. Open the disk image, move the app to Applications, then launch it from there instead of running it from the mounted image.
Official website: clashplus.io
A desktop option for managing multiple subscriptions and override configurations. Both architecture links currently point to an x64 build. Apple Silicon devices may need Rosetta; this is not a native ARM64 installer.
An alternative interface for use across devices. Both Apple Silicon and Intel links in the current listing point to an AMD64 build; check compatibility on Apple Silicon. After importing your subscription, review the mode and policy groups.
An archived option for users who rely on the existing menu bar workflow. Both links currently point to an x86_64 build, which requires compatibility support on Apple Silicon. Verify support for newer macOS releases and configuration fields. For new installs, consider one of the clients above.
| Check | What to choose or do |
|---|---|
| macOS version | Use a supported version of macOS. Minimum version requirements vary by app; check the app details and installer prompts. |
| Chip type | In “About This Mac,” choose ARM64 for an Apple M-series chip or x64 for an Intel processor. |
| Compatibility | Rosetta may be required to run x64 apps on Apple Silicon. The download label doesn’t guarantee the file’s actual architecture. |
| Network permissions | Approve requests for system proxy access, network extensions or helper services based on your needs. Check the app’s documentation before granting permissions you don’t recognize. |
If you see a security warning on first launch, verify the download source and app name, then check the specific reason under “System Settings → Privacy & Security.” Don’t broadly disable macOS security features just to launch an app. Quit older menu bar processes before updating to avoid connecting the new interface to an old service that’s still running.
Choose arm64-v8a for most recent phones. Check armeabi-v7a for older 32-bit devices. If you’re unsure of the architecture, Clash Meta for Android offers a universal build. Permission to install the app and permission to connect through a VPN are separate steps.
An installer for 64-bit ARM phones. Import and select a configuration before connecting. When Android prompts you for VPN access, verify the app name. You can adjust background activity and battery settings as needed.
Official website: clashplus.io
Available for ARM64, ARM and universal builds. Choose the build that matches your device where possible; the universal build is useful if you can’t identify the architecture. After importing a configuration, select it—adding a subscription alone doesn’t switch the active configuration.
Builds are available for ARM64 and compatible ARM devices. If Android says the app can’t be installed, don’t keep retrying over the existing install. First check your Android version, processor architecture and whether the installed app came from a release signed with a different key.
For Android users with a compatible configuration format. Surfboard isn’t a Clash YAML client; before downloading, check that your provider supplies a supported configuration. Simply changing a file extension won’t make it compatible.
| Check | What to choose or do |
|---|---|
| macOS version | Minimum Android versions vary by client. If the installer reports incompatibility, check the app’s documentation. |
| Processor | arm64-v8a is 64-bit ARM; armeabi-v7a is compatible 32-bit ARM. Universal builds include multiple architectures. |
| Install permissions | Grant permission to install apps only to the browser or file manager you’re using to open the installer. You can revoke it afterward. |
| Network setup | Android typically allows only one standard VPN connection at a time. Check for another VPN or local traffic-filtering app before connecting. |
If the connection drops when the screen locks, check battery optimization and background restrictions, then review the client logs. If only one app can’t connect, check its routing rules or bypass list before reinstalling. If a signing conflict means you must uninstall the old app, export your configuration first to avoid losing local rules and subscription details.
Install Clash Plus from the App Store. Check device compatibility on the store listing, then return to the app and import your subscription. The first time you connect, iOS will ask to add a VPN configuration; approve it to connect.
For managing subscriptions and proxy settings on iPhone and iPad. After installing, make sure the subscription URL is complete and select a policy group. To enable automatic updates, configure the option provided by the app.
Official website: clashplus.io
| Check | What to choose or do |
|---|---|
| System compatibility | Check the App Store listing under “Compatibility” for supported iOS and iPadOS versions and device requirements. |
| Installation and updates | Install through the App Store and update the app there. Updating the app is separate from updating your subscription. |
| VPN configuration | Follow the system prompt to add a configuration on your first connection. Other networking tools can affect the connection, so test them separately. |
| Subscription | Use a subscription URL you’re authorized to access. If the link expires or the service ends, contact the subscription provider. |
Complete subscription setup and test the connection on Wi-Fi first, then try cellular data. If only one network fails, check its DNS, captive portal and access restrictions instead of changing all your rules. Hide identifying parameters in your subscription URL before sharing screenshots.
Choose DEB for Debian, Ubuntu and compatible distributions; choose RPM for Fedora and other RPM-based systems. These GUI clients are for AMD64 desktops. For headless servers and routers, see the Mihomo core section.
Start here for Linux desktops. Choose the package format for your distribution and install it with your software installer or package manager to handle dependencies. After launching, check whether the tray, system proxy and service mode are supported in your desktop environment.
An AMD64 DEB package for compatible distributions. Desktop environments handle system proxy settings differently, so test browsers and terminal apps separately. A desktop interface doesn’t mean every process will automatically use the same proxy settings.
| Check | What to choose or do |
|---|---|
| Distribution | Use the package format supported by your distribution. Don’t try to use a DEB as an RPM, or vice versa, by changing the file extension. |
| Architecture | Desktop builds target AMD64 / x86_64. Run uname -m to check your architecture; aarch64 isn’t supported by these builds. |
| Desktop environment | A working desktop session and runtime dependencies are required. Check the package manager and client prompts for specific dependencies. |
| Network permissions | TUN and routing require the appropriate permissions. Verify the local proxy first, then enable system-wide routing gradually. |
If installation fails due to dependencies, keep the full error message and resolve it with your distribution’s package manager; don’t skip dependencies. Headless deployments don’t need a desktop environment just to run the core. If a service won’t start, check the configuration path, execute permissions and port conflicts before investigating the firewall or DNS.
For server, router and command-line deployments. Desktop users can use one of the GUI clients above. Core builds require you to provide your own configuration, service management and network permissions; they don’t include a full subscription management interface.
| Operating system | Target architecture | File and download |
|---|---|---|
| Windows | AMD64 / x64 | Download AMD64 · ZIP |
| Windows | ARM64 | Download ARM64 · ZIP |
| macOS | Intel / AMD64 | Download Intel · GZ |
| macOS | Apple Silicon / ARM64 | Download Apple Silicon · GZ |
| Linux | AMD64 · Debian-based | Download AMD64 · DEB |
| Linux | AMD64 · Binary | Download AMD64 · GZ |
| Linux | ARM64 | Download ARM64 · GZ |
| Linux | ARMv7 | Download ARMv7 · GZ |
| Linux | MIPS · softfloat | Download MIPS · GZ |
| Check | Requirement |
|---|---|
| System and architecture | The binary must match the target operating system, instruction set and ABI. For routers, confirm firmware compatibility too. |
| Configuration directory | Prepare readable configuration files and any required rule resources. The service account needs the necessary directory permissions. |
| Ports and permissions | Make sure the listening ports are available. Transparent proxying, TUN and policy routing require additional network permissions. |
| Recovery plan | Before changing the default route or DNS remotely, keep a local management path available and have a way to restore networking after stopping the service. |
Extracting the binary doesn’t install it as a system service. First run it in the foreground from a terminal, confirm the configuration parses and the ports are listening, then set up startup behavior. Linux binaries may need execute permission. Services use a different working directory than interactive shells, so specify the configuration path explicitly.
The commands below assume the current Linux directory contains a binary named mihomo and a configuration file named config.yaml. Check the configuration first, then start the core in the foreground. These commands don’t create transparent proxy rules.
chmod +x ./mihomo
./mihomo -t -f ./config.yaml
./mihomo -f ./config.yamlFor router deployments, define which device handles the gateway, DNS and forwarding to avoid loops caused by both the main router and a secondary router taking control. If the configuration parses but traffic can’t get through, check the listen address, rule references and outbound connections instead of repeatedly replacing the binary.
Read the OpenWrt secondary-router deployment guide →Get the client running first, then enable network control one layer at a time. Changing one type of setting at a time makes issues easier to isolate.
The operating system, processor architecture and package format must all match. x64 and AMD64 usually mean the same desktop instruction set and don’t require an AMD processor; ARM64 is a different architecture. A file downloading successfully doesn’t mean your device can run it. For older systems without confirmed support, check the app requirements rather than relying on archived software as a long-term solution.
Before switching clients, note your subscription URL and export local overrides, custom rules and policy group settings. Generic subscription content may be reusable, but client-specific scripts, interface preferences and configuration directories may not be. Before uninstalling, make sure you can read the backup. Don’t leave your only copy of a configuration in an app directory you’re about to remove.
Open the “Subscription” or “Configuration” page, paste the full URL and import it. Once downloaded, select that configuration, choose an available outbound option in the policy groups, then enable the system proxy. Check that your browser can reach the sites you expect, and that sites meant to connect directly still do. Don’t rely on the tray icon alone to confirm a working connection.
TUN isn’t required on first launch. Enable it only if you need to route apps that don’t use the system proxy, and check service permissions, the virtual network adapter and DNS settings. System proxy and TUN work differently. If you’re also using another VPN or network filter, check for routing and DNS conflicts.
For an installation failure, save the installer’s exact error. For a startup failure, check the client logs. For a subscription failure, verify the URL and service status. Each issue has a different fix. If the download hasn’t finished, check the browser’s download list and available disk space. If the app starts but can’t connect, downloading it again usually won’t fix a rule or subscription issue.
Before sharing logs, hide identifying parameters in subscription URLs, node credentials and external controller keys. The error type, steps to reproduce and operating system version are usually enough for initial troubleshooting. See the Clash setup guide for the full walkthrough, or use the Troubleshooting guide to find help by symptom.
Architecture, updates and configuration setup. Select a question to expand the answer.
Start with Clash Plus on Windows, macOS, Android or iOS; for Linux, try Clash Verge Rev. Check your operating system and processor architecture before choosing an installer. If you already have a working setup, export your subscription URL, overrides and rules before switching.
x64 and AMD64 usually refer to the same 64-bit desktop architecture, regardless of processor brand. ARM64 uses a different instruction set. arm64-v8a suits most recent Android phones, while armeabi-v7a is for compatible 32-bit devices. If you’re unsure, choose the universal build of Clash Meta for Android.
For some clients, the Apple Silicon and Intel links currently point to the same x64 installer. The link label doesn’t mean the file is a native ARM64 build. Apple Silicon devices may need Rosetta; for a dedicated ARM64 installer, use the Apple Silicon option for Clash Plus.
The client installer and subscription configuration are separate. After installing, import a subscription link you’re authorized to use or a local configuration, select it, and check the policy groups. Then enable the system proxy or, if needed, TUN. Installing the app does not provide proxy service.
Export your current configuration first, and note your subscription URL, override scripts, custom rules and port settings. Quit the running client before installing an update; don’t run multiple proxy clients at once. After updating, make sure your configuration is still selected, then verify the system proxy and DNS.
The Mihomo core reads configurations and handles proxy traffic. It isn’t a desktop app with subscription management. Core builds are mainly for servers, routers and command-line deployments. For a first setup, use one of the GUI clients above to avoid managing services, permissions and routing yourself.