FlClash is available for Android, Windows, macOS and Linux, but each platform uses different package formats and CPU builds. GitHub currently marks v0.8.98 as the Latest release. Before downloading, first identify your operating system and processor architecture, then choose the matching installation package.
The direct links below cover common device types, but FlClash publishes multiple builds for different processors and package formats. Use these entries only when the listed platform and architecture match your device; otherwise select the corresponding asset from the same GitHub release.
Use this installer on most 64-bit Windows PCs with Intel or AMD processors. Windows on ARM devices require an ARM64 build instead of the standard amd64 Setup package.
Choose this build for Apple Silicon Macs using M-series chips. Intel-based Macs need the separate amd64 build, so confirm the processor type in About This Mac before installing.
Most current Android phones and tablets use arm64-v8a. Older 32-bit ARM devices may require armeabi-v7a, while x86_64 is mainly relevant to emulators and a smaller group of x86 Android devices.
Use the AppImage on common 64-bit Intel or AMD Linux desktops when you want a portable build. Debian or Ubuntu users may prefer DEB, Fedora or RHEL users may prefer RPM, and ARM devices require an ARM64 package.
FlClash package names describe the target platform, processor architecture and installation format. The safest order is: identify the operating system, confirm the CPU architecture, then choose the package type you want. These files are different builds of the same FlClash client, not separate editions.
Most Windows PCs with Intel or AMD processors use amd64. Windows on ARM devices use ARM64. Setup packages are intended for normal installation, while ZIP builds are useful when you prefer a portable client without a traditional installer.
Apple Silicon Macs use arm64 builds and Intel Macs use amd64 builds. The processor type matters more than the macOS version itself, so check About This Mac before choosing the package.
Android APK selection is based on ABI. arm64-v8a is the normal choice for most modern devices, armeabi-v7a is for older 32-bit ARM hardware, and x86_64 is mostly used by emulators or specific x86-based devices.
Choose AppImage when you want a portable Linux build, DEB for Debian and Ubuntu based distributions, and RPM for Fedora or RHEL based distributions. CPU architecture still matters, so amd64 and ARM64 packages are not interchangeable.
macOS users who manage applications with Homebrew can install FlClash through the chen08209/tap repository and the flclash cask instead of downloading a DMG manually.
For regular use, choose the GitHub release marked Latest. Pre-release builds are intended for testing changes before they enter the main release line, so they are better suited to users who specifically want to verify newer fixes or behavior.
Downloading FlClash only installs the client. To begin using it, you still need to complete the platform installation, add a valid subscription or local Profile, and enable the network entry method that matches your device and traffic requirements.
Check Android ABI, Windows amd64 or ARM64, macOS Apple Silicon or Intel, and the Linux package format before installation. A package built for the wrong architecture may fail to install or start.
Complete the normal installation flow for the operating system and grant any required application or network permissions. Linux users should check the dependencies documented for their distribution, while macOS users can choose either a direct package or the documented Homebrew method.
After the client starts, import a subscription link or local Profile and confirm that the configuration loads successfully. Then select the required proxy group or mode and enable Android VPN, desktop System Proxy or TUN according to the traffic scope you want FlClash to handle.
Download FAQ
These answers focus on the decisions that matter before and immediately after downloading FlClash: platform support, CPU architecture, package format, installation method and the first Profile.
The official FlClash project supports Android, Windows, macOS and Linux. Package formats and CPU architectures differ by platform and release.
Use amd64 on most Intel and AMD Windows computers. Choose ARM64 only on Windows on ARM devices. After identifying the architecture, choose between the available installer or portable package listed in the relevant GitHub release.
Apple Silicon Macs with M-series chips use arm64 builds, while Intel Macs use amd64 builds. You can also install FlClash through the Homebrew cask method documented by the project.
arm64-v8a is the correct APK for most modern Android devices. armeabi-v7a is intended for older 32-bit ARM hardware, while x86_64 is usually relevant to emulators and a limited number of x86 Android systems.
Use AppImage when you want a portable Linux application, DEB on Debian or Ubuntu based systems, and RPM on Fedora or RHEL based systems. Package format and CPU architecture must both match the device.
FlClash installs the client and Mihomo runtime, but it does not include proxy nodes or a subscription service. A valid subscription link or local Profile is still required before the client can load proxy groups, Rules, DNS settings and other runtime configuration.
