Open-source Clash client · Powered by mihomo
A cross-platform Clash client: use one compatible subscription on desktop and mobile. FlClash includes subscription management, rule-based routing, and TUN mode.
Start by identifying your operating system, then check your processor architecture. FlClash offers desktop and Android clients; iOS requires a separate compatible client. Whether you can reuse a subscription depends on its format, protocol support, and your provider’s device limits. A similar interface does not mean every setting can be transferred as-is.
A good fit for everyday desktop use. Choose from clients such as FlClash, Clash Plus, and Clash Verge Rev. Check your processor type in system settings before downloading. On first launch, import a profile and enable the system proxy to test your browser connection. If you need to route traffic from more apps, follow the TUN setup guide and grant the required permissions.
Download →Choose the package for your Apple Silicon or Intel Mac; check your chip in About This Mac. After installation, grant any network permissions requested by macOS. Before switching clients, quit your existing proxy app so the system proxy does not point to a closed process.
Download →Choose a client such as FlClash or Clash Meta for Android, and make sure the package architecture matches your device. On first connection, approve the system VPN request. For a persistent background connection, check battery optimization and background activity permissions. Per-app proxy settings affect only selected apps; they do not replace domain rules in your profile.
Download →On iPhone or iPad, use the download page to open the Clash Plus App Store listing. Its official website is clashplus.io. Before importing, make sure your subscription supports the client, then allow it to add a VPN configuration on first launch. Desktop file paths and system proxy options cannot be transferred directly to mobile.
Download →On desktop Linux, choose Clash Verge Rev or FlClash and select a package that matches your distribution. Whether the system proxy works depends on your desktop environment and the app. Servers and routers are usually better suited to running the mihomo core directly. TUN requires network permissions; review your routing and DNS settings before enabling it.
Download →The downloads page lists available clients, package architectures, and system requirements. Keep your existing profile before switching clients. Updating a subscription and updating an app are separate tasks.
View all clients →Follow a request from profile setup to its outbound route, and see what the client handles versus the core.
FlClash manages subscription links and local profiles together on the Profiles page. Add a link, download its contents, then select the profile you want to use. The auto-update interval controls when the client fetches the subscription again; it is separate from app updates. You can save multiple profiles, but check that your proxy group selections still work when switching between them. A subscription refresh may overwrite rules in a remote profile, so save long-term customizations using a method supported by the client. Unlike a static file imported just once, subscription management makes it easier to receive ongoing node and rule changes from your provider. The subscription source remains responsible for keeping the link valid.
See how to import a subscription →In rule mode, requests are checked in sequence against domains, destination addresses, or rule sets. The first match sends the request to a direct policy or proxy group. Unlike global mode, rule mode preserves routing decisions based on the destination instead of sending every request through one global group. FlClash provides the interface for selecting policies; the active profile supplies the rules. To troubleshoot a particular site, check the matched rule in the connection log before changing rule order. Entries placed after a catch-all rule will not take effect. Proxy group names must match those referenced by rules, so check references before renaming a group to avoid profile load errors.
Learn rule syntax and matching order →TUN routes traffic that meets the routing conditions through a virtual network interface to the core, making it useful for apps that ignore system proxy settings. The system proxy instead provides a proxy address to apps that support it, so the two methods cover different traffic. Before enabling TUN, verify your profile and nodes with the regular proxy, then check administrator permissions, the virtual interface, and DNS settings. TUN does not affect whether a subscription is valid, and results can vary by network. If the device also runs another VPN, virtual machine networking, or security software, test compatibility one item at a time and keep a clear way to restore network access by turning TUN off.
Review connections and permissions →The Clash ecosystem includes different cores and clients, so profile compatibility needs to be checked on its own. FlClash is based on mihomo and supports the protocols and rules available in that core. The multi-core compatibility section compares formats across the ecosystem; it does not mean FlClash can switch freely between every core. When migrating an older Clash profile, common rules may still work, but check whether the core supports newer protocols, DNS fields, and rule-set options. A subscription containing only nodes also needs proxy groups and rules. First confirm the format provided by your service, then check which core the target client uses; this is more reliable than judging by the client name alone.
Check protocol and core compatibility →FlClash uses Flutter for a cross-platform interface, with similar workflows for profiles, proxies, and logs on desktop and Android. You can import the same compatible subscription on both, but local switches, file paths, and system permissions still need to be set for each device; using one link does not sync them automatically. Mobile connections use the system VPN interface, while desktop setups distinguish between the system proxy and TUN. For iOS, use another client listed on the downloads page. When moving to a new device, check your subscription’s simultaneous connection limit, then review proxy group selections, DNS, and background permissions so device-specific differences are not mistaken for a node issue.
See clients available for each platform →For your first setup, get one verifiable connection working before adding custom rules or expanding traffic capture. These three steps are for users who already have a compatible subscription. The client loads the profile; the subscription provider is responsible for node and service availability.
Install a client that matches your operating system and processor architecture. Open the Profiles page, add your subscription link, and save it. Once the download completes, select the profile and check that proxy groups appear on the Proxies page. If you received a single-node link, first confirm the client supports importing it directly. Pasting an ordinary webpage URL into the subscription field usually will not produce a usable profile.
Give profiles names that make their purpose clear, and store subscription links somewhere secure. Access tokens in a link may be tied to your account, so redact them before sharing logs or screenshots. If import fails, check that the address is complete and the subscription has not expired, then confirm the format with your provider. Reinstalling the client repeatedly is unlikely to help.
Select rule mode on the dashboard, then choose an available outbound option for the required proxy group on the Proxies page. Rule mode preserves the profile’s existing split between direct and proxied traffic. Global mode can help with a brief comparison or troubleshooting, but it does not rewrite the profile’s rules. After changing modes, make a new request to test the result; existing connections may not switch routes immediately.
On desktop, start by enabling the system proxy. On mobile, allow the VPN configuration when prompted by the system. Enable TUN separately only if needed, and check its permissions. Avoid changing the mode, DNS, and traffic capture method all at once; otherwise, it is hard to tell which setting affected the connection.
After connecting, visit a specific destination and check the connection log or records for its domain, matched rule, and outbound policy. Opening a page in the browser is only a first check; also confirm that the apps you want to proxy are being captured. If only one or two apps have problems, check their own proxy settings and whether they still point to an old port.
For timeouts, troubleshoot in this order: local network, subscription validity, traffic capture status, DNS, and node. Change one setting at a time and retest, noting which combination restores the connection. Once everything works, enable automatic subscription updates. If a later update fails, you will still have a known-good profile to compare against.
The client interface, proxy core, and subscription each have different roles. Understanding how these three layers fit together helps you choose what to download, know what to update, and find the right place to start troubleshooting. This site provides downloads and guides; refer to the corresponding open-source repositories for code and release history.
FlClash is an open-source client built with Flutter and mihomo. Flutter provides the foundation for its cross-platform interface, while mihomo handles proxy protocols, DNS, and rules. FlClash is part of the Clash configuration ecosystem; it is not a single app that combines every legacy Clash client. Different clients may use similar configuration syntax while differing in system integration and maintenance schedules.
To check a project’s status, review its repository release notes, commit history, and issue discussions. Release notes are the best place to see whether an update affects a feature you use; issue discussions can add reproduction details for specific system environments. Public records let you trace changes—they are more informative than using a star count to predict stability on every device.
FlClash organizes profile management, proxy selection, and log viewing into an interface you can use. How requests match rules and which protocol establishes a connection depend on the core and active profile. A switch in the interface does not guarantee that your service’s nodes support the corresponding feature. Likewise, core support for a protocol is not enough without complete, correct node parameters.
mihomo continues the technical direction of Clash Meta and keeps expanding its protocol and rule capabilities. Original Clash, Meta, and mihomo often appear together in subscription documentation; treat them as compatibility details to verify when choosing a client. For more on protocol trade-offs, resource usage, and mobile use cases, see the protocol guide.
An app update replaces the client program and may include interface fixes, system compatibility changes, or a different bundled core. A subscription update fetches profile content again, mainly affecting nodes, proxy groups, and rules. They are not interchangeable: if a subscription URL has expired, updating the app usually cannot restore access. If a profile uses newer fields, refreshing the subscription will not make an old core recognize them.
Before updating, keep a working profile and any important local settings, and read the release notes relevant to your system. After updating, verify your existing connection before enabling new features. If a profile fails to load, use field or rule errors in the logs to find the cause. Do not delete the entire settings directory straight away; you could lose records needed to roll back.
Installing a client is only part of the setup; you still need a working profile. Subscriptions usually come from an existing service account or a self-hosted service. FlClash does not determine which nodes a subscription contains. When choosing a source, check the protocol format, device limits, update URL, and service documentation. Shared profiles from unknown sources may include DNS, routing, or remote rule settings that are unsuitable for your setup. Understand what they do before importing.
When reporting an issue, include your operating system, steps to reproduce, and redacted error logs. Never post subscription URLs, node passwords, access tokens, or account details in a public discussion. If you do not have a subscription yet, read the subscription source guide. To make sense of unfamiliar fields, use the quick glossary to distinguish nodes, policy groups, rule sets, and DNS.
If Git is installed, copy the command to clone the repository locally. Cloning the code is for reading or development, not installing the client. For everyday use, choose an installer from the downloads page.
Open the FlClash repository ↗
git clone https://github.com/chen08209/FlClash.gitStart with the specific symptom and narrow down the cause step by step. Before reading, note your active profile, outbound mode, and traffic capture method so you can compare them with the checks in the guide. After changing a setting, make a new connection request rather than judging a new rule by an existing connection.
Check each item in order: local network, subscription validity, system proxy and TUN status, DNS settings, then the node itself. This helps avoid wasting time switching nodes at random.
Read the troubleshooting steps →Learn the three-part structure of a rule, common rule types, top-to-bottom matching priority, the no-resolve option, and rule-set references—with examples of common mistakes.
Read the rule guide →Learn what GeoIP and GeoSite data files do, how to update them manually or on a schedule, and how to write GEOIP and GEOSITE rules in a profile.
Read the database guide →