HandBrake AV1 Encoder Not Showing: How to Fix It

If the HandBrake AV1 encoder is not showing, the cause usually falls into one of three categories: the installed HandBrake build does not include the expected encoder, the computer lacks compatible hardware or drivers for hardware AV1 encoding, or a preset and container choice is creating the wrong expectation. Playback compatibility is a separate issue. HandBrake may successfully encode AV1 even when the resulting file will not play smoothly on an older television, phone, browser, or media box.

The most important distinction is between software and hardware encoding. A software AV1 encoder such as SVT-AV1 runs on the CPU and does not require an AV1-capable graphics processor. Intel QSV AV1 and other hardware encoders require specific GPU generations, suitable drivers, operating-system support, and a HandBrake build capable of accessing that hardware. Work through the following checks in order, and stop as soon as the expected encoder appears and completes a short test encode.

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

Before reinstalling drivers or changing advanced settings, confirm exactly what is missing. Open a short, ordinary video file in HandBrake. A basic MP4 or MKV containing H.264 video is a useful test because it removes optical-disc scanning, unusual codecs, damaged files, and copy-protection issues from the diagnosis.

After HandBrake finishes scanning the source, open the Video tab and inspect the Video Encoder menu. Do not rely only on the names in the Presets panel. A preset is a collection of settings, while the Video Encoder menu shows the encoders HandBrake can actually offer in the current environment.

1.1 Identify What Is Actually Missing

There are several different symptoms that users may describe as the HandBrake AV1 encoder not showing:

• No AV1 option appears anywhere in the Video Encoder menu.
• A software AV1 option appears, but Intel QSV AV1 is missing.
• AV1 appears in the encoder menu, but no dedicated AV1 preset is visible.
• The encoder appears initially but fails when the encode starts.
• The encode succeeds, but the destination device cannot play the file.

These symptoms do not have the same fix. If software AV1 is available but QSV AV1 is absent, HandBrake already has AV1 support and the remaining question concerns hardware detection. If the encoder is selectable and starts encoding, stop trying to make it appear. Any later playback problem should be investigated as a compatibility issue instead.

1.2 Run a Short Range Test

Select a general preset, choose MP4 or MKV as the format, and set the range to a few seconds or one chapter if the source supports chapters. Select the AV1 encoder you want to test and send the output to a local folder with ample free space.

Success means the queue starts, video frames are encoded, and HandBrake creates a playable output file. Once that happens, the encoder is available. There is no benefit in reinstalling HandBrake or changing graphics drivers solely because an AV1-named preset is absent.

2. Check the HandBrake Settings Directly Related to This Problem

2.1 Install a Current Official HandBrake Build

Confirm that HandBrake came from the official HandBrake website or the official distribution channel identified by the project. Old packages maintained by an operating-system repository can lag behind the current release, while unofficial or customized builds may have a different collection of libraries and hardware integrations.

Open HandBrake's About window and note the displayed version and build information. Compare it with the current release offered by the official project. If the installation is old or its origin is uncertain, uninstall it and install the current official build for the operating system.

Success means a software AV1 encoder appears in the Video Encoder menu after HandBrake restarts, assuming the official build supports it on that platform. If software AV1 appears but a hardware AV1 choice remains absent, the HandBrake installation is probably no longer the main problem.

2.2 Distinguish Software AV1 From Intel QSV AV1

Software AV1 and Intel QSV AV1 are not interchangeable labels for the same capability. SVT-AV1 performs encoding on the CPU. It can therefore be available on a computer whose GPU has no AV1 encoder. CPU encoding may be considerably slower, particularly on older processors or at high resolutions, but GPU generation is not what determines whether the software encoder exists in the menu.

Intel QSV AV1 uses Intel's Quick Sync Video path and requires Intel graphics hardware with AV1 encoding capability. The mere presence of an Intel CPU, an Intel integrated GPU, or a Quick Sync logo does not guarantee AV1 hardware encoding. Many older Intel platforms support hardware H.264 or H.265 encoding but not AV1 encoding.

If SVT-AV1 is visible and QSV AV1 is not, success may simply mean using SVT-AV1. Continue troubleshooting only if hardware encoding is specifically required and the computer's exact Intel GPU model officially supports AV1 encode, not merely AV1 decode.

2.3 Check the Encoder Menu Rather Than Preset Names

HandBrake presets are starting points. They can choose a codec, resolution, frame rate behavior, quality setting, audio configuration, and container, but the absence of an AV1 preset does not prove that the encoder is unavailable.

Choose a general preset, open the Video tab, and manually inspect the encoder list. If AV1 can be selected and a short encode completes, the problem is solved. Save a custom preset afterward if you want an easily reusable AV1 configuration.

2.4 Use a Suitable Container

MKV is a practical troubleshooting container because it accommodates a broad range of video, audio, and subtitle combinations. MP4 can also carry AV1, but the rest of the playback chain must understand the resulting combination of container, codec, profile, audio, and subtitles.

For diagnosis, use MKV first if an existing MP4 preset behaves unexpectedly. This does not make an unavailable hardware encoder appear, but it can separate encoder detection from muxing or compatibility failures. Success means the encode begins and produces a valid MKV file. You can test MP4 afterward if your intended players require it.

3. Check Hardware, Drivers, Sources, and Playback Factors

3.1 Verify AV1 Encode Support for the Exact GPU

Look up the exact GPU model rather than relying on a family name such as Intel Graphics, NVIDIA GeForce, or AMD Radeon. Hardware AV1 decoding and hardware AV1 encoding are separate capabilities. A GPU may play AV1 efficiently but be unable to create AV1 video.

Intel Arc discrete graphics include models with hardware AV1 encoding, while many older Intel integrated graphics generations do not. Some newer integrated Intel graphics also provide AV1 encoding, but capability depends on the specific processor and graphics architecture. Likewise, only supported generations of competing GPUs expose their respective AV1 hardware encoders.

On Windows, identify the display adapters in Device Manager or Task Manager. On macOS, use System Information. On Linux, use the desktop system-information utility or tools supplied by the distribution. If a machine has both integrated and discrete graphics, record both models.

If the manufacturer's specification says only AV1 decode, no HandBrake setting or driver update can add a physical AV1 encoder. Use software AV1 or another hardware codec such as H.264 or H.265. That is the correct stopping point for older hardware.

3.2 Update the Graphics Driver

A compatible GPU still needs a driver that exposes its media engine correctly. Install the current stable graphics driver supplied by the GPU manufacturer or, when appropriate for a laptop, the computer manufacturer. Restart the system after installation so HandBrake can rescan the available hardware interfaces.

Windows users should also check whether Device Manager shows a generic display adapter, which can indicate that the full vendor driver is missing. Linux users need a compatible graphics stack, kernel, media driver, permissions, and device access. Running HandBrake inside a container, sandbox, virtual machine, or remote session can prevent it from seeing the host GPU even when the hardware itself supports AV1.

Success means the relevant hardware encoder appears after the restart and completes a small encode. If the exact GPU supports AV1 encode but the option remains absent, the Activity Log should be checked before more software is installed.

3.3 Account for Multi-GPU and Disabled Graphics Configurations

Some desktop systems disable integrated graphics when a discrete card is installed. Some laptops dynamically switch between graphics processors. If the AV1-capable device is disabled in firmware, hidden by a virtual environment, or unavailable to the current session, HandBrake cannot use it.

Confirm that the AV1-capable adapter is enabled and visible to the operating system. Connect displays and adjust firmware settings only according to the computer manufacturer's documentation. Do not make speculative firmware changes merely to expose an encoder that the hardware does not support.

3.4 Simplify the Source File

A complex source can make an encoder issue look more mysterious than it is. Test with a short, locally stored MP4 or MKV file that opens correctly in a trusted player. Avoid beginning the diagnosis with a damaged recording, network file, unusual variable-frame-rate capture, incomplete camera transfer, or optical disc.

HandBrake can process DVDs and Blu-ray sources that it can read, but this guide does not recommend bypassing access controls or copying material without permission. If an optical source fails to scan, test the encoder with a normal video file first. An encoder that works with the simple file is not missing. The original source requires separate investigation.

3.5 Reduce Audio and Subtitle Complexity

Audio and subtitle settings usually do not determine whether AV1 appears in the Video Encoder menu. They can, however, cause an encode or muxing job to fail after AV1 has been selected.

For a clean test, keep one audio track and encode it to a broadly supported format such as AAC. Remove subtitle tracks temporarily, especially bitmap subtitles, imported files, or tracks configured to burn into the picture. Disable passthrough options during the test if the source audio format may not fit the selected container.

Success means a minimal file encodes correctly. Add required audio and subtitle tracks back one at a time. Stop changing video encoder settings when the failure returns only after a particular audio or subtitle option is restored.

3.6 Confirm Playback Compatibility Before Committing to AV1

Encoding support does not guarantee playback support. Older televisions, phones, streaming boxes, browsers, editing programs, and operating systems may lack AV1 decoding or may support only certain AV1 profiles, resolutions, frame rates, bit depths, or containers.

Before converting a large library, make a one-minute sample using the intended container, resolution, frame rate, audio format, and subtitle configuration. Test that exact file on every important destination device. Software playback on a computer may work while a television's hardware decoder rejects the same file.

Success means the sample plays with normal video, audio, seeking, and subtitle behavior on the actual destination. If it does not, use a more compatible codec such as H.264 or H.265, or adjust the container and ancillary tracks. Do not confuse this playback decision with HandBrake encoder availability.

4. Use the Activity Log to Separate Guesswork From Evidence

HandBrake's Activity Log records the application build, source scan, selected encoder, hardware detection, filters, audio and subtitle handling, destination details, and errors returned during the job. It is the most useful evidence when HandBrake is not working as expected.

4.1 What to Look For in the Log

Open the Activity Log after scanning the source and again after attempting a short encode. Look for:

• The HandBrake version and platform near the beginning of the log.
• The selected video encoder in the job configuration.
• Messages about Quick Sync, hardware devices, or unavailable implementations.
• Driver initialization or permission failures.
• Source decoding errors that occur before encoding begins.
• Container, audio, subtitle, storage, or destination write errors.

If the log identifies a software AV1 encoder and shows encoded frames, AV1 is functioning. If it reports that a hardware device cannot be initialized, concentrate on the exact GPU, driver, operating-system access, and multi-GPU configuration. If it fails while reading the source, replace the source for testing instead of repeatedly changing the encoder.

4.2 Preserve the Full Log When Requesting Help

Save the complete log for the failed test rather than copying only the final error line. The earlier sections provide context about hardware detection and selected settings. Remove personal file paths if necessary, but do not remove the encoder and platform information needed for diagnosis.

A useful support request should state the operating system, HandBrake version, installation source, exact CPU and GPU models, selected encoder, container, and whether a software AV1 option is visible. This turns a vague HandBrake troubleshooting question into a specific hardware or configuration problem.

5. Run a Clean Temporary Encode With Minimal Settings

A clean test establishes whether the encoder works independently of an old preset or complicated source. It should not overwrite your existing presets or source media.

1. Restart HandBrake and open a short local MP4 or MKV source.
2. Select a standard general preset as the starting point.
3. Choose MKV as the temporary output container.
4. Open the Video tab and select the available software or hardware AV1 encoder.
5. Leave advanced encoder options empty or at their defaults.
6. Keep one audio track and encode it to AAC.
7. Remove subtitle tracks for this temporary test.
8. Choose a writable local destination with sufficient free space.
9. Encode a short range and inspect the Activity Log.

If this test works, the HandBrake installation and chosen encoder are functional. Reintroduce the original container, preset adjustments, audio tracks, subtitles, filters, and source one at a time. The first restored element that causes failure identifies the next area to investigate.

If software AV1 is still absent in a current official build, collect the Activity Log and verify the installation platform and package source. If only hardware AV1 is absent, compare the exact GPU's published specifications with the encoder you expected. Do not continue changing quality, frame rate, or audio settings because those controls cannot create missing hardware capability.

6. Quick Fix Checklist

• Install the current official HandBrake build for your operating system.
• Check the Video Encoder menu, not only the preset list.
• Look for software AV1 separately from Intel QSV AV1.
• Verify that the exact GPU supports AV1 encode, not only decode.
• Install a suitable current graphics driver and restart the computer.
• Confirm that the AV1-capable GPU is enabled and visible to the operating system.
• Test with a short local MP4 or MKV source.
• Use MKV, one AAC audio track, and no subtitles for the first test.
• Read the Activity Log for hardware initialization or source errors.
• Test the finished sample on the intended playback device.

Stop changing settings when the expected encoder completes a short encode and the output works on the intended device. At that point, save the successful configuration as a custom preset and add optional features gradually.

7. Frequently Asked Questions

7.1 Why Is SVT-AV1 Available but Intel QSV AV1 Missing?

SVT-AV1 is a software encoder that runs on the CPU. Intel QSV AV1 requires Intel graphics hardware with AV1 encoding capability, plus compatible drivers and operating-system access. An older Intel processor may support Quick Sync for H.264 or H.265 without supporting AV1 hardware encoding.

7.2 Does an AV1-Capable GPU Always Support AV1 Encoding?

No. Product descriptions sometimes use AV1 support to mean hardware decoding for playback. Encoding is a separate capability. Check the manufacturer's detailed specifications for the exact GPU or processor and confirm that AV1 encode is explicitly listed.

7.3 Why Is There No AV1 Preset Even Though AV1 Appears in the Video Menu?

Presets and encoders are different. HandBrake may expose an AV1 encoder without presenting a preset whose name contains AV1. Select a general preset, choose AV1 manually in the Video tab, complete a test, and save a custom preset if needed.

7.4 Can Installing a New Driver Add AV1 Encoding to an Old GPU?

A driver can expose supported hardware correctly, but it cannot add a physical AV1 encoding engine to a GPU that lacks one. If the GPU does not support AV1 encode, use the software AV1 encoder or select another codec supported by the available hardware.

7.5 Why Does the AV1 File Encode Successfully but Fail to Play?

The player or device may not support AV1, the chosen container, the encoded profile, the bit depth, the resolution, or one of the audio and subtitle formats. Test a short sample on the actual destination device before running a long encode. A playback failure does not mean the HandBrake encoder was missing.

7.6 Should I Use Software AV1 or Hardware AV1?

Use software AV1 when hardware encoding is unavailable or when its speed and output characteristics suit the project. Use hardware AV1 when the system supports it and faster encoding is a priority. Compare short samples at practical settings rather than assuming one encoder is best for every source. Playback compatibility should be confirmed regardless of which encoder produced the file.