Hardware Encoding in Avidemux: NVENC, Quick Sync, VA-API & VideoToolbox Setup
Hardware encoding means compressing video with a dedicated media block on your GPU instead of the general-purpose CPU. Your NVIDIA, Intel, or AMD chip (or Apple Silicon) has silicon whose entire job is encoding H.264/HEVC frames — it does the same job as software encoders like x264, but many times faster and with far less CPU load and battery drain. Avidemux can hand its frames to these accelerators if your build and system expose them: which encoders appear in the Video Output dropdown depends on your operating system, GPU, drivers, and how your particular Avidemux build was compiled.
Avidemux 2.8.1 is the latest stable release (2.8.2 is the nightly/development line). Hardware encoder support is one of the features that varies most between builds — official packages and distribution builds may differ — so treat everything below as “may be available on your system” rather than guaranteed. This page explains what to look for and how to decide whether hardware encoding fits your job.
Which hardware encoders may appear on each platform
| Platform | Vendor technology | What you may see in Video Output |
|---|---|---|
| Windows + NVIDIA GPU | NVENC (NVIDIA’s hardware encoder) | H.264 and/or HEVC entries identified as NVENC |
| Windows + Intel GPU | Intel Quick Sync Video | H.264 and/or HEVC entries identified as Quick Sync |
| Windows + AMD GPU | AMD hardware encoder | H.264 and/or HEVC entries identified for AMD |
| Linux | VA-API (the cross-vendor Linux acceleration API) | H.264 and/or HEVC entries identified as VA-API |
| macOS | VideoToolbox (Apple’s media framework) | H.264 and HEVC entries identified as VideoToolbox — including HEVC encoding support added in the 2.8 line |
Honesty note: seeing these entries at all requires a build that includes the encoder plugin and working GPU drivers. If your Video Output dropdown shows only x264/x265/Copy, your build simply does not expose hardware encoders — that is normal, especially on some Linux distribution packages. Do not trust any guide (including this one) that claims specific driver versions or exact menu labels; those change between builds.
How to select a hardware encoder
- Open the Video Output dropdown (left panel).
- Look for entries whose names identify a hardware path — words like NVENC, Quick Sync, VA-API, or VideoToolbox alongside H.264 or HEVC. The exact labels depend on your build.
- Select one, then open its Configure button to see what options your build exposes (quality/speed trade-off controls, profile, level). Available options vary by build and GPU — only what you see on your own screen is real.
- Set Audio Output and Output Format as usual (e.g. AAC audio, MP4 Muxer) and save.
If the encoder you want is missing: check that your GPU drivers are up to date, and check whether your Avidemux build was compiled with that encoder enabled (official Windows builds differ from some Linux distro builds). On Linux, VA-API also needs the correct VA-API driver package for your GPU installed and working.
Reality check: quality vs speed
Hardware encoders are dramatically faster than CPU encoding — often real-time or faster — but they come with real trade-offs:
- Files are usually larger at the same visual quality. Hardware encoders make decisions on the fly; they do not offer the slow, exhaustive analysis modes (like multi-pass encoding) that make software x264 so efficient. A hardware-encoded file can be noticeably bigger than an x264 file that looks the same.
- No two-pass encoding. If you need to hit an exact target file size, software encoding is the reliable path.
- Best for fast turnaround, not archival compression. Hardware encoding shines when speed is the priority — quick conversions, drafts, same-day uploads. It is a poor fit when your goal is the smallest possible file at a given quality.
When to stick with software x264/x265
- You want the smallest possible file at a given quality — see the compression guide.
- You need maximum quality for archival or final delivery.
- You need exact file-size control via two-pass encoding — see x264/x265 settings explained.
- Your build does not expose a hardware encoder — x264 is the dependable fallback everywhere.
4K and HDR notes
Hardware encoders handle 4K resolutions far more comfortably than CPU encoding does — what would be a slow grind in x264 can run at usable speed through NVENC, Quick Sync, VA-API, or VideoToolbox. That said, two caveats:
- 4K encodes are still large. HEVC hardware encoders help, but 4K files take serious disk space either way.
- Avidemux’s HDR metadata support is limited. HDR content (HDR10 color primaries, transfer characteristics, mastering-display metadata) may not be fully carried through the encode in Avidemux — do not assume your output preserves HDR signaling just because the input was HDR. If HDR fidelity matters, verify the output’s metadata on your own system before committing to a large batch.
- Check the system requirements page for general performance expectations.
Frequently asked questions
Does Avidemux support hardware encoding?
Yes, if your build exposes it. Depending on the platform, GPU, drivers, and build, the Video Output dropdown may list NVENC (NVIDIA), Intel Quick Sync, AMD hardware encoders, VA-API (Linux), or VideoToolbox (macOS) entries. If your build shows only x264/x265/Copy, hardware encoding is not available in that build.
Why is my hardware encoder missing from the Video Output list?
The most common reasons are a build compiled without that encoder plugin, outdated or missing GPU drivers, or (on Linux) a missing VA-API driver package for your GPU. What appears depends on your exact build, GPU, and driver stack.
Is hardware encoding better quality than x264?
No — hardware encoders are much faster but usually produce larger files at the same visual quality, because they lack the slow analysis modes and two-pass encoding of software encoders. Hardware encoding is best for fast turnaround; software x264/x265 is best for smallest size and maximum quality.
Can I hardware-encode 4K or HDR video in Avidemux?
4K hardware encoding generally works where the encoder is available and runs much faster than CPU encoding. For HDR, be cautious: Avidemux’s HDR metadata support is limited, so HDR signaling may not be fully preserved — verify the output on your own system if HDR fidelity matters.