HandBrake 1.6.0, released on December 28, 2022, added AV1 video encoding through two different paths: CPU-based SVT-AV1 and hardware-based Intel Quick Sync Video (QSV). The distinction matters: SVT-AV1 can run without AV1-capable graphics but is generally slower, while QSV requires compatible Intel graphics, drivers, and operating-system support. HandBrake’s download page lists version 1.11.2 as current as of August 18, 2026, so 1.6.0 is now a historical release, not the version most people should install.
What HandBrake 1.6.0 added
The headline change was AV1 encoding, not just the ability to open or play AV1 video. HandBrake 1.6.0 bundled SVT-AV1 1.4.1 for software encoding and added Intel QSV AV1 for compatible hardware. The release also included AV1 decoding through the libdav1d library. See the release announcement and full 1.6.0 release notes.
AV1 is designed to deliver efficient video compression. In suitable conditions, it can produce a smaller file than older codecs at comparable visual quality, but that is not guaranteed: the encoder, settings, source material, and playback target all affect the result. A noisy or grainy source, for example, can be difficult to compress, and a fast hardware encode may prioritize throughput over file size.
Version 1.6.0 also introduced 4K AV1 presets for general use, Intel QSV, and Matroska (MKV). Other release changes included a VP9 10-bit encoder; NVENC and VCN HEVC 10-bit support; additional H.264 and H.265 chroma-subsampling profiles; H.265 4:2:2 support for VideoToolbox on Apple Silicon; Intel Deep Link Hyper Encode support; and updates to deinterlacing, autocropping, scaling, filters, translations, and presets. VP8 presets were removed. The release notes list the full set of changes.
Recommended Free Tools
#1 Best Overall
- Intel Arc A380 Chipset
- 6GB, 96-bit, GDDR6 memory, 15.5 Gbps graphics memory speed
- 3x DisplayPort 2.0 ready, up to 8K@60Hz, 1x HDMI 2.0
SVT-AV1 or Intel QSV: which encoder should you use?
These encoders make different trade-offs. SVT-AV1 runs on the CPU; QSV uses an Intel media engine. Their quality controls are not directly interchangeable, so the same-looking quality number or setting does not make a fair comparison.
| Encoder | What it uses | Best fit | Main trade-off |
|---|---|---|---|
| SVT-AV1 | CPU software encoding | Archival or batch encoding when compression efficiency matters more than turnaround time | Often much slower, with substantial CPU use; speed depends on the processor, preset, resolution, frame rate, filters, and source |
| AV1 QSV | Intel graphics hardware’s media engine | Faster encoding and higher throughput on a compatible system | Requires supported Intel hardware and software; compression efficiency may differ from SVT-AV1 at a similar perceived quality |
Choose SVT-AV1 for time-flexible encodes
SVT-AV1 is the software route in 1.6.0, so it does not require an AV1-capable Intel GPU. It is a reasonable choice when you can let an encode run and want to prioritize file-size efficiency. Expect speed and resource use to vary significantly with the CPU, resolution, preset, and footage; a high-resolution or demanding job can take a long time.
Choose QSV when compatible hardware and speed matter
QSV is intended to accelerate the video-encoding stage using a dedicated media engine. The CPU still handles other parts of the workflow, which can include decoding, filters, audio, subtitles, synchronization, and muxing. HandBrake therefore notes that CPU use can remain high during a QSV encode. Its QSV documentation also explains supported configurations and performance considerations.
What hardware does Intel QSV AV1 require?
“Intel Quick Sync” does not mean every Intel processor can encode AV1. AV1 hardware encoding depends on the graphics or media engine in the specific system, the driver, operating-system support, and whether HandBrake can access that hardware. An Intel CPU may support QSV for other codecs without supporting AV1 encoding.
Rank #2
- Advanced Intel Arc Performance: Intel Arc B570 GPU with 10GB GDDR6 memory on 160-bit bus delivers excellent 1440p gaming and content creation performance
- Next-Gen Xe2-HPG Architecture: Features Intel Xe2-HPG architecture with Xe Matrix Extensions (XMX) for advanced AI acceleration and upscaling technology
- High Clock Speeds: GPU clock speed of 2600 MHz with 19 Gbps memory speed ensures smooth, responsive gaming experiences
- Intel XeSS 2 Technology: Supports Intel Xe Super Sampling 2 for enhanced performance and image quality through AI-powered upscaling
- Efficient Dual Fan Cooling: Dual striped axial fans with 0dB silent cooling technology provide optimal thermal performance during intense gaming sessions
HandBrake’s current QSV documentation lists Coffee Lake, 9th-generation Core, or later systems with Intel HD, Iris Xe, or Arc graphics among supported configurations, with current Intel GPU drivers required on Windows 10 or later. That is current guidance, not a definitive statement of the minimum configuration supported by the original 1.6.0 release. Intel’s codec-support list identifies AV1 encoding for Arc A-Series and B-Series, as well as several Intel Core Ultra graphics families. Check the exact graphics model in Intel’s AV1 support documentation rather than relying on the CPU brand alone.
A discrete Arc card can provide AV1 encoding even if the processor’s integrated graphics cannot. Laptop and desktop configurations can differ, and a capable GPU may still be unavailable to HandBrake if the driver or media stack is missing or outdated.
Windows and Linux considerations
- Windows: Install a current Intel graphics driver and confirm that HandBrake detects the device. The 1.6.0 Windows release required the .NET 6 Desktop Runtime; current HandBrake releases have different runtime requirements. The current download page and release information are the appropriate references for a current installation.
- Linux: Current HandBrake guidance for Intel Arc calls for kernel 6.2 or later, up-to-date Mesa, enabled HuC firmware, and current Intel GPU firmware. The Flatpak distribution may also need the official QuickSync plugin. Requirements can vary by hardware and distribution; consult the current QSV guide.
How to encode AV1 in HandBrake
Encoder names and controls can vary between HandBrake releases and operating systems. In 1.6.0, look for SVT-AV1 for CPU encoding or AV1 QSV for compatible Intel hardware. Do not assume a preset is available just because it appears in documentation: HandBrake can disable hardware presets if it cannot detect a supported device.
- Install HandBrake from its official download page or another official distribution source.
- Open HandBrake and load the source video.
- Choose a destination container. MP4 is often a practical starting point for broader compatibility; MKV may suit workflows that need Matroska features. Neither container guarantees playback on every device.
- Open the Video tab and select SVT-AV1 for CPU encoding or AV1 QSV (or the equivalent label in your version) for supported Intel hardware.
- Choose the encoder’s quality or speed settings. Treat them as encoder-specific: do not assume a numeric value matches the quality of a different encoder.
- Use the source frame rate as a starting point, and avoid filters you do not need. Filters and other pipeline work can affect both speed and output.
- Check the audio and subtitle tracks, then encode a short, representative sample.
- Inspect the sample’s picture quality, file size, encode time, and playback on the devices that matter. If it meets your needs, queue the full job.
The original 1.6.0 preset documentation lists names including “Fast 2160p60 4K AV1,” “HQ 2160p60 4K AV1 Surround,” “Super HQ 2160p60 4K AV1 Surround,” “AV1 MKV 2160p60 4K,” and “AV1 QSV 2160p60 4K.” These indicate HandBrake’s intended speed, quality, and file-size positioning; they do not guarantee a particular result for every source. See the 1.6.0 official preset list.
Rank #3
- Next-Gen Intel Arc Graphics: Powered by Intel Arc A580 GPU with Intel Xe HPG microarchitecture, featuring 384 XMX engines for enhanced AI acceleration and content creation.
- High-Performance Memory: 8GB GDDR6 on a 256-bit interface running at 16 Gbps, delivering excellent bandwidth for 1440p gaming and creative workloads.
- Factory Overclocked: Engine clock set at 2000 MHz out of the box, providing optimized performance for smooth gameplay and multimedia tasks.
- Advanced Dual-Fan Cooling: Features a dual-fan design with striped axial fans and an ultra-fit heatpipe for efficient thermal management. 0dB Silent Cooling stops fans completely at low temperatures for silent operation.
- Durable Construction: Includes a stylish metal backplate for enhanced PCB rigidity and a premium aesthetic, backed by ASRock's Super Alloy components for long-term reliability.
How to check that QSV is actually working
- Confirm that the AV1 QSV encoder is selectable rather than missing or disabled.
- Check HandBrake’s activity log for the encoder selected and any initialization errors.
- Monitor GPU media-engine activity with your operating system’s performance tools, if available.
- Run short tests against the same source using QSV and SVT-AV1. Compare elapsed time and visual results, not merely matching slider numbers.
High CPU utilization alone does not prove that QSV failed: HandBrake still uses the CPU for other stages of the encode. Conversely, selecting a hardware-oriented preset is not proof that the hardware encoder initialized successfully. HandBrake’s preset documentation and QSV guide describe hardware availability and related caveats.
Quality, speed, and file size: make a fair test
AV1’s compression efficiency is a potential advantage, not a promised file-size reduction. The outcome depends on the footage, encoder, preset, quality target, bit depth, and filters. QSV may finish sooner while producing a larger file than a more time-intensive software encode; that is a throughput-versus-compression trade-off, not necessarily a malfunction.
For a useful comparison, encode a representative clip from the material you actually plan to convert. Include difficult scenes, such as motion, fine detail, or grain. Judge the result at normal viewing size on the intended display, and note both encode time and file size. Do not compare SVT-AV1’s quality number directly with QSV, x264, or x265: the scales and encoder behavior are not equivalent.
Will an AV1 file play on your devices?
Encoding support and playback support are separate. A device or app may handle AV1 in one container but not another, or support AV1 video while lacking efficient decoding for a particular bit depth. Check the complete playback chain: television, phone, browser, desktop player, media server, and the target application.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #4
- 2GB/GDDR5/64-bit: Expertly designed by ASUS, with more performance than built-in solutions
- One-slot design: Fits in a small case, leaving room for additional expansion cards
- Super quite: Silent passive cooling is perfect for quite home theater PCs and multimedia centers.
- HDMI x4: Supports up to four high-definition displays for enhanced multitasking and productivity
- Easy to install: Plug and play - no cables from the power supply are needed
- Verify support for AV1 in the chosen container, MP4 or MKV.
- Check whether the device supports the output bit depth, including 10-bit, and any HDR features in the file.
- Consider whether AV1 decoding is hardware-accelerated; a device without suitable decoding may rely on software or struggle with playback.
- Test the audio and subtitle combination too. A video stream that is supported does not guarantee that every track or container feature is.
- If a media server transcodes the file, check whether it can decode and deliver the chosen format without an unwanted conversion.
Before converting a large library, test a short file on every important playback device. Keep an H.264 or HEVC version when older hardware or an unknown audience makes compatibility more important than storage savings.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting AV1 and QSV problems
AV1 is missing from the encoder list
First check whether SVT-AV1 is available. If it is, software AV1 encoding may work even when the system cannot use QSV. If AV1 QSV is missing, confirm that the graphics hardware supports AV1 encoding, update HandBrake and the graphics driver, and check the activity log. On Linux, verify the relevant media components and, for Flatpak, whether the QuickSync plugin is installed. Missing hardware AV1 does not necessarily mean HandBrake lacks all AV1 encoding.
QSV is disabled, fails, or is unexpectedly slow on Linux
Check the kernel, Mesa, HuC firmware, Intel firmware, and Flatpak plugin requirements for your setup. HandBrake documents a possible workaround for affected low-power QSV configurations: set lowpower=0 in the encoder’s advanced options. The GUI advanced-options format is option1=value1:option2=value2; the CLI equivalent is --encopts="option1=value1:option2=value2". Save a new preset after changing the option. This setting is not a universal fix for Linux QSV problems; see the QSV troubleshooting documentation.
The CPU remains busy during a QSV encode
This can be normal because QSV accelerates video encoding, not every step in HandBrake’s pipeline. Decoding, filters, audio, subtitles, synchronization, and muxing can still use the CPU.
Best Value
- Intel ARC A310, 4GB GDDR6
- 4x HDMI Display Output
- SPARKLE Exclusive 50W Design
- Single-fan, Single-slot configuration
The AV1 output will not play
Try the file in a current desktop player to distinguish a device limitation from an encode problem. Then check container support, bit depth, HDR, audio, and subtitles. If an older device cannot decode AV1 reliably, try a compatible format such as H.264 or HEVC rather than assuming that changing the container alone will solve it.
Should you install HandBrake 1.6.0 today?
For a new installation, use the current release unless you have a specific reason to reproduce a 1.6.0-era workflow. The HandBrake download page lists version 1.11.2 as current on August 18, 2026; later releases can differ in bundled libraries, available features, interface labels, and platform requirements. Download only from HandBrake’s official site, its GitHub repository, or Flathub, as directed by the official download page.
If you must run 1.6.0 on Windows, its release notes called for the .NET 6 Desktop Runtime; do not apply that historical requirement to current versions. The 1.6.0 announcement also warned that custom presets might not be compatible with newer versions, so export or back them up before upgrading. Older releases are available through HandBrake’s download archive.
Other tools and when they make sense
HandBrake remains a focused, preset-driven transcoder. FFmpeg is a more scriptable option for automation and precise command-line workflows, while Shutter Encoder offers a graphical interface for a broader set of media operations. They are alternatives for different workflows, not automatic replacements for HandBrake. Official project pages: FFmpeg and Shutter Encoder.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
