Clash Plus
Ideal for desktop users who want to import subscriptions, switch policies, and configure the system proxy quickly. The Windows installer uses the standard EXE format.
TYPE CASE / DOWNLOAD
Identify packages by operating system, processor architecture, and format. Confirm the device platform first, then choose a graphical client from the matching section. Server and router users can continue to the Mihomo core section.
CASE / 01
The selected tab is synced to the page URL. When you share a link with a platform anchor, recipients can jump directly to the corresponding packages.
Desktop packages are primarily x64. For everyday use, start with Clash Plus; if you prefer different interfaces or configuration workflows, compare Clash Verge Rev, FlClash, and Clash Nyanpasu.
Ideal for desktop users who want to import subscriptions, switch policies, and configure the system proxy quickly. The Windows installer uses the standard EXE format.
A desktop client built on the Mihomo core, suited to managing multiple subscriptions, configuration overrides, rule mode, and TUN mode. This site provides a Windows x64 installer.
A cross-platform graphical client with a broadly consistent interface and workflow across desktop and mobile devices. Choose either the installer or the portable ZIP package.
A desktop Clash management tool with subscription configuration, proxy group selection, and connection status monitoring. A Windows x64 installer is provided here.
An archive entry for the classic desktop client, useful for reading older configurations or completing a migration. For new installations, choose a client that is still maintained.
| Check | Recommendation | Before Installation |
|---|---|---|
| System | Windows 10 or later | Keep the system networking components and WebView runtime available |
| Processor | x86-64 | The graphical client packages on this page are primarily x64 |
| Permissions | A standard installation requires system confirmation | TUN mode may require elevated permissions and driver approval |
Check the chip name in About This Mac first. Choose arm64 for Apple M-series chips and x64 for Intel processors; matching the package to the device makes installation and future updates more straightforward.
Provides DMG installers for both Apple Silicon and Intel, suitable for configuring subscriptions, policy groups, and the system proxy through a graphical interface.
For macOS users who need Mihomo configuration features, rule overrides, and TUN settings. Select the package matching your chip before downloading.
The cross-platform interface makes it easier to keep a familiar workflow across devices. The manifest lists separate chip entries, all using the DMG format.
An archived menu-bar client for macOS, suitable for existing users migrating configurations. For new devices, compare the three actively updated clients above first.
| Check | Apple Silicon | Intel |
|---|---|---|
| Architecture Label | arm64 | x64 or x86_64 |
| Device Identification | Apple M-series chip | About This Mac shows an Intel processor |
| Package Format | DMG disk image | DMG disk image |
Most recent devices use arm64-v8a. Older 32-bit devices can use armeabi-v7a; when the model and architecture are unclear, prefer a client that offers a universal package.
For mainstream 64-bit Android phones and tablets, with subscription import, policy switching, and guidance for granting VPN connection permission.
An Android client with Mihomo-related capabilities, offering arm64, 32-bit ARM, and universal packages. Choose a dedicated package when the architecture is known; otherwise choose the universal package.
For users who run FlClash on both desktop and mobile. Android packages are split into arm64-v8a, armeabi-v7a, and x86_64 builds.
A rule-based proxy client for Android using a universal APK package. Best suited to users familiar with subscription configuration, policy groups, and rule modes.
| Package Label | Supported Devices | How to Choose |
|---|---|---|
arm64-v8a | Most phones and tablets released in recent years | Prefer 64-bit ARM devices |
armeabi-v7a | Older 32-bit ARM devices | Choose only when the device architecture matches |
universal | Supports several common architectures | Use when the architecture cannot be confirmed |
On iOS, get Clash Plus from the App Store. After installation, import a subscription in the app and approve VPN configuration permissions when prompted by the system.
A graphical client for iPhone and iPad. Approve the system VPN configuration permission on the first connection, then select policy groups and connection modes in the app.
Official site: clashplus.io
| Check | Details |
|---|---|
| How to Get It | Install from the app listing in the App Store |
| Importing Configuration | Paste a subscription URL or import a configuration file in the client |
| First Connection | Approve VPN configuration permissions when prompted by the system |
Linux desktop users can choose DEB or RPM according to their distribution's package system. These graphical clients target amd64 desktop environments; for servers and other processor architectures, go to the Mihomo core section.
A Mihomo graphical client for Linux desktops. Choose DEB for Debian and Ubuntu-based systems, and RPM for Fedora and RHEL-based systems.
The Linux build of a cross-platform graphical client. This site provides an amd64 DEB from a fixed manifest, suitable for Debian, Ubuntu, and related desktop distributions.
| Distribution Family | Package Format | Architecture |
|---|---|---|
| Debian / Ubuntu | .deb | amd64 |
| Fedora / RHEL / Rocky Linux | .rpm | x86_64 |
| Servers / Routers | Compressed Core or Service Package | Go to the Mihomo core section and choose by architecture |
CORE / 02
For users running servers, routers, containers, or maintaining service processes themselves. Everyday desktop and mobile users should choose a GUI client above.
| System | Processor Architecture | Format | Use Case | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | Common 64-bit Intel / AMD devices | Download Core |
| Windows | arm64 |
ZIP | Windows on ARM devices | Download Core |
| macOS | amd64 |
GZ | Intel processor devices | Download Core |
| macOS | arm64 |
GZ | Apple Silicon devices | Download Core |
| Linux | amd64 |
DEB | Debian / Ubuntu servers | Download Core |
| Linux | amd64 |
GZ | General 64-bit server deployments | Download Core |
| Linux | arm64 |
GZ | 64-bit ARM servers and routers | Download Core |
| Linux | armv7 |
GZ | 32-bit ARMv7 routers | Download Core |
| Linux | mips-softfloat |
GZ | MIPS devices using software floating point | Download Core |
CONFIG
The command-line core typically reads YAML configuration. Before deployment, check listener ports, proxy nodes, policy groups, rules, DNS, and control interface fields. Do not run desktop-client-only overrides as a standalone configuration without adapting them.
SERVICE
On servers, use the system service manager to handle startup, shutdown, and logs. Routers also require planning around firmware directories, startup scripts, and firewall rules.
PROOF / 03
File names usually record the application, system, version, architecture, and package format. Check each part before downloading to reduce architecture conflicts during installation.
FILENAME COMPOSITION
Application-Version-System-Architecture.Extension
Start with the extension to identify the installation method: Windows commonly uses .exe or .zip, macOS uses .dmg, Android uses .apk, and Linux desktops commonly use .deb and .rpm. Compressed core packages must be extracted, given execute permission, and started with parameters you configure yourself.
Next, check the architecture. x64, x86_64, and amd64 usually refer to common 64-bit Intel or AMD platforms; arm64 and arm64-v8a refer to 64-bit ARM; armv7 and armeabi-v7a target older 32-bit ARM devices. Similar architecture names can still imply different operating systems and packaging methods, so verify them together.
DESKTOP
Prefer a client with an installer and graphical interface. After installation, import the subscription on the Profiles or Configuration page, then set the proxy mode, policy groups, and system proxy.
MOBILE
On Android, verify the APK architecture first; install on iPhone and iPad through the App Store. Approve VPN configuration permissions through the system flow on the first connection.
SERVER
Choose the Mihomo core and maintain the YAML configuration, service process, logs, and firewall yourself. If you only need desktop proxy controls, a graphical client's configuration workflow is clearer.
NOTES / 04
A concise reference covering client selection, processor architecture, and package formats.
For a straightforward graphical interface, start with Clash Plus. If you need rule editing, subscription management, and desktop proxy controls, compare Clash Verge Rev, FlClash, and Clash Nyanpasu based on your workflow. Clash for Windows is discontinued and is mainly useful for reading and migrating older configurations.
Apple Silicon corresponds to arm64 for M-series chips; Intel corresponds to x64 or x86_64. Open About This Mac to check the chip or processor name, then use the matching DMG entry.
Most recent Android phones use arm64-v8a; older 32-bit devices can use armeabi-v7a. If you cannot confirm the processor architecture, use the universal package for Clash Meta for Android.
Debian, Ubuntu, and derivatives generally use DEB; Fedora, RHEL, Rocky Linux, and similar systems generally use RPM. AppImage is portable and usually starts after you grant it execute permission. This page's Linux client section provides the corresponding formats from a fixed manifest.
Most desktop and mobile users should choose a client with a graphical interface. The Mihomo core is better suited to servers, routers, containers, and users who manage YAML configurations and system services themselves.
After installation, open the Configuration or Profiles page, paste the subscription URL, and import or update it. Then choose the proxy mode, policy groups, and available nodes before enabling the system proxy. For initial setup, continue with the Clash usage guide; for field details, see the YAML manual.