October 6, 2026 · PlexBeam
You download a beautiful 4K HDR movie, hit play on your 1080p TV, and the image looks washed out with pale faces, blown-out skies, and flat contrast. That is what happens when HDR content plays on an SDR display without proper tone mapping. The HDR color and brightness data needs to be compressed into the narrower SDR range, and how that compression happens determines whether the result looks great or terrible.
HDR video encodes brightness information using a Perceptual Quantizer or Hybrid Log-Gamma transfer function that can represent peak brightness levels far beyond what SDR displays can reproduce. HDR also uses the BT.2020 color space, which covers a wider range of colors than the BT.709 color space used by SDR content. Tone mapping is the process of converting both the luminance and color information from the wider HDR range into the narrower SDR range while preserving as much of the original artistic intent as possible.
The tone mapping algorithm must make decisions about how to compress the dynamic range. Simply clipping values that exceed the SDR range produces harsh highlights and lost detail. A good tone mapping curve gradually compresses the brightness range so that highlights remain visible and shadows retain detail, even though the absolute range is narrower than the HDR original. The best algorithms preserve relative contrast relationships so that the image looks natural on an SDR display even though it lacks the peak brightness and color gamut of the HDR version.
Plex includes built-in tone mapping that activates automatically when an HDR source is transcoded for an SDR client. When a client device does not support HDR playback, Plex detects the mismatch and applies tone mapping during the transcode process. The result is an SDR stream that preserves the intended look of the content rather than the washed-out image you would see without tone mapping.
Software tone mapping runs on the CPU and is available on any Plex server regardless of GPU. It produces good results but is computationally expensive. A single 4K HDR to SDR transcode with software tone mapping can consume an entire modern CPU, leaving no headroom for additional streams or other server tasks. For servers that handle occasional HDR transcodes with minimal concurrent users, software tone mapping works but scales poorly.
Hardware tone mapping offloads the tone mapping computation to the GPU alongside the video decode and encode operations. This is dramatically more efficient than software tone mapping and allows the server to handle multiple simultaneous HDR to SDR transcodes without the CPU bottleneck. Plex supports hardware tone mapping on NVIDIA GPUs with NVENC and Intel processors with Quick Sync, provided the hardware generation is recent enough to include the necessary capabilities.
The quality difference between hardware and software tone mapping has narrowed significantly in recent Plex versions. Early hardware tone mapping implementations produced noticeably different results from the software path, but current implementations are visually comparable for most content.
HDR10 uses static metadata that defines a single set of brightness parameters for the entire movie. The maximum content light level and maximum frame average light level values tell the tone mapper the brightest point in the entire movie. Because these values represent the absolute maximum, the tone mapping curve must be conservative enough to handle the brightest scene while still producing acceptable results in darker scenes. This one-size-fits-all approach works reasonably well but can produce suboptimal results in scenes whose actual brightness is far below the metadata maximum.
Dolby Vision and HDR10+ include per-scene or per-frame metadata that describes the brightness characteristics of each individual scene. This allows the tone mapper to optimize its curve for each scene independently, producing better results than static metadata across the full duration of the movie. However, Plex tone mapping support for dynamic metadata formats is more limited than for HDR10, and the dynamic metadata may be discarded during transcoding, falling back to the HDR10 base layer.
Not every GPU that supports hardware transcoding supports hardware tone mapping. The capability requires specific hardware features that are only present in certain GPU generations.
The most effective optimization is eliminating the need for tone mapping by using client devices that support HDR playback natively. When the client handles HDR directly, Plex sends the original HDR stream without any server-side processing. Modern streaming devices, recent smart TVs, and gaming consoles generally support HDR10 at minimum.
Check the Plex dashboard during an active HDR transcode to confirm that hardware tone mapping is being used. If the dashboard shows software transcoding despite having a capable GPU, the issue may be a driver version, a Plex server version, or a configuration setting preventing hardware acceleration.
If you have both HDR and SDR versions of the same content, maintaining separate libraries prevents SDR clients from accidentally triggering HDR transcodes. Share the SDR library with users whose devices do not support HDR, and the HDR library only with users who have capable displays and clients.
PlexBeam handles HDR to SDR tone mapping on dedicated remote GPUs, providing hardware-accelerated conversion for all your remote users without requiring a local GPU or consuming server CPU resources.
Why tone mapping and 10-bit encoding crush CPUs and most GPUs.
The three Plex playback modes and what triggers each one.
Configure lossless surround sound passthrough for DTS, Dolby Atmos, and TrueHD.
Join the pre-beta waitlist and lock in 50% off for life.
Claim My Early-Adopter Spot →