Color Shift After Export: Why Your Monitor, Render and Final File Disagree

Why You See a Color Shift After Export

Treat the pipeline as a chain: monitor, display transform, render output, exported file, player. A color shift after export means one link changed the numbers or the label. The table lists the links we could document.

Fix 1: Match the Display Setting to the Monitor

Autodesk’s 3ds Max 2024 documentation lists display choices in the default OCIO config, including sRGB, Gamma 2.2 Rec.709, Rec.1886 Rec.709, AdobeRGB and DCI-P3 D65, and says the Display setting should match your monitor’s calibration. Maxon says the same for Redshift: the display transform should match your monitor, usually sRGB. A wide-gamut monitor viewed through an sRGB setting can produce a color shift after export, because what you approve on screen is not what the file contains. We found no official page on ICC profile behavior, so profile or calibrate the monitor with your calibration tool’s own guidance.

Fix 2: Pick One Delivery Target

For SDR web video, YouTube’s upload page recommends BT.709 for color space, transfer, primaries and matrix, and H.264 High Profile with 4:2:0 and progressive scan. It also says unspecified values are assumed to be BT.709, equivalent values are treated as the same, and unsupported color spaces are converted to BT.709 by mapping pixel values. RGB color matrices are not recommended: the matrix is treated as unspecified and inferred from the primaries, and an sRGB transfer is converted to BT.709. Setting the display and output to BT.709 deliberately avoids a color shift after export caused by those conversions.

Fix 3: Tag the Export, and Convert Only When Needed

FFmpeg’s codec options include color_primaries, color_trc, colorspace and color_range, with values such as bt709, smpte170m, bt2020 and iec61966_2_1 for the transfer. The documentation notes that color_range as an input option is only a hint to the decoder. The h264_metadata bitstream filter can write colour_primaries, transfer_characteristics, matrix_coefficients and video_full_range_flag into the stream. Our reading is that these change the labels, not the pixels. When pixels must be converted, FFmpeg’s scale filter has options named in_color_matrix, out_color_matrix, in_range and out_range.

A command built from those documented option names looks like this. Test it on a short clip, because we did not run it for this guide.

ffmpeg -i input.mov -vf scale=out_color_matrix=bt709:out_range=tv -c:v libx264 -pix_fmt yuv420p -color_primaries bt709 -color_trc bt709 -colorspace bt709 -color_range tv output.mp4

If a color shift after export appears only in the exported file, compare a frame from the render and a frame from the file in the same viewer before you change anything else.

Fix 4: Check Full Versus Limited Range

YouTube documents that full-range color is converted to limited range. If blacks look crushed or washed after upload, a double or missing range conversion somewhere upstream is a likely suspect, and the FFmpeg range options in Fix 3 are the places to check. This is our interpretation; the documentation states the conversion but not the symptoms.

Fix 5: Test in More Than One Player

View the same file in a browser, a desktop player and QuickTime or your editor, then upload a short test clip to the target platform and compare. Community posts report that QuickTime on macOS shows BT.709 video differently, but we could not confirm that from Apple’s documentation, so treat it as a reason to test and not as a rule. If you also see banding in the gradients, read banding in gradients after rendering. For the wider set of quality problems, see fixing render noise and flicker in animation.

Where a Color Shift After Export Starts: The Five-Stage Chain

A color shift after export can start at any of five stages: the monitor setting, the display transform in the 3D app, what the render output saves, the labels or conversion applied on export, and the platform’s own processing. The table maps each stage to what the vendor pages document, so you can find which stage your file went wrong at.

Tagging Versus Converting: What FFmpeg Actually Changes

FFmpeg exposes color_primaries, color_trc, colorspace and color_range as options, with values such as bt709, smpte170m, bt2020 and iec61966_2_1. The h264_metadata bitstream filter writes colour_primaries, transfer_characteristics, matrix_coefficients and video_full_range_flag into an H.264 stream. The scale filter is a separate tool with matrix and range conversion options.

Fix 6: Choose What the Render Output Saves

In the 3ds Max Render Output Defaults, Autodesk describes two choices: No Conversion saves untransformed rendering-space values, and Display or View Transform bakes a display transform and tone map into the file. Our interpretation: a file saved with No Conversion can look different from the viewport, which is one more way to get a color shift after export, although Autodesk does not describe the symptom.

Maxon states that LDR outputs such as JPG and PNG need the view transform baked in, and that baking it clamps highlights to 1.0. For compositing and grading, Maxon recommends an unclamped linear EXR saved without the view transform. Pick one of the two on purpose for each file instead of exporting everything the same way.

Step-by-Step Export Check for a Color Shift After Export

Use this order for every delivery. It follows the vendor pages in the tables above and keeps one decision per step.

1. Set the display. In 3ds Max choose the Display option that matches your monitor calibration, and in Redshift set the display transform to match the monitor, usually sRGB.
2. Decide the file’s job. A delivery file bakes the transform in, and a grading master is an unclamped linear EXR without the view transform.
3. Pick the delivery target. For SDR web video YouTube recommends BT.709 for color space, transfer, primaries and matrix, with H.264 High Profile, 4:2:0 and progressive scan.
4. Export once, then label or convert. Use the FFmpeg color options to label the file, or the scale filter only when the pixel values must change.
5. Check the range. Confirm whether the file is full or limited range, because YouTube converts full range to limited range.
6. Compare. Open a short clip in more than one player and compare the same frame with the viewport before you export the whole sequence.

What We Could Not Verify

We could not read official pages on QuickTime gamma, ICC profile behavior, the sRGB versus Rec.709 transfer difference, Adobe Premiere or After Effects export color behavior, or Blender’s video output color space options. We also did not verify the behavior of FFmpeg’s zscale or colorspace filters. If your color shift after export persists after the checks above, the cause is likely in one of those areas.

Sources

• YouTube Help, Recommended upload encoding settings: support.google.com (checked 2 November 2026)
• FFmpeg Documentation, Codecs (general options): ffmpeg.org (checked 2 November 2026)
• FFmpeg Documentation, Bitstream Filters (h264_metadata): ffmpeg.org (checked 2 November 2026)
• FFmpeg 7.1 source listing, vf_scale (option names): ffmpeg.org (checked 2 November 2026)
• Autodesk, 3ds Max 2024 Help, Color Management Settings: help.autodesk.com (checked 2 November 2026)
• Maxon, Redshift for Cinema 4D, Color Management and OCIO/ACES: help.maxon.net (checked 2 November 2026)
• FFmpeg bitstream filters documentation, h264_metadata: ffmpeg.org
• FFmpeg filters documentation, scale: ffmpeg.org

FAQ