Downloads
Flux is available for Windows, macOS, and Linux. All builds are self-contained — the runtime is included, so you do not need to install anything else before running the application.
- Windows
- macOS
- Linux
The Windows build is a portable archive. Extract it and run FileFlows.Flux.exe.
Third-party tools for local processing
Local video and audio processing requires FFmpeg and FFprobe. Flux invokes these tools directly from your system PATH.
Download a static build of FFmpeg from ffmpeg.org/download.html.
- Extract the archive.
- Add the
binfolder to your system PATH, or copyffmpeg.exeandffprobe.exeinto the same folder asFileFlows.Flux.exe.
The macOS build is packaged as a .dmg installer. Open it and drag Flux to your Applications folder.
Third-party tools for local processing
Local video and audio processing requires FFmpeg and FFprobe. Flux invokes these tools directly from your system PATH.
Install FFmpeg using Homebrew:
brew install ffmpeg
If you do not have Homebrew, install it first from brew.sh.
The Linux build is distributed as a Flatpak package. It bundles the required runtime and runs on most modern Linux distributions with Flatpak support.
Third-party tools for local processing
Local video and audio processing requires FFmpeg and FFprobe. The Flatpak runtime provides its own isolated environment. You have two options:
- Install FFmpeg inside Flatpak — The easiest way is to grant the Flatpak access to the system's FFmpeg binary, or install it via the Flatpak SDK.
- Use a system-wide FFmpeg — If FFmpeg is installed on the host system, the Flatpak may need the
--filesystem=homepermission (already included) and proper PATH propagation.
If local video or audio processing is important to you on Linux, the most reliable approach is to ensure ffmpeg and ffprobe are available in a location the Flatpak sandbox can access.
Verifying your setup
After installing the dependencies, open Flux and try a local conversion. If a required tool is missing, Flux will report the failure in the job log and mark the job as failed. You can view the log by clicking the job in the queue and selecting View Log.