If you have a 3 hour 1080p video that is only 5.2 GB, it is already pretty heavily compressed. Potentially a better comparison is what happens if you feed NVENC a 36 GB file and then run the AV1, H.265, and H.264 encoders through it. They should all be a lot smaller than the source, but do the files get progressively larger as you move to the older codecs? Another test might be to change the compression level on your AV1 job. How small can you get it through NVENC before new artifacts becomes noticeable? Maybe NVENC doesn't correlate exactly with the software encoder. Answer from DataMeister1 on reddit.com
🌐
Reddit
reddit.com › r/handbrake › the point of av1 nvenc?
r/handbrake on Reddit: The point of AV1 NVENC?
February 10, 2024 -

Since I recently got a RTX4090, I ran a little comparison AV1 encoding in Handbrake between software (SVT) and NVENC.

The same system was used for both runs, Ryzen 9 5900X, 64GB RAM, RTX4090, latest nvidia drivers as of yesterday 2/9/24, latest Handbrake as of same date, Win10x64.

Input file was the same, my standard video that I use for testing: a 3h 1920x1080 25fps h.264 recording of a concert. Input file size 5.2GB.

Software SVT AV1 encoding using standard preset took 1h58min. File size was reduced to 3GB. Visual quality subjectively indistinguishable from the input file on a 4k monitor.

NVENC AV1 encoding using the exact same settings otherwise, took 9min 56s. File size increased to 10.1GB. Visual quality same.

Isn't the whole point of AV1 to preserve visual quality while reducing file size? The NVENC AV1 does not do that. Software encoder does, at the cost of 12x longer encoding time (on this particular system I use).

At this time, I don't see the point of someone using NVENC for AV1 encoding in its current state. Unless they were in a hurry and didn't care for file size, which in my opinion is an unlikely scenario.

Am I missing something here?

🌐
GitHub
github.com › HandBrake › HandBrake › issues › 4605
NVEnc AV1 support ? · Issue #4605 · HandBrake/HandBrake
October 14, 2022 - Description of the feature or enhancement you'd like to see in HandBrake The new 4000 series, have AV1 encode and decode acceleration, can we expect to see this implemented in HandBrake ? For now I only see H.264&H.265 Nvidia NVenc, no A...
Author   HandBrake
Discussions

AV1 versus H.265 with NVENC
I couldn't find any differences visually, but file size is bit smaller in AV1 than H265. More on reddit.com
🌐 r/handbrake
18
0
November 14, 2024
Nvenc AV1 is out on latest snapshot builds.. thoughts of quality?
My OP was a little misunderstood I guess, to everyone who responded,, I'm comparing Turing/Ampere HEVC encoding to Ada Lovelace AV1. It's known that x265 at Faster and higher still produces a better end result than even Nvidia AV1, software encoders of previous generations beat even the newest hardware AV1. The point i'm driving is that i'm seeing no gains/advantages from Nvenc HEVC to NVenc AV1.. I tried low bitrates, average ones, higher ones, and I cannot see any benefits/improvements to fast scene quality or in static scenes. Perhaps NVenc AV1 encoders (Rigaya/Handbrake's implementation specifically) are in their infancy and can be improved. But at the same time, i'm pretty sure the API is set in stone IN the AV1 encoder on the GPU, you can't improve it's quality.. Or i'm doing something completely wrong, there seems to be no options in the Handbrake implementation for NVEnc AV1 but i've used command line Rigaya's NVenc which doesn't have much for AV1, but you can increase the B frames, lookahead, etc.. I guess i'm expecting too much this early on and afraid that there's no real gains over HEVC hardware encoding. Edit: I am using single pass with a set bitrate instead of CRF because CRF values are not equal from HEVC to AV1.. More on reddit.com
🌐 r/handbrake
10
5
March 21, 2023
Sharing my best settings for video compression on handbrake: NVENC vs CPU with H264 /H265 / AV1 on a RTX 4070
Did you disable the psy-vis options in x265? Otherwise using objective metrics like SSIM/PSNR/VMAF is misleading at best, and really dishonest. x265 will be both faster and score higher on objective measures with psy-vis disabled, even if it looks worse to actual humans watching the video. For VMAF comparisons, the best x265 tune is probably PSNR (disables adaptive quant, psy-rd, and cutree) since there's no tune VMAF. Also fast isn't a particularly well balanced x265 preset, I'd try both veryfast and slow. More on reddit.com
🌐 r/handbrake
18
8
September 26, 2024
AV1 10-bit (NVENC) 8 bit and 10 bit have exactly the same file size only in the nightly version
Problem Description I encoded the same video into 8 and 10 bits, but both have exactly the same file size only in the nightly version In version 1.7.1 the file sizes were different and it was notic... More on github.com
🌐 github.com
4
December 18, 2023
🌐
9to5Linux
9to5linux.com › home › news › apps › handbrake 1.7 released with amd vcn av1 and nvidia nvenc av1 encoders
HandBrake 1.7 Released with AMD VCN AV1 and NVIDIA NVENC AV1 Encoders - 9to5Linux
November 16, 2023 - HandBrake 1.7 open-source video transcoder app is now available for download with AMD VCN AV1 and NVIDIA NVENC AV1 encoders, Linux updates.
🌐
YouTube
youtube.com › watch
AV1 NVENC Transcoding on RTX 40 Series using HandBrake Nightly Build no OBS or Video Editors Needed - YouTube
As of upload date HandBrake does not have NVENC AV1 encoding yet but after a little searching I found that using their nightly build it has support for AV1 N...
Published   July 23, 2023
🌐
Wccftech
wccftech.com › home › hardware › handbrake adds av1 support for nvidia rtx 40 “ada” & amd rx 7000 “rdna 3” gpus
Handbrake Adds AV1 Support For NVIDIA RTX 40 "Ada" & AMD RX 7000 "RDNA 3" GPUs
November 18, 2023 - Developers behind Handbrake were a bit late when it came to supporting current-gen mainstream GPUs, since in the previous 1.60 update, the tool debuted with AV1 encoding for Intel's QuickSync. The tool now has the option to utilize AMD's VCN AV1 encoder exclusive to RDNA 3 "Radeon RX 7000" GPUs, as well as NVIDIA's NVENC AV1 encoder featured on GeForce RTX 40 "Ada" GPUs.
🌐
Tom's Hardware
tomshardware.com › pc components › gpus
HandBrake AV1 video transcoding gets hardware speed boost on both AMD and Nvidia GPUs | Tom's Hardware
November 19, 2023 - HandBrake Team this week released HandBrake 1.7.0 which adds support for hardware-accelerated AV1 transcoding on the latest graphics processors from AMD and Nvidia. As a result, HandBrake 1.7.0 now supports hardware-accelerated AV1 transcoding ...
Find elsewhere
🌐
VideoCardz
videocardz.com › news › graphics › video coding & streaming
Handbrake 1.7.0 released, supports AV1 encoding on GeForce RTX 40 and Radeon RX 7000 GPUs - VideoCardz.com
November 17, 2023 - AV1 encoding for everyone (with supported hardware) Handbrake stable gets support for AV1 encoding for supported NVIDIA and AMD GPUs Finally, the 1.7.0
🌐
XDA Developers
xda-developers.com › home › news › handbrake 1.7.0 adds amd and nvidia av1 encoding support
HandBrake 1.7.0 adds AMD and Nvidia AV1 encoding support
November 17, 2023 - Users with RDNA3 graphic cards can now use HandBrake's AMD VCN AV1 encoder, while GeForce RTX 40 graphics card owners can use the Nvidia NVENC A1 encoder.
🌐
Reddit
reddit.com › r/handbrake › nvenc av1 is out on latest snapshot builds.. thoughts of quality?
r/handbrake on Reddit: Nvenc AV1 is out on latest snapshot builds.. thoughts of quality?
March 21, 2023 -

I've been doing some playing around with the new Nvenc AV1 10bit encoder in Handbrake (as well as Rigaya's tool) and unfortunately regular NVEnc h265 still offers more detailed quality, especially under 1000kbit.. It seems like NVenc AV1 is over-smoothing everything.. anyone else experiencing the same thing? Maybe there's a certain point of bitrate where AV1 takes over? I was hoping for that up to 30% more gains bit for bit but i'm definitely not seeing it (using various side-by-side video comparison tools and the like), nor am I seeing motion handling any better with a static bitrate.

Top answer
1 of 3
1
My OP was a little misunderstood I guess, to everyone who responded,, I'm comparing Turing/Ampere HEVC encoding to Ada Lovelace AV1. It's known that x265 at Faster and higher still produces a better end result than even Nvidia AV1, software encoders of previous generations beat even the newest hardware AV1. The point i'm driving is that i'm seeing no gains/advantages from Nvenc HEVC to NVenc AV1.. I tried low bitrates, average ones, higher ones, and I cannot see any benefits/improvements to fast scene quality or in static scenes. Perhaps NVenc AV1 encoders (Rigaya/Handbrake's implementation specifically) are in their infancy and can be improved. But at the same time, i'm pretty sure the API is set in stone IN the AV1 encoder on the GPU, you can't improve it's quality.. Or i'm doing something completely wrong, there seems to be no options in the Handbrake implementation for NVEnc AV1 but i've used command line Rigaya's NVenc which doesn't have much for AV1, but you can increase the B frames, lookahead, etc.. I guess i'm expecting too much this early on and afraid that there's no real gains over HEVC hardware encoding. Edit: I am using single pass with a set bitrate instead of CRF because CRF values are not equal from HEVC to AV1..
2 of 3
1
30% gains with a good encoder. Unfortunately it takes time to write, or to create in hardware, a good encoder, and hardware encoders have the not small disadvantage that they can't not be improved in software. I guess they can do some small improvements and tune some parameters, but nothing too big. The next version of the Nvenc AV1 will surely be better, but you will have to buy a new GPU to use it 🤷‍♂️ Disclaimer: I didn't test it.
🌐
Reddit
reddit.com › r/handbrake › sharing my best settings for video compression on handbrake: nvenc vs cpu with h264 /h265 / av1 on a rtx 4070
r/handbrake on Reddit: Sharing my best settings for video compression on handbrake: NVENC vs CPU with H264 /H265 / AV1 on a RTX 4070
September 26, 2024 -

I've often heard that NVENC offers great speed but lower quality or larger file sizes, so I ran some benchmarks to see for myself. I compared file sizes, compression time, and quality using the FFMetrics tool on my RTX 4070 GPU and AMD 5800X CPU.

I used a 1.8GB H.264 720p video as the source and aimed to compress it to 550MB with a target VMAF score of 90 (a quality measure comparing the original to the compressed version).

Note: These results are based on a single test run, and outcomes may vary depending on your hardware and file types. My goal was fast compression with acceptable quality, prioritizing smaller file sizes.

Results:

  1. CPU (H.265, fast, quality 25):

    • 592MB, VMAF: 87.98, took 20 minutes.

  2. H.265 NVENC (slow, quality 32):

    • 556MB, VMAF: 87.66, 778 avg fps (97 seconds).

  3. AV1 NVENC (medium, quality 38):

    • 558MB, VMAF: 89.62, 1051 avg fps (72 seconds).

AV1 NVENC was the clear winner with faster compression speeds, comparable file size, and better quality.

Conclusion:

If you have an Nvidia GPU, use the AV1 NVENC encoder for fast compression and good quality. I recommend setting quality to 38 with the medium speed preset in Handbrake for optimal results.

In Handbrake you can take the preset that is on Hardware section and just adjust the quality and dimensions you want.

🌐
HandBrake
handbrake.fr › docs › en › 1.7.0 › technical › video-codecs.html
HandBrake Documentation — Video codecs
In hardware: Intel QuickSync, AMD VCE, Nvidia NVENC and ARM devices though MediaFoundation.
🌐
GitHub
github.com › HandBrake › HandBrake › issues › 5606
AV1 10-bit (NVENC) 8 bit and 10 bit have exactly the same file size only in the nightly version · Issue #5606 · HandBrake/HandBrake
December 18, 2023 - t": "0", "crop-right": "0", "crop-top": "0", "height": "1080", "width": "1920" } }, { "ID": 11, "Settings": { "mode": "0" } } ] }, "PAR": { "Num": 1, "Den": 1 }, "Metadata": {}, "SequenceID": 0, "Source": { "Angle": 1, "Range": { "Type": "chapter", "Start": 1, "End": 1 }, "Title": 1, "Path": "f:\\handbrake test\\test.ts", "HWDecode": 4 }, "Subtitle": { "Search": { "Burn": false, "Default": false, "Enable": false, "Forced": false }, "SubtitleList": [] }, "Video": { "Encoder": "nvenc_av1_10bit", "Level": "auto", "MultiPass": false, "Turbo": false, "ColorMatrixCode": 0, "Options": "", "Preset": "
Author   HandBrake
🌐
GitHub
github.com › HandBrake › HandBrake › issues › 6945
Add Tune UHQ for AV1_NVENC, feature of NVENC 13.0 · Issue #6945 · HandBrake/HandBrake
June 7, 2025 - I can use NVENC 13.0's Tune UHQ for AV1 through FFMPEG on my RTX 4070 Ti and RTX 5060 Ti, but Handbrake is missing out.
Author   HandBrake
🌐
GitHub
github.com › HandBrake › HandBrake › issues › 5123
Nvenc AV1 presets not functioning as intended. · Issue #5123 · HandBrake/HandBrake
May 5, 2023 - Using NVENC AV1(not 10bit), I tested Presets Slowest, Medium and Fastest, all producing identical file outputs. I started with the Fast 1080p30 preset, changed the FPS to constant 60 and the bitrate to 6000kbps. I could reproduce this on someone elses machine. If there is anything else you need, I am happy to provide it. HandBrake ...
Author   HandBrake
🌐
Reddit
reddit.com › r/handbrake › new to handbrake and i have 3 beginner questions on various settings.
r/handbrake on Reddit: New to handbrake and I have 3 beginner questions on various settings.
March 27, 2025 -

I’m looking to convert my library to all AV1. I’ve been reading about how AV1 encoding is creating better quality and smaller file sizes than h.265. All my devices stream from Plex and I have a few AV1 files that playback fine so I’d like to capture the advantages of AV1 for my library. My goal is to retain quality while maximizing shrinking the file size. There is no speed constraints(and solar panels so free power) as I have a spare PC that will do nothing but run handbrake and these files will maybe only get played once every few years and largely sit in an archive on my Plex Server. My library is all h.264 and h.265.

  1. My first question is on the video tab under the video encoder dropdown. I see 4 AV1 options. AV1 (SVT), AV1 10-bit (SVT), AV1 (NVEnc), and AV1 10-bit(NVEnc). What’s the difference between those 4 and which is generally the best for my objective of maximum file size shrinkage with no-minimal file quality loss?

  2. On the same video tab under encoder options there is a slider named Encoder preset that goes from 13 to -1. It says this trades off compression efficiency vs compression speed. For my use case I believe I want maximum efficiency and minimal speed(please correct me if I’m wrong). It doesn’t say what the numbers represent. Is 13 max efficiency and min speed or is -1 max efficiency and min speed?

  3. Same video tab under quality is there an ideal number for my objective? It suggests 20-23 for HD sources which my content is all 1080p or 4k. It says 0 would give me a higher file size(which I don’t want, but would going to 63 ruin the quality). Given speed is of no concern for me are there any suggestions on what to go for?

Thank you in advance for any guidance.

Top answer
1 of 5
7
SVT-AV1 is a branch of AV1 that preserves the same quality as AV1 with a much faster speed. Handbrake doesn’t support the other (AOM AV1) because the quality is essentially the same, but it’s much much slower. Your NVENC encoder is your hardware encoder, it’s mostly meant for on-the-fly encoding. NVENC is built for speed at the cost of quality, so for your purposes you’ll want to use the software encoder; SVT-AV1. I would also suggest always using 10-bit encoders even if your video isn’t in 10-bit, as it’s a more advanced color compression that will further reduce the size, and eliminate any color banding if possible. So, your optimal encoder is SVT-AV1 10-bit. A higher number (13) will give you a faster speed at the cost of lower quality. A lower number (-1) will be slower with better quality. I wouldn’t suggest using -1 though, as it’s mostly used for benchmarking, and sometimes gives worse results than faster presets. So, if you truly don’t care about speed, go with preset 0 However, that is really slow, so if you don’t want to wait… months (depending on the size of your library) I’d suggest something a bit faster. If you have a good enough CPU then experiment with 4-1. I don’t know where you’re looking or getting those numbers from, but look at the official handbrake quality guide , which suggests an RF value of 25-35 for SVT-AV1 1080p sources. This affects speed very minimally, as this setting is mostly the balance between quality and file size. A higher number (35) will result in a smaller file size at a worse quality than a lower number (25) being higher quality at a greater file size. I don’t know your priorities in terms of file size / quality, but I personally start seeing a quality loss at RF 25/26 from my Blu Ray rips with my 4K color grading monitor, so it may be slightly more for you - depending on how your viewing it and your source quality. Follow the linked guide, start in the middle and adjust from there based on the size/quality tradeoff you want. Bonus: Every time you encode you lose quality. The more preserves the original video is, the better the encoded video will be, and the better compressed it is. Encode from the source files if you still have them. If not, then consider if it’s worth decreasing the size of your library for any kind of quality loss. Again, experiment with the RF values. If this is purely through Plex, it will automatically transcode any incompatible video for delivery to the client, so you don’t have to worry about comparability, and is probably why you haven’t had any problems playing AV1 so far, so it’s not guaranteed your device supports AV1.
2 of 5
2
I can answer a few of your questions: NVEnc doesn't support Dolby Vision, but AV1 SVT does. So, if you're compressing a 4K source and want to keep your Dolby Vision metadata, 10-bit SVT is the only way. Try some test encodes and see how you feel about them. Personally, I compress at a higher quality than most because if I wanted to see compression artifacts I would just fire up Netflix. Compression artifacts are especially noticeable in dimly lit scenes, primarily in the shadows.
🌐
GitHub
github.com › HandBrake › HandBrake › issues › 6418
NVENC AV1 CQ range wrong · Issue #6418 · HandBrake/HandBrake
November 16, 2024 - Problem Description Hi, the current NVENC AV1 "Constant Quality" (CQ) range in HandBrake is 0-51. However the range actually supported by the encoder is 0-63. See: FFmpeg/FFmpeg@aead614 A...
Author   HandBrake