AV1 vs HEVC for Plex: Quality and Size Compared
Published 2026-10-16 · PlexBeam
AV1 and HEVC are the two modern codecs competing for space in Plex libraries. Both deliver dramatically better compression than H.264. AV1 compresses further — but encodes slower and has less client support. HEVC is faster to encode and plays on more devices — but produces larger files. This guide compares them with real-world data relevant to Plex server operators.
Compression Efficiency
At equivalent visual quality:
| Metric | AV1 (SVT-AV1) | HEVC (x265) |
| File size at same quality | Baseline | 20-30% larger |
| Quality at same bitrate | Better | Good |
| 4K HDR efficiency | Excellent | Very good |
| Low bitrate performance | Significantly better | Good |
The gap widens at lower bitrates. For streaming at 4-8 Mbps (common for remote Plex users), AV1 looks noticeably better than HEVC. At high bitrates (20+ Mbps), the difference is subtle.
Encoding Speed
Encoding speed matters for batch conversion of existing libraries:
Software Encoding
- HEVC (x265 medium preset): A 2-hour 1080p movie encodes in roughly 2-4 hours on a modern 8-core CPU.
- AV1 (SVT-AV1 preset 6): The same movie takes 4-8 hours. SVT-AV1 is the fastest AV1 software encoder but still significantly slower than x265.
- AV1 (libaom preset 4): Reference encoder. Extremely slow — 20-60 hours for a single movie. Not practical for batch conversion.
Hardware Encoding
- HEVC (NVENC): Near real-time encoding. A 2-hour movie in 15-30 minutes on an RTX 3060 or newer.
- HEVC (Quick Sync): Similar speed to NVENC on 10th Gen+ Intel.
- AV1 (NVENC, RTX 4000+): Near real-time. Quality is good but below software AV1 encoding.
- AV1 (Quick Sync, 12th Gen+): Fast but quality lags behind NVENC AV1 and software AV1.
Plex Client Compatibility
This is the decisive factor for most Plex operators:
HEVC Compatibility
- NVIDIA Shield TV: Yes
- Apple TV 4K (all generations): Yes
- Fire TV Stick 4K (all generations): Yes
- Roku Ultra: Yes
- Smart TVs (2018+): Generally yes
- Web browsers: Limited (Safari yes, Chrome/Firefox partial)
- Mobile devices (2018+): Generally yes
AV1 Compatibility
- NVIDIA Shield TV: No (Tegra X1 lacks AV1)
- Apple TV 4K (2022+ A15): Yes
- Fire TV Stick 4K Max (2nd gen): Yes
- Chromecast with Google TV (2022): Yes
- Smart TVs (2022+): Generally yes
- Web browsers: Yes (all modern browsers)
- iPhone 15 Pro+: Yes
- Older devices: No
HEVC has significantly broader compatibility today. The NVIDIA Shield — one of the most popular Plex clients — cannot direct play AV1.
Storage Savings
For a library of 1,000 movies averaging 8 GB each in H.264:
- Convert to HEVC: Average file size drops to approximately 4-5 GB. Total library: 4-5 TB (savings of 3-4 TB).
- Convert to AV1: Average file size drops to approximately 3-4 GB. Total library: 3-4 TB (savings of 4-5 TB).
AV1 saves roughly 1 TB more than HEVC for a 1,000-movie library. Whether that extra saving justifies the slower encoding and reduced client support depends on your priorities.
Quality at Specific Bitrates
For Remote Streaming (4-10 Mbps)
Remote Plex users often watch at reduced bitrate due to bandwidth constraints. At these bitrates:
- AV1 at 6 Mbps looks as good as HEVC at 8-10 Mbps.
- AV1 preserves fine detail and reduces blocking artifacts better than HEVC at the same bitrate.
- Dark scenes and gradients — traditionally problem areas for compression — look significantly better in AV1 at low bitrates.
For Local Direct Play (20+ Mbps)
At high bitrates where both codecs have plenty of bits to work with, the visual difference is minimal. Both AV1 and HEVC look transparent (indistinguishable from the source) at 20+ Mbps for 1080p content.
Transcoding Considerations
When a client cannot direct play the codec, the Plex server transcodes. The codec choice affects transcoding load:
- HEVC source: Hardware HEVC decode is widespread. Intel 7th Gen+, NVIDIA GTX 1050+, and AMD Polaris+ all handle it. Server impact is moderate.
- AV1 source: Hardware AV1 decode requires Intel 12th Gen+ or NVIDIA RTX 4000+. Without these, AV1 software decode crushes the CPU. A single 4K AV1 transcode can consume 8-16 cores.
If your server lacks hardware AV1 decode and some users have older devices, AV1 files create a severe transcoding bottleneck.
Recommendation by Scenario
Choose HEVC When
- Your users have mixed devices (some pre-2022).
- Your server lacks hardware AV1 decode.
- You want to convert your library quickly (faster encoding).
- You use an NVIDIA Shield as a primary client.
Choose AV1 When
- All your users have 2022+ devices.
- Your server has hardware AV1 decode (Intel 12th Gen+ or RTX 4000+).
- Storage savings are a priority and you can wait longer for encoding.
- You primarily serve remote users at lower bitrates where AV1's advantage is largest.
Hybrid Approach
Maintain HEVC as your primary library format for universal compatibility. Encode new content in AV1 if your hardware supports it and your user base is trending toward modern devices. As older devices are retired, gradually convert the library to AV1 for the storage and quality benefits.
Future Outlook
AV1 adoption is accelerating. Every major chip maker now includes AV1 hardware decode in new products. Within 2-3 years, AV1 compatibility will approach what HEVC has today. Libraries encoded in AV1 now are future-proofed, while HEVC libraries will remain compatible indefinitely but miss the compression gains.