FlClash is a multi-platform proxy client designed to provide a simple, easy-to-use, open-source, and ad-free solution for managing proxies based on Clash Meta. It supports multiple operating systems, including Android, Windows, macOS, and Linux, making it versatile for users across different devices.
Key Features:
Multi-platform Support: Runs seamlessly on Android, Windows, macOS, and Linux.
Adaptive Design: Supports various screen sizes and color themes, with a modern Material You-inspired UI.
WebDAV Sync: Enables data synchronization via WebDAV for seamless configuration management across devices.
Subscription Links: Supports subscription links for easy setup of proxy configurations.
Dark Mode: Offers a dark theme for reduced eye strain in low-light conditions.
Audience & Benefit:
Ideal for developers, IT professionals, and privacy-conscious users who need reliable proxy management without ads or intrusive tracking. FlClash provides a clean, efficient tool to maintain secure and flexible network connections across devices.
Available as an open-source solution, FlClash can be installed via winget on supported platforms.
README
FlClash
A multi-platform proxy client based on ClashMeta. Simple to use, open source and ad-free.
One app for Android, Windows, macOS and Linux, with x64 and ARM64 builds on the desktop.
mihomo (Clash.Meta) core with rule routing, proxy groups, latency tests, system proxy and TUN mode.
Profiles from a subscription link or a file, with a built-in editor, override scripts, and custom rules,
proxies and proxy groups.
Live views of connections, requests, DNS queries and logs.
Material You design with Apple-style interaction: dynamic color, light and dark themes, continuous corners,
sheets that snap between heights, and layouts that adapt from phones to desktops.
Backup and restore through WebDAV or a local file.
Platform touches: a Quick Settings tile, per-app proxy and Android TV support on Android; a tray menu and
global hotkeys on the desktop.
Open source and ad-free, licensed under GPL-3.0.
Download
Get the latest build from GitHub Releases, or open the
website, which picks the right file for your device.
Platform
Packages
Notes
Android
APK for arm64-v8a, armeabi-v7a and x86_64
Most phones use arm64-v8a. Also on the F-Droid repository below.
Windows 10 and later
Installer (.exe) or portable .zip, for x64 and ARM64
Pick ARM64 on Snapdragon and other ARM laptops.
macOS 12 and later
DMG for Apple Silicon and Intel
Also on Homebrew.
Linux
.deb, .rpm and AppImage, for x64 and ARM64
See the tray note below.
Homebrew
brew tap chen08209/tap
brew install --cask flclash
Linux tray icon
The .deb package installs its own dependencies. With the AppImage or the .rpm, install the AyatanaAppIndicator
library so the tray icon can show:
Import a profile from a link. Opening a link in this form imports the subscription into FlClash. The clashmeta://
and flclash:// schemes work the same way.
clash://install-config?url=
Automate on Android. Tasker, MacroDroid and similar apps can start, stop or toggle the proxy by starting an
activity with one of these actions:
adb shell am start -a com.follow.clash.action.TOGGLE
Build from source
You need Flutter 3.47 (release builds use 3.47.6),
Go 1.27 and Rust installed through rustup. Each platform builds on its own
host, except Android, which builds anywhere.
git clone --recursive https://github.com/chen08209/FlClash.git
cd FlClash
flutter pub get
dart setup.dart android # or windows, macos, linux
Packages land in dist/. The Go core and the Rust libraries are compiled as part of the Flutter build.
Platform
Also needed
Android
Android SDK with the NDK. Add --arch arm64 to build a single ABI.
Windows
GCC (MinGW-w64) for the core and Inno Setup 6 for the installer.
macOS
Xcode and Node.js. The script installs appdmg through npm.
Linux
Debian or Ubuntu. The script installs the build packages with apt and downloads appimagetool.
Run dart setup.dart --help for the remaining options, such as --targets to build only some package formats.
Support
Starring the repository is the easiest way to support the project. Questions and announcements go to the
Telegram channel; bugs and feature requests go to
GitHub Issues.
