AV1 Codec Support and Transcoding in Plex
AV1 is the newest major video codec in the Plex ecosystem. It delivers better compression than HEVC — roughly 30% smaller files at the same visual quality — and it is royalty-free. But support across Plex clients and server hardware varies widely. Some devices direct play AV1 natively. Others require the server to transcode, and not all servers have hardware that can decode or encode AV1 efficiently. This guide covers the current state of AV1 in Plex.
What AV1 Offers
- Better compression: AV1 produces smaller files than HEVC at equivalent quality. A 1080p movie encoded in AV1 is typically 20-30% smaller than the same movie in HEVC at the same visual quality.
- Royalty-free: No licensing fees. HEVC has a complex patent licensing situation that has slowed adoption. AV1 avoids this entirely.
- Modern features: Built-in support for 10-bit color, HDR, film grain synthesis, and efficient encoding of screen content.
Client Direct Play Support
AV1 direct play depends entirely on the client device having AV1 hardware decode:
| Device | AV1 Direct Play |
| NVIDIA Shield TV Pro (2019) | No (Tegra X1 lacks AV1 decode) |
| Google Chromecast with Google TV (4K, 2022) | Yes |
| Amazon Fire TV Stick 4K Max (2nd gen) | Yes |
| Apple TV 4K (2022, A15 chip) | Yes |
| Roku Ultra (2024) | Yes |
| Samsung TVs (2022+) | Yes (via built-in Plex app) |
| LG TVs (2023+) | Yes (via built-in Plex app) |
| Web browsers (Chrome, Edge, Firefox) | Yes (software decode) |
| iPhone 15 Pro and newer | Yes |
| Older devices | No — requires server transcode |
The divide is generational. Devices from 2022 onward generally include AV1 hardware decode. Older devices do not.
Server Hardware for AV1 Transcoding
When a client cannot direct play AV1, the Plex server must transcode it to H.264 or HEVC. AV1 decoding is computationally expensive — hardware acceleration is essential.
Hardware AV1 Decode
- Intel 12th Gen+ (Alder Lake): Hardware AV1 decode via Quick Sync. The iGPU can decode AV1 and encode to H.264 or HEVC for client delivery.
- NVIDIA RTX 4000 series: Hardware AV1 decode via NVDEC. Combined with NVENC for output encoding.
- AMD RDNA 3: Hardware AV1 decode. Plex support depends on driver and platform.
Software AV1 Decode
Without hardware AV1 decode, the server falls back to software decoding using the CPU. AV1 software decode is significantly more demanding than H.264 or HEVC. A single 4K AV1 transcode can consume 8-16 CPU cores. Multiple simultaneous AV1 transcodes are not feasible with software decode on typical server hardware.
AV1 Encoding in Plex
Plex currently transcodes AV1 source files to H.264 or HEVC for delivery to incompatible clients. Plex does not encode output streams in AV1 — the transcoder outputs in H.264 (most common) or HEVC based on client capability.
Hardware AV1 Encode
- Intel 12th Gen+: Can encode AV1 via Quick Sync. Fast but quality lags behind software encoding.
- NVIDIA RTX 4000 series: NVENC AV1 encoding. Best hardware AV1 encode quality currently available.
Even though these GPUs can encode AV1, Plex's transcoder pipeline typically encodes to H.264 for maximum client compatibility. AV1 output encoding may be used in future Plex versions.
When to Use AV1 Files
Good Use Cases
- Storage-constrained libraries: AV1 files are 20-30% smaller than HEVC. For large libraries, this saves significant storage.
- Modern client fleet: If all your Plex users have devices from 2022 or newer, AV1 direct plays everywhere.
- Web-only users: Modern browsers decode AV1 efficiently. If your users primarily watch through the Plex web app, AV1 works well.
Poor Use Cases
- Mixed device fleet: If users have older devices (Shield TV, older Roku, pre-2022 Fire TV), AV1 files trigger server transcoding for every playback.
- Server without hardware AV1 decode: Software AV1 transcoding is too CPU-intensive for reliable real-time playback.
- 4K HDR content for mixed clients: 4K HDR AV1 to 1080p SDR transcoding combines the heaviest decode (AV1) with tone mapping — extremely demanding.
Dual-Library Strategy
Until AV1 client support is universal, consider maintaining two versions of frequently watched content:
- AV1 versions for clients that can direct play them (smaller files, better quality-per-bit).
- HEVC or H.264 versions for older clients that cannot handle AV1.
This uses more storage but eliminates transcoding entirely. Users are directed to the library matching their device capability.
Converting to AV1
If you want to start building an AV1 library:
- FFmpeg with libaom-av1: Software encoding. Highest quality but very slow — a 2-hour 1080p movie may take 8-24 hours depending on speed settings.
- FFmpeg with libsvtav1 (SVT-AV1): Faster software encoding with good quality. The recommended encoder for batch conversion.
- NVIDIA NVENC AV1: Hardware encoding on RTX 4000+. Fast with good quality. Use
-c:v av1_nvencin FFmpeg. - Intel Quick Sync AV1: Hardware encoding on 12th Gen+. Fast but slightly lower quality than NVENC.
Always encode from the highest quality source available. Converting from H.264 or HEVC to AV1 is a generational loss — quality never improves, only file size decreases.
Troubleshooting
AV1 File Triggers Transcoding on a Supported Device
- Check the specific AV1 profile and level. Some devices support AV1 Main profile but not High profile.
- Verify the device firmware is updated. AV1 decode may have been added in a firmware update.
- Check the audio track — an incompatible audio codec can force a full transcode even if the video would direct play.
AV1 Transcode Stutters or Buffers
- Server lacks hardware AV1 decode. Add a GPU with AV1 support or convert files to HEVC for broader compatibility.
- Reduce the output bitrate to give the transcoder more headroom.
- Check if the transcoder temp directory is on an SSD.