OPTICS LAB / PACKAGE INDEX

Clash Downloads and Platform Installers

Identify your operating system and processor architecture first, then choose a GUI client or the Mihomo core. Downloads are organized by maintenance status, file format, and use case. Version details appear only when valid manifest data is available.

Choose an operating system View Mihomo core
  • Five operating-system options
  • Architecture and format guide
  • Archived client labels
CHECKPOINT 00

Check three details before downloading

Packages for the same operating system are not necessarily interchangeable. Processor architecture, file format, and maintenance status directly affect installation.

  1. 01

    Verify the operating system and architecture

    Windows and Linux systems commonly use AMD64 or x64. Apple M-series chips use ARM64, while Android devices typically use arm64-v8a. If unsure, check the system information instead of judging by the device's appearance.

  2. 02

    Distinguish clients from the core

    GUI clients include interfaces for importing configurations, switching policies, controlling the system proxy, and viewing logs, making them suitable for personal devices. Mihomo is the core executable and requires you to provide the configuration file, startup method, and service management.

  3. 03

    Check the maintenance status

    Projects marked “Discontinued” are retained for archival use and migration of older configurations. On a new device, choose a maintained client that supports current system permissions and network interfaces.

LAB RECORD 01

Choose a client by operating system

After switching platforms, review the system requirements before choosing a client from the current panel. Different clients can use the same types of Clash configuration, but interface labels, permission settings, and core update methods may differ.

PLATFORM / WINDOWS

Windows GUI Clients

Most desktop installations use 64-bit Windows. Installers suit the standard setup process, while archives are intended for users who need to manage the program directory manually. If Windows requests network access on first launch, allow the client to access the required networks.

Check Recommendation
System 64-bit Windows 10 or Windows 11
Architecture x64 / AMD64
Permissions Installation, system proxy, or TUN features may require administrator approval

Clash Plus

A GUI client for everyday desktop use, with configuration management, policy switching, and system proxy controls.

Clash Plus
Top pick Actively maintained
Download Windows installer

Clash Verge Rev

A desktop GUI client for Windows users who need rule mode, TUN, and configuration-file management.

Clash Verge Rev
Recommended
Download x64 installer

FlClash

A cross-platform GUI client. On Windows, use the standard installer or download the archive to manage the program directory yourself.

FlClash
Download installer Download ZIP

Clash Nyanpasu

Provides desktop interfaces for configuration, proxy modes, and connection details, suitable for users who prefer a standalone desktop experience.

Clash Nyanpasu
Download x64 installer

Clash for Windows

An archived client for restoring older environments or migrating configurations. For a new installation, compare the currently maintained Windows clients first.

Discontinued Archived
Download archived installer
LAB RECORD 02

Mihomo Core Architecture Table

The Mihomo core is intended for servers, routers, gateway devices, and manually managed services. For ordinary desktops and mobile devices, use one of the GUI clients above to manage the system proxy, subscriptions, policy groups, and logs.

System Processor architecture Format Intended use Download
Windows AMD64 ZIP Common 64-bit Windows servers or command-line environments Download
Windows ARM64 ZIP Windows on ARM devices Download
macOS Intel x64 GZ Command-line deployment on an Intel-based Mac Download
macOS Apple Silicon GZ Command-line deployment on an Apple M-series Mac Download
Linux AMD64 DEB 64-bit devices using the Debian package system Download
Linux AMD64 GZ Generic compressed core; configure the working directory manually Download
Linux ARM64 GZ 64-bit ARM servers, development boards, and routing devices Download
Linux ARMv7 GZ Some 32-bit ARMv7 routers and development boards Download
Linux MIPS softfloat GZ Routing devices in soft-float MIPS environments Download
CORE / CONFIG

Configuration file location

The command-line core reads a YAML configuration. Before deployment, define the configuration path, data directory, and log output location so the service can find its configuration and write to the required directories.

CORE / SERVICE

Service management

For continuous operation, use the operating system's service manager and specify the service user, working directory, and restart policy. After changing the configuration, run the core once in the foreground and observe it before returning control to the service manager.

LAB RECORD 03

Complete the initial setup in order

Installing the client is only the preparation stage. On first launch, complete configuration import, policy selection, system network integration, and connection verification in sequence.

01

Launch the client and approve system permissions

On first launch, a desktop client may request network access, background operation, or administrator privileges; a mobile client will request permission to create a VPN configuration. Grant the permissions required by the features you plan to use. If TUN is not needed yet, verify basic connectivity with the system proxy first.

If macOS blocks the app on first launch, approve it through the security settings provided by the system. If a Linux GUI client does not start after installation, run it once from a terminal and review any dependency or permission messages.

OBSERVE / PERMISSION
  • The app opens to its main interface normally
  • The system proxy or VPN control is available
  • The log does not show continuously repeated startup errors
02

Import a subscription or local configuration

Paste a working subscription URL on the configuration or subscription page, or select a local YAML file. After the import completes, set the new entry as the active configuration. Its presence in the list does not mean it is enabled.

If no nodes or policy groups appear, check for download errors and confirm that the imported content uses a configuration format recognized by Clash or Mihomo. Do not repeatedly toggle the system proxy to hide a problem in the configuration itself.

OBSERVE / PROFILE
  • A new entry appears in the configuration list
  • The target entry is now the active configuration
  • The corresponding policy groups appear on the proxy or policy page
03

Choose the mode and system network interface

When getting started, use rule mode so each connection is routed directly or through a proxy according to the configuration rules. Global mode sends more connections through one proxy policy, while direct mode bypasses proxy rules. Neither should be used as an ambiguous long-term troubleshooting switch.

On desktop systems, enable the system proxy first. If you need to capture traffic from more applications, review the client's TUN permissions and DNS settings. Mobile clients route device traffic through the system VPN interface.

OBSERVE / ROUTE
  • The active mode matches the configuration's intended behavior
  • Each policy group has a specific node or automatic policy selected
  • At least one of system proxy, TUN, or VPN is enabled
04

Use logs to verify rule matches

After connecting, open a specific test destination while watching the connections or logs page. A useful test confirms the target domain, matched rule, final policy, and selected node—not merely whether a client toggle changed color.

If the destination is unreachable, first determine whether the connection entered the client, then isolate DNS, rule, node, and system proxy issues. Change only one variable at a time and retest so you can identify which change had an effect.

OBSERVE / LOG
  • The target connection appears in the log or connection list
  • The matched rule is the expected one
  • There are no connection loops, resolution failures, or permission errors
View the basic configuration guide Read the complete cross-platform installation guide
LAB RECORD 04

Download and Installation FAQ

These questions cover package formats, processor architectures, and initial setup. When troubleshooting a connection, check the client installation, configuration validity, and system network interface separately.

Should I choose a GUI client or the Mihomo core?

For everyday desktop and mobile use, choose a GUI client. It provides interfaces for subscription imports, policy groups, the system proxy, TUN or VPN permissions, and logs, making it easier to complete setup through the UI.

The Mihomo core is better suited to servers, routers, gateway devices, and automated deployments. It requires manual management of the YAML configuration, startup arguments, service permissions, and update process. If you only want to import a subscription and switch nodes on a personal computer, there is no need to start with the command-line core.

Should I download the EXE or ZIP for Windows?

For a standard installation, choose the EXE installer. It places program files and creates launch entries using the client's predefined setup process. A ZIP must be extracted manually to a stable directory; moving or deleting that directory can prevent the client from launching later, so this format is better suited to users familiar with manual directory management.

Whichever format you choose, verify the client name and processor architecture first. Do not overwrite one client's directory with configuration files from an older client; import them or follow the documented migration process instead.

Should I choose Apple Silicon or Intel for macOS?

Choose Apple Silicon or ARM64 for a Mac with an M-series chip. Choose Intel or x64 for an older model listed as having an Intel processor. You can check the Chip field in About This Mac or System Information.

Choosing the wrong architecture may prevent the app from opening or make it depend on a compatibility translation layer. Using the installer that matches the processor usually avoids startup issues caused by an extra compatibility layer.

What is the difference between arm64, arm, and universal on Android?

arm64-v8a is used by most recent 64-bit Android phones and tablets. armeabi-v7a targets some older 32-bit ARM devices. A universal package supports more architectures but is usually larger.

If the device settings do not show the architecture, look up the processor specifications or choose universal when the client provides it. An installation failure is not always caused by architecture; also check the Android version, available storage, and installation permissions.

What should I do if there is still no internet access after importing a configuration?

First verify that the new configuration is active, not merely downloaded. Then open the policy groups and select a specific node or automatic policy. Finally, check that the system proxy, TUN, or mobile VPN is enabled.

Keep the connection log open and request a specific domain. If no connection appears in the log, focus on the system network interface. If a connection appears but reports resolution or handshake errors, check DNS, node status, and configuration rules. Following this order avoids changing multiple settings at once.

Can I keep using a discontinued client?

An archived client may still run on some older systems and can help read or migrate old configurations. However, system network interfaces, certificate requirements, core behavior, and subscription formats continue to change, and a discontinued client will not receive ongoing compatibility fixes.

For a new installation, choose a client that is still maintained. Before migrating, record the subscription sources, policy group selections, and custom rules, then keep a restorable copy of the configuration. Remove the old environment only after confirming that the new client connects correctly.