fastflix.org

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.

FastFlix is a free graphical interface for encoding video to H.264, HEVC, and AV1. It is not an encoder itself: it sits on top of FFmpeg (version 4.3 or greater required, 5.0+ recommended) and gives you a GUI to drive software and hardware encoders, HDR metadata, audio, subtitles, and cover art from one place. It suits anyone who wants control over encoding settings without hand-writing FFmpeg commands.

What FastFlix actually does

FastFlix is a front end. The heavy lifting is done by FFmpeg and, for hardware encoding, by separate encoder binaries. That distinction matters for two reasons:

• If an encoder is missing from the list, it is usually because your FFmpeg build was not compiled with it.
• Hardware encoders require both the right GPU and additional binaries that you download and link manually.

Software vs. hardware encoding

The site splits encoders into two groups.

Software encoders

These run on your CPU and need no special hardware. Supported encoders include x265, x264, rav1e, AOM AV1, SVT AV1, VP9, and VVC, with varying support for HDR10, HDR10+, audio, subtitles, covers, and bt.2020.

Hardware encoders

These require matching hardware:

Most Nvidia, Intel, and AMD hardware encoders come from rigaya's encoders, which must be downloaded separately, extracted to a folder of your choice, and linked in the FastFlix Settings panel.

AV1 hardware encoding is limited to the latest GPU generations: Intel Arc, Nvidia 4000 series, and AMD 7000 series.

What you need before it works

1. Install FFmpeg and ffprobe, and make sure both are on your PATH and executable.
2. Use FFmpeg 4.3 or greater; the latest master build is recommended and is required for some features.
3. If you want hardware encoding, install the matching rigaya encoder binaries and point FastFlix at them in Settings.

A practical warning from the project: the FFmpeg in your package manager may not support all encoders or options. Static builds from the FFmpeg download page are suggested for Linux and Mac.

Where to get it and how to get help

Releases with binaries for Windows, macOS, and Linux are published on GitHub. The GitHub wiki holds help and further detail, and bugs go to the GitHub issue tracker.

How it differs from a typical transcoder

A normal transcoder hides encoding decisions behind presets. FastFlix exposes them: you choose the encoder, whether it runs on CPU or GPU, and how HDR10, HDR10+, audio, subtitles, covers, and bt.2020 are handled. The trade-off is setup work — FFmpeg on your PATH, plus separate hardware encoder binaries if you go the GPU route. If you want a GUI over FFmpeg's encoder options rather than a one-click converter, that trade-off is the point.

Use software encoding when you want the broadest format support and the most consistent results across machines, and use hardware encoding when you have a compatible GPU and want faster encodes. FastFlix is a free GUI for H.264, HEVC, and AV1 hardware and software encoding, and it relies on FFmpeg (version 4.3 or greater required, 5.0+ recommended) for the actual encoding work. The right choice depends less on preference and more on which encoders your FFmpeg build and hardware can actually provide.

Software encoding: best for compatibility and format coverage

Software encoders run on the CPU and do not require specific graphics hardware. FastFlix lists these software encoders: x265, x264, rav1e, AOM AV1, SVT AV1, VP9, and VVC.

Their feature support, as shown on the FastFlix page, is broad:

✓* means limited support.

A key caveat: if one of these software encoders is not listed in your FastFlix setup, it is because your version of FFmpeg does not have that encoder compiled in. So software encoding gives you the widest feature set, but only if your FFmpeg build includes the encoders you want.

Hardware encoding: faster, but with hardware and setup requirements

Hardware encoders use a GPU or dedicated encoding block. FastFlix supports:

• Nvidia GPU for NVEnc
• Intel GPU/CPU for QSVEnc
• AMD GPU for VCEEnc
• VAAPI (Linux) for compatible hardware
• Apple VideoToolbox (macOS)

Most Nvidia, Intel, and AMD encoders use rigaya's hardware encoders, which must be downloaded separately, extracted to a directory of your choice, and then linked in the FastFlix Settings panel. This is an extra setup step that software encoding does not require.

AV1 hardware encoding is only supported on the latest generation of graphics cards, specifically Intel Arc, Nvidia 4000 series, and AMD 7000 series.

Hardware encoder feature support

AV1

HEVC / H.265

AVC / H.264

Apple VideoToolbox (macOS)

✓* means limited support.

How to decide

Choose software encoding if:

• You need HDR10+ support (x265 and rav1e are the options listed with it).
• You want cover art support across the most encoders.
• You do not have a compatible GPU, or you do not want to download and configure rigaya's encoders separately.
• You want the same encoder behavior regardless of which machine you run FastFlix on.

Choose hardware encoding if:

• You have a supported Nvidia, Intel, AMD, VAAPI, or Apple VideoToolbox setup.
• Speed matters more than the widest possible feature coverage.
• You are encoding AV1 and have an Intel Arc, Nvidia 4000 series, or AMD 7000 series card.
• You are on macOS and want to use Apple VideoToolbox for H.264 or HEVC.

Before you start either path

FastFlix requires FFmpeg and ffprobe executables on your PATH, and they must be executable. Version 4.3 or greater is required for most usage; the latest master build is recommended and required for some features. The version in your package manager may not support all encoders or options. Static builds for Linux and Mac are available from the FFmpeg download page.

If you plan to use hardware encoding, download rigaya's Nvidia NVENC, AMD VCE, and Intel QSV encoders, extract them to a folder on your hard drive, and link them in the FastFlix Settings panel before expecting them to appear.

FastFlix is a GUI, not a self-contained encoder — it drives FFmpeg and (optionally) rigaya's hardware encoder tools underneath. So before you can encode anything you need FFmpeg 4.3 or greater (5.0+ recommended) with ffmpeg and ffprobe on your PATH and executable, plus the right GPU or platform for whichever hardware encoder you plan to use. Software encoding needs nothing beyond FFmpeg; hardware encoding needs both the matching hardware and, for most Nvidia/Intel/AMD encoders, a separate rigaya download that you link manually in FastFlix's Settings panel.

The one hard requirement: FFmpeg

FastFlix does the heavy lifting through FFmpeg, so this is non-negotiable:

• Version: 4.3 or greater is required for most usage. The latest master build is recommended and is required for some features.
• Executables: both ffmpeg and ffprobe must be on your PATH and must be executable.
• Watch out for package-manager builds: the FFmpeg in your system package manager may not support all encoders or options. If a software encoder you expect is missing from FastFlix's list, that's usually why — your FFmpeg build simply doesn't have it compiled in.
• Where to get a build: the FFmpeg download page offers static builds for Linux and Mac.

You can install FastFlix itself from the releases page (binaries for Windows, macOS, and Linux).

Software encoders: no extra hardware

If you only use software encoders, FFmpeg is the whole story. FastFlix lists these, with feature support varying by encoder:

✓* means limited support. Again, if one of these isn't listed in your copy of FastFlix, it's because your FFmpeg version doesn't have that encoder compiled in.

Hardware encoders: matching hardware required

Each hardware encoder needs the corresponding hardware present:

• NVEnc / NVEncC — Nvidia GPU
• QSVEnc / QSVEncC — Intel GPU or CPU
• VCEEnc / VCEEncC — AMD GPU
• VAAPI — compatible hardware on Linux
• Apple VideoToolbox — macOS

The extra step most people miss

Most of the Nvidia, Intel, and AMD encoders use rigaya's hardware encoders, which are not bundled. You must:

1. Download the rigaya tool (Nvidia NVENC, AMD VCE, or Intel QSV).
2. Extract it to a folder of your choice on your hard drive.
3. Link to that folder in FastFlix's Settings panel.

Skip step 3 and FastFlix won't find the encoder even though the files are on disk.

AV1 hardware encoding is generation-limited

AV1 hardware encoding only works on the latest generation of graphics cards — specifically Intel Arc, Nvidia 4000 series, and AMD 7000 series. Older GPUs won't expose an AV1 hardware encoder regardless of what you install.

Quick pre-flight checklist

• [ ] FFmpeg 4.3+ (5.0+ recommended), with ffmpeg and ffprobe on PATH and executable
• [ ] FastFlix installed from the releases page
• [ ] If using hardware encoding: the matching GPU/platform
• [ ] If using NVEnc/QSV/VCE: rigaya's tool downloaded, extracted, and linked in FastFlix Settings
• [ ] If targeting AV1 hardware: Intel Arc, Nvidia 4000 series, or AMD 7000 series

Common stumbling points

• "My encoder isn't in the list." Either your FFmpeg build lacks it, or (for hardware) you haven't linked rigaya's tool in Settings.
• ffmpeg works in a terminal but FastFlix can't find it. It's not on PATH for the environment FastFlix launches in, or it isn't marked executable.
• Everything installs but hardware encoding fails. Confirm the GPU generation actually supports the codec you picked — AV1 is the usual trap here.

For more detail, see the FastFlix GitHub wiki; bugs go to the GitHub issue tracker.

FastFlix supports HDR10 and HDR10+ metadata passthrough, but the exact combination depends on which encoder you pick. AV1 encoding is available both in software (rav1e, AOM AV1, SVT AV1) and in hardware, though hardware AV1 requires a current-generation GPU: Intel Arc, Nvidia 4000 series, or AMD 7000 series. If your goal is HDR10+ output, only a subset of encoders qualify — check the tables below before you commit to a preset.

HDR support by encoder type

FastFlix's own encoder tables distinguish between full support (✓) and limited support (✓*). HDR10 and HDR10+ are tracked separately, and bt.2020 (the wide-gamut color space that HDR workflows normally need) is listed as its own row.

Software encoders

Two things stand out. First, x265 is the only software encoder in the table with HDR10+ support. Second, SVT AV1's HDR10 support is marked as limited rather than full, so if HDR10 fidelity matters, rav1e or AOM AV1 are the safer AV1 choices in software.

If an encoder you expect to see is missing from this list, the page's explanation is that your FFmpeg build simply doesn't have it compiled in — it isn't a FastFlix limitation.

Hardware encoders

Hardware encoding requires the matching hardware: an Nvidia GPU for NVEnc, Intel GPU/CPU for QSVEnc, AMD GPU for VCEEnc, or compatible hardware for VAAPI (Linux) and Apple VideoToolbox (macOS).

AV1 (Intel Arc, Nvidia 4000 series, AMD 7000 series only):

HEVC / H.265:

AVC / H.264: no HDR10 or HDR10+ support in any of NVEncC AVC, VCEEncC AVC, or QSVEncC AVC. Only bt.2020 is listed.

Apple VideoToolbox (macOS): H264 and HEVC VideoToolbox both list bt.2020 support, but no HDR10 or HDR10+ rows.

VAAPI (Linux): VAAPI H264, HEVC, VP9, and MPEG2 all list bt.2020, with no HDR10 or HDR10+ rows.

AV1 specifics

AV1 hardware encoding is explicitly restricted to the latest generation of graphics cards: Intel Arc, Nvidia 4000 series, and AMD 7000 series. Older GPUs will not expose an AV1 hardware encoder, so you'd fall back to software AV1 (rav1e, AOM AV1, or SVT AV1).

Note that the rigaya hardware encoders (NVEncC, QSVEncC, VCEEncC) are not bundled. You download them separately, extract them to a folder of your choice, and point FastFlix at that folder in the Settings panel. FFmpeg and ffprobe must also be on your PATH and executable — version 4.3 or greater is required for most usage, and the latest master build is recommended and needed for some features. A package-manager FFmpeg may not include all encoders or options.

Choosing an encoder for HDR10+ or AV1

• HDR10+ output, any codec: x265 (software) or one of NVEncC/QSVEncC/VCEEncC in AV1 or HEVC. Nothing else in the tables lists HDR10+.
• AV1 with full HDR10: rav1e or AOM AV1 in software, or any of the three hardware AV1 encoders.
• AV1 with HDR10+: hardware AV1 only (NVEncC, QSVEncC, VCEEncC) — no software AV1 encoder lists HDR10+.
• H.264 with HDR: not available; the AVC hardware encoders have no HDR10/HDR10+ rows.

One caveat worth flagging: the audio column in the source tables uses the same ✓/✓* notation, and several hardware encoders show limited (✓*) audio support. If your workflow depends on audio handling alongside HDR, verify that combination in FastFlix itself rather than assuming the HDR rows tell the whole story.