Client and Core Downloads

Clash Download and Platform Selection

Choose a graphical client for your operating system and compare processor architectures, package formats, and use cases. First-time users should start with a client marked “Top Pick,” then consider other options based on interface preferences and system compatibility.

Windows / macOS / Linux Android / iOS Graphical Clients and Mihomo Core
Platform Packages

Choose an Operating System

The platform label is synced to the address bar, so copying the current URL preserves your selected system. Each client card explains its primary use and package differences.

Windows Clients

Graphical clients for everyday desktop use. Installers add a Start menu entry and an uninstall option; portable archives are useful when you want to keep a separate configuration directory. Windows on ARM users should note that the main graphical client packages on this page target x64.

x64 Desktop Systems

Clash Verge Rev

A popular Mihomo graphical client for desktop use, with controls for the system proxy, TUN, configuration overrides, and service mode. It suits users who understand rule modes and proxy groups and want finer control over traffic interception.

  • Package format: EXE installer
  • Processor: Windows x64
  • Best for: Users who need full desktop controls

FlClash

Its consistent cross-platform interface suits users who work across Windows, Android, or Linux. The installer is intended for standard desktop environments, while the archive runs from a separate directory for easier configuration migration and backup.

  • Installer: Creates system shortcuts automatically
  • Archive: Run independently after extraction
  • Processor: Windows AMD64

Clash Nyanpasu

A graphical client centered on subscription management, proxy group selection, and desktop controls. It suits Windows users who want to update configurations, switch rule modes, control the system proxy, and view runtime logs in one window.

  • Package format: EXE installer
  • Processor: Windows x64
  • Best for: Centralized subscription and configuration management

Clash for Windows

Discontinued

Retained for users who need compatibility with legacy configurations or older workflows. This client is archived and no longer receives ongoing feature updates; for new installations, prefer Clash Plus, Clash Verge Rev, FlClash, or Clash Nyanpasu above.

  • Package format: EXE installer
  • Use case: Migrating and supporting legacy environments
  • Status: Archived release

Windows System Requirements

Item Recommended condition Pre-installation check
Operating system 64-bit Windows 10 or Windows 11 Complete system updates and confirm that your account can install desktop applications
Processor x64 / AMD64 Check the system type in Settings > System information
Network access Allow the client to access the network and change proxy settings The first time you enable TUN or service mode, administrator approval may be required
Command-Line and Embedded Environments

Mihomo Core Downloads

Servers / Routers

The standalone core is intended for servers, software routers, containers, and users who maintain configuration files themselves. Regular desktop and mobile users should prefer the graphical clients above, which handle subscriptions, core startup, system proxy settings, and runtime status.

System Architecture and format Supported environment Download
Windows AMD64 · ZIP 64-bit Intel / AMD servers and command-line environments Download AMD64
Windows ARM64 · ZIP Windows on ARM devices Download ARM64
macOS Intel x64 · GZ Macs with Intel processors Download Intel
macOS Apple Silicon · GZ Macs with Apple M-series chips Download Apple Silicon
Linux AMD64 · DEB Debian and Ubuntu servers Download DEB
Linux AMD64 · GZ Generic x86_64 Linux environments Download AMD64
Linux ARM64 · GZ 64-bit ARM servers and routers Download ARM64
Linux ARMv7 · GZ 32-bit ARMv7 routers and development boards Download ARMv7
Linux MIPS softfloat · GZ MIPS routers using software floating point Download MIPS

Graphical Clients vs. the Core

Mihomo parses configurations, establishes connections, and executes rules. Graphical clients build on the core with subscription updates, proxy group selection, system proxy controls, TUN settings, and log viewing. For personal computers or phones, a graphical client is usually the better choice.

What is needed for a standalone deployment?

In addition to the executable, prepare a valid configuration file, working directory, log management, and startup method. When deploying on a router or server, confirm the listen address, port, firewall, and DNS settings first, then enable traffic forwarding step by step to avoid changing too many network parameters at once.

First Step After Installation

From Package to Working Configuration

Downloading a client is only the setup phase. On first launch, import a configuration, choose a proxy mode, and confirm that system traffic is reaching the client.

01

Complete the installation

Use the system wizard for desktop installers; on macOS, move the app to Applications; on Android, open it after installation and grant the required VPN permissions. Linux users should choose DEB, RPM, or AppImage for their distribution.

02

Import a subscription

On the client’s subscription, configuration, or Profiles page, paste the complete subscription URL and download or update it. If the provider supplies a local configuration file, import it from a file instead. After import, you should see the configuration name and proxy groups.

03

Choose a mode

For everyday use, start with Rule mode so the configuration decides which connections use the proxy. Global mode sends more connections through the current proxy policy and is useful for short tests; Direct mode pauses proxying while leaving the client running.

04

Enable traffic interception

Start with the system proxy for browsers and regular desktop apps. Command-line tools, games, and apps that ignore system proxy settings may require TUN mode. After connecting, visit a familiar website and check the logs for DNS, port, or permission errors.

Download FAQ

Choosing Packages and Architectures

Choose a package by operating system and processor first, then configure subscriptions and connections. These questions cover the most common decisions when downloading for the first time.

Which Clash client should I download first?

For the fastest installation and subscription import, start with Clash Plus for your platform. Windows and macOS users can also choose Clash Verge Rev, FlClash, or Clash Nyanpasu based on interface preferences. For service mode, configuration overrides, and detailed TUN controls, compare Clash Verge Rev; for a similar workflow across operating systems, consider FlClash.

Should I choose Apple Silicon or Intel for macOS?

Open About This Mac from the Apple menu. If Chip shows Apple M1, M2, M3, M4, or a later Apple processor, choose Apple Silicon or ARM64. If Processor shows Intel, choose Intel or x64. A native build usually reduces compatibility-layer dependencies and lets the client core run under the correct architecture.

What is the difference between Android ARM64, ARM, and universal builds?

Recent Android phones and tablets usually use 64-bit ARM processors, corresponding to ARM64-v8a. Older 32-bit devices use armeabi-v7a or ARM. Universal builds include multiple architectures, so they are larger but more convenient when the device architecture is unknown. Some emulators and specialized devices may require x86_64.

Why can’t I connect immediately after installation?

The client manages configurations and traffic interception, but the installer does not include a working subscription. Import the complete URL from the subscription or configuration page, wait for the update to finish, then choose a proxy group and mode. Desktop systems also need the system proxy or TUN enabled; mobile devices require approval of the system VPN request.

Do regular users need to download the Mihomo core separately?

Usually not. The graphical clients above already include or manage the core required to run, along with subscription updates, proxy switching, and log viewing. Standalone Mihomo files are mainly for servers, software routers, containers, automation scripts, or command-line environments where configurations are maintained manually.