HDR is a combination of content, metadata, transfer function and display capability. A file can carry HDR metadata and still look wrong on a display or player that does not handle it correctly. A TV that accepts an HDR signal may not reproduce the full brightness or color range the content describes.
FAST-VID does not promise HDR preservation or HDR output and does not expose HDR selection or conversion controls. This guide explains the format differences and the compatibility chain.
What HDR means
Dynamic range is the difference between the darkest and brightest parts of an image. SDR formats have a conventional range and transfer function. HDR content is mastered for a wider range, with brighter highlights and often a wider color gamut.
HDR is not simply “more contrast.” It involves a transfer function that maps code values to light, color primaries, metadata about the intended mastering display and content brightness, and a display capable of reproducing enough of that range.
A higher peak brightness specification does not guarantee a better picture. Contrast, black level, local dimming, color volume, tone mapping and room lighting all affect the result.
HDR10, HDR10+, Dolby Vision and HLG
HDR10 is a widely used HDR format based on static metadata. The metadata can describe the mastering display and content light levels, but it does not change per scene. It is commonly associated with 10-bit HEVC and BT.2020 primaries.
HDR10+ adds dynamic metadata, allowing brightness information to change scene by scene or frame by frame. The display still has to support the format and apply the metadata correctly.
Dolby Vision is a proprietary HDR system that can use dynamic metadata and its own processing and certification requirements. Support depends on the device, player, content and license chain; not every Dolby Vision file is handled the same way.
HLG (Hybrid Log-Gamma) was designed for broadcast and is defined in ITU-R BT.2100 alongside PQ. It can be displayed on SDR displays with some compatibility, but the result is not identical to a dedicated HDR presentation. A player or display still needs to handle HLG correctly.
Static and dynamic metadata
HDR metadata describes the intended presentation: mastering display characteristics, maximum content light level, maximum frame-average light level and, for dynamic formats, scene-specific information. It is guidance for the display’s tone-mapping process.
Static metadata gives one set of values for the title. Dynamic metadata can adjust the target as the content changes. Dynamic metadata is not automatically “better” if the display, player or content pipeline ignores it or implements it poorly.
Metadata is separate from the codec and container. A file may use HEVC, AV1 or another codec and carry HDR information in a particular way. The player must understand both the codec and the HDR signaling.
The compatibility chain
HDR playback requires the source file, container, codec, HDR metadata, player software, graphics pipeline, cable, display input and panel to work together. A failure at any point can produce SDR fallback, washed-out colors, clipped highlights or an unsupported-format message.
Some TVs enable HDR only on specific HDMI inputs or require an “enhanced” input setting. A receiver or soundbar in the chain may not pass the format. A computer may tone-map HDR to SDR while on battery or when the display mode changes.
Apple’s HDR support page, for example, notes that compatible Macs, macOS, an HDR10 display and the right cable/adapter are all required, and that HDR may be converted for an external HDR10 display. That is a useful illustration of the chain: format support is not just a file property.
Tone mapping and incorrect-looking HDR
Tone mapping compresses the content’s brightness and color range to fit a display. A good tone mapper preserves the creative intent; a poor one can make highlights dull, shadows muddy or colors oversaturated.
If HDR looks washed out, the player may be sending HDR content to an SDR display without proper mapping. If highlights are clipped, the display may lack the brightness or local dimming needed for the intended grade. If colors look strange, the color primaries or transfer function may be misinterpreted.
Do not judge HDR from a still frame alone. Motion, highlight detail and the viewing environment matter. Compare the same scene in SDR and HDR on the target display when possible.
Format support versus panel performance
A device can decode an HDR format without reproducing its full intent. “HDR10 compatible” may mean the input is accepted and tone-mapped, not that the panel reaches the mastering brightness or color volume.
Peak brightness, black level, contrast, local dimming, color gamut and processing are separate from format compatibility. A bright display with poor contrast may look less convincing than a dimmer display with good contrast.
Check the specific model, firmware, input and player. A format logo is not a complete performance specification.
| Format | Metadata model | Practical note |
|---|---|---|
| HDR10 | Static | Widely used baseline; display tone mapping matters |
| HDR10+ | Dynamic | Requires compatible display/player support |
| Dolby Vision | Dynamic, proprietary system | Device and content support vary |
| HLG | Scene-referred broadcast design | SDR compatibility is useful but not identical |
What FAST-VID does and does not provide
FAST-VID offers MP4 video, MP3 audio and conditional M4A for supported public links. It does not expose HDR selection, HDR-to-SDR conversion, metadata editing or color-management controls.
The source and supported output path determine what happens to HDR signaling. FAST-VID does not promise HDR preservation or HDR output, and it does not guarantee that a downloaded file will play as HDR on any display.
If HDR matters for a project, inspect the actual output and test it in the intended playback chain. Use a dedicated editor or remuxing tool for HDR-specific work.
A practical HDR checklist
Confirm the file’s codec, container, bit depth, color primaries, transfer function and metadata. Then confirm that the player, cable, receiver and display support the same combination. Check the display’s HDR input setting.
Test a bright highlight and a dark scene. Look for clipped detail, banding, black crush and unnatural color. If the result is wrong, identify which link in the chain is falling back to SDR rather than assuming the file is bad.
Display capability and metadata handling
A display’s peak brightness, black level, local dimming and color gamut determine how much of an HDR grade it can reproduce. The same HDR10 file can look different on two “HDR-compatible” TVs because their tone-mapping and panel performance differ.
Check that the display input is in the correct mode and that the player passes the HDR signaling through. If the chain falls back to SDR, the result may still be watchable but will not represent the HDR intent.
Frequently asked questions
Is HDR the same as 10-bit video?
No. 10-bit precision is common in HDR workflows, but HDR also needs a suitable transfer function, color primaries, metadata and display capability.
Is Dolby Vision better than HDR10?
Not universally. Dolby Vision can use dynamic metadata and its own processing, but the result depends on the content, display, player and implementation.
Why does HDR look washed out on my TV?
The player or display may be tone-mapping incorrectly, HDR may not be enabled on that input, or the display may lack the brightness/contrast needed for the grade.
Does HDR10+ require a special display?
Yes. The display and player must support HDR10+ dynamic metadata; otherwise the content may fall back to another HDR or SDR presentation.
Does FAST-VID preserve HDR?
No guarantee is made. FAST-VID does not expose HDR controls or promise HDR output; source processing and device support vary.
Sources and references
- ITU-R BT.2100: HDR television
- HDR10+ official site
- Dolby: Dolby Vision
- Apple: Play HDR video on Mac
- Microsoft: HDR and Advanced Color
- FFmpeg documentation
Try FAST-VID
Open the FAST-VID downloader for a supported public link. HDR preservation is not guaranteed; inspect the output and test it on the target display.