4K Direct Play in Plex: Device and Network Requirements
Direct play sends the original media file to the client unchanged — no transcoding, no quality loss, no server CPU usage. For 4K content, direct play is not optional. 4K transcoding is resource-intensive, often produces visible quality degradation, and can overwhelm servers that handle 1080p transcodes easily. Getting every 4K stream to direct play is the single most important optimization for a 4K Plex library. This guide covers exactly what is needed.
Why 4K Must Direct Play
Transcoding a 4K file means the server decodes the original 4K stream and re-encodes it in real time — typically to a lower resolution or different codec. The problems:
- Quality loss: Re-encoding 4K to 1080p at streaming bitrates produces noticeably worse output than a native 1080p encode. The transcoder has less time and fewer bits than the original encoder had.
- Server load: A single 4K HEVC to 1080p H.264 transcode uses 2-4x more resources than a 1080p to 1080p transcode. A server that handles 15 simultaneous 1080p transcodes may manage only 3-4 4K transcodes.
- HDR issues: Transcoding 4K HDR content to SDR without proper tone mapping produces washed-out, unwatchable output. Hardware tone mapping (10th Gen+ Intel, Pascal+ NVIDIA) handles this, but not every server has it.
- Buffering: 4K source files have high bitrates (40-100+ Mbps). Real-time transcoding at these input rates requires sustained disk and CPU/GPU throughput. Any hiccup causes buffering.
Client Device Requirements
The client must natively decode the codecs used in your 4K files. The most common 4K codecs:
| Codec | Common In | File Size |
| HEVC (H.265) 10-bit | Most 4K content | Moderate |
| HEVC HDR10 | Standard 4K HDR | Moderate-Large |
| HEVC Dolby Vision | Premium 4K releases | Moderate-Large |
| AV1 | Newer streaming content | Smaller |
| H.264 4K | Some older 4K encodes | Very large |
Client Compatibility by Device
| Device | HEVC 4K | HDR10 | Dolby Vision | Atmos | AV1 |
| NVIDIA Shield Pro | Yes | Yes | Yes | Yes | Yes |
| Apple TV 4K (2022+) | Yes | Yes | Yes | Yes | Yes |
| Chromecast with Google TV 4K | Yes | Yes | Yes | DD+ Atmos | Yes |
| Amazon Fire TV Stick 4K Max | Yes | Yes | Yes | DD+ Atmos | No |
| Roku Ultra | Yes | Yes | No (DV profile 5) | DD+ only | Yes |
| Roku Streaming Stick 4K | Yes | Yes | No | DD+ only | Yes |
| Xbox Series X/S | Yes | Yes | Yes | Yes | Yes |
| PlayStation 5 | Yes | Yes | No | No | No |
| Plex Web (browser) | Varies by browser | No | No | No | Varies |
| Smart TV apps (LG/Samsung) | Yes | Yes | Varies | Varies | Varies |
The NVIDIA Shield Pro and Apple TV 4K (2022+) are the most capable Plex clients for 4K direct play. They support virtually every codec, container, HDR format, and audio format without triggering a transcode.
Display Requirements
The TV or projector must support the signal being sent:
- 4K resolution: The display must accept 3840x2160 input. Sending 4K to a 1080p display forces Plex to transcode down to 1080p.
- HDR: For HDR10 and Dolby Vision content, the display must support the respective HDR standard. Sending HDR to an SDR display triggers server-side tone mapping (transcoding).
- HDMI 2.0 or later: HDMI 2.0 supports 4K at 60fps with HDR10. HDMI 2.1 adds support for higher frame rates and enhanced Dolby Vision profiles.
Network Requirements
Minimum Bandwidth
4K direct play sends the full original bitrate to the client. Network throughput must exceed the file's bitrate with headroom:
- 4K streaming encodes: 15-25 Mbps. A 100 Mbps network handles these easily.
- 4K high-bitrate encodes: 40-60 Mbps. Gigabit wired is comfortable. Good Wi-Fi 5 or Wi-Fi 6 handles this.
- 4K remuxes: 60-100+ Mbps. Wired gigabit recommended. Wi-Fi works if signal is strong and no other devices are competing for bandwidth.
Local vs Remote
Local 4K direct play on a wired gigabit network has no bandwidth issues — even multiple simultaneous 4K remux streams fit within gigabit capacity.
Remote 4K direct play requires upload bandwidth matching the file's bitrate. Most home internet connections have 10-50 Mbps upload — far below what 4K remuxes need. For remote 4K, either use lower-bitrate 4K encodes (15-25 Mbps) or accept that remote users will get transcoded 1080p instead.
Plex Settings for Direct Play
Client Settings
- Quality: Set to Original or Maximum on every 4K client. Any quality setting below Original forces a transcode.
- Direct Play: Ensure Allow Direct Play is enabled in the client's advanced settings.
- Direct Stream: Enable Allow Direct Stream as a fallback. Direct stream remuxes the video without re-encoding — the video quality is identical to direct play.
Server Settings
- Remote stream bitrate: If set too low in Settings, Remote Access, remote clients cannot direct play high-bitrate 4K files. Set to Original or the highest value your upload bandwidth supports.
- Transcoder settings: The transcoder quality setting does not affect direct play. It only matters when transcoding occurs.
Separate 4K Library Strategy
Many Plex users maintain separate libraries for 4K and 1080p versions of the same content:
- 4K Library: Shared only with users and devices that can direct play 4K. Quality set to Original for these users.
- 1080p Library: Shared with all users including those on mobile, web browsers, and remote connections with limited upload bandwidth.
This prevents 4K files from being transcoded to 1080p when a client cannot handle them. Instead, the client plays the native 1080p version — which looks better than a real-time transcode from 4K and uses zero server resources.
How to Set Up
- Store 4K and 1080p versions in separate folders (e.g.,
/media/movies-4k/and/media/movies/). - Create separate Plex libraries for each.
- Share the 4K library only with users whose devices and connections support 4K direct play.
- All users get the standard 1080p library.
Common Direct Play Blockers
Subtitles
PGS and ASS/SSA subtitles require server-side burn-in, which forces a video transcode. Use SRT (text-based) subtitles instead — Plex clients render these locally without transcoding.
Audio Codec
If the client cannot play the audio codec (e.g., TrueHD Atmos on a device that only supports AAC), Plex transcodes the audio. This may also trigger a video transcode depending on the container format. Files with both a lossless and a compatible lossy audio track (e.g., TrueHD + AAC) allow the client to select the compatible track without transcoding.
Container Format
Some clients cannot direct play certain container formats. MKV is universally supported on most Plex clients. MP4 is also widely supported. Unusual containers (AVI, WMV, TS) may trigger a remux or transcode on some devices.
Troubleshooting
4K File Transcoding Despite Capable Client
- Check the client's quality setting — it may be set to something other than Original.
- Check Plex Dashboard or Tautulli for the specific transcode reason. It shows whether the trigger is video codec, audio codec, subtitle, or bandwidth limit.
- Verify the client is on a wired connection or strong Wi-Fi. Weak Wi-Fi triggers automatic quality reduction.
HDR Content Looks Washed Out
- The display does not support HDR, or the HDMI chain is not configured for HDR passthrough.
- Check TV settings — some TVs require enabling HDR per HDMI input (Enhanced Signal Format, HDMI Deep Color, or similar setting name).