Why Dolby Vision looks green or purple on Mac, and how to fix it

You open a Dolby Vision movie on your Mac and faces turn green, skies turn purple, or the whole frame looks washed in magenta. It plays fine on an Apple TV or iPhone. That mismatch is common, and it is almost never your display.

Why it happens

Dolby Vision comes in profiles. Profile 5 stores the picture in a Dolby-specific colour encoding (IPT-PQ-c2) and has no HDR10 or SDR base layer that an ordinary player could fall back to. The colours only come out right after the player applies the Dolby Vision metadata (the “RPU”) to reshape each frame. A player that does not do that reads the data as normal video, and the result is a green or magenta cast.

Profile 8.x files are different: they carry a compatible HDR10 or SDR base layer. If a player ignores the Dolby Vision data, you typically still get a reasonable (if less accurate) picture. That is why people see the tint on certain files and not others.

Mac users report exactly this: in a long Infuse community thread, Profile 5 files show a green and magenta cast on macOS while the same content looks right on tvOS and iOS.

1. Confirm the file is Profile 5

Inspect the video stream with a tool such as MediaInfo, or with the player’s own details. Look for the Dolby Vision profile (Profile 5 is often written as dvhe.05) and whether the file has a compatible base layer. If it says Profile 8.1, the cause is likely something else, such as missing colour tags or a display mode problem; see how to check HDR playback on Mac.

2. Use a player that processes Profile 5

This is the real fix. Choose a player whose documentation explicitly lists Profile 5 and that applies the RPU reshaping, not one that only “opens” the file. Opening a file proves nothing about the colour. See how to play Dolby Vision MKV files on Mac for how to check a player’s profile support.

3. Check the Mac and display

Apple says HDR playback needs compatible content, macOS, Mac hardware and an HDR10-capable display, and that third-party displays may need HDR turned on in Displays settings. Work through Apple’s HDR checklist, but remember that a correct display setup does not cure a Profile 5 file that the player does not process.

4. Know the workarounds, and their limits

Some users report that remuxing a Profile 5 MKV to MP4 with Subler, which keeps the Dolby Vision information, lets QuickTime or Infuse show it correctly (also described in the thread above). It can work, but it adds a conversion step for every file, and results vary by file and app. Re-encoding the video is riskier: it can throw away the dynamic metadata that the picture depends on.

What we measured

We played one Dolby Vision Profile 5 sample (the Mystery Box encoding sample, HEVC Main 10, 4K, 59.94 fps) on a MacBook Pro with an M1 Pro. VLC 3.0.20 and Elmedia Player 8.24 both showed a colour cast on that file, QuickTime Player 10.5 did not open it, and Stoic showed correct colour. The benchmark page lists the setup, the method and the CPU and memory numbers. It is one file on one Mac, run on an early Stoic build, so treat it as evidence for that test, not a guarantee for every file.

How Stoic handles Profile 5

Stoic supports Dolby Vision Profiles 5 and 8.1 in local files on Apple silicon Macs running macOS 26 or later, and reshapes each frame using the file’s Dolby Vision data. Its inspector shows the Dolby Vision and colour details it detected and flags anything it had to infer. Stoic does not claim Profile 7 support.

Common questions

Is my display or Mac broken?

Almost certainly not. If the same file looks right on an Apple TV or iPhone, the display and the file are fine; the Mac player’s handling of the file is the variable.

Why do some Dolby Vision files look fine in any player?

Those are usually Profile 8.x files with a compatible base layer, so a player that skips the Dolby Vision data still has a usable picture to show.

Should I convert the file to fix the colours?

Only after you have identified the mismatch. A remux can repair container metadata without touching the video. A re-encode can lose Dolby Vision data. Start by changing the player.