跳转到主要内容
Formats & playback 5 min read

Why HDR Video Looks Washed Out: The Compatibility Truth

Video shot in HDR mode looks rich on your own display and flat gray on everyone else’s — the file isn’t broken. HDR and SDR display pipelines are speaking different languages.

What separates HDR from SDR

SDR (standard dynamic range) is the CRT-era standard: about 100 nits of peak brightness and a limited color gamut — decades of video were mastered inside this safe range. HDR records 1000+ nits plus the wider BT.2020 gamut: highlights truly bright, shadows layered, colors denser.

The extra data only pays off through a chain that can read it: an HDR-capable screen and a player that understands HDR metadata. Any missing link turns the extra information into a source of misinterpretation.

The wash-out mechanism

On a non-HDR screen or player, the bright data gets mapped wrongly: a 1000-nit sun squeezed into a 100-nit standard. The result is not "darker" but a collapsed contrast curve — chalky skies, bloodless faces, muted colors. The file is intact; the display side translated it badly.

That is also why "fine on my screen, gray after upload": your device speaks HDR, the receiving chain does not. One file, two pipelines, two different looks.

Spotting it and fixing it

Confirming HDR: run a codec inspection for two tells — a 10-bit pixel format (yuv420p10le and friends; SDR mainstream is 8-bit) and color characteristics naming bt2020 / PQ / HLG. Most HDR video is HEVC-encoded (H.264-era HDR is rare), so an "unopenable HEVC file" deserves an HDR-mode question first.

Fixes depend on the receiver: for devices or platforms without HDR support, prepare an SDR version — the cleanest fix is switching HDR off at capture time. Converting existing HDR footage to SDR requires tone mapping; a plain transcode without mapping stays gray. Major platforms auto-map on upload, but quality varies — a self-made SDR version stays in your control.

Frequently asked questions