Default pickPreferred
FlClash
If you do not depend on an old profile or a specific tutorial, start with FlClash. It is the clearer starting point for this use case.
FlClash vs ClashX
FlClash: A good fit for multi-device users who want one familiar workflow across platforms. ClashX: Familiar menu bar behavior for users following older ClashX tutorials.
FlClash vs ClashX: Key Differences
Compare FlClash and ClashX by platform support, maintenance status, subscription import, proxy modes, tutorial coverage and best-fit users before choosing.
| Item | FlClash |  ClashX |
|---|---|---|
| Best for | Users who want a similar experience across desktop and Android | Mac users who prefer a menu bar workflow |
| Learning curve | Low to medium | Low to medium |
| Supported platforms | Windows / Mac / Android | Mac |
| Subscription import | Common subscription imports | Subscription link and local profiles |
| Proxy modes | Desktop proxy workflow plus Android VPN workflow | System proxy, rule and global |
| Core / ecosystem | Mihomo | Clash |
| Positioning | Unified desktop and Android experience | Classic macOS menu bar client |
| Repository / store status | Active, not archived | Public, not archived |
| Releases / store page | View releases | View releases |
| Links | FlClash / Tutorial | ClashX / Tutorial |
| Repository | chen08209/FlClash | alvincrisuy/clashX |
| Public repository | Yes, public GitHub repository | Yes, public GitHub repository |
| Open-source status | Yes, public repo with GPL-3.0 license | Yes, public repo with MIT license |
| License | GPL-3.0 | MIT |
| Author / maintainer | chen08209 | alvincrisuy |
| Official source type | GitHub repository | GitHub repository |
| Verification source | GitHub API, 2026-05-18 | GitHub API, 2026-05-18 |
How to Choose Between FlClash and ClashX
For a new setup, start with FlClash when it matches your platform and workflow; choose ClashX when you rely on existing profiles, older tutorials or a specific feature.
When to choose the otherSpecific needs
ClashX
Choose ClashX when you already use it, or when a tutorial, profile or required feature clearly depends on it.
How to decide
New users need a starting point; existing users need migration fit
New users should follow the default pick; existing users should check migration fit first. If you already have a related setup or a tutorial requires it, ClashX still makes sense.