Exported video looks washed out on Mac? The gamma shift, fixed

When an exported video looks washed out on a Mac, the grade is usually fine and the file is being interpreted differently from how you graded it. The most common cause is a gamma mismatch: macOS colour management displays video tagged as Rec.709 with a different tone curve from a grading setup calibrated to gamma 2.4, so shadows look lifted and colours look thinner in QuickTime Player and Safari. The next most common causes are a full range versus limited range mix-up and missing or wrong colour tags. Check the exported file on a waveform scope before you touch the grade: if the levels match your timeline, the problem is playback, not pixels.

What "washed out" usually means

People describe the same symptom in several ways: lifted blacks, milky shadows, less contrast, flatter colour. The export looks right inside the editor, then looks paler in QuickTime, a browser or after uploading.

The pixel values in the file and the pixel values in your timeline are probably very close. What changed is how the player turns those values into light on your screen. Three things control that.

• The transfer function (gamma). This is the curve that maps code values to brightness. Two players using different curves on the same file show different pictures.
• The levels range. Video can store black at a code value above zero (limited or video range) or at zero (full range). If the player assumes the wrong one, black turns grey.
• The colour tags. A video file carries metadata saying which primaries, transfer function and matrix it uses. Players on macOS read these tags and adjust the picture. Missing or wrong tags mean the player guesses.

Cause 1: the Rec.709 gamma shift

This is the classic Mac complaint, and it is not a bug so much as two reasonable standards meeting.

Broadcast and many grading workflows view Rec.709 material on a display set to gamma 2.4, in a dim room. macOS, using ColorSync, interprets a file tagged with the Rec.709 transfer function according to the camera curve in that standard and maps it to your display profile. The practical effect is that midtones and shadows come out lighter than on a 2.4 reference monitor. Your carefully crushed blacks look lifted, and saturation seems to drop because contrast dropped.

You see this most when:

• You graded on an external monitor or a viewer set to gamma 2.4, then watched the export in QuickTime Player or Safari on the Mac's own screen.
• You compare the export side by side with your editor's viewer, and the editor is not using the same colour management as the system player.
• Different browsers disagree with each other, because colour management of video has varied between browsers and versions.

Nothing is wrong with the file. Two viewers are applying two curves.

Cause 2: full range versus limited range

Most delivery video uses limited range, where black sits at code value 16 and white at 235 in 8-bit terms. Computer graphics and some screen recordings use full range, where black is 0 and white is 255.

If a limited range file is shown as if it were full range, black displays as dark grey and white as light grey: the picture looks flat and washed out. If a full range file is shown as limited range, the opposite happens, with crushed shadows and clipped highlights.

This usually comes from an export setting, a tag that does not match the data, or a conversion step in between (a screen recorder, a transcoder, or a platform re-encode). It is different from the gamma shift: a levels problem affects black and white points directly, while the gamma shift mainly lifts the midtones and shadows.

Cause 3: missing, wrong or mixed colour tags

A file can be tagged Rec.709, Display P3, Rec.2020, or carry no tags at all. Each player then makes its own decision.

• Untagged files. The player assumes something, and different players assume different things. This is a common reason a file looks right in one app and wrong in another.
• Mismatched tags. A file graded for Rec.709 but tagged as Display P3, or the reverse, shifts both saturation and contrast.
• HDR on an SDR path. An HLG or PQ clip, for example from a recent iPhone, dropped into an SDR timeline without a proper conversion can look grey and dull, or the export can be tagged as HDR when you meant SDR.

Check with scopes before you blame the grade

Your eyes are the least reliable instrument here, because the whole problem is that different viewers show different pictures. Scopes read the values, not the display.

1. Pick a reference frame. Choose a shot with true black and a bright highlight, or add a few frames of black and white at the start of a test export.
2. Note the timeline values. On the waveform, check where black and white sit on that frame in your timeline.
3. Re-import the export. Bring the exported file back into your editor as a new clip and put it on the timeline.
4. Compare the waveforms. If black and white land at the same levels as the original, the file is correct and the shift is in playback. If black has risen or the whole trace is squeezed toward the middle, you have a levels or conversion problem in the export.
5. Check the tags. In the Finder, Get Info on the file and look at the colour profile line, or use a media inspection tool. Note the primaries, transfer function and matrix, and whether they match what you intended.

Fixes that hold up

If it is the gamma shift

• Decide who the file is for. For broadcast, keep your gamma 2.4 grade and judge it on a calibrated reference, not in QuickTime. For web and social, where most viewers watch on phones and laptops, consider grading or checking the result in a viewing setup that matches those devices.
• Use your editor's output options. DaVinci Resolve, in recent versions, offers a Rec.709-A output setting aimed at matching how Macs display video, and a preference to use Mac display colour profiles for viewers. Premiere Pro has display colour management and colour settings that have changed across recent releases. Check the vendor documentation for the version you run.
• Grade where you deliver. If your editor's viewer is colour managed by macOS, what you see while grading is closer to what QuickTime will show.

If it is levels

• Match range to delivery. Export limited range for normal delivery unless a recipient asks for full range.
• Fix screen recordings early. Convert full range sources once, at the start, rather than hoping the final export sorts them out.
• Re-check after every converter. Each transcode is a chance for a range flag and the data to disagree.

If it is tags

• Tag deliberately. Choose one output colour space per deliverable and make sure the file is tagged for it.
• Convert HDR on purpose. If a clip is HLG or PQ and the delivery is SDR, use a real transform to SDR rather than letting it pass through.
• Test on the target. Platforms re-encode uploads, so post a short private test and compare it with your export on the same device before the full release.

If the colour work itself needs attention after all, our guides to colour grading software on Mac and matching a grade to a reference still cover the craft side.

Where cinemaOS fits

cinemaOS, from Momentum Studios, is a Mac-native editor for Apple silicon, and its Finisher workspace is where grading happens. It does not make the Rec.709 gamma question go away, because that is a property of the standards and the viewer, not of any single editor. What it gives you is the tools to check rather than guess.

• Scopes in the grade. Finisher has the grade controls and the scopes together, so you can read levels while you work. The one-minute grade tutorial shows the basic flow, including watching the picture and the scopes together.
• Honest limits. No grade fixes wrong or missing source colour metadata, and no editor controls how the recipient's player displays the file, so you still need to check the export on the recipient's side.

It runs on Macs with Apple silicon, with Windows planned for November 2027. You can try it free for 60 days, with no card and no automatic charge.

FAQ

Why does my video look fine in my editor but washed out in QuickTime?

Usually because the editor's viewer and QuickTime apply different tone curves or colour management to the same file. If you graded for gamma 2.4 and QuickTime displays the Rec.709 tag through ColorSync, shadows and midtones look lighter. Re-import the export and compare waveforms: matching levels mean the file is fine.

Will changing the export codec fix a washed-out video?

Rarely on its own. ProRes, H.264 and HEVC can all carry the same picture correctly. What matters is the levels range, the colour tags and the output colour space. A codec change only helps if it also changes one of those, which is why you should check with scopes rather than switching codecs at random.

Should I grade for gamma 2.2 or 2.4?

It depends on where the film will be watched. Gamma 2.4 suits broadcast and dim-room viewing. Web and phone audiences watch in brighter rooms on displays that behave differently. Many editors grade once for the main delivery and check a web version on typical devices. Agree the target with whoever receives the file before you start.