Choose your operating system, then check the CPU architecture. Use a GUI client on desktop and mobile; use the Mihomo core on devices where you manage services yourself.
After installing a client, import an existing subscription or local configuration.
Keep your existing configuration before installing a new client. Use the notes below each download button to check the architecture and package format; device names alone don’t guarantee compatibility.
For a new setup, start with Clash Plus. Compare alternatives if you need to keep using another client’s workflow. The GUI installers below are x64; Windows ARM devices must meet the system’s app-compatibility requirements. These are not native ARM64 packages.
A good fit if you want to import configurations and switch policies through a graphical interface. Install the client, import an existing subscription, and enable the system proxy after confirming the configuration is active. If another proxy app is running, quit it first to avoid competing changes to system proxy settings.
For desktop users who need subscription management, rule overrides, and service mode. After installing, check both the app settings and the active configuration; an interface toggle may not correspond to a field in the subscription file. Before enabling TUN, make sure the service component has the required permissions.
A good fit if you want a similar workflow across desktop and mobile. The installer is convenient for a standard setup; the archive lets you choose where to keep the program files. Portable storage does not isolate system services or proxy settings. Disable proxy control and save your configuration before moving the program directory.
Another desktop GUI option for comparing configuration management workflows. When migrating, import the original subscription rather than copying another client’s entire data directory. After changing cores or updating a configuration, check the logs for protocol parsing results and verify the connection.
Kept as an archive for reproducing older setups and reference during configuration migrations. For new installations, choose a client above that is still maintained. Older cores may not recognize newer protocols or configuration fields. If an import fails, check compatibility before trying to reinstall repeatedly.
| Check | Requirements and guidance |
|---|---|
| Processor | Check the system type in Windows Settings under System information. This section primarily offers x64 packages; verify compatibility requirements separately for ARM devices. |
| Windows version | Use a supported Windows release and check the selected installer’s version requirements. Current clients are not guaranteed to run on older versions. |
| Service permissions | Standard system proxy use and TUN have different permission requirements. Follow Windows prompts to grant administrator access when installing a service or virtual network adapter. |
Check About This Mac for your chip type. Apple Silicon and Intel use different native packages. Some architecture links currently point to the same x64 file, as noted below; check the actual package before downloading.
Choose the ARM64 or x64 disk image for your chip. Open it, move the app to Applications, and launch it from there. Follow macOS prompts to review permissions on first launch. After importing a subscription, test browser access with the system proxy before configuring other traffic interception as needed.
For users who need desktop configuration management and rule editing. Both current links point to an x64 disk image. Apple Silicon users should check Rosetta compatibility first; these are not native ARM64 packages. After installation, check whether service mode needs additional permissions.
A cross-platform GUI for managing configurations. Both links in the current macOS listing point to an AMD64 package; Apple Silicon devices need compatible runtime support. Don’t infer the architecture from the platform label. If macOS says the app can’t run, check the package type and OS version first.
Archived for reference when maintaining an existing setup or migrating; not recommended for new devices. Both links in the current listing are x86_64 disk images. Before migrating, note your subscription and local rules, then import them into the new client instead of copying old app preferences over.
| Check | Requirements and guidance |
|---|---|
| Chip type | Use a native ARM64 package on Apple Silicon and x64 on Intel. Check Rosetta requirements to run x64 apps on Apple Silicon. |
| Windows version | Follow the installation requirements for the specific app. A matching CPU architecture does not guarantee support for older macOS versions. |
| First launch | After confirming the download source, follow Privacy & Security settings to open the app. Don’t disable system security protections entirely just to run one app. |
Most recent phones use ARM64; older devices may need ARMv7. Check your device details, or use the client’s universal package if you’re unsure. After installation, Android will ask you to authorize the VPN connection.
For ARM64 Android devices. After downloading the APK, grant install permission only to the app you’re using to install it. When you start the client, import a configuration, and connect, Android will request VPN permission. Confirm the app name, approve the request, then check the client’s connection log.
For Android users with Clash configurations. Packages are available for ARM64, ARMv7, and universal devices. Choose the package for your device; if you’re unsure, try the universal build. If the connection drops when the screen locks, check background activity and battery restrictions before repeatedly switching nodes.
For users already familiar with FlClash on desktop. Android packages are available for ARM64 and ARMv7. Android VPN permission is separate from the desktop system proxy toggle. If another app is using the device’s VPN connection, disconnect it before starting this client.
Another Android configuration option, using its own supported configuration syntax. A Clash YAML file is not automatically compatible with Surfboard. Before downloading, confirm your configuration source can provide a compatible format and check that the required protocols and rule features are supported.
| Check | Requirements and guidance |
|---|---|
| Architecture and version | Check whether you need ARM64 or ARMv7, and confirm the Android version required by the installer. A universal package does not bypass OS version requirements. |
| Connection permissions | Using the system VPN interface requires your approval. Other VPN apps and clients may compete for the same connection. |
| Background activity | Once the connection is stable, adjust battery restrictions only as needed. Allow background activity for clients that need a persistent connection, rather than loosening permissions for every app. |
Check Clash Plus compatibility and installation details in the App Store. System requirements, feature descriptions, and pricing are as shown in the store listing when you view it.
After installing from the App Store, import an existing configuration, then follow the system prompts to add a VPN configuration. You can return to the client during a connection to check the active policy and rules. If no policies are available after importing, check that the subscription updated successfully and that its contents are supported by the client.
| Check | Requirements and guidance |
|---|---|
| Device compatibility | Check the App Store compatibility section for the iOS version on your iPhone or iPad. |
| Connection authorization | Follow the system prompt to add a VPN configuration when connecting. You may need to authorize it again after deleting the app or resetting settings. |
| Configuration source | Have an existing subscription or a configuration file supported by the client ready. Installing from the store and importing a subscription are separate steps. |
Desktop users should choose DEB or RPM for their distribution. The GUI packages here are AMD64 / x86_64. For routers, ARM boards, or headless servers, use the Mihomo core tab to check the architecture.
For Linux desktop users who need a GUI. Choose the package format used by your distribution: Debian-based systems use DEB, while RPM-based distributions use RPM. Don’t just change the file extension. If desktop runtime libraries are missing, install the dependencies through your system package manager, then configure service permissions if needed.
An AMD64 DEB package for desktop Linux. Confirm your distribution uses the corresponding package system before installing and importing a configuration. Whether apps use the system proxy depends on the desktop environment and the apps themselves; command-line tools may not inherit desktop proxy settings.
| Check | Requirements and guidance |
|---|---|
| Processor | Check the architecture with uname -m. x86_64 matches the AMD64 packages here; don’t install an AMD64 GUI package on aarch64. |
| Runtime environment | A GUI client requires a working desktop environment and the relevant runtime libraries. Check your package manager’s output for specific dependencies. |
| Package format | DEB and RPM belong to different package management systems. Check service permissions, TUN, and firewall settings for your distribution. |
For server, router, and self-managed process deployments. Most desktop and mobile users should choose a GUI client above. The core does not include a subscription management interface or automatically configure proxy handling on your device.
| System | CPU architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · x64 host | Download AMD64 |
| Windows | ARM64 | ZIP · ARM64 host | Download ARM64 |
| macOS | Intel / AMD64 | GZ · Intel chip | Download Intel |
| macOS | Apple Silicon / ARM64 | GZ · Apple chip | Download Apple Silicon |
| Linux | AMD64 | DEB · Install with a package manager | Download AMD64 DEB |
| Linux | AMD64 | GZ · Manual deployment | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM | Download ARM64 GZ |
| Linux | ARMv7 | GZ · ARMv7 environment | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ · Check ABI and byte order | Download MIPS GZ |
| Check | Before deployment |
|---|---|
| Configuration file | Prepare a configuration Mihomo can parse, and confirm that its protocols, rule providers, and external file paths are suitable for the target device. |
| Execution and permissions | After extracting a GZ archive, set executable permissions as required by your system. Listening on ports, using TUN, and changing routes may require additional permissions. |
| Process management | Start the core in the foreground first and check the logs before configuring a service manager. Confirm the working directory, configuration directory, and log output location before enabling startup at boot. |
Learn how original Clash, Meta, and mihomo relate and how their protocol support differs in the core and configuration compatibility guide. The same file format does not mean an older core can recognize every field.
Subscription URLs may contain access credentials. Don’t include them in public screenshots, forum posts, or support requests. When troubleshooting, share the error message, client name, and system architecture. Remove credentials and personal subscription URLs before sharing configuration snippets.
Follow the steps to complete your initial setup →First identify whether the issue is with installation, configuration, or traffic handling, then follow the relevant troubleshooting steps.
On desktop and mobile, start with the GUI client for your platform. Use its interface to import subscriptions, choose policies, and configure system settings. The Mihomo core is intended mainly for server and router users who manage startup options, configuration files, and services themselves.
The client reads your configuration and handles proxying and traffic routing; it does not generate working server connection details. After installation, import an existing subscription or local configuration, enable it, choose a policy, and verify that the rules match as expected. Never share subscription URLs or credentials in your configuration.
Check your device’s CPU architecture first. x64 and AMD64 usually refer to the same 64-bit architecture; ARM64 is a different architecture. Older Android devices may need an ARMv7 package. A universal package supports multiple architectures, but not necessarily every OS version. Check the package’s actual architecture and system requirements.
Back up your subscription URL, local rules, and override settings first, then import the original subscription or configuration into the new client. A GUI client’s settings file is not necessarily a portable configuration. If fields or protocols are unsupported, check the new client’s actual core and configuration format rather than relying on the file extension.
Make sure the configuration is enabled, the policy group has a working node selected, and check the connection log. Then check whether the system proxy is enabled and whether the target app honors system proxy settings. Enable TUN only if network-level interception is actually needed, and follow the guide to check service permissions, DNS, and routing.
Only let one client at a time control the system proxy or TUN. Multiple clients can conflict over listening ports, system proxy settings, and virtual-interface routes. When testing a migration, quit the old client and disable its proxy control before starting the new one. Keep the original configuration so you can roll back.