FlClashX is an open-source client from the Clash family: a fork of the FlClash project running on the mihomo core. Like any client in that family, it takes not an individual server but a profile — a configuration that already contains every location, the selection groups, and the routing rules.
This article is about the client itself: which builds exist, how to add a profile from a subscription link, what it does better than the alternatives, and what its single but hard limitation is. The step-by-step guide specific to RuSolv lives in the documentation; this piece is about the app in general.
What FlClashX is
Clash is not a protocol — it is a configuration format and a family of clients that read it. Such a config describes proxies (in our case VLESS + Reality nodes), groups for switching between them, and a list of rules: which traffic goes into the tunnel and which goes straight out.
FlClashX is one implementation, a fork of FlClash running on the mihomo core. For a user that means a familiar interface with "Profiles" and "Proxies" tabs, and full control over the rules if you want it.
The key property of the format: routing rules in a Clash config are global — they apply to the whole profile, not to an individual server entry. That single detail is why FlClashX behaves differently from the other two popular clients.
Which devices FlClashX runs on
The app is distributed only through its GitHub releases page — it has no app-store presence. Release v0.4.2, dated 18 July 2026, contains 14 builds (each with a checksum file alongside):
- Android — universal, arm64-v8a, armeabi-v7a, x86_64
- Windows — x64 and ARM64, installer and portable zip
- macOS — Apple Silicon and Intel
- Linux — AppImage, deb, rpm; deb also for ARM64
- iPhone, iPad — not a single build
Note two things short guides usually skip: Windows has a separate ARM64 build, and Linux ships ordinary deb and rpm packages alongside the AppImage. There is no need to run an AppImage on a system that handles packages.
No version for iPhone or iPad exists
This is not "it is missing from the Russian store" or "it is hard to find" — a build for iOS and iPadOS does not exist at all. In that same v0.4.2 release, not one of the 14 builds targets iOS, and the app is absent from the App Store too, Russian and American storefronts alike. The project simply does not publish such a version.
The practical consequence is simple: if the device to connect is an iPhone or iPad, FlClashX is out at the first step. That leaves Happ and Hiddify — and with a Russian Apple ID, only Happ, because Hiddify is absent from the Russian App Store. On everything else — Android, Windows, macOS, Linux — FlClashX is available with no regional caveats, precisely because it is not distributed through app stores at all.
Step 1. Download a build
Take the file for your system and architecture from the project's releases page. On macOS that is a choice between the Apple Silicon and the Intel build, on Windows between x64 and ARM64; on Android the universal APK is enough if you would rather not think about it.
Check which repository you are downloading from. FlClashX is a fork, and the original FlClash project exists separately with releases of its own. These are two different apps with very similar names.
Step 2. Add a profile
FlClashX has no one-tap import: the app registers no URL scheme of its own, so the subscription address is pasted by hand or read from a QR code. The order is:
- Open the "Profiles" tab.
- Tap "+" and choose adding a profile by URL.
- Paste the subscription link from the service's dashboard — or scan the QR code.
- Wait for the download: the app fetches the config and shows the profile in the list.
- Select that profile if it was not selected automatically.
From then on the profile updates without your involvement — the client periodically reloads it from the same link, so new locations turn up on their own.
Step 3. Pick a location and turn on the VPN
Go to the proxies tab, choose the location you want from the list, and switch on the system VPN. On first launch the system asks permission to create a VPN profile — on Android that is a separate dialog; on desktop systems the app may need elevated rights for TUN mode.
Check the result the same way you would with any other client: has the external IP address changed, do the sites you need open, has latency stayed within reason.
Routing rules apply to everything at once
This is where FlClashX beats the other two clients, and it is worth understanding why.
When a service wants part of your traffic to skip the tunnel — the typical example being Russian resources such as Yandex, VK, or Gosuslugi staying on the direct connection — it describes that as a list of rules. In a Clash config that list is global: it applies to the whole profile. So FlClashX applies the rules it is sent immediately and with no configuration. Nothing to pick, enable, or write in.
For comparison: in Happ routing is attached to a specific location entry, so split tunnelling exists there as a separate entry marked "(Whitelist)" that you have to choose by hand. And Hiddify discards the rules from the subscription entirely.
Split tunnelling depends not only on the client but on whether the service enabled it at all. In a Clash config it is all or nothing: either the rules are in the profile or they are not, and switching locations inside the app changes nothing. If Russian sites go through the tunnel, the rules are not in the profile — that is a question for the service.
Common problems
The profile will not load
Check that the subscription link is current and the plan has not expired. If you re-issued the link in your dashboard, the previous one stops working immediately: delete the old profile and add the new one.
The app says it cannot parse the profile
A profile-parsing error usually means what came back from the link was not a Clash config but something else — a plain list of vless:// links, for instance. Clash-family clients do not understand that response. The format is chosen by the server from the User-Agent header, so this is fixed on the service's side, not in the app's settings.
A link from Happ will not open
An address of the form happ://crypt5/... is Happ's own encrypted format, and no other client can read it. What you need is an ordinary subscription address beginning with https://. Re-issue the link in your dashboard.
The locations look out of date
Refresh the profile on the "Profiles" tab by hand — that works faster than waiting for the next automatic update.
FlClashX, Happ, or Hiddify
- FlClashX applies routing rules to the whole profile with no configuration; builds exist for four systems, including ARM64 and Linux packages. The downsides are that no iOS version exists at all, and neither does one-tap import.
- Happ ships for iPhone and iPad, Russian App Store included, with one-tap import. The downside is that split tunnelling means picking a separate location entry.
- Hiddify ships for everything except the Russian App Store, but discards routing rules and picks the server by its own latency measurement.
An ordinary subscription link beginning with https:// works in all three: the server identifies the client from the User-Agent header and returns the configuration in its format. Try any of them without re-issuing anything.
Where to get a subscription
FlClashX works with a subscription from any service able to serve a Clash config. With RuSolv it is the very same link the other two clients use: it carries every location, and — if any of the locations you were issued has split tunnelling enabled — the rules for Russian sites too. The free tier covers one VLESS device with 10 GB of traffic a month. The step-by-step version of this guide for RuSolv is in the documentation.
Bottom line
FlClashX is the best choice wherever routing matters: the rules a service sends are applied immediately and to the entire profile, not to one entry. Builds exist for Android, Windows, macOS, and Linux, including variants that rarely get a mention — ARM64 for Windows, deb and rpm for Linux. And one hard limitation worth checking first: for iPhone and iPad, this app does not exist.
