Why colors can look different
An image's look often appears different because the external viewer uses different color management or display correction (gamma, color space, ICC/OCIO, or tone mapping) than the VFB.
For example:
- The VFB may show sRGB, ICC, or OCIO display corrections that are not applied in the other app.
- Linear images (EXR) without applying display corrections look flatter in simple viewers.
- The VFB displays 32-bit color depth, while .jpgs or .pngs display only 8-bit.
- Some viewers are not fully color-managed and may ignore embedded profiles or your monitor’s ICC profile.
- Wide‑gamut monitors, OS HDR mode, True Tone/Night Shift, or vendor color enhancements can change the appearance.
Color banding and compression differences
Color banding happens when limited color depth cannot represent subtle transitions, so a gradient breaks into visible steps. Compression (for example, JPEG) further quantizes colors, which can amplify banding compared to higher bit‑depth formats.
The example below compares a 32‑bit EXR (full color information) with an 8‑bit JPEG saved at minimum file size to exaggerate compression artifacts. With EXR or VRIMG, you preserve smooth gradients and typically see no difference between the V-Ray Frame Buffer (VFB) and Adobe Photoshop when color management is consistent.
Troubleshooting
- Check file bit depth: 8‑bit outputs are more prone to banding than 16‑/32‑bit.
- Re‑save with higher quality settings if you used aggressive JPEG compression.
- Confirm color profile and gamma settings match between the VFB and your editing application.
-
Test on another display to rule out monitor limitations.
Prevention
- Use EXR or VRIMG (16‑/32‑bit floating point) to preserve smooth gradients. If you must use PNG or TIFF, choose 16‑bit per channel.
- Avoid heavy compression and prefer lossless formats (.tiff, .tga). If you must use JPEG, use the highest quality to reduce quantization artifacts.
- Keep color management consistent. Use appropriate color profiles/spaces and ensure VFB and your image editor use matching settings to avoid unintended banding.
- Render enough samples. Adequate sampling reduces noise without crushing gradients; avoid aggressive clamping or tone mapping that can reduce gradient precision.
- Verify your display. A monitor capable of a wide color range (and higher bit depth) will reveal gradients more accurately.
Contrast (display correction) differences
Display correction uses gamma (transfer) curves to compensate for the nonlinear way people perceive light, ensuring images look correct on monitors. These curves map raw rendering data to display values so colors and contrast appear accurate across devices.
Industry-established standards such as sRGB, Gamma 2.2, ACEScg, provide a good balance between compatibility and image quality. Using a different display correction curves in the VFB and in the external viewer can lead to visible differences in brightness, contrast or color.
sRGB vs Gamma 2.2
The most common difference when saving images is between the sRGB and Gamma 2.2 curves. An image saved with Gamma 2.2 typically looks slightly brighter than the same image viewed with sRGB display correction, with differences most noticeable in darker areas.
Troubleshooting
3ds Max, for example, applies a Gamma 2.2 correction to 8-bit render output, while the default VFB display correction is sRGB. This can cause slight differences when the image is previewed in other software. If you get matching results when you switch the VFB Display Correction to Gamma 2.2, then this is the reason.
Preserving the sRGB look
- Output renders to a linear format such as .EXR
- Open the image in a post-processing application like Photoshop
- Set the color profile of the compositing software to sRGB (often named sRGB IEC61966-2.1)
-
Export the image to a non-linear format of your choice (.jpg, .png, .tiff) with the Color Profile applied (baked) in the image.
Related articles
Working with the 3ds Max color management (OCIO defaults).