Profiles and subscriptions
Add configuration from remote subscription links or local files, keep the intended profile active, and refresh remote sources when they change.
ClashMeta / Mihomo · Flutter · Android · Windows · macOS · Linux
FlClash is an open-source, ad-free proxy client built with Flutter and based on ClashMeta (Mihomo). It brings profiles, proxy groups, rule-based routing, DNS controls, desktop System Proxy and TUN, Android VPN integration, connection monitoring and WebDAV data sync into one consistent interface.

FlClash is the user-facing control layer around Mihomo. It keeps profile sources, proxy selection, routing rules, DNS, network entry methods and runtime status in one adaptive Flutter interface instead of treating every task as a raw YAML workflow.
Add configuration from remote subscription links or local files, keep the intended profile active, and refresh remote sources when they change.
Review nodes, strategy groups and routing behavior from the interface while Mihomo evaluates the final Rules and selects the configured outbound path.
On desktop, use System Proxy for apps that follow OS proxy settings or TUN when broader traffic capture is required.
Manage DNS-related options, Hosts, Fake-IP behavior and IPv6 settings together with the active profile and routing rules.
Inspect runtime connections, request activity, logs, traffic usage and network speed to understand how the current configuration is behaving.
Back up and synchronize FlClash application data through WebDAV so important client settings are easier to preserve across devices.
FlClash manages the interface, profiles and platform integration; Mihomo executes proxy connections, routing, DNS and TUN behavior; profiles, proxy groups and rules define the actual network policy.
The Flutter client provides the cross-platform UI, profile management, platform integration, runtime controls and data backup workflows.
Client layerThe core runtime processes proxy protocols, groups, Rules, DNS, connections and TUN behavior from the final configuration.
Core runtimeRemote subscriptions and local files provide the base configuration source that FlClash prepares for Mihomo.
Config sourceGroups organize available outbounds, while Rules decide which policy, DIRECT path or other action handles matching traffic.
Routing policyDNS options work alongside routing, while System Proxy, Android VPN and TUN determine how device traffic reaches the core.
Network layerWebDAV can be used to back up and synchronize FlClash application data independently of the current installation.
Backup & syncGetting Started
The setup path is consistent across platforms, but the final network entry method differs: desktop can use System Proxy or TUN, while Android uses the operating system VPN interface.
Choose the Android, Windows, macOS or Linux build that matches your device and CPU architecture, then confirm the client starts normally.
Import a subscription link or local configuration file, update it successfully, and make sure the intended profile is active.
Review proxy groups and select the policy you need, then use Rule, Global or Direct mode according to the active configuration and test goal.
Use System Proxy for standard desktop apps, Android VPN on mobile, or desktop TUN when broader traffic capture is required.
FlClash is useful when you want the same configuration model across Android and desktop instead of maintaining unrelated proxy workflows on each device.
Use FlClash to keep profile sources, proxy groups, routing choices and network controls visible in the same client while Mihomo handles the underlying traffic.
Use connection lists, request records, logs, traffic usage and network speed to check whether traffic is reaching Mihomo and which part of the configuration needs attention.
Preserve FlClash application data through WebDAV so important settings are easier to restore or carry between supported devices.
Architecture
FlClash is the client interface, Mihomo is the execution core, profiles and rules define policy, and the operating system provides the network environment.
| Layer | FlClash | Mihomo | Profiles / Rules | Operating System |
|---|---|---|---|---|
| Primary role | Cross-platform GUI and controls | Proxy and routing core | Configuration and policy | Runtime environment |
| Platform scope | Android / Windows / macOS / Linux | Runs with the client build | Portable configuration model | Android / Windows / macOS / Linux |
| Visual management | Profiles, proxies, rules and status | Exposes core state and behavior | Defines nodes, groups and Rules | Provides native permissions and UI integration |
| Traffic entry | System Proxy / VPN / TUN controls | Processes accepted traffic | Stores related network options | Provides proxy, VPN or virtual interface APIs |
| Profile handling | Import, update, activate and override | Loads the final generated config | Remote source or local file | Stores files and app data |
| Runtime diagnostics | Connections / Requests / Logs | Tracks connections and traffic | Explains intended routing policy | Supplies network state and permissions |
| Project boundary | Open-source proxy client | Open-source proxy core | Not a proxy service | Not a subscription or node provider |
FAQ
These answers define what FlClash is, how it relates to Mihomo, which platforms it supports, and where profiles, rules, TUN and WebDAV fit.
FlClash is an open-source, ad-free multi-platform proxy client based on ClashMeta (Mihomo). It is built with Flutter and supports Android, Windows, macOS and Linux.
FlClash is the user-facing client and platform integration layer. Mihomo is the core runtime that executes proxy connections, Rules, DNS, proxy groups and TUN behavior.
The official project supports Android, Windows, macOS and Linux. Package formats and CPU architectures vary by platform and release.
No. FlClash is a client application. It does not itself provide proxy nodes, subscription plans or network service; those come from the configuration sources you choose to use.
System Proxy changes desktop OS proxy settings for apps that follow them. Android uses the operating system VPN interface. Desktop TUN uses a virtual network interface to capture a broader range of traffic.
A Profile is a configuration source managed by FlClash. It can come from a remote subscription link or a local configuration file and is prepared into the final configuration that Mihomo loads.
Override keeps local changes separate from the base profile. Standard Override handles structured settings and added rules, while Override Script allows more flexible configuration transformations.
Yes. The project explicitly supports data synchronization through WebDAV, which can help preserve FlClash application data across supported devices.
Explore FlClash
Use the download page for Android, Windows, macOS and Linux builds, then continue with the configuration guide for profiles, routing modes, System Proxy, Android VPN and TUN.