4K HDR Streaming in Plex: Server, Network, and Client Setup
Getting 4K HDR content to stream reliably through Plex requires the entire chain to work: the server must handle the files, the network must carry the bitrate, and the client must decode the codec and display the HDR metadata. When any link breaks, you get buffering, washed-out colors, or an unnecessary transcode that degrades the image. This guide covers each piece.
Server-side requirements
The server's job in a 4K HDR direct play scenario is simple — read the file and send it. No GPU or CPU transcoding is needed. Any modern CPU with SATA or NVMe storage can serve multiple 4K direct play streams simultaneously.
The server becomes important when transcoding is involved. A 4K HDR file that must be transcoded (because the client cannot handle HEVC, or because tone mapping is needed for an SDR display) demands significant GPU resources. For this workload:
- Intel Quick Sync (11th gen+): Handles 2-3 simultaneous 4K HDR tone mapping sessions. Built into the CPU, no extra hardware
- NVIDIA NVENC (Turing+): Handles 3-5 simultaneous 4K HDR transcodes with better tone mapping quality than older Intel generations. Requires a discrete GPU and Plex Pass
- CPU-only: A single 4K HDR transcode can saturate an 8-core CPU. Not practical for more than one simultaneous stream
Plex Pass is required for hardware transcoding. Without it, all transcoding uses the CPU regardless of available GPU hardware.
Network bandwidth
4K content has high bitrate requirements that many home networks underestimate:
- 4K remux (Blu-ray quality): 50-100 Mbps per stream. A 4K HDR remux of a visually complex film can sustain 80+ Mbps during action sequences
- 4K compressed (high quality encode): 15-40 Mbps depending on encoder settings and source complexity
- 4K transcoded (Plex adaptive): 8-20 Mbps at typical Plex quality settings
For local streaming, Gigabit Ethernet handles any 4K stream easily. WiFi is more variable — 802.11ac (WiFi 5) on the 5 GHz band delivers 200-400 Mbps in practice, enough for one or two 4K remux streams if the signal is strong. WiFi 6 improves reliability for multiple simultaneous streams. Older 2.4 GHz connections cannot sustain 4K remux bitrates.
For remote streaming, your upload bandwidth is the bottleneck. Serving a 4K remux remotely requires 80+ Mbps sustained upload — most residential connections cannot provide this. Remote 4K usually requires either transcoding to a lower bitrate or pre-optimizing files to 15-20 Mbps.
Client device compatibility
Not all Plex clients handle 4K HDR equally. The client must support three things: HEVC decoding (nearly all 4K content uses HEVC/H.265), HDR metadata processing (HDR10 at minimum, ideally HDR10+ and Dolby Vision), and sufficient network connectivity.
Clients that reliably direct play 4K HDR:
- NVIDIA Shield Pro: The most compatible Plex client for 4K HDR. Supports HEVC, HDR10, HDR10+, Dolby Vision (player-led), and lossless audio passthrough
- Apple TV 4K (2021+): Excellent 4K HDR support including Dolby Vision. Some lossless audio formats require transcoding to a compatible format
- Amazon Fire TV Stick 4K Max: Good HEVC and HDR10 support. Dolby Vision support varies by generation. Budget-friendly option
- Smart TV built-in apps: Quality varies dramatically by manufacturer and model year. Samsung, LG, and Sony TVs from 2020+ generally support HEVC and HDR10. Older models often force transcoding
Clients that typically cannot direct play 4K HDR: web browsers (no HEVC support in Chrome or Firefox), older Roku models (some lack HEVC), and most game consoles (PlayStation and Xbox Plex apps have limited HDR support).
Plex server settings for 4K HDR
Key settings in Plex Web under Settings → Transcoder:
- Use hardware acceleration when available: Enable this. Even if most streams direct play, the ones that need transcoding will use the GPU instead of overwhelming the CPU
- Use hardware-accelerated video encoding: Enable this alongside the above setting
- Enable HDR tone mapping: Enable this if you have users with SDR displays. Without it, HDR content played on an SDR display looks washed out and low contrast. With it, Plex converts HDR to SDR using the GPU
- Maximum simultaneous video transcode sessions: Set this based on your hardware. Prevents your server from accepting more transcodes than it can handle, which would cause all streams to stutter
Client-side settings
The most common cause of unnecessary 4K transcoding is the client's quality setting being too low. In each Plex client app:
- Set local streaming quality to Original or Maximum
- Set remote streaming quality to Original if your upload bandwidth supports it, otherwise set it to the highest quality your connection can sustain
- Enable "Allow Direct Play" and "Allow Direct Stream" if those options appear
- Disable "Automatically Adjust Quality" unless you are on a highly variable connection — it can trigger unnecessary transcodes during momentary bandwidth dips
When HDR looks wrong
If colors look washed out, overly bright, or have a green/purple tint during HDR playback:
- Washed out on an SDR display: Tone mapping is not active. Confirm it is enabled in Plex server settings and that your GPU supports it (NVIDIA Turing+ or Intel 11th gen+ for best results)
- Washed out on an HDR display: The display may not be switching to HDR mode. Check the display's input settings — many TVs require HDR to be enabled per HDMI port (often labeled "Enhanced" or "HDMI Deep Color")
- Green or purple tint: Usually a color space conversion error. Update GPU drivers. On Linux, ensure NVIDIA driver 525+ or Intel Mesa 23.0+. If the problem persists, disable hardware tone mapping and test with software fallback
- HDR badge missing on content you know is HDR: Plex reads HDR metadata from the file. If the metadata is missing or the file was encoded incorrectly, Plex treats it as SDR. Use MediaInfo to verify the file actually contains HDR metadata
Separating 4K and non-4K libraries
Many Plex users maintain separate libraries for 4K and 1080p versions of the same content. This prevents a situation where a client that cannot handle 4K accidentally triggers a 4K transcode when a 1080p version would have direct played. Plex does not automatically select the lower-resolution version for less capable clients — it serves whatever is in the library the user browses. Separate libraries let users (or you as the admin) point capable clients at the 4K library and everyone else at the 1080p library.
Related Articles
More Articles
Browse our full library of guides and tutorials.