Portable Flux or the Windows installer: which package should you use?

What the installer handles

The Windows installer places the application and bundled components in its installation directory and registers the native browser host. The release documents package contents and installation behavior. Do not confuse the setup executable with an extension ZIP or a source archive; each has a different purpose.

Keep the portable package together

Extract the complete archive rather than copying only the desktop executable. The native host and media tools are part of the package. Open Flux once from its final location so startup can register or repair the bridge. If you later move the folder, open the app again and check Settings → Browser integration.

Download and update checks

• Use the official GitHub release for either package.
• Compare the package with its SHA-256 entry.
• Read the publisher-signing note.
• Keep the application and extension packages compatible.
• For a same-version repair rebuild, follow the release’s manual refresh instructions.

Portable does not mean no network activity

A portable folder changes how application files are placed, not how sources are contacted. Downloads still reach the chosen servers; torrents reach peers and discovery services; update checks contact GitHub. Review privacy and sharing settings just as you would for an installed copy. Keep task data accessible if you expect pause and restart recovery to work.

Windows and Linux. One download space.

Install the RPM with dnf, then open Flux once as your normal user to register the browser bridge. The same Chromium and Firefox extension packages work on Linux. Update RPM installations through your package manager.

Linux validation uses a controlled Fedora environment, not every RPM distribution. Flatpak/Snap browsers may need an extra host connection. Firefox ZIP packages remain temporary unsigned extensions.

sudo dnf install ./Flux-2.6.6-linux-x86_64.rpm
flux-desktop