TYPE CASE / DOWNLOAD

Clash Downloads and Platform Packages

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.

  • Free forever
  • Open source
  • Multi-platform clients
  • Chinese configuration guides

CASE / 01

Choose a Client by Operating System

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.

PLATFORM / WINDOWS

Windows Clients

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.

Top pick

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.

Clash Verge Rev

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.

FlClash

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.

Clash Nyanpasu

A desktop Clash management tool with subscription configuration, proxy group selection, and connection status monitoring. A Windows x64 installer is provided here.

Discontinued

Clash for Windows

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.

Windows Requirements

CheckRecommendationBefore Installation
SystemWindows 10 or laterKeep the system networking components and WebView runtime available
Processorx86-64The graphical client packages on this page are primarily x64
PermissionsA standard installation requires system confirmationTUN mode may require elevated permissions and driver approval

CORE / 02

Mihomo Core and Architecture Packages

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

Configuration Files

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

Process Management

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

How to Read Package Names

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
Application Version Platform Processor Format

Read the Name from the Suffix Backward

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

Desktop Users

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

Mobile Devices

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

Servers and Routers

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

Common Download and Installation Questions

A concise reference covering client selection, processor architecture, and package formats.

Which Clash client should you choose for Windows?

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.

How do Apple Silicon and Intel packages differ on macOS?

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.

Should Android users download arm64, arm, or universal?

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.

What is the difference between DEB, RPM, and AppImage on Linux?

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.

Should you choose the Mihomo core or a graphical client?

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.

How do you import a subscription after downloading a client?

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.