HandBrake Intel Quick Sync Greyed Out: How to Fix It

When HandBrake Intel Quick Sync is greyed out, missing, disabled, or unavailable, the problem usually falls into one of four categories: the computer does not expose a compatible Intel graphics processor, the operating system cannot access the required Intel driver stack, HandBrake has disabled or failed to detect the hardware encoder, or the selected preset and format combination is incompatible. The steps below help you identify which category applies without repeatedly changing unrelated video, audio, or subtitle settings.

Intel Quick Sync Video, often shown as Intel QSV in HandBrake, uses supported Intel graphics hardware to accelerate video encoding. It is not available merely because a computer has an Intel-branded processor. A supported and enabled Intel integrated GPU or compatible Intel Arc GPU must be visible to the operating system, have a working driver, and be supported by the HandBrake build and operating system in use.

1. Confirm the Symptom With a Small Test Encode or Preview

Begin by confirming exactly what is unavailable. Open a short, ordinary video file that HandBrake can scan successfully. A small MP4 phone clip, camera sample, or screen recording is better for diagnosis than a damaged file, a complex disc source, or an unusual professional format.

After the scan finishes, open the Video tab and inspect the Video Encoder list. Depending on your hardware and HandBrake build, supported choices may include labels such as H.264 (Intel QSV), H.265 (Intel QSV), AV1 (Intel QSV), or similar Intel QSV variants. Not every Intel GPU supports every codec.

1.1 Distinguish Missing Encoders From a Failed Encode

These symptoms point to different problems:

• No Intel QSV options appear: HandBrake probably did not detect a usable Intel hardware encoder.
• An Intel QSV option is greyed out: the current container, preset, codec profile, or another selected option may be incompatible.
• QSV can be selected but the encode fails: the Activity Log is needed to identify a driver, device, memory, or media-processing error.
• The encode completes but playback fails: the encoder may be working correctly, while the playback device does not support the output codec, profile, bit depth, or resolution.

If a QSV encoder appears and completes a 30-second test that plays correctly, the original visibility problem is solved. Stop changing drivers and firmware at that point. Return to the intended source and add settings gradually.

1.2 Test a Hardware-Oriented Preset

Choose a preset that explicitly uses Intel QSV if one is available in your HandBrake installation. Alternatively, start with a standard preset and manually choose H.264 (Intel QSV). Set a short range by selecting seconds or chapters rather than encoding the entire source.

Use MP4, a common resolution, and default filters for the first test. H.264 is normally the most useful baseline because support is broader than for newer codecs. Success means HandBrake starts the job, the Activity Log identifies an Intel QSV encoder, and the output plays normally.

2. Check the HandBrake Settings Directly Related to This Problem

Do not begin by changing audio bitrates, subtitle appearance, chapter markers, or destination folders. Those options generally do not determine whether Intel QSV appears in the video encoder list.

2.1 Review Hardware Encoder Preferences

Open HandBrake Preferences and inspect the Video, Advanced, or hardware-related section. The exact wording and location can differ among releases and operating systems. If your version offers an option that permits Intel Quick Sync hardware encoders, ensure it is enabled. A separate Quick Sync decoding option concerns hardware-assisted decoding and should not be confused with QSV encoding.

Restart HandBrake after changing a hardware preference. Hardware capabilities are commonly detected when the application starts. Success means the Intel QSV entries appear in the Video Encoder menu after reopening the source.

2.2 Reset an Incompatible Preset

A customized preset can preserve a combination that is invalid for the selected encoder. Load a built-in preset, choose MP4, and select H.264 (Intel QSV). Leave encoder profile, level, and advanced options at automatic or default values for the test.

If QSV becomes selectable, the hardware and driver are probably functional. Compare the working preset with the custom one instead of continuing with operating-system repairs. Reintroduce resolution, frame-rate, quality, profile, and filter changes one at a time.

2.3 Update HandBrake From an Official Build

Use a current official HandBrake release appropriate for the operating system. Unofficial repository packages and custom builds can be compiled without the same hardware support or can depend on different media libraries. Avoid assuming that every package carrying the HandBrake name exposes identical QSV capabilities.

If an official build detects QSV while a third-party build does not, the package is the differentiating factor. Keep the working build and stop modifying unrelated encoding settings.

3. Check the Hardware, Operating System, and Driver Path

QSV visibility depends on a complete path from the Intel GPU through firmware, the operating system, its graphics driver, and HandBrake. A break anywhere in that chain can remove the encoder list entries.

3.1 Verify That Compatible Intel Graphics Exist

An Intel CPU alone does not guarantee Quick Sync support. Some Intel processors lack integrated graphics, and certain desktop CPU models are sold with the integrated GPU disabled. Older Intel graphics generations may support only specific codecs or may not meet the requirements of current software paths.

Check the exact CPU model and graphics device in the computer manufacturer's specifications or Intel's official product database. For discrete Intel Arc graphics, verify that the card is detected correctly and that the system meets Intel's high-level platform, firmware, driver, and configuration requirements. Codec availability on Arc still depends on the particular encoder, bit depth, and HandBrake support.

Success means the operating system identifies a real Intel graphics adapter by model, not merely a generic display device.

3.2 Enable the Intel GPU in Firmware and Windows

On a desktop with a separate graphics card, the motherboard may automatically disable the Intel integrated GPU. Enter the BIOS or UEFI setup and look for settings such as integrated graphics, iGPU, internal graphics, multi-monitor, or iGPU multi-monitor. Names vary by manufacturer. Enable the Intel GPU without changing unrelated firmware options.

In Windows, open Device Manager and expand Display adapters. The Intel GPU should appear without a warning symbol. If it is disabled, enable it. If it is completely absent, check firmware settings, processor specifications, and motherboard support before reinstalling HandBrake.

You do not necessarily need to connect the monitor to the Intel video output, but some systems expose the integrated GPU more reliably when it is enabled in firmware. Once Device Manager shows the Intel adapter correctly, restart HandBrake and check the encoder list. If QSV appears, stop changing BIOS settings.

3.3 Install a Working Intel Graphics Driver

A generic Microsoft display driver may provide basic desktop output without exposing the media encoding interfaces HandBrake needs. Install a current graphics driver from Intel or, when required for a laptop or customized system, from the computer manufacturer.

On Windows, confirm that Device Manager names the Intel graphics model rather than showing Microsoft Basic Display Adapter. Restart Windows after installation, even if the installer does not force a restart. Then reopen HandBrake and run the small H.264 QSV test.

If a newer driver caused the problem and QSV previously worked, consult the computer manufacturer or Intel for a supported rollback rather than downloading drivers from an unverified archive. Success is demonstrated by QSV appearing and completing an encode, not merely by a driver installer reporting completion.

3.4 Understand Windows, Linux, FreeBSD, and macOS Differences

HandBrake's Intel QSV documentation covers Windows, Linux, and FreeBSD, but actual availability still depends on the platform build, supported Intel hardware, and a functioning graphics or media driver stack. Windows typically obtains the required components through the Intel graphics driver.

Linux requires the relevant Intel userspace media driver and access to the GPU device, commonly exposed through Direct Rendering Manager device nodes. Distribution packages, container permissions, group membership, kernel support, and the selected Intel media driver can all affect detection. A desktop that renders through Intel graphics does not automatically prove that hardware video encoding is available to HandBrake.

On FreeBSD, availability can depend on the HandBrake package, graphics stack, device permissions, and hardware generation. Check how the installed package was built and whether the operating system exposes the Intel media device before assuming a HandBrake preference is responsible.

On macOS, HandBrake uses Apple's VideoToolbox framework for supported hardware encoding rather than presenting Intel QSV encoders in the same manner as Windows or Linux. Therefore, searching for an Intel QSV label on macOS can lead to a false diagnosis. Inspect the available VideoToolbox encoders instead. If VideoToolbox is available and works, the absence of an Intel QSV label is expected rather than a fault.

3.5 Consider Linux Low-Power Mode and Driver Clues

Some Intel codec and hardware combinations use low-power encoding paths. On Linux, the Activity Log may mention low-power mode, oneVPL, Media SDK compatibility, a VA-API or media-driver component, an initialization failure, or an unsupported implementation. Treat these messages as clues rather than instructions to apply random kernel parameters.

First verify that the distribution's recommended Intel media driver is installed for the GPU generation, that the user running HandBrake can access the render device, and that HandBrake is not isolated by a container or sandbox without GPU access. If a Flatpak, container, or remote session cannot see the render device, compare it with a supported native package or explicitly configured GPU access.

Do not force low-power options unless the hardware, driver documentation, and log indicate they are required. Success means HandBrake initializes the Intel implementation and lists the codec supported by that GPU.

3.6 Separate Source and Output Compatibility Problems

The source file usually does not control whether QSV appears in the encoder list, but it can affect whether a job succeeds. Corrupt timestamps, unsupported decoding formats, unusual bit depths, or extremely large dimensions can cause failure after QSV has been selected.

The destination container and encoder configuration matter more. If a modern codec is unavailable or greyed out, test H.264 QSV in MP4. If that works, the missing H.265 or AV1 choice may reflect the GPU's codec capabilities rather than a broken QSV installation.

Audio and subtitle tracks rarely determine whether the hardware video encoder is visible. However, an unsupported passthrough audio format, subtitle burn-in operation, or complex filter can fail or slow the complete job. For diagnosis, use a basic AAC audio track, disable subtitles, and avoid filters. Add them back only after the video test succeeds.

Finally, do not confuse encoding success with playback compatibility. An older television, browser, phone, or media player may reject HEVC, AV1, 10-bit output, high resolutions, or advanced profiles even though HandBrake encoded the file correctly.

4. Use the Activity Log to Separate Guesswork From Evidence

The HandBrake Activity Log records the hardware and software encoders detected, the chosen job settings, and many initialization errors. Open the log after scanning a source and again after attempting a short encode.

4.1 What to Look For in the Log

• References to Intel QSV, Quick Sync, oneVPL, or an Intel hardware implementation
• The Intel GPU model or adapter selected for the job
• A message stating that no compatible hardware implementation was found
• Driver initialization, device access, memory allocation, or unsupported codec errors
• The actual encoder selected, which confirms whether HandBrake silently used software instead
• On Linux, render-device, permissions, VA-API, media-driver, or low-power path clues

If the log lists Intel hardware and begins encoding with a QSV encoder, detection is working. Investigate the first meaningful error after initialization instead of reinstalling every component. If the log contains no Intel hardware references at all, return to GPU visibility, package support, and drivers.

4.2 Save the Complete Log When Requesting Help

Copy the complete activity log for the failed test, removing personal file paths if necessary. Include the operating system, exact Intel CPU or GPU model, HandBrake source, and whether the Intel adapter appears in the operating system. A screenshot of a greyed-out menu is less useful than a log showing capability detection and the failed job.

Do not share copyrighted source material or attempt to bypass copy protection. Diagnose with media you created, public test media, or content you are authorized to convert.

5. Run a Clean Temporary Encode With Minimal Settings

A controlled test determines whether HandBrake, QSV, or the original job is responsible. Use the following sequence:

1. Restart the computer after confirming the Intel GPU and driver.
2. Open an official HandBrake build.
3. Load a short, known-good video file.
4. Select a built-in general or QSV hardware preset.
5. Choose MP4 as the container.
6. Select H.264 (Intel QSV) as the video encoder.
7. Leave profile, level, frame rate, dimensions, and filters at safe defaults.
8. Use AAC audio and disable subtitle tracks temporarily.
9. Encode 30 to 60 seconds to a local folder with adequate free space.
10. Inspect the Activity Log and play the resulting file.

If this encode succeeds, QSV is working. Stop adjusting drivers, BIOS options, and HandBrake preferences. Rebuild the original job by changing one category at a time, such as codec, dimensions, filters, audio, and subtitles.

If H.264 QSV works but HEVC, AV1, 10-bit, or another variant does not appear, check the codec capabilities of the exact Intel GPU. Hardware generations differ, and HandBrake cannot expose a hardware encoder that the GPU does not implement.

5.1 Why the CPU Can Still Bottleneck QSV

Quick Sync accelerates video encoding, but it does not move every part of a HandBrake job onto the GPU. Source decoding may run on the CPU, and filters such as deinterlacing, denoising, scaling, cropping, subtitle burn-in, and frame-rate conversion can consume substantial CPU resources. Audio encoding, file parsing, and container writing also remain part of the pipeline.

A QSV job can therefore show high CPU usage or run slower than expected while still using the hardware encoder correctly. The Activity Log is the reliable place to confirm encoder selection. Compare a clean encode without filters against the original job before concluding that QSV is not working.

6. Quick Fix Checklist

• Confirm that the exact Intel CPU or Arc GPU supports the desired hardware codec.
• Verify that the Intel graphics adapter is enabled in BIOS or UEFI.
• Confirm that the Intel GPU appears normally in Device Manager or the operating-system hardware tools.
• Install a supported Intel or computer-manufacturer graphics driver.
• Use an official, current HandBrake build for the operating system.
• Enable any applicable Intel hardware encoder preference, then restart HandBrake.
• Test H.264 (Intel QSV) in MP4 with a built-in hardware preset.
• On Linux or FreeBSD, verify the media driver, render-device access, package support, and permissions.
• On macOS, look for VideoToolbox rather than expecting an Intel QSV label.
• Read the Activity Log before changing audio, subtitle, or playback settings.
• Stop troubleshooting once a short QSV test completes and plays correctly.

7. Frequently Asked Questions

7.1 Why Is Intel Quick Sync Missing Even Though I Have an Intel CPU?

The processor may lack integrated graphics, its integrated GPU may be disabled, or its graphics generation may not support the requested codec. A dedicated graphics card can also cause some desktop firmware to disable the Intel GPU automatically. Verify the exact processor model and confirm that an Intel graphics adapter is visible to the operating system.

7.2 Why Does H.264 QSV Appear but H.265 or AV1 QSV Does Not?

Codec support is hardware-specific. An Intel GPU can support H.264 encoding without supporting HEVC, AV1, 10-bit output, or every profile. A working H.264 QSV test proves that the basic Quick Sync path is available. The absent codec may simply exceed the GPU's capabilities.

7.3 Can Reinstalling HandBrake Fix Greyed-Out QSV Encoders?

It can help if the installation is damaged or an unofficial package lacks QSV support, but reinstalling will not enable a disabled GPU or replace a missing Intel media driver. Check the Activity Log and operating-system hardware detection first. If you reinstall, use the official build and retest with default preferences.

7.4 Does the Monitor Need to Be Connected to the Intel GPU?

Not always. Many systems can expose the Intel media engine while a monitor is connected to another graphics card. However, the integrated GPU must remain enabled and visible to the operating system. Firmware behavior differs among motherboard and computer manufacturers.

7.5 Why Is HandBrake Still Using a Lot of CPU With QSV?

QSV accelerates video encoding, not the entire conversion pipeline. Decoding, filters, subtitle burn-in, audio processing, and scaling may still use the CPU. Check the Activity Log for the selected QSV encoder, then compare performance with filters and subtitles disabled.

7.6 When Should I Stop Troubleshooting?

Stop changing system settings when a short H.264 QSV test starts successfully, the Activity Log identifies the Intel hardware encoder, and the output plays correctly. At that point, any remaining failure is likely tied to the original source, codec, preset, filters, audio, subtitles, destination, or playback device rather than QSV detection.