How to tell if a video is really HDR on a Mac

To tell if a video is really High Dynamic Range on a Mac, you must inspect the file’s internal stream metadata to verify that it carries 10-bit color depth, BT.2020 color primaries, and a PQ or HLG transfer function. Because video file names are frequently mislabeled or altered by uploaders, checking technical stream tags is the only certain way to confirm authentic HDR.

On macOS, you can confirm whether a movie is genuine HDR using three reliable methods: inspecting stream parameters with dedicated diagnostic utilities like MediaInfo or ffprobe, checking format badges inside an intelligent media player library, or observing hardware Extended Dynamic Range (EDR) highlight illumination on an XDR display.

Why do video file names lie?

Many Mac users assume that if a video file is named Dune.Part.Two.2024.2160p.UHD.HDR.x265.mkv, the video is guaranteed to be HDR. In reality, file names are unverified text strings.

As detailed in our guide on video file names explained, release titles are often generated automatically or altered by online uploaders. Common discrepancies include:

• SDR tone-mapped downconversions: An uploader may take a 4K HDR Blu-ray source, down-convert the colors to standard 8-bit Rec. 709 SDR to save file size, but leave the “HDR” tag in the file title.
• Upscaled SDR video: Standard 1080p SDR content is occasionally re-encoded into a 4K HEVC container with fake HDR tags to attract online clicks.
• Stripped metadata: Converting an MKV file to MP4 using naive tools can strip SMPTE ST 2086 mastering metadata or Dolby Vision RPU tracks, leaving behind an un-tonemapped file that renders with washed-out, milky colors.

To know whether your video delivers true dynamic range, you must look past the file name and examine the bitstream itself.

Method 1: Inspect stream metadata with MediaInfo or ffprobe

The most definitive method to verify HDR is examining the video stream’s codec headers. True consumer HDR video requires three foundational technical parameters:

1. Bit depth: Must be 10 bits (or 12 bits on rare production masters). Standard SDR video is 8 bits.
2. Color primaries: Must be flagged as BT.2020 (Rec. 2020). Standard video uses BT.709.
3. Transfer characteristics: Must use PQ (SMPTE ST 2084) for formats like HDR10 and Dolby Vision, or HLG (ARIB STD-B67 / ITU-R BT.2100) for broadcast streams.

Inspecting with MediaInfo

MediaInfo is a free, open-source technical analysis tool available for macOS via Homebrew (brew install mediainfo or brew install --cask mediainfo). When you open a movie in MediaInfo and select the Text view, look at the Video stream section:

• Standard HDR10 file: Shows Color primaries: BT.2020, Transfer characteristics: PQ, and Mastering display luminance with explicit minimum and maximum nits (such as 1 000 cd/m2). CTA-861.3 static metrics will appear as Maximum Content Light Level (MaxCLL) and Maximum Frame-Average Light Level (MaxFALL).
• Dolby Vision file: Displays a dedicated line: HDR format: Dolby Vision, Version 1.0, Profile 8.1 (or Profile 5 / Profile 7).
• Broadcast HLG file: Displays Transfer characteristics: HLG or ARIB STD-B67.

For a full tutorial on reading these parameters, read our complete guide to MediaInfo on Mac.

Animation

One curve for the whole film, or one per scene

Night streetSunlit beachCandle-lit room

Neon signs graded at 400 nits

HDR10 one curve for the whole film

– nits

Dolby Vision, HDR10+ a curve for each scene

– nits

Inspecting with ffprobe

If you prefer using the Terminal, ffprobe—the lightweight stream analyzer bundled with FFmpeg—can inspect stream tags without a graphical interface. To check a file, run:

ffprobe -v error -select_streams v:0 \
  -show_entries stream=pix_fmt,color_space,color_transfer,color_primaries \
  -of default=noprint_wrappers=1 input.mkv

A genuine HDR video will output:

pix_fmt=yuv420p10le
color_space=bt2020nc
color_transfer=smpte2084
color_primaries=bt2020

If pix_fmt says yuv420p (without the 10le 10-bit suffix) and color_transfer reports bt709, the video is standard SDR regardless of what the file name claims. To master command-line video diagnostics, check our tutorial on how to use ffprobe.

Method 2: Check format badges in your player library

Inspecting terminal outputs for every video in your collection takes time. A more convenient approach is using a media player library that parses container headers during scanning.

Traditional players like QuickTime Player fall short here:

• QuickTime Player’s Movie Inspector (Command-I) only reveals basic canvas dimensions, pixel dimensions, and the primary video codec (such as “HEVC”). It frequently fails to indicate whether static metadata or dynamic Dolby Vision tracks are present.
• QuickTime Player refuses to open the Matroska (.mkv) container entirely, which is the dominant container format for high-bitrate HDR movies and Blu-ray remuxes.

Modern macOS media players inspect stream headers when you import folders into your library, displaying explicit visual badges next to each title:

When you see a verified format badge in your library, you know the player has validated the underlying bitstream. For a deeper understanding of baseline formats, consult our guide to what is HDR10 and our explainer on what is Dolby Vision.

Method 3: Observe hardware EDR brightening on your screen

The third way to confirm that a video is playing in authentic HDR is observing how your Mac screen physically responds.

Apple handles HDR video using Extended Dynamic Range (EDR). Unlike external PC monitors that flash black and lock the entire screen into an inflexible HDR mode, macOS mixes SDR windows and HDR video surfaces together on the same desktop.

If you own an Apple Silicon Mac with a Liquid Retina XDR display (14-inch and 16-inch MacBook Pro models) or an Apple Pro Display XDR:

1. Open the video in an HDR-capable video player.
2. Position the player window so that you can see surrounding macOS elements, such as the white menu bar, a Finder window, or your desktop wallpaper.
3. Observe the highlights inside the movie, such as car headlights, explosions, sunshine, or neon signs.

If the video is true HDR and rendering correctly, those specular highlights will appear physically brighter than the white background of your Finder window. The display’s mini-LED backlight pushes up to 1,600 nits of light into the video highlights while keeping the surrounding desktop windows locked to your standard SDR brightness setting (typically 200 to 500 nits).

If you drag an SDR video next to an HDR video, the SDR video’s brightest white elements will never exceed the white of your desktop windows. This optical contrast confirms that macOS has allocated hardware headroom for the video layer. To learn how Apple calculates this headroom ratio, read our guide on EDR and XDR explained.

What to do if an HDR video looks wrong on Mac

If your diagnostic tools confirm that a video carries valid HDR tags but the picture looks incorrect during playback, check these three common configuration traps:

1. The video looks washed out and milky: This occurs when a player decodes Rec. 2020 colors or the PQ curve into an SDR window without applying tone mapping. The black levels rise to dark grey and highlights clip. Use a player engineered with native macOS Metal EDR support.
2. The colors look neon green and purple: This happens when you open a Dolby Vision Profile 5 file in an older player like VLC 3.0. Profile 5 uses a color space called IPTPQc2. If a player treats it as standard YCbCr, colors corrupt completely.
3. The image is extremely dim: If you are watching on battery power or in a brightly sunlit room, macOS may be suppressing HDR headroom to save battery, or your eyes may be struggling to adapt to high ambient room light.

Verifying your video files with accurate diagnostic tools ensures you never waste time watching mislabeled files or flawed downconversions. By combining MediaInfo stream checks with a player that displays clear format cards, you can sit back and enjoy clear, theater-grade HDR every time.