Windows x64 and ARM64
Most Intel and AMD Windows systems use amd64. Windows on ARM uses ARM64. The v0.8.94 release includes an amd64 Setup/ZIP and a Windows ARM64 ZIP build.
Download FlClash
for Android, Windows, macOS and Linux
FlClash is released for Android, Windows, macOS and Linux. The current Latest release is v0.8.94. Choose the package that matches your operating system, CPU architecture and installation method before downloading.
Choose the FlClash build that matches your device
These are common v0.8.94 download choices. If your device uses a different CPU architecture or package format, use the build guidance below before selecting another Release asset.
Windows x64 Setup
For most Intel and AMD 64-bit Windows PCs. This link opens the v0.8.94 amd64 setup installer.
macOS Apple Silicon
For Apple Silicon Macs with M-series chips. Intel Macs should use the separate macOS amd64 DMG.
Android ARM64
For most modern Android phones and tablets. Other official APKs are available for armeabi-v7a and x86_64 devices.
Linux x64 AppImage
For common Intel and AMD 64-bit Linux desktops. v0.8.94 also provides amd64 DEB/RPM and an ARM64 DEB build.
How to choose the correct FlClash package
Start with the operating system, then match CPU architecture and package format. Different assets are builds of the same FlClash client, not separate products.
macOS Apple Silicon and Intel
Use the arm64 DMG on Apple Silicon Macs and the amd64 DMG on Intel Macs. Check About This Mac if you are unsure which processor your device uses.
Android APK architecture
The official Android release provides arm64-v8a, armeabi-v7a and x86_64 APKs. Most current phones and tablets use arm64-v8a.
Linux AppImage, DEB and RPM
Use AppImage for a portable x64 desktop option, DEB on Debian/Ubuntu families, and RPM on Fedora/RHEL families. v0.8.94 also includes an ARM64 DEB.
Install with Homebrew
The official README provides a Homebrew path for macOS: tap chen08209/tap and install the flclash cask. This is useful if you manage desktop apps through Homebrew.
Stable and pre-release builds
For everyday use, prefer the GitHub Release marked Latest. Builds with a pre-release tag are intended for testing newer changes and may be less stable.
Install and start FlClash in three steps
Choose the correct package, complete the platform-specific installation, then import a Profile and enable the network entry method for your device.
Choose the correct package
Match Android ABI, Windows amd64/ARM64, macOS Apple Silicon/Intel, or the Linux package format and CPU architecture to your device.
Install FlClash
Complete the normal system installation. On Linux, the official README lists libayatana-appindicator3-dev and libkeybinder-3.0-dev as required dependencies; macOS users can also install through Homebrew.
Add a Profile and enable network access
Import a subscription link or local configuration, choose the intended proxy group and mode, then use Android VPN, desktop System Proxy or TUN according to your platform and traffic needs.
Download FAQ
FlClash download and installation FAQ
These questions cover supported platforms, Windows and macOS architecture, Android APKs, Linux packages and what to do after installation.
Which operating systems does FlClash support?+
The official FlClash project supports Android, Windows, macOS and Linux. Package formats and CPU architectures differ by platform and release.
Should I download Windows amd64 or ARM64?+
Use amd64 on most Intel and AMD Windows computers. Choose ARM64 only for Windows on ARM devices. v0.8.94 provides an amd64 installer/ZIP and a Windows ARM64 ZIP.
Which macOS build should I download?+
Use the arm64 DMG on Apple Silicon Macs with M-series chips and the amd64 DMG on Intel Macs. The official README also documents a Homebrew cask installation method.
Which Android APK should I use?
Most modern Android phones and tablets use arm64-v8a. Older 32-bit ARM devices may use armeabi-v7a, while x86_64 is more common on emulators and a small number of x86 devices.
Should I use AppImage, DEB or RPM on Linux?+
AppImage is a portable option for common x64 desktops. Debian/Ubuntu families usually use DEB, while Fedora/RHEL families use RPM. Also confirm whether your system is amd64 or ARM64.
Why does FlClash still need a Profile after installation?+
FlClash is the client and Mihomo runtime, not a proxy node or subscription provider. You still need a valid subscription link or local Profile to define proxy groups, Rules, DNS and other runtime behavior.