Why Does My Color Grade Look Different After Exporting (October 2026) Complete Guide

You spent hours perfecting your color grade. Every shadow, every highlight, every skin tone looked exactly right in your timeline. Then you exported the video, played it back, and something was off. Maybe the colors looked washed out. Maybe they were too saturated. Maybe the blacks were crushed or the whole image had a weird tint.

If you are asking why your color grade looks different after exporting, the short answer is this: your editing software uses one set of color space and gamma settings during preview, and your export uses another. When those settings do not match, the exported file interprets color data differently than what you saw on your timeline. This mismatch is the root cause behind almost every color shift complaint from video editors and colorists.

The most common fix is to verify that your export color space tag and gamma setting match your timeline settings. For most Rec.709 projects, that means exporting with Rec.709 gamma 2.4 (or BT.1886) and making sure your display profile is not applying an unexpected color transform. On Mac systems, switching to Rec.709-A in your viewer or export settings resolves the QuickTime gamma shift that makes exports look brighter than expected.

In this guide, I will walk you through every reason your exported colors do not match your timeline, from color space mismatches and gamma curve conflicts to QuickTime display issues and social media platform compression. I will also give you step-by-step fixes for both Premiere Pro and DaVinci Resolve, plus an export settings checklist you can use on every project.

Quick Overview: The Real Reason Your Colors Shift

Color shifts after export almost always come down to one thing: the way your software tags and interprets color metadata changes between your editing timeline and your final rendered file. Your NLE (non-linear editor) shows you one version of your image during editing. The exported file may carry different color metadata, or no metadata at all, which causes the media player or platform to interpret the colors differently.

Here is the 3-step quick fix that resolves most color shift issues:

1. Set your project color space to Rec.709 and gamma to 2.4 (or BT.1886) in both your timeline and export settings.
2. On Mac, use Rec.709-A as your viewer color space to match how QuickTime will display the file.
3. Always test your export in the same player your audience will use, not just your editing software’s built-in viewer.

Those three steps fix roughly 80% of color shift problems. The remaining 20% involve codec-specific issues, monitor calibration problems, and platform compression artifacts, which I cover in detail below.

Why Does My Color Grade Look Different After Exporting? The 5 Most Common Causes

When editors notice their color grade looks different after exporting, the problem usually falls into one of five categories. Understanding which category your issue belongs to is the first step toward fixing it permanently.

1. Color Space Mismatch — Your project is set to one color space (like Rec.709) but your export settings specify a different one (like sRGB or Rec.2020). The software converts between them, and the conversion changes how colors appear. This is the single most common cause of color shift after export.

2. Gamma Curve Conflicts — Gamma controls the brightness curve of your image. If your timeline uses gamma 2.4 but your export tags the file with gamma 2.2, the exported video will look slightly brighter and flatter. This 0.2 gamma difference is subtle but very noticeable to trained eyes.

3. Display Profile and Player Differences — QuickTime Player on Mac applies its own color management, which can make Rec.709 video look brighter than it does in Premiere Pro or DaVinci Resolve. VLC, YouTube, and iPhone screens all handle color differently too. The export might be correct, but the player is showing it wrong.

4. Codec and Compression Settings — Some codecs like H.264 and H.265 apply their own color subsampling (typically 4:2:0), which reduces color information. If you graded in a high-bitrate format and export to a heavily compressed delivery codec, you lose fine color detail. The grade is still there, but compression smooths away subtle distinctions.

5. Platform Compression (Social Media) — When you upload to Instagram, YouTube, or TikTok, the platform re-encodes your video. Instagram’s compression is particularly aggressive and can shift saturation, crush blacks, and alter skin tones. Even a perfectly exported Rec.709 file can look different after platform processing.

Color Space Mismatch: The #1 Cause Explained

A color space defines the range of colors (the gamut) that a device or file can represent. Think of it as a box that contains every color your video can possibly show. If you grade your video using a large color space but export using a smaller one, colors that fall outside the smaller box get clipped or compressed. The result is a visible shift in saturation and hue.

The most common color spaces in video production are:

Rec.709 — The standard color space for HD video and broadcast television. It has a relatively small gamut but is universally supported across devices. If you are delivering for YouTube, broadcast, or general web video, Rec.709 is your target.

sRGB — The standard color space for computer displays and the web. It is nearly identical to Rec.709 in gamut but uses a slightly different gamma curve. Many social media platforms assume sRGB.

Rec.2020 — A wide-gamut color space designed for UHD and HDR content. It can represent far more colors than Rec.709, but most consumer displays cannot show the full range. Exporting in Rec.2020 when your target platform expects Rec.709 will make colors look oversaturated on standard screens.

DCI-P3 — A wide-gamut color space used in digital cinema projection. Some modern displays and phones support P3, which can make Rec.709 content appear more saturated than intended if the display expands the gamut.

Here is where the mismatch happens. If your DaVinci Resolve project is set to Rec.709 for the timeline, but your export preset defaults to Rec.2020 or leaves the color space tag unassigned, the exported file will either look flat (too wide a gamut squeezed into standard display) or oversaturated (standard gamut stretched by a wide-gamut display). Always verify that your export color space matches your timeline color space.

Understanding Color Spaces: sRGB, Rec.709, and Beyond

One of the most common questions from new colorists is: what is the difference between color space and gamma? These two terms get used together so often that many editors conflate them, but they control completely different aspects of your image.

Color space defines which colors can be displayed. It sets the boundaries of the gamut. A wide-gamut color space like Rec.2020 can show more saturated reds, greens, and blues than a narrow one like sRGB.

Gamma defines how bright those colors appear. It is a curve that maps dark values to light values. A higher gamma number (like 2.6) produces darker midtones and deeper contrast. A lower gamma number (like 2.2) produces a brighter, flatter image.

You can have a Rec.709 color space with gamma 2.2, gamma 2.4, or even gamma 2.6. The color space stays the same (same gamut boundaries), but the image looks noticeably different at each gamma setting. This is why two people can both say “I am working in Rec.709” and still get different-looking exports.

For practical purposes, here are the standard combinations most editors should use:

— Web and social media video: Rec.709, gamma 2.2 or 2.4
— Broadcast television: Rec.709, gamma 2.4 (BT.1886 standard)
— Digital cinema (DCP): DCI-P3, gamma 2.6
— HDR streaming: Rec.2020 with PQ or HLG transfer function
— Still photos for web: sRGB, gamma 2.2

One source of confusion worth clearing up: Rec.709 and sRGB share almost the exact same color gamut. The difference is in the gamma. sRGB uses a piecewise gamma curve that averages around 2.2. Rec.709 uses a curve defined by the BT.1886 standard, which is typically implemented as gamma 2.4 for broadcast viewing. This means exporting an sRGB-tagged image when you meant to export Rec.709 will make your video look slightly brighter and flatter.

Gamma Curve Conflicts: 2.2 vs 2.4 vs 2.6

If you have ever wondered why your export looks slightly brighter or darker than your timeline, gamma is likely the culprit. The gamma curve controls how your video maps brightness values, and even small differences are visible to the human eye.

Here is what each common gamma setting does to your image:

Gamma 2.2 produces a brighter, more open image. It is the standard for computer displays and web content in the sRGB color space. Many social media platforms expect gamma 2.2. If your audience will watch your video primarily on phones and laptops, gamma 2.2 is a safe choice.

Gamma 2.4 produces a slightly darker, more contrasty image. It is the BT.1886 standard for broadcast television and professional video delivery. Most professional colorists grade at gamma 2.4 because it matches controlled viewing environments (dimly lit rooms with calibrated monitors). If you deliver to broadcast or streaming services, use gamma 2.4.

Gamma 2.6 is specifically for digital cinema. It is the standard gamma for DCP (Digital Cinema Package) delivery in DCI-P3 color space. Unless you are delivering for theatrical projection, you should not use gamma 2.6.

The conflict arises when your editing software and export settings use different gamma values. For example, if your DaVinci Resolve timeline is set to Rec.709 gamma 2.4 but your export preset defaults to gamma 2.2, the exported file will look noticeably flatter than what you graded. The colors are technically the same, but the brightness curve has shifted.

As one experienced colorist on the Lift Gamma Gain forum explained: “My little workaround for this issue is to make a 2.4 to 2.2 adjustment LUT and have it applied to the GUI viewer in the color management section.” This kind of adjustment LUT compensates for the gamma difference between grading and viewing environments.

The fix is simple: always check your export gamma setting before rendering. In Premiere Pro, open the Advanced section of the export dialog and verify the gamma tag. In DaVinci Resolve, check the Color Space and Gamma dropdown in the Render Settings panel.

QuickTime Gamma Shift: The Mac User’s Nemesis

If you edit on a Mac, you have probably experienced this: your video looks perfect inside DaVinci Resolve or Premiere Pro, but when you open the exported file in QuickTime Player, it looks washed out and too bright. This is not a bug in your export. It is a known color management issue with QuickTime on macOS.

QuickTime Player applies its own color interpretation to video files. On Mac systems, QuickTime assumes a different gamma than what most NLEs use for Rec.709 display. This causes the image to appear brighter, with lifted shadows and reduced contrast. The effect is commonly called the “QuickTime gamma shift.”

Apple partially addressed this by introducing Rec.709-A (the “A” stands for Apple). Rec.709-A is a color space tag specifically designed to make QuickTime display Rec.709 content correctly on Mac displays. When you tag your export with Rec.709-A, QuickTime interprets the file the same way your NLE displayed it during grading.

However, Rec.709-A is not a universal solution. It is an Apple-specific tag that other players and platforms may not recognize. If you deliver the same file to YouTube, VLC on Windows, or an Android phone, the Rec.709-A tag may be ignored or misinterpreted.

Here is the practical recommendation for Mac users:

— Set your DaVinci Resolve viewer to Rec.709-A so your timeline preview matches QuickTime.
— Export with standard Rec.709 gamma 2.4 for delivery to platforms like YouTube.
— Accept that QuickTime will show your export slightly differently than VLC or YouTube.
— Test your export in the actual player or platform your audience will use, not just QuickTime.

As one Reddit user on r/davinciresolve noted: “QuickTime displays colors way off, which I understand, since DaVinci introduced Rec.709-A to fix that.” This is a widely recognized issue in the colorist community, and understanding it prevents hours of frustration trying to “fix” an export that is actually correct.

Why Your Instagram and YouTube Videos Look Different?

Even if your export is perfect, the platform where your video ends up can change how it looks. Social media platforms re-encode every uploaded video, and that re-encoding process can shift colors, crush blacks, and reduce saturation.

Instagram is the worst offender. When you upload a video to Instagram, it gets compressed aggressively to reduce file size for mobile streaming. This compression typically reduces color depth from 10-bit to 8-bit, applies 4:2:0 chroma subsampling, and raises the black level slightly. The result is a video that looks flatter and less saturated than your exported master.

A Reddit user on r/davinciresolve described the problem: “The video looks perfect in VLC and DaVinci Resolve. After uploading to Instagram, there’s a noticeable color shift, even though gamma 2.2 should be optimized for it.” This is a common complaint, and the answer is that Instagram’s compression pipeline is beyond your control.

While you cannot prevent platform compression, you can minimize its impact with smart export settings:

For Instagram and TikTok: Export at 1080p (do not upscale to 4K, as Instagram will compress it harder). Use H.264 with a bitrate between 8-12 Mbps. Set color space to Rec.709 and gamma to 2.2 (slightly brighter to compensate for compression darkening). Keep your blacks above legal minimum (do not crush below 16 on the 0-255 scale) because compression will crush them further.

For YouTube: YouTube handles color better than Instagram but still re-encodes your file. Export at the highest resolution you can (4K if possible, even if your footage is 1080p, because YouTube assigns higher bitrate to 4K uploads). Use H.264 or ProRes with Rec.709 gamma 2.4. YouTube generally preserves Rec.709 colors well.

For Vimeo: Vimeo offers the most accurate color reproduction of the major platforms. Export at full quality in ProRes or H.265 with Rec.709 gamma 2.4. Vimeo’s compression is gentler and preserves more color detail.

The key takeaway: your export can be technically perfect and still look different on a social media platform. Always upload a test clip first, check it on multiple devices, and adjust your grade if the platform’s compression degrades specific elements like skin tones or shadow detail.

Monitor Calibration and Why It Matters

Here is a hard truth that many editors do not want to hear: if your monitor is not calibrated, you cannot trust any color decision you make. You might be grading to compensate for your display’s inaccuracies rather than grading the actual footage.

An uncalibrated monitor can be too warm (making everything look yellow), too cool (making everything look blue), too bright (making you think your video is brighter than it actually is), or too contrasty (crushing blacks that are not actually crushed in the data). When you export, the file contains the correct color values. But because you graded based on what your monitor showed you, the export may look wrong on other displays.

Monitor calibration means using a hardware colorimeter or spectrophotometer to measure your display’s color output and create a profile that corrects any inaccuracies. Popular calibration tools include the X-Rite i1Display, Calibrite ColorChecker Display, and Datacolor SpyderX.

For professional color grading, a calibration probe alone is not enough. You should also use a calibrated reference monitor or an externally calibrated display connected via a video I/O device (like a Blackmagic UltraStudio). This bypasses your computer’s operating system color management and shows you the raw video signal exactly as it will appear on delivery displays.

Forum users consistently report that monitor calibration is the single most overlooked factor in color accuracy. If you are grading on an uncalibrated laptop screen in a bright room, your export will almost certainly look different on other devices. The grade was never accurate to begin with, you just could not tell.

At minimum, calibrate your monitor every 4-6 weeks, grade in a controlled lighting environment (dim, neutral-colored walls, no direct sunlight), and set your monitor brightness to around 100-120 nits for Rec.709 SDR grading.

Data Levels vs Video Levels: Full Range vs Limited Range

One of the more technical causes of color shift involves data levels, also called full range vs limited range (or video range). This setting controls how your video’s black and white points are mapped.

Full range (data levels) uses the entire 0-255 range in 8-bit video. Black is 0, white is 255. This is what computer displays, web browsers, and most consumer devices expect for RGB content. Most computer-generated graphics, screen recordings, and game captures use full range.

Limited range (video levels) uses only 16-235 in 8-bit video. Black is 16, white is 235. The values 0-15 and 236-255 are reserved for timing and synchronization data. This is the broadcast television standard, and most professional video cameras record in limited range.

When full range and limited range get mixed up, you see obvious problems. If you export a full-range video but tag it as limited range (or the player interprets it as limited range), your blacks will be raised to dark gray and your whites will be dull. The image looks washed out.

Conversely, if you export limited-range video and the player interprets it as full range, your blacks get crushed to pure black and your highlights get blown out. The image looks too dark and contrasty.

The fix is to know what your source footage uses and keep your levels consistent throughout the pipeline. Most camera footage (from cinema cameras like the Sony FX3, RED, or Blackmagic) uses limited video range. If your source is limited range, export as limited range. Do not let your software expand to full range during export unless you have a specific reason.

In DaVinci Resolve, check the “Data Levels” setting in your project preferences. Set it to “Video” for standard camera footage. In Premiere Pro, the “Render at Maximum Bit Depth” and color management settings affect how levels are handled during export.

How to Fix Color Shifts in Premiere Pro?

Premiere Pro has several settings that affect color during export. If you are seeing a color shift in your Premiere Pro exports, follow these steps:

Step 1: Check your sequence color space. Right-click your sequence in the Project panel, go to Sequence Settings, and verify the Working Color Space is set to Rec.709. If you are working with HDR footage, make sure the color space matches your intended delivery format.

Step 2: Set the correct viewer gamma. In Premiere Pro 2026, go to the Settings menu (the wrench icon in the Program Monitor). Under “Viewer Gamma,” you will see options for Rec.709 2.4 and QuickTime. If you are on a Mac and your exports look washed out in QuickTime, set Viewer Gamma to QuickTime so your timeline preview matches what QuickTime will show.

Step 3: Configure export settings. In the Export dialog, choose your format (H.264 for web delivery). Click on the Video tab and scroll to the bottom. Open the Advanced section. Here you will find the Color Space and Gamma settings. For Rec.709 delivery, set Color Space to Rec.709 and Gamma to Rec.709 (Gamma 2.4). Do not leave these on “Auto” or “Match Source” if you want consistent results.

Step 4: Enable color management. Make sure “Color Management” is enabled in your project settings. Go to File > Project Settings > General and check that “Color Management” is turned on. This ensures Premiere applies consistent color transforms throughout the editing pipeline.

Step 5: Render and test. Export a short test clip (10-15 seconds) before rendering the entire project. Open the test in QuickTime, VLC, and upload it privately to YouTube. Compare all three to your timeline. If they match, proceed with the full export.

As one Reddit user on r/premiere recommended: “Go to the export tab, set your export settings (H.264, 422HQ) and make sure to drop down Advanced and set the gamma tags to Rec.709 – gamma 2.4, hit export.” This straightforward fix resolves the majority of Premiere Pro color shift complaints.

Another common Premiere Pro issue is that the Lumetri Color panel may apply effects that do not render correctly during export. If you are using adjustment layers with Lumetri effects, verify that the effects are applied to the correct tracks and that your render settings include all effects. Sometimes, disabling and re-enabling Lumetri before export forces a fresh render that preserves your grade.

How to Fix Color Shifts in DaVinci Resolve?

DaVinci Resolve is built for professional color grading, but it still has export settings that can cause color shifts. Here is how to ensure your DaVinci Resolve exports match your timeline:

Step 1: Set project color science. Go to Project Settings (gear icon) > Color Management. Set the Color Science to “DaVinci YRGB Color Managed” for modern workflows. Set the Timeline Color Space to Rec.709-A (if on Mac) or Rec.709 Gamma 2.4 (for standard delivery).

Step 2: Configure output color space. In the same Color Management panel, set the Output Color Space to match your delivery target. For web video, use Rec.709-A on Mac or Rec.709 Gamma 2.4 for cross-platform delivery. The Output Color Space determines how your exported file is tagged.

Step 3: Check render settings. Go to the Deliver page. In the Render Settings panel, under “Advanced Settings,” find the Color Space tag and Gamma tag options. These should match your project Output Color Space. If you are delivering Rec.709, set both to Rec.709 with the correct gamma.

Step 4: Verify your viewer matches export. In the Color page, check the viewer (the monitor showing your graded image). If it shows Rec.709-A, your export should also be tagged Rec.709-A. If the viewer and export tags do not match, you will see a shift.

Step 5: Use the right codec. For maximum color fidelity, export in ProRes 422 HQ or DNxHR HQX. These are mastering codecs that preserve full color depth. For web delivery, you can transcode to H.264 afterward, but always verify the H.264 output against the ProRes master.

One frustrated DaVinci Resolve user on Reddit wrote: “I am actually going insane with the mismatch of DaVinci’s color display vs. how it looks after exporting.” If you feel the same way, the issue is almost certainly in your Color Management settings. The fix is to make your timeline color space, output color space, and export color space tag all use the same Rec.709 variant and gamma.

For DCP delivery specifically, an expert on the DCPomatic forum explained: “In Resolve, it’s Rec.709 or BT.1886. In DCP-o-matic player, it’s a retransformation from DCI X’Y’Z’ at gamma 2.6 for 14fL/48cd/sqm. This is meant for a very different viewing environment.” If you are delivering for cinema, you need to use the correct DCI-P3 and gamma 2.6 settings, and you should use a dedicated DCP encoding tool rather than a standard video export.

Premiere Pro vs DaVinci Resolve: Export Settings Comparison

Both Premiere Pro and DaVinci Resolve can produce accurate Rec.709 exports, but the settings are in different places. Here is a side-by-side comparison of the key settings you need to check in each application:

Color Space Setting: In Premiere Pro, find this under Sequence Settings > Working Color Space. In DaVinci Resolve, find this under Project Settings > Color Management > Timeline Color Space. Both should be set to Rec.709 for standard delivery.

Gamma Setting: In Premiere Pro, find this under Export > Advanced > Gamma. In DaVinci Resolve, find this under Project Settings > Color Management > Output Gamma, and also in Deliver > Advanced Settings > Gamma Tag. Both should specify gamma 2.4 for broadcast or 2.2 for web.

Viewer Display: Premiere Pro has a dedicated Viewer Gamma setting in the Program Monitor wrench menu. DaVinci Resolve uses the Color Management settings to determine viewer display. Both need to be set to match your intended output to avoid timeline-to-export mismatch.

Export Codec Options: Premiere Pro offers H.264, H.265, ProRes, and DNxHR. DaVinci Resolve offers the same plus QuickTime DNxHR and additional formats. For color-critical delivery, both should use ProRes 422 HQ or DNxHR HQX as intermediate masters.

Color Management Approach: Premiere Pro uses a simpler color management system that can sometimes default to “off” or “basic.” DaVinci Resolve uses a more advanced color management system (DaVinci YRGB Color Managed or ACES) that requires explicit configuration. Both systems produce correct results when configured properly, but DaVinci Resolve gives you more control and more ways to get it wrong.

Export Settings Checklist for Consistent Color

Use this checklist before every export to prevent color shifts. Print it, pin it to your wall, and run through it every single time.

1. Verify project color space — Confirm your timeline and project color space is set to Rec.709 (or your intended delivery color space). Do not leave it on auto-detect.

2. Check gamma setting — Confirm gamma is set to 2.4 for broadcast/streaming or 2.2 for web/social media. Match it between timeline and export.

3. Set export color space tag — In your export settings, explicitly set the color space tag to Rec.709 (or Rec.709-A on Mac). Do not leave it on “Auto” or “Match Source.”

4. Verify data levels — Ensure your data levels are set to “Video” (limited range, 16-235) for camera footage. Use “Full” (0-255) only for screen recordings or computer-generated content.

5. Choose the right codec — Use ProRes 422 HQ or DNxHR HQX for mastering. Use H.264 at high bitrate (15+ Mbps for 1080p, 35+ Mbps for 4K) for web delivery.

6. Test in multiple players — Before full export, render a 10-second test. Open it in QuickTime, VLC, and your target platform (YouTube private upload). Compare all three to your timeline.

7. Check on a second display — View your test export on at least one other device (phone, different monitor, TV). If it looks consistent across devices, your settings are correct.

8. Document your settings — Once you find settings that work, save them as a preset. Use the same preset for every project with the same delivery target.

Common Export Mistakes to Avoid

After analyzing hundreds of forum posts and community discussions, I have identified the mistakes that cause the most frustration. Avoid these and you will eliminate most color shift problems before they happen.

Mistake 1: Trusting QuickTime as your reference player. QuickTime on Mac applies its own color management that differs from how YouTube, VLC, and most other players display video. One r/premiere user reported: “Colors completely different after export. I spent 2 hours on a video and when I exported it everything was super yellow/orange and dark.” The export was likely fine, but QuickTime was displaying it incorrectly. Always test in VLC or your target platform, not just QuickTime.

Mistake 2: Leaving export color space on “Auto.” Both Premiere Pro and DaVinci Resolve have an “Auto” or “Match Source” option for export color space. This setting guesses what color space to use, and it guesses wrong surprisingly often. Always manually set the color space tag.

Mistake 3: Grading on an uncalibrated laptop screen. Laptop displays are bright, saturated, and inconsistent. They are designed to look impressive, not accurate. If you grade on an uncalibrated laptop, your export will look different on every other display. Invest in a calibration probe and use it.

Mistake 4: Using different gamma for timeline and export. This is the most preventable mistake on this list. If your timeline is gamma 2.4, export at gamma 2.4. If your timeline is gamma 2.2, export at gamma 2.2. The settings must match.

Mistake 5: Ignoring the Rec.709 vs Rec.709-A distinction on Mac. If you edit on a Mac and deliver to QuickTime or Apple devices, Rec.709-A ensures your colors display correctly in Apple’s ecosystem. Standard Rec.709 will look slightly off in QuickTime. Know which one your audience needs.

Mistake 6: Not testing before full export. A 10-second test render takes 30 seconds and saves you from discovering a color shift after a 2-hour render. Always test first.

HDR to SDR Conversion: Why Colors Change

If you graded your video in HDR (High Dynamic Range) and need to deliver an SDR (Standard Dynamic Range) version, expect significant color and brightness changes. HDR content uses a wider color gamut (Rec.2020) and higher peak brightness (up to 1000+ nits) compared to SDR (Rec.709 at around 100 nits). Converting between them is not a simple brightness adjustment.

During HDR to SDR conversion, the software must map the wider HDR gamut into the smaller SDR gamut. Colors that exist in HDR but fall outside the SDR gamut get clipped or compressed. Extremely bright highlights get toned down. The overall image can look flat and undersaturated compared to the HDR original.

To get the best SDR version from an HDR grade:

— Use a tone-mapping method like DaVinci Resolve’s HDR to SDR transform or a dedicated LUT.
— Grade the SDR version separately rather than relying on automatic conversion.
— Check skin tones specifically, as they are most affected by gamut compression.
— Verify your SDR export on a standard display, not an HDR-capable monitor.

Never assume an automatic HDR to SDR conversion will produce an accurate result. The math is approximate, and different software uses different tone-mapping algorithms. Always review and adjust the SDR version manually.

Color Management for Still Photographers

The same principles apply to still photography. If your JPEG or PNG export looks different from your Lightroom or Photoshop edit, the cause is almost always a color profile mismatch.

In Photoshop, when you use “Export As” or “Save for Web,” there are two checkboxes that control color: “Convert to sRGB” and “Embed Color Profile.” If you leave “Convert to sRGB” unchecked, your image retains its working color space (typically ProPhoto RGB or Adobe RGB), which most web browsers and devices will misinterpret as sRGB. The result is a flat, desaturated image.

If you check “Convert to sRGB” but leave “Embed Color Profile” unchecked, the conversion happens correctly but the file has no metadata telling other applications what color space it uses. Most applications will assume sRGB, which is usually fine, but color-managed applications may guess wrong.

The correct settings for web export from Photoshop: check both “Convert to sRGB” and “Embed Color profile.” This ensures the colors are converted to the web-standard color space and the file carries metadata confirming that fact.

In Lightroom, the Export dialog has a Color Space dropdown under File Settings. Set it to sRGB for web delivery. For print, use Adobe RGB or ProPhoto RGB depending on your printer’s capabilities. Always soft-proof your image in the target color space before exporting to check for out-of-gamut colors.

FAQs

Frequently Asked Questions

Stop Guessing, Start Grading with Confidence

Understanding why your color grade looks different after exporting comes down to one principle: color management must be consistent from timeline to export to playback. When your color space, gamma, and data levels match across every stage of the pipeline, your exported video will look exactly like what you graded.

The most common fix is also the simplest: verify your export color space tag and gamma setting before every render. Set them to match your timeline, test with a short clip, and save those settings as a preset. Once you build this habit, color shifts after export become a thing of the past.

Remember that some platforms (especially Instagram) will always alter your colors through compression. You cannot control that. What you can control is delivering a technically accurate export that looks right on calibrated displays and standard players like VLC and YouTube. Get that right, and you have done your job as a colorist.