A greyed-out Hardware Preset in HandBrake is not a broken install and not a missing feature. It is HandBrake reporting the result of a check it ran on your machine — and the official documentation gives exactly one explanation for it, with only two branches.
What a greyed-out Hardware Preset actually means
HandBrake's official presets page describes the Hardware group like this:
"HandBrake's Hardware Presets encode video using dedicated media engines provided by modern graphics hardware, and are optimized for maximum encoding speed."
Then, in a single sentence, it gives the entire documented reason those presets can be unselectable:
"HandBrake will disable any Hardware Preset where the associated hardware and software drivers are not detected, or are outdated."
That sentence is worth reading slowly, because three things in it do the work.
First, there are only two causes. Not detected, or outdated. Anything else you read about disabled hardware presets is not coming from HandBrake's documentation.
Second, it says "hardware and software drivers." Both halves are part of what gets checked. A GPU physically present in the machine is not by itself what the sentence describes as detected — the driver is named alongside it.
Third, the scope is "any Hardware Preset," not the group. The sentence disables presets individually, and every one of them is judged against the same pair of conditions: the associated hardware and software drivers are not detected, or are outdated.
What HandBrake deliberately does not tell you
HandBrake's documentation publishes no minimum driver version, no minimum GPU generation, and no list of supported chips for its hardware encoders. It says "outdated" and stops there. It also does not document how to view the detection result, or any log that would tell you which of the two causes applied to you.
So when a forum reply tells you that you need a specific driver build number to un-grey NVENC, understand where that number came from: not the official docs. Check the official documentation rather than a thread.
The fastest fix
Given that the documented failure has two branches, the fix has two steps, in this order.
- Confirm the machine has the media engine that preset is associated with. An NVENC preset is asking for NVIDIA hardware; a QSV preset is asking for Intel Quick Sync Video. If the machine does not have it, the preset staying greyed is correct behaviour, not a fault to chase.
- Install the current driver from the hardware vendor, then look at the preset list again. Because HandBrake publishes no version threshold, "current" is the only target you can actually aim at — there is no documented number to match.
If neither step changes anything, you have reached the end of what the official documentation covers. HandBrake's troubleshooting page addresses installation and launch problems — on Windows, for instance, the .NET Desktop Runtime requirement — and has no entry for disabled presets, so it will not rescue this.
If you landed here because you have a file to shrink today and the fast encoder path is blocked, you do not have to wait on a driver at all:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That runs in your browser tab, with no install and no preset list to un-grey. The same engine powers Clapr's video compressor if you want the standalone tool page.
Which presets you are actually missing
Here is HandBrake's official Hardware Presets table:
| Preset | Type | Video | Audio | Encoding Speed |
|---|---|---|---|---|
| AV1 QSV 2160p60 4K | MP4 | AV1 | AAC stereo | Very Fast |
| H.265 NVENC 2160p60 4K | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 NVENC 1080p60 | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 QSV 2160p60 4K | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 QSV 1080p60 | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 VCN 2160p60 4K | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 VCN 1080p60 | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 MF 2160p60 4K | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 MF 1080p60 | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 Apple VideoToolbox 2160p60 4K | MP4 | H.265 | AAC stereo | Very Fast |
| H.265 Apple VideoToolbox 1080p60 | MP4 | H.265 | AAC stereo | Very Fast |
Two things stand out once you see the whole list.
Every entry except one is H.265, and every entry outputs MP4 with AAC stereo audio. There is no H.264 hardware preset in the official list at all. If you came looking for a fast H.264 export, the Hardware group was never where it lived — greyed out or not.
Resolution and frame rate in these names are ceilings. HandBrake states that when you select one of its presets, "higher resolution video will be downscaled to a maximum resolution, and higher frame rates will be peak limited to a maximum frame rate." A 1080p30 source handed to an H.265 NVENC 1080p60 preset is not upscaled or interpolated upward — the limits only cut down.
The group covers Intel Quick Sync Video (QSV), NVIDIA NVENC, AMD VCN, Microsoft Media Foundation (MF), and Apple VideoToolbox. One naming wrinkle: HandBrake's video codecs page lists the H.264 and H.265 hardware encoders as "Intel QuickSync, AMD VCE, Nvidia NVENC and ARM devices though MediaFoundation," while the presets table uses VCN for the AMD entries. The official pages use both spellings.
Greyed out is not the same as missing
These two symptoms get mixed up constantly, and the fix is completely different.
- Greyed out — the preset is in the list but unselectable. That is the hardware/driver check above.
- Not in the list at all — the preset was renamed or removed in a HandBrake update. For example, HandBrake states that as of 1.6.0 the Discord presets were renamed Social, and as of 1.6.0 all 2160p60 presets were renamed 2160p60 4K. If you are following a tutorial and the name simply is not there, see where HandBrake's Discord preset went.
If a preset name is visible but dim, no rename is involved. Stop looking for a replacement name.
Encoding fine without a hardware preset
The software path is not a downgrade in quality terms — it is a downgrade in speed, and HandBrake never quantifies by how much.
HandBrake says that most of its official presets use the x264, x265, or SVT-AV1 video encoders with a Constant Rate Factor, "sometimes abbreviated CRF or simply RF." Its default suggestion for newcomers is explicit: "The default Fast 1080p30 preset is a good choice if you're just getting started. It's fast and compatible across a wide range of software and devices."
If you want to steer quality yourself, HandBrake's recommended RF ranges for the x264 and x265 encoders are:
- RF 18-22 for 480p/576p Standard Definition
- RF 19-23 for 720p High Definition
- RF 20-24 for 1080p Full High Definition
- RF 22-28 for 2160p 4K Ultra High Definition
Those numbers apply to x264 and x265 only. SVT-AV1 has its own separate set, and for other encoders HandBrake says only to "start with a value in the middle of the scale, and adjust in small increments as desired."
Mac users, one trap. If you do get Apple VideoToolbox working, its quality scale runs the other way. HandBrake explains that for x264, x265 and SVT-AV1 a lower RF number produces higher quality video and a higher RF number produces lower quality video, then adds:
"This is reversed for other encoders, such as Apple VideoToolbox, where a higher number produces higher quality. In all cases, adjusting HandBrake's quality control to the right always increases quality, and adjusting the control to the left always decreases quality."
On speed: the official tables use words, not numbers — Very Fast, Fast, Standard, Slow, Very slow. Hardware presets sit at Very Fast, and so do the General "Very Fast" presets. HandBrake publishes no multiplier for how much faster a hardware encode is, so treat any specific speed claim you read elsewhere with suspicion.
How to tell it worked
The preset becomes selectable. That is the entire test, because HandBrake's documentation describes no detection log, readout, or diagnostic screen to check instead.
FAQ
Why is NVENC greyed out in HandBrake? Because HandBrake did not detect the associated hardware and software drivers, or found them outdated. Those are the only two reasons its documentation gives for disabling a Hardware Preset.
Do I need a specific driver version for HandBrake QSV? HandBrake does not publish one. Its documentation says drivers that are "outdated" cause the preset to be disabled, but gives no minimum version, GPU generation, or model list. Check the official documentation before trusting a number from a forum post.
Does HandBrake disable hardware presets one at a time or all at once? The documented wording is per preset: it disables any Hardware Preset where the associated hardware and software drivers are not detected, or are outdated. Beyond that sentence, HandBrake's documentation does not describe what the list looks like in any particular configuration.
Is hardware encoding worse quality than x264 or x265? HandBrake's documentation does not rank them against each other. What it does say is that quality values are not comparable across encoders at all — an x264 encode at RF 25 should not be expected to match an x265 or SVT-AV1 encode at RF 25, because each scale maps only to its own rate control.
What should I use if I cannot un-grey anything? The software presets. Fast 1080p30 is HandBrake's own starting recommendation, and the RF ranges above let you tune from there. For a one-off file, the browser compressor on this page is faster to reach than any install — see all Clapr tools for format conversions too.
Every HandBrake behaviour above is cited from HandBrake's official documentation, checked 16 September 2026. More troubleshooting walkthroughs live in the fix guides, including what HandBrake's Social 25 MB presets actually guarantee.
