Color changes between develop and Web Module (darker, redder, contrastier)

At this point, I think two things. One, using untagged files here is throwing a wild card into the mix, likewise assigning the display profile. We know what that both of those do in a normal color management chain. It either breaks the chain, or nulls it out. We don't need more unknown factors, we need less.

I think we should stick to properly and correctly tagged material, just to keep variables down so that we can identify what is actually taking place.

Second - and this is just my personal feeling and opinion - these already highly saturated test images make it difficult to see what's going on. It confuses and overloads the eye with redundant information. It's much more immediately obvious with "normal" images, with colors that people can recognize from memory.

I can't explain why some see it and some don't. From where I sit, this is consistent and unambiguous.

As I never use the web module I haven't followed this discussion.

But now that I take a look, it's clear that this is sRGB data straight to wide gamut display - it's all oversaturated in the familiar way we know from non-color managed software.

Could this be a MacOS vs Windows thing? MacOS has a color management hand everywhere; while Windows is strictly hands off. If the application doesn't do it, it doesn't happen.

Apologies if that's already been covered upthread

I read it and they were aware of the issue 2 years ago and it still exists in the latest release. I have done further a/b testing today and the uploaded galleries are much closer to the color/contrast of the develop module than the web module but not exact.

Silly me, to think they should look good in the web module. If I generate and load a "we preview" action it looks more accurate but who has the time to do that when working a job?

Stephen

The web module is not color managed, and will display images over saturated if you have a wide gamut monitor. Your images have not changed – it's just the way they display that has changed. On a wide gamut monitor, images will inevitably display over saturated in applications that aren't color managed.

Library and Develop are color managed, and will display correct colors.

You can, if you wish, post a bug report/feature request here: Lightroom Classic CC | Photoshop Family Customer Community

I thinks it's reasonable to expect from a professional image editor that all modules are color managed. (the Import module isn't color managed either)

Not sure if you have considered a different workflow instead of building a web gallery? You can create a collection, sync it to Lightroom Web and share it via a link. Anyone with the link can access the gallery. You can choose how to display the gallery with a couple of options; title it etc.

Regarding your current issue of the difference in views from the Library to Web module can you upload a screen shot to show what you are describing.

Do you have 'Use Graphics Processor' checked or unchecked in the Preferences/Performance tab?

PS - When I was using the Web module and creating galleries, I used a plugin from The Turning Gate and never ran into the issue you are describing. It always produced great results.