Why Is a Software Encoder Missing in FastFlix?

A software encoder is missing from FastFlix almost always because the FFmpeg build you have installed was not compiled with that encoder. FastFlix is a GUI, not an encoder itself: it calls FFmpeg (and, for hardware, separate rigaya tools) to do the actual work, so the encoder list you see reflects what your FFmpeg binary supports. The fix is to install a fuller FFmpeg build rather than to change anything inside FastFlix.

How FastFlix decides which encoders to show

FastFlix detects available encoders by querying the FFmpeg and ffprobe executables on your system. Two conditions must hold before an encoder appears:

• FFmpeg and ffprobe must be on your PATH and must be executable. If FastFlix can't find them, you'll see a much shorter list — or none at all.
• The FFmpeg build must include that encoder. FFmpeg is compiled with a chosen set of encoders, and many distributions ship a reduced set.

The site states this directly: if one of the listed software encoders is not shown, it is because your version of FFmpeg does not have that encoder compiled in.

The software encoders FastFlix expects

FastFlix documents support for these software encoders:

✓* means limited support. If an encoder in this table is absent from your FastFlix install, the cause is the FFmpeg build, not FastFlix.

Fix: install an FFmpeg build that includes the encoder

1. Check your current version. Run ffmpeg -version in a terminal. FastFlix requires version 4.3 or greater, and 5.0+ is recommended. The latest master build is recommended and is required for some features.
2. Check whether the encoder is present. Run ffmpeg -encoders and search the output for the encoder name (for example libx265, libsvtav1, libaom-av1). If it isn't listed, that build cannot provide it.
3. Replace the build if needed. The FFmpeg from your package manager may not support all encoders or options. Download a static build instead — the site points to the FFmpeg download page for static Linux and Mac builds.
4. Put the binaries on your PATH. Both ffmpeg and ffprobe must be executable and discoverable. Restart FastFlix afterward so it re-queries the encoders.

Expected result: the missing encoder appears in FastFlix's encoder list once the new FFmpeg is detected.

If a hardware encoder is missing instead

Hardware encoders follow a different rule. They require both the right hardware and a separate download:

• Hardware: Nvidia GPU for NVEnc, Intel GPU/CPU for QSVEnc, AMD GPU for VCEEnc, compatible hardware for VAAPI (Linux) or Apple VideoToolbox (macOS).
• Separate tools: Most Nvidia, Intel, and AMD encoders use rigaya's hardware encoders, which must be downloaded separately, extracted to a folder of your choice, and then linked in the FastFlix Settings panel.

So a missing NVEncC, QSVEncC, or VCEEncC entry usually means the rigaya tool hasn't been downloaded and linked, not that FFmpeg is at fault. Note also that AV1 hardware encoding is limited to the latest generation of graphics cards — Intel Arc, Nvidia 4000 series, and AMD 7000 series.

Common sticking points

• Package-manager FFmpeg looks fine but lacks encoders. This is the most frequent cause; switching to a static or master build resolves it.
• ffprobe missing while ffmpeg is present. Both are required, so FastFlix may fail to enumerate encoders even though encoding itself would work.
• Editing FastFlix settings won't add software encoders. Software encoder availability comes entirely from FFmpeg; only the rigaya hardware tools are linked manually in Settings.