Installers for Windows, macOS, Android, iOS, and Linux in one place. Most users should start with a GUI client; check the core section for servers, routers, or command-line environments.
A single client may offer multiple architecture builds. The primary button covers most devices; other architectures are listed nearby as clear alternatives.
Most Windows 10 and Windows 11 PCs with Intel or AMD processors should use the x64 installer. Import your subscription after installation, then enable the system proxy. Check TUN settings only if you need to route command-line or game traffic.
For Windows users who want to complete installation, subscription import, and proxy mode switching quickly. Settings are centralized, so you do not need to edit YAML files directly for everyday configuration updates.
A desktop client powered by the Mihomo core, with proxy group switching, subscription management, rule inspection, and TUN configuration. Suitable for users who need comprehensive network controls.
The same interface spans desktop and mobile platforms, making it easier to keep a consistent workflow across devices. On Windows, choose the installer or keep the ZIP archive as a portable alternative.
A GUI client for desktop environments, with clearly separated subscription, proxy group, and system proxy controls. Best for users who understand the differences between Rule, Global, and Direct modes.
Kept for existing configurations, older-device migration, and restoring legacy environments. For new installations, the actively maintained GUI clients above are recommended for newer core capabilities and better system compatibility.
| Item | Recommendation | Details |
|---|---|---|
| System | Windows 10 or Windows 11 | Newer systems generally provide more complete networking components and permission management. |
| Processor | x64 | Choose x64 for most Intel and AMD desktops and laptops. |
| Permissions | Allow system changes during installation | Enabling TUN or service mode may require administrator privileges. |
Check the chip type in About This Mac first. Choose Apple Silicon or ARM64 for M-series chips, and x64 for Intel processors. On first launch, macOS may ask you to approve the app and network extension permissions.
Offers separate Apple Silicon and Intel downloads, with a GUI for managing subscriptions, proxy modes, and the system proxy. Just confirm your Mac’s chip type before installing.
For macOS users who need Mihomo rules, TUN, and configuration editing. The current download is resolved by architecture from the release list; check the core status in the client after installation.
The interface is similar across Windows and Android, making it suitable for users who manage computer and phone configurations together. Still choose the download that matches your Mac’s chip.
A legacy menu bar client retained for existing workflows and restoring older configurations. On a new device, compare the maintained clients above before choosing an archived release.
| Item | How to choose | Details |
|---|---|---|
| Apple Silicon | Choose ARM64 or Apple Silicon | For Macs with M-series chips. |
| Intel | Choose x64 or Intel | For Macs with Intel processors. |
| First launch | Approve permissions when prompted | Network extensions, the system proxy, and TUN may each request authorization. |
Most recent Android phones and tablets use ARM64. Older devices may need ARMv7; if you are unsure, use the universal package for Clash Meta for Android. After installation, Android displays a VPN permission prompt the first time you connect.
For common ARM64 Android devices, with subscription import, proxy group selection, and connection controls. A good fit for recent mainstream phones and tablets, with a straightforward installation process.
Offers ARM64, ARMv7, and universal packages for users who need to match a specific device architecture or support older hardware. If you do not know the processor type, the universal package avoids guesswork.
For users already running FlClash on desktop who want a similar interface on their phone. Provides ARM64, ARMv7, and x86_64 builds.
Universal Android package
A rule-based proxy client for Android and an alternative for different configuration workflows. The universal package is suitable when you do not want to identify the processor architecture separately.
| Package | Common devices | Recommendation |
|---|---|---|
| ARM64 | Recent phones and tablets | When the architecture is unknown but the device is relatively new, start here. |
| ARMv7 | Older 32-bit ARM devices | Check this version only if ARM64 will not install. |
| Universal package | Devices with an unknown architecture | The file is usually larger, but avoids architecture guesswork. |
| x86_64 | Some emulators and specialized devices | Typical physical phones should not use this option. |
Install Clash Plus on iPhone or iPad through the App Store. Open the app, follow the prompts to add a subscription, and allow iOS to create a network connection configuration. You can then choose proxy groups and connection modes in the app.
A GUI client for iPhone and iPad. Supports subscription import, proxy group selection, rule modes, and connection controls for managing Clash configurations on mobile devices.
| Item | Requirement | Details |
|---|---|---|
| Device | iPhone or iPad | Open the app’s listing through the App Store on the device. |
| Network permissions | Approve on first connection | The system displays a prompt to authorize creation of a network connection configuration. |
| Configuration | Subscription link or configuration file | After installation, you still need to import a usable configuration before a proxy connection can be established. |
For Ubuntu, Debian, and derivatives, choose DEB; for Fedora and RHEL-based distributions, choose RPM. GUI clients suit desktop environments, while servers and routers should use the Mihomo core section below.
For Linux computers with a desktop environment, offering DEB and RPM packages. Manage subscriptions, rule modes, the system proxy, and Mihomo-related settings in the client.
Provides DEB, RPM, and AppImage desktop packages. DEB suits Debian-based distributions, RPM suits Fedora-based systems, and AppImage is an alternative when you prefer not to use the system package manager.
| Format | Common distributions | Highlights |
|---|---|---|
| DEB | Debian、Ubuntu、Linux Mint | Can be installed and removed through the system package manager. |
| RPM | Fedora and RHEL-based distributions | For desktop systems using the RPM package ecosystem. |
| AppImage | Multiple desktop distributions | Grant execute permission, then run it as a portable alternative. |
Core packages are intended for servers, routers, container hosts, and self-managed environments. Most computer and phone users should choose a GUI client above instead of manually handling configuration, services, and startup tasks.
| System | Architecture | File format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | Common Intel and AMD computers and servers | Download |
| Windows | ARM64 | ZIP | Windows on ARM devices | Download |
| macOS | Intel AMD64 | GZ | Macs with Intel processors | Download |
| macOS | Apple Silicon ARM64 | GZ | Macs with M-series chips | Download |
| Linux | AMD64 | DEB | Debian and Ubuntu servers | Download |
| Linux | AMD64 | GZ | Generic Linux binary archive | Download |
| Linux | ARM64 | GZ | 64-bit ARM servers and routers | Download |
| Linux | ARMv7 | GZ | 32-bit ARMv7 routers and embedded devices | Download |
| Linux | MIPS softfloat | GZ | MIPS devices using a soft-float ABI | Download |
The core reads configuration, opens proxy listening ports, and applies rules. Subscription updates, tray menus, system proxy switching, and startup behavior must be provided by a management panel, service script, or GUI client.
For a first run, you need at least ports, proxy nodes, proxy groups, and rules. Add advanced DNS, TUN, rule providers, and external controller settings one at a time after the basic connection works.
For embedded devices, verify available storage, RAM, and the system ABI in addition to architecture. Being able to extract a file does not guarantee compatibility; architecture or dependency errors in the runtime log are more useful indicators.
Downloading is only the first step. The client still needs a configuration source, proxy mode, and system network permissions. Handling these in order is easier to troubleshoot than changing many switches at once.
Run the installer on Windows; open the DMG and follow the prompts on macOS; open the matching architecture package on Android; install from the App Store on iOS; and choose DEB, RPM, or AppImage on Linux. Approve required permissions when prompted on first launch.
Open the Subscription, Configuration, or Profiles page, paste the subscription link from your service provider, and import or update it. You should then see the configuration name, proxy groups, and rules. If the list is empty, check that the link is complete, then review the client’s parsing details.
Rule mode is usually the best starting point for everyday use, letting rules decide whether traffic goes direct or through a proxy. Global sends more connections through one proxy group for short tests; Direct pauses proxy handling. After choosing a mode, select an available node in the main proxy group.
Browsers and desktop apps that follow system proxy settings usually work with the system proxy alone. Command-line tools, games, and apps that ignore system proxy settings may need TUN. Test one method at a time so you can identify which layer is causing a problem.
First decide which package to download, then work out how to connect. These questions cover the most common decisions during an initial download.
Most users should choose the featured or recommended GUI client for their platform. GUI clients include subscription import, proxy mode switching, rule inspection, and system proxy controls, so you do not need to manage core files separately. For servers, routers, or existing management panels, choose the Mihomo core instead.
Most Windows PCs use x64. Apple Silicon Macs use ARM64, while Intel Macs use x64. Recent Android devices are usually ARM64; older ones may use ARMv7. If you are completely unsure, choose a client with a universal build. For servers and routers, check the system page or existing package name to confirm the exact architecture.
No. System proxy and TUN are traffic-routing methods built into the client, so you can switch between them after installing the same GUI client. The system proxy mainly covers apps that follow system settings; TUN uses a virtual network interface to handle a broader range of traffic and may require additional permissions. For first-time setup, verify the subscription with the system proxy before trying TUN.
Archived download links remain available for existing configurations and older devices. Both clients are no longer maintained, so new installations are generally better served by clients that are still being updated. If you continue using an archived version, avoid copying configuration fields that require a newer core and keep a backup of your working configuration.
The Mihomo core provides command-line operation, proxy listeners, rule matching, DNS, TUN, and other low-level capabilities for servers, routers, and self-managed environments. GUI clients add settings screens, subscription management, system proxy switching, log viewing, and system integration, making them better for everyday computers and phones.
After installing and launching the client, open the subscription or configuration page, paste the subscription URL provided by your service, and import or update it. Once the configuration appears, choose a proxy group, then enable the system proxy or TUN mode as needed. If the update fails, check for extra spaces in the link and confirm that the network can reach the subscription URL.