Open-source ecosystem · Continuously updated clients for every platform

FlClash Download: Clash Clients and Configuration Guides for Every Platform

Download Clash View Guides

Find Windows, macOS, Android, iOS, and Linux clients in one place, then follow clear steps for subscription imports, rule-based routing, and DNS configuration.

Free forever Open source English documentation mihomo ecosystem
5 platforms covered GPL-3.0 open-source license mihomo core ecosystem
CLIENT / GUI CONFIG / YAML ROUTING / RULES DNS / FAKE-IP PLATFORM / 5
ENGINEERING REFERENCE

From Client Access to Rule Execution

The Clash client handles configuration management and system integration, while cores such as mihomo listen on ports, resolve DNS, match rules, and select proxy policies. The four key stages below follow a practical configuration workflow, explaining what each stage solves and where to find more detail.

RULE ENGINE

Rules are matched in order; proxy groups choose the exit

Rule-based routing answers one question: “Where should each connection go?” The rules section checks domains, IPs, processes, or rule sets from top to bottom, then sends a match to the specified proxy group. Put more specific rules first and fallback rules last to avoid common mismatches.

Unlike traditional proxy tools with a single on/off switch, the Clash ecosystem separates matching conditions from node selection. The same rules can be reused over time; when nodes change, update the subscription or adjust the proxy groups instead. For syntax details, see the rules section in the configuration reference.

config.yaml / rules
rules:
  - DOMAIN-SUFFIX,example.org,DIRECT
  - GEOIP,LAN,DIRECT
  - RULE-SET,work,Work
  - MATCH,Proxy
PLATFORM INDEX

Choose a Clash Client by Operating System

The download page lists available graphical clients, use cases, and system requirements by platform. It does not distribute installer files directly; it takes you to the section for your current device so you can compare client options.

Windows

Ideal for everyday desktop use. Choose a graphical client such as Clash Plus, Clash Verge Rev, FlClash, or Clash Nyanpasu, then configure the system proxy, startup behavior, and TUN interception as needed.

Go to Downloads

macOS

Supports both Apple Silicon and Intel devices. Check your processor architecture before choosing an installer, then follow the system prompts to grant app permissions and configure the network extension on first launch.

Go to Downloads

Android

Intercept app connections through the Android VPN interface. Common choices include Clash Plus, Clash Meta for Android, FlClash, and Surfboard. Before importing, confirm the subscription format and background-running permissions.

Go to Downloads

iOS

Install Clash Plus from the system store and use the system VPN configuration for interception. On mobile, also check on-demand connection, cellular data permissions, and background restrictions.

Go to Downloads

Linux

Graphical clients work well on desktops, while servers, routers, and lightweight environments are better suited to direct mihomo deployment. Before installation, distinguish the package format, processor architecture, and service permissions.

Go to Downloads
View all clients →
QUICK START

A Three-Step Path from Installation to Connection Testing

When using the client for the first time, there is no need to change complex rules immediately. Install the client, import a configuration, and verify a basic connection first. Once the main path works, handle DNS, TUN, local network access, or overrides. This makes each problem easier to isolate.

View the Full Guide →
  1. 01

    Install the Client for Your Platform

    Open the download page and choose your operating system and processor architecture. Complete the permission setup requested by the desktop OS, or approve VPN configuration access on mobile. After the first launch, keep the default port and basic options.

  2. 02

    Import a Subscription or YAML File

    Paste the subscription URL on the configuration page or load a YAML file from local storage. After refreshing, check that the configuration parsed successfully and that the proxy page shows proxy groups and available nodes.

  3. 03

    Choose a Policy and Verify Routing

    Select the primary proxy group first, then enable the system proxy or mobile VPN. Test both direct and proxied destinations, and check the logs for matched rules to confirm that traffic exits as expected.

OPEN SOURCE CONTEXT

Understand the Boundaries Between Client, Core, and Configuration

The Clash ecosystem consists of multiple independent projects. To decide whether a client fits your device, look beyond its interface name and confirm its core, supported configuration fields, system integration method, and maintenance status.

Project Evolution

Clash established a rule-driven proxy configuration model: nodes handle connections, proxy groups handle selection, and rules handle routing. The community later developed desktop clients, mobile clients, and derived cores around this model. Although today’s clients look different, they still expose similar structures for configuration, proxies, connections, and logs.

Open-Source Ecosystem

Different clients are usually maintained by different teams, so release schedules and platform support vary. This site organizes download links, client comparisons, terminology, and configuration documentation separately to avoid treating “Clash,” “mihomo,” and a specific graphical client as one project. Choose based on platform compatibility and actual feature requirements.

Core Relationships

Graphical clients mainly handle configuration management, system proxies, tray menus, log viewing, and update entry points. Cores such as mihomo handle protocol connections, DNS, rule matching, proxy groups, and traffic forwarding. If a configuration field is not recognized, check both the core used by the client and its supported syntax instead of reinstalling only the interface.

Update Mechanisms

Client updates, core updates, subscription refreshes, and GeoIP or GeoSite data updates follow four separate paths. Upgrading a client does not necessarily change subscription content, and refreshing a subscription does not automatically fix local overrides. Keep a configuration that loads correctly and record where you make changes so you can identify differences quickly after an update.

COMMON CHECKS

Common Questions Before Getting Started

What if no proxy groups appear after importing a subscription?

First check the refresh result and parsing errors in the logs, then confirm that the subscription contains proxy-groups. If it includes nodes but no proxy group definitions, the client will not automatically create a complete routing structure. See installation and configuration issues for more solutions.

Should I use the system proxy or TUN?

For initial testing, start with the system proxy because it is simpler and easier to observe. Use TUN when you need to intercept applications that ignore system proxy settings, after reviewing its routing, DNS, and permission requirements. Compare the related concepts in the glossary.

What if the destination is still unreachable after switching nodes?

Check whether the proxy group actually selected that node, which rule matched the request, whether DNS returned the expected result, and whether the system proxy or VPN is still enabled. Avoid changing several components at once, or it will be difficult to identify the real cause.

What should I prepare before editing YAML?

Keep a copy of the configuration that currently loads correctly, use spaces for indentation, and avoid Tab characters. Change one logical block at a time, run a configuration check after saving, and only then enable the new configuration. Look up field details in the configuration reference.

View all FAQs →
LATEST NOTES

Recent Clash Configuration and Troubleshooting Articles

These articles cover client interfaces, YAML structure, and DNS troubleshooting. Each focuses on one specific topic, making it easy to consult after completing the basic installation.

View all articles →