Clients / Installers / Core

Clash Downloads
Platforms and Architectures

Choose your operating system, then select a package. Use a graphical client for everyday configuration; use the Mihomo core for self-managed deployments.

Clash Plus is featured first in the Windows, macOS, Android, and iOS sections. Clash Verge Rev leads the Linux section. Client downloads are listed separately from configuration instructions; after installation, continue with the setup guide.

Choose the interface, core, and configuration separately.

Being part of the Clash ecosystem doesn't mean every client has the same features. The client handles the interface; the core handles connections. The core must also support the protocols and rules in your subscription. Check your device architecture before choosing, and keep your original configuration before migrating.

Client Downloads

Windows Clients

Current desktop downloads are primarily x64 builds. Check your system type under Settings → System → About to distinguish processor architecture from OS bitness. On ARM devices, first confirm compatibility support; an x64 installer is not a native ARM build.

Clash Plus

Clash Plus

Featured

Windows graphical client. After installation, import a subscription, then choose a policy and traffic-routing method.

Download Clash Plus · x64
PACKAGE
EXE installer
ARCH
x64

Manage subscriptions and connection settings through a graphical interface. On first launch, check the configuration list and confirm the import succeeded before enabling the system proxy. TUN changes virtual network adapters and routing, so configure it separately after basic connectivity works. Official site: clashplus.io.

Clash Verge Rev

Clash Verge Rev

Windows

A desktop configuration manager for users who need to switch subscriptions, review rules, and manage services.

Download Clash Verge Rev · x64
PACKAGE
EXE installer
ARCH
x64

Handle features that require service permissions separately from the standard system proxy. First confirm the configuration loads, then check that the service is running. If a port is already in use, close the old client to avoid two processes competing for the same port or default route.

FlClash

FlClash

Windows

Installer and ZIP downloads are available. For everyday desktop use, choose the installer.

Download FlClash · Installer Download ZIP · AMD64
PACKAGE
EXE / ZIP
ARCH
AMD64

Extract the ZIP to a writable folder before running the program; don't launch it from an archive preview. Before updating, note the actual data directory. It may differ from the extracted program folder, and deleting the program files may not remove existing settings.

Clash Nyanpasu

Clash Nyanpasu

Windows

Another option for desktop configuration management. Check configuration merge and override settings when migrating.

Download Clash Nyanpasu · x64
PACKAGE
EXE installer
ARCH
x64

When migrating from another client, import the original subscription first, then restore custom rules one at a time. Distinguish between options shown in the interface and the configuration ultimately passed to the core. When troubleshooting rule issues, check the active configuration, not just the subscription source file.

Clash for Windows

Discontinued

Archived releases for reproducing legacy environments and reference during migration. For new deployments, choose one of the clients listed above.

Download Clash for Windows · Archive
STATUS
Archived software
PACKAGE
EXE installer

With development discontinued, don't expect compatibility with current systems or core features. Older versions may not support newer protocol fields. Save your subscriptions, rules, and scripts before migrating. Once you've verified the new client, remove the old app's startup entry and system proxy settings.

Windows Requirements

CheckWhat to look forAfter installation
Windows versionUse a Windows version that is still supported by Microsoft. Check each client's release notes for its minimum version.Once the app opens normally, import your configuration and save any specific installation error messages.
Architecture and permissionsPackages in this section are primarily x64. TUN or service installation may require administrator privileges.Test the system proxy first. Install services only if needed, and avoid running multiple traffic-interception tools at once.

Installation and Migration Checklist

A successful installation doesn't mean the connection is configured.

Establish one connection you can verify

After opening the client, find the configuration or subscription manager and import a URL or file from a trusted source. Confirm the download completed and the configuration is enabled, then choose a route in the policy group. For your first setup, start with rule mode, enable the system proxy, and test your browser. If the browser works but other apps don't, check whether those apps follow the system proxy before setting up TUN.

Keep your original configuration when migrating

Before switching clients, export subscription details, local rules, overrides, and scripts. The original subscription, the runtime configuration generated by the client, and preferences saved in the interface are three different kinds of data; copying a single YAML file may not restore the whole setup. Restore the original subscription first to establish a basic connection, then add custom changes one at a time to pinpoint any issue.

Recheck traffic routing after updates

App or core updates can change defaults, service status, and configuration compatibility. After updating, check the system proxy, listening address, selected policy, and DNS, then test your usual apps. The desktop proxy toggle may not cover every process, and TUN needs the right routing and DNS settings. For platform-specific permissions and steps, see the cross-platform guide.

Download and Installation FAQs

Should I download a client or the Mihomo core for my first setup?

Desktop and mobile users should start with a client that has a graphical interface for importing configurations, choosing policies, and viewing logs. The Mihomo core is intended mainly for servers, routers, and users who manage startup options themselves; it does not include a full desktop interface.

Which should I choose: ARM64, x64, or a universal package?

Check your processor and operating system architecture in system information. x64 and AMD64 usually refer to the same 64-bit architecture; ARM64 is for compatible ARM devices. If you can't confirm your Android architecture, choose the universal package. An architecture option in a download list does not always mean there's a separate build, so check the actual filename and project release notes.

What else do I need after downloading a client?

You'll need a valid subscription URL or configuration file from a trusted source. The installer itself does not provide proxy service. After importing, make sure the configuration is enabled and a policy group is selected, then enable the system proxy or set up TUN if needed. Subscription URLs may contain credentials, so don't share them publicly.

Can I still use my old configuration now that Clash for Windows is discontinued?

Some basic settings can be moved to another client, but check protocol support, rule fields, DNS settings, and local paths one by one. Clash for Windows and ClashX Meta are listed here as archived downloads. Back up your configuration before migrating, and avoid enabling system proxy or TUN in two clients at once.

Why can't my browser connect even though the client is installed?

First make sure you've imported a subscription and selected an available policy. Then check the system proxy, listening port, and proxy mode. Installing the app alone does not provide proxy service. If TUN is enabled, also check service permissions, routing, and DNS. Change one setting at a time, and don't run multiple VPN or proxy clients simultaneously.

Will updating the client overwrite my subscription or custom rules?

Whether an update preserves your data depends on the client, installation method, and data directory. Before updating, export your configuration and note your subscription source, local rules, and overrides. Refreshing a subscription may overwrite manual changes to remote configuration; keep long-term customizations in a supported override or merge configuration.