FlClash Guide: The Cross-Platform mihomo GUI Client

FlClash is an open-source proxy client built with Flutter, with the mihomo core bundled inside it. Its selling point is consistency: the same app, the same layout and the same handful of switches on your phone, your Mac and your Linux desktop, all driven by the same subscription URL.

That makes it a natural pick if you move between devices and dislike relearning an interface each time. It is deliberately lean — fewer knobs than a desktop-first client like Clash Verge Rev — which is a feature for most people and a limitation for tinkerers.

This guide covers what FlClash is, which build to download for each platform, how to import a subscription, the day-to-day controls, and how it compares with Clash Verge Rev.

What FlClash actually is

FlClash is a graphical front end. The networking work is done by mihomo, the open-source core maintained by the MetaCubeX community, which is shipped inside the app — you never download or configure a core separately. Because it is written in Flutter, one codebase produces builds for Android and for desktop systems, which is why the interface looks the same everywhere instead of following each platform's native conventions.

Practically, that means FlClash reads standard Clash/mihomo YAML configurations, understands the same proxy groups and routing rules as every other client in this family, and can consume a subscription meant for Clash Verge Rev or Clash Meta for Android without modification. The project is developed in the open at github.com/chen08209/FlClash.

Which build do you need?

This site mirrors FlClash 0.8.94 in the formats below:

Platform	File	Which one to take
Android	APK	arm64 for any recent phone; armv7 only for older 32-bit devices
macOS	dmg	Intel build for Intel Macs, Apple Silicon build for M-series
Linux	deb / AppImage	deb on Debian and Ubuntu derivatives; AppImage anywhere else

All of these are in the download center. A Windows build exists as well, published on the project's GitHub releases page rather than mirrored here.

Running the AppImage on Linux

An AppImage is a self-contained file rather than an installed package — nothing is registered with your package manager. Mark it executable once, then run it:

chmod +x FlClash-*.AppImage
./FlClash-*.AppImage

Move it somewhere permanent (~/Applications is a common choice) before creating a launcher shortcut, since the path is baked into whatever shortcut you make. Deleting the file is the whole uninstall procedure.

Import a subscription and connect

Copy the subscription URL from your provider's dashboard, preferring the Clash/mihomo format when several are offered.
Open the profiles section in FlClash and use the add button.
Choose URL as the import type, paste the link, and save. FlClash downloads the configuration and lists it as a profile.
Tap or click the profile to activate it, then pick a server in the proxies view.
Start the connection. On Android, accept the system VPN prompt the first time; on desktop, enable the system proxy or TUN switch.

Wording differs slightly between releases and platforms, so follow the meaning rather than the exact labels. Import steps for the other mihomo clients are collected in the subscription import guide.

The controls you will actually use

Server selection. The proxies view lists the groups from your subscription. Choosing inside a group changes what every rule pointing at that group uses — you rarely need to touch more than the main selector.
Latency tests. Run them from the group view to see what is responsive right now, then pick from the fast ones. A single test result is a snapshot, not a verdict.
System proxy (desktop). Writes the local proxy into your OS network settings so cooperative applications use it — the light-touch option, explained in the system proxy article.
TUN / VPN mode. Captures traffic at the network layer instead, so applications that ignore proxy settings are covered too. On Android this is simply what starting the tunnel does; on desktop it needs elevated privileges.
Profile updates. Refresh manually when servers start timing out, or set an update interval so the configuration stays current by itself.

FlClash or Clash Verge Rev?

Both are open source, both embed mihomo, both accept the same subscriptions — so the decision is about fit, not capability. FlClash wins on breadth and simplicity: it is the only one of the two that also runs on Android, and its interface is uncluttered enough that a first-time user is not hunting through settings pages. Clash Verge Rev is desktop-first and exposes more: profile editing and merging, richer connection views, finer control over how the core is launched.

A reasonable split is FlClash on the phone and whichever you prefer on the desktop; nothing stops you from running both on different machines against one subscription. If you want the full field, including the non-Clash options, see the client comparison.

Frequently asked questions

Do I need to install mihomo separately?

No. The core is bundled inside FlClash, and the app manages starting and stopping it. Installing the standalone binary is only useful if you want to run the core yourself from a terminal.

Can I use the same subscription in FlClash and another client?

Yes — a subscription URL is just an address that returns a configuration file, and each client fetches it independently. Whether you may keep several devices connected at once is a matter of your provider's own terms, not the client's.

Is FlClash a VPN?

It uses the VPN interface on Android and TUN mode on desktop to capture traffic, but it is a proxy client: it routes connections according to your rules through servers you supply. It does not, by itself, make you anonymous.