# Transitioning to an sRGB workflow

**URL:** <https://discourse.threejs.org/t/transitioning-to-an-srgb-workflow/62623>\
**Category:** Questions\
**Tags:** color-space\
**Created:** [March 11, 2024, 3:42pm UTC](https://discourse.threejs.org/t/transitioning-to-an-srgb-workflow/62623 "2024-03-11T15:42:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![donmccurdy](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/donmccurdy/32/33209_2.png) [@donmccurdy](https://discourse.threejs.org/u/donmccurdy)\
**Post date:** [March 11, 2024, 4:00pm UTC](https://discourse.threejs.org/t/transitioning-to-an-srgb-workflow/62623/2 "2024-03-11T16:00:55Z")

</div>

You might find it saves time to jump directly to r152+. Some names and default settings were changed in r152, making the linear workflow the default.

In any case. It’s very likely that your `material.map` is sRGB, and in the linear workflow you’ll need to annotate that texture with `.encoding = sRGBEncoding`, equivalent to `.colorSpace = SRGBColorSpace` in r152+. With a lightmap, either sRGB or Linear-sRGB are valid choices. Ideally we’d know which was selected when _exporting_ the lightmap, without knowing it might require trial and error.

The settings of your renderer also matter a lot – have you seen the guide at [Updates to Color Management in three.js r152](https://discourse.threejs.org/t/updates-to-color-management-in-three-js-r152/50791) ? That would be good to read through, if not. The ‘correct’ settings for textures will look wrong, if the renderer is not also configured correctly. In r152+ you do not need to change the renderer defaults.

Aside – If you’re using post-processing, you’ll need OutputPass in newer three.js versions, or GammaCorrectionShader in older versions. Ideally sharing a simple demo can help to identify any other pieces of the problem that would matter to your app.

---

_[View the full topic](https://discourse.threejs.org/t/transitioning-to-an-srgb-workflow/62623)._
