Installers / System Architecture / Configuration Setup
For Windows, macOS, Android, and iOS, start with Clash Plus; for Linux, start with Clash Verge Rev. Choose the right processor architecture, then import a subscription. Installing a client and getting a working configuration are separate steps.
Choose an operating system first, then select a download button on its card. Versions appear on the card when available in the manifest. Check the relevant release notes, installer, or store listing for minimum OS versions and compatibility.
Most Intel and AMD PCs should use the x64 installer. For a first setup, follow this order: install the client, import a subscription, select rule mode, then enable the system proxy. Consider TUN mode and service permissions only if an app doesn't use the system proxy.
A good choice for setting up a day-to-day proxy from a subscription. After installation, make sure the active configuration is selected, then choose a node in the proxy groups. System proxy and TUN are different traffic-routing methods; you don't need to enable both when you first launch the app.
Before replacing a device or reinstalling, save your subscription source, ports, and custom rules. Official site: clashplus.io.
For users who want to manage subscriptions, rules, and proxy policies from one desktop app. If you use configuration overrides, check how the new client loads them so you don't miss existing DNS or rule changes when importing a subscription.
Service mode may require administrator approval. If your network stops working after enabling it, turn off TUN first and test connectivity with the system proxy. Then check the service and network adapter status.
Consider FlClash if you want a similar experience across desktop and mobile. AMD64 and x64 refer to the same common desktop architecture; x64 doesn't mean the app only works on AMD processors.
After migrating from another client, check the mixed port, startup behavior, and configuration update schedule. You can reuse a subscription, but interface preferences from the old client won't necessarily carry over.
For users comparing desktop configuration management options. When testing a new client, quit the old proxy process first to prevent port conflicts or both apps from changing your system proxy settings.
If a subscription works in another client but fails after migration, check the specific configuration fields and core compatibility instead of repeatedly reinstalling the app. Keeping a backup of the old setup makes differences easier to track down.
For reproducing legacy environments, migrating configurations, or viewing the old interface. The project is no longer maintained, so new users should choose a client above. Older cores may not recognize newer protocols, rule extensions, or configuration fields.
Don't remove required subscription fields just to keep the old interface. A safer approach is to back up your configuration, import the subscription into a maintained client, and verify it step by step.
| Check | What to check |
|---|---|
| Operating system | Use a Windows version that is still supported. Check each client's release notes for its minimum version. |
| Processor | Go to Settings → System → About to check your system type. The x64 packages here are common x64 builds, not native ARM64 packages. |
| Permissions and ports | System proxy and TUN service permissions are different. If a port is already in use, quit the old process first, then change the port if needed. |
Check your chip in Apple menu → About This Mac. Apple Silicon and Intel use different architectures. The buttons below reflect the available download listings; confirm the actual filename and app architecture rather than assuming a listing guarantees native support.
Choose the installer for your chip, open the disk image, and follow the installation prompts. On first launch, import a configuration and select rule mode. Verify your browser can connect before deciding whether to route more traffic through the app.
Grant network extension or VPN permissions only for the action you're taking. Back up your configuration before updating so you don't mistake a proxy permission issue for a subscription failure. Official site: clashplus.io.
For desktop users who manage multiple configurations and check proxy groups. Both fallback files in the current listings are marked x64. Apple Silicon users should confirm compatibility and whether Rosetta is needed; this file is not a native ARM build.
After migrating your configuration, check that the system proxy points to the current listening port. If you still can't connect after quitting the app, check whether your system network settings still point to a stopped local proxy.
For users already running FlClash on another device who want a similar workflow. The current fallback filename is amd64. Apple Silicon users should confirm compatibility before installing; the download listing doesn't guarantee a native ARM build.
After importing a subscription, check that each proxy group has a working node selected. Even if the same subscription works on your phone, desktop still needs its own system proxy, startup settings, and any required system permissions.
For migrating or reviewing an existing ClashX Meta setup; not recommended as a first install. Both current fallback files are x86_64. Apple Silicon users should check compatibility before running them.
An older client's core may not support newer subscription requirements. If you encounter an unsupported protocol or configuration option, migrate to a maintained client rather than assuming everything works because the menu bar says the app is running.
| Check | What to check |
|---|---|
| Chip type | If About This Mac shows an Apple chip, choose a build explicitly marked arm64. Intel processors need x64. |
| Operating system version | Minimum macOS versions vary by client; check the release notes and installer prompts. Older clients may not work with newer macOS versions. |
| Permissions and security alerts | Verify the app source and read the alert details. Grant only the permissions needed for the feature; don't disable system-wide protection to dismiss an unknown alert. |
Most newer phones use ARM64, while some older 32-bit devices need ARMv7. After installation, you'll usually need to approve the system VPN connection request. If another VPN app is installed, check whether both apps are trying to use the same connection.
A good choice for first-time users who want to manage subscriptions in a GUI. This listing is for ARM64; both your device architecture and Android version must meet the app requirements. The processor brand alone isn't enough to determine compatibility.
Import and activate a subscription before starting the connection. If it drops when the screen locks, check whether battery management is limiting background activity. Official site: clashplus.io.
For users who need Meta configuration features and are comfortable checking settings in detail. Choose the build for your architecture; if you're unsure, consider the universal build. Universal doesn't mean compatible with every Android version.
If configuration import fails, check the error details and subscription format. After connecting, review the app's per-app routing settings to make sure the apps you need aren't excluded from the proxy.
For users who want a similar configuration workflow on desktop and Android. Check your phone's architecture before downloading the right APK. If Android can't parse the package, check that the download completed and that your system meets the minimum requirements.
Android VPN permission works differently from a desktop system proxy. If only some apps can't connect, check per-app settings, rule matches, and DNS logs before trying a different node.
For users with a compatible Surfboard configuration. Its configuration format differs from Clash clients, so you can't import every Clash YAML file as-is. First check which formats your subscription provider supports.
When converting a configuration, check supported protocols and rules too; node count alone doesn't show whether conversion worked. If your subscription only provides Clash format, use one of the Clash clients above.
| Check | What to check |
|---|---|
| System and architecture | Check the Android version and CPU architecture in device information. A 64-bit processor may still be running a restricted system environment. |
| Installation permissions | Grant install permission only to the source used to open the APK. If there's a signature conflict, back up your configuration before dealing with the old app. |
| Connection and background activity | Approve the system VPN request. If the connection drops when the screen locks, check background activity, battery optimization, and other VPN connections instead of repeatedly reinstalling the app. |
Check the App Store listing for Clash Plus compatibility, system requirements, and app details. After installing, import a subscription, add the VPN configuration when prompted, then check your active policy and connection status.
Install and update through the store listing, and check its requirements for device compatibility. On first use, add a configuration and approve the VPN connection. Installing the app doesn't create a personal subscription.
If the connection fails after switching between Wi-Fi and mobile data, first make sure the current network works, then check your nodes and proxy groups. Official site: clashplus.io.
| Check | What to check |
|---|---|
| System requirements | Check the minimum iOS version and compatible devices on the App Store listing. Requirements for other platforms don't apply to your phone. |
| VPN configuration | Approve the VPN permission when you connect for the first time. If device management policies restrict VPN access, check with your administrator first. |
| Configuration setup | Import a valid subscription or compatible configuration, then check your proxy groups and selected nodes. Don't share your subscription URL publicly. |
If you have a desktop environment, start with a GUI client. Debian- and Ubuntu-based systems typically use deb packages; Fedora and other distributions may use rpm, depending on their package management. Check your architecture first: the GUI packages here are for AMD64 / x86_64.
For managing configurations, the system proxy, and connection logs in a desktop environment. Use your distribution's package manager to handle dependencies, rather than copying installation commands from another distribution. Don't ignore missing dependency warnings.
System proxy settings may not cover terminal programs or every desktop app. If you need to route more traffic, understand TUN permissions, routing, and DNS configuration before enabling and verifying each setting.
For users on Debian-based systems who want to keep using FlClash. This is an AMD64 deb package; it isn't for direct installation on ARM routers, and deb isn't a universal format for every Linux distribution.
After launch, verify that the configuration parses and the local listening port is available, then check whether the desktop proxy is working. Servers without a graphical session are better suited to the Mihomo core below, with services managed separately.
| Check | What to check |
|---|---|
| Architecture and distribution | Run uname -m to check the architecture, and inspect /etc/os-release to identify the distribution. x86_64 corresponds to the AMD64 packages here. |
| Desktop dependencies | GUI clients need a suitable desktop environment. Check the installer output and release notes for specific dependencies and system library requirements. |
| Services and networking | TUN, routing, and DNS interception require appropriate permissions. Before making remote changes, have a way to restore access in case a routing change disconnects you. |
MIHOMO / CORE
For users managing their own server, router, or runtime environment. The core handles proxies, rule-based routing, and DNS; it isn't a full client with a subscription management interface. Most desktop and mobile users should choose a GUI client above.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · zip | Download AMD64 core |
| Windows | ARM64 · zip | Download ARM64 core |
| macOS | Intel AMD64 · gz | Download Intel core |
| macOS | Apple Silicon ARM64 · gz | Download Apple Silicon core |
| Linux | AMD64 · deb | Download AMD64 deb |
| Linux | AMD64 · gz | Download AMD64 core |
| Linux | ARM64 · gz | Download ARM64 core |
| Linux | ARMv7 · gz | Download ARMv7 core |
| Linux | MIPS soft-float · gz | Download MIPS soft-float core |
For routers, also check the CPU instruction set, bitness, endianness, and floating-point support. MIPS soft-float isn't a universal package for all MIPS devices. If your device requires a different byte order, don't install a build based only on the word “MIPS.”
A gz file is a compressed archive, not a graphical installer. Extract it, set the required execution permissions, and prepare configuration and runtime directories. Before exposing the control interface, restrict its listening address and access permissions so the management port isn't exposed to the public internet.
First get one connection working and verified, then expand the traffic you route. Download speed, node speed tests, and access to a target service measure different things; no single number can tell you whether the whole setup is working.
Enter a subscription URL in the import screen or select a local configuration file. After the update completes, make it the active configuration and check that the expected proxy groups appear. Subscription credentials are private information; don't reveal them in screenshots or error reports.
For everyday use, select rule mode and choose a node for each proxy group. On desktop, enable the system proxy and test in a browser; on mobile, confirm the VPN is connected. Enable TUN only when you need to route apps that don't use the system proxy, then check permissions, DNS, and routing.
Once connected, record your ports, configuration source, and any necessary overrides. Quit the old client before upgrading to avoid both apps changing the system proxy. After migrating, test the apps you rely on before removing the old setup. If something goes wrong, change one setting at a time to identify whether the cause is a node, rule, or system setting.
Follow the steps to make your first connection →Compare clients side by side →
Check the file, architecture, and configuration before troubleshooting proxy routing. Expand the answers below, or see FAQs for more network troubleshooting.
Start with Clash Plus for Windows, macOS, Android, and iOS; for Linux, start with Clash Verge Rev. Clients manage configurations and connections, but you'll still need to import a working subscription or local configuration after installation. If your current setup is stable, back it up before migrating. There's no need to run multiple clients at once.
Check your processor architecture in system information first. Windows x64 installers are for common Intel and AMD desktop processors. For Apple Silicon, choose a build explicitly marked arm64; Intel Macs need x64. Newer Android phones typically use ARM64, while older 32-bit devices use ARMv7. If you're unsure, consider a universal build. Always check the actual filename and app requirements; a platform listing alone doesn't guarantee a native build.
Make sure the download is complete and the file extension matches your system, then check the architecture and OS version. Android install parsing errors often stem from an architecture mismatch, system requirements, or a signature conflict. For Windows and macOS security alerts, verify the file source and read the details rather than disabling system-wide protection. Back up your configuration before reinstalling or removing the old app.
The installer doesn't include a personal subscription. Import and activate a valid configuration, select an available node, then enable the system proxy or TUN mode if needed. First confirm your regular internet connection works and the subscription updated successfully; then check the connection logs. Node speed tests are only a guide—test access to the service you need.
For the same client, an in-place update is usually recommended when its release notes say so. Different signatures, distribution channels, or migrations between clients may not be compatible. Export your configuration before updating and note your ports, rule overrides, and TUN settings. Quit the old process before installing, and don't run two system proxies or TUN connections at once. If the update causes problems, restore your backup.
Mihomo is the core program that handles proxies, rules, and DNS; it doesn't include a full desktop management interface. GUI clients bring configuration imports, proxy group selection, logs, and system proxy settings together in one interface. Most desktop and mobile users should choose a GUI client. Server and router users can choose a core build for their OS and architecture, then configure services and permissions themselves.