Tutorials Video

Why Your Grade Looks Different on Every Other Screen

Intermediate · ~14 min

Overview

A grade looking correct on your timeline and wrong everywhere else has three possible causes, and they need different fixes. Your monitor is lying to you. Your export is tagged wrongly. Or the player at the other end is doing something to the picture you did not ask for. Work out which one you have before changing a single wheel, because regrading to compensate for a mis-tagged export bakes the error in permanently.

What You Need

The graded timeline and at least one export from it
Two devices you did not grade on, ideally a phone and a television
A reference clip with known values, such as colour bars or a shot with skin tones you know well
Your export settings visible, in particular the colour space and transfer tags

Steps

Establish whether the problem survives a round trip

Import your own export back into a new timeline in the same software and put it beside the graded original. Matching means your export is faithful and the problem lives downstream, in the player or the second screen. Not matching means the export step is changing the image, and the fix is in your render settings rather than in your grade. Sixty seconds here decides which half of this page applies to you.

Check what your export is tagged as, not what it looks like

A video file carries metadata describing which colour space and transfer function the pixels are in. A player reads the tag and converts accordingly. Deliver Rec.709 footage tagged as Rec.2020, and every correct player will dutifully make it wrong. Check the tags on your exported file with a media inspector rather than trusting the export dialog, because a preset carried over from another project is the usual source of a mismatch.

Rule out the monitor before you blame the file

A display in a vivid or dynamic picture mode adds saturation and contrast on top of whatever it receives. Grading on one means compensating for the display, so a correct file looks flat everywhere else. Put the monitor in its standard or sRGB mode, turn off any dynamic contrast, and grade again. Room lighting matters as much: a bright screen in a dark room reads as brighter than it is, and the grade comes back too dark on a phone in daylight.

Look at what the platform did to your upload

Streaming platforms re-encode every upload into their own ladder of qualities. The re-encode is lossy, it is often done at a lower bitrate than you delivered, and on some platforms it applies its own tone mapping when the source is tagged as high dynamic range. Compare the platform version against your own file rather than against your timeline, and check whether the difference appears only after upload. If it does, no amount of regrading fixes it and the answer is a different delivery spec.

Test on a phone in a bright room, deliberately

Most viewers watch on a phone, often outdoors or under office lighting, at a brightness the phone chose. Shadow detail you spent an hour on disappears entirely in those conditions. Check every grade on a phone in a bright room before you sign it off. A grade surviving those conditions survives most things, and nothing in a dark suite predicts it.

Fix only the cause you found

A mis-tagged export is fixed in the render settings and needs no regrade. A lying monitor is fixed by changing the picture mode and then regrading honestly. A platform re-encode is fixed by delivering to the platform specification rather than fighting it. Changing the grade to compensate for any of the three produces a file wrong in a second way, and the day someone fixes the real cause your grade becomes obviously broken.

Pro Tips

Keep one reference shot with familiar skin tones in every project and check it on each device. Known material beats a test pattern for spotting a shift you would otherwise talk yourself out of.
Turn off any "enhance" setting on the television you test with. Motion smoothing, dynamic contrast and vivid modes are on by default and all three change what you see.
Export a short test before the full render. A two-minute clip tells you whether the tags are right and costs nothing compared with re-rendering an hour of programme.
Grade in a room with consistent lighting. A window behind you changes your perception of the same image between morning and evening more than most grades change it.
Note the delivery specification at the start of a project rather than at the end. Choosing a colour space after grading means converting, and converting after the fact rarely lands where you wanted.

Knowledge Base

What You'll Learn

The table below turns the symptom into the likely stage of the chain. The sections after it cover the two causes people most often get backwards.

Symptom to stage

What you see	Likely stage	First check
Export matches timeline, other screens differ	Display or player	Picture mode on the other screen
Export differs from timeline	Render settings	Colour space and transfer tags
Only the uploaded version differs	Platform re-encode	Delivery spec against platform guidance
Washed out and flat everywhere	Log footage delivered untransformed	Whether a conversion was applied at all
Oversaturated everywhere but your suite	Your monitor is in a vivid mode	Set the display to standard and regrade
Dark and muddy on phones only	Grading environment too dark	Check on a phone in a bright room

The tag is not the picture

The most expensive misunderstanding in this area is treating a colour space tag as a description of how a file looks. It is an instruction telling the player how to interpret the numbers. The pixels do not change when the tag does, but everything downstream treats them differently.

This is why a file looking perfect in your software and wrong in a browser is usually a tagging problem rather than a grading one. Your software knows what it made and ignores the tag. The browser has only the tag to go on. Two correct programs, one file, two different pictures.

Check tags with a media inspector on the exported file itself. An export preset carried between projects is the usual culprit, and the dialog will happily report the setting you chose rather than the setting written.

Grading in the dark, delivering to daylight

A grading suite is dim on purpose, so your eyes adapt and fine shadow detail becomes visible. Your audience is on a phone on a train. Detail separated by two or three points of luminance in your suite is a single black shape to them.

Nothing about this argues for grading in a bright room, which brings its own problems. It argues for checking in one. Keep a phone on the desk, look at every graded sequence on it before sign-off, and treat anything vanishing there as a note rather than an acceptable subtlety.

Where This Fits

This sits under Color Grading in DaVinci Resolve, the pillar for the grading side of the site. Monitor Setup and Calibration for Grading covers getting your own display honest in the first place, which prevents most of what this page diagnoses, and ACES Color Management covers the managed pipeline for projects where the conversions need to be explicit.

FAQ

Q: Why does my video look washed out after uploading?
A: Usually log or wide-gamut footage delivered without the conversion applied, or a file tagged as a colour space it is not in. Import your own export back into a new timeline first. Matching the original points at the platform, not matching points at your render settings.

Q: Should I regrade to make it look right on my phone?
A: Only if your monitor is the problem. Regrading to compensate for a mis-tagged export or a platform re-encode bakes in a second error, and the file becomes obviously wrong the day the real cause is fixed.

Q: Do I need an expensive reference monitor?
A: No, and a consumer display in standard mode with dynamic contrast turned off gets you most of the way. Consistent room lighting and checking on real target devices matter more than the panel for most work.

Q: Why does it look different in a browser than in my editor?
A: Your editing software knows what it created and ignores the file tags. A browser has only the tags. Both are behaving correctly, which is why the file is the thing to inspect rather than either program.