Why does Lightroom Classic’s Library module show extra grain or banding compared with Develop?
Asked 8/19/2023
4 views
2 answers
0
In Lightroom Classic, some of my photos look different in Library than they do in Develop. The issue is not mainly color shift — on certain images, Library appears to add grain, texture, or faint vertical banding that I do not see in Develop. It does not happen on every image. I’m using the latest Lightroom Classic, and updating graphics/processor drivers did not help. Why would Library show these artifacts, and which module should I trust when judging image quality?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
2y ago
2 Answers
2
The issue is probably the type of preview the library module is using.
The library module and the develop module do not use the same files unless you create and edit smart previews (or non-raw files). Only the develop module shows you your actual raw image with edits. You can get close to that for the other modules if you have LR create 1:1 previews, but they are slow to create and take a lot of extra room.
Also note that compression (smaller size viewing) can cause artifacts like banding (lines) in gradients/smooth tone areas to appear. But I've never heard of it causing noise... I would guess that's a low quality preview version of an added grain edit.
The answer is to only use the develop module for critical evaluation.
Originally by user70370. Source · Licensed CC BY-SA 4.0
user70370
2y ago
0
Generated from our catalog & community — verify before relying on it.
This is most likely caused by the preview file that Library is displaying, not by Lightroom actually changing your edited RAW.
In Lightroom Classic, Develop typically renders the actual RAW with your edits, while Library often shows a generated preview. If that preview is lower quality or not 1:1, it can show artifacts such as extra grain-like texture or banding/lines in smooth areas. Compression and reduced-size previews can make this more noticeable.
So the safest approach is:
- Trust Develop for critical evaluation of detail, noise, and final image quality.
- If needed, build 1:1 previews in Library to make it closer to Develop, though this takes more time and disk space.
In short, Library and Develop are not always showing the same rendered source, so preview artifacts in Library can explain the differences you’re seeing.
Recommended products
UniqueBot
AI2y ago
Your Answer
Related Questions
Why do deleted or moved photos still appear in Lightroom Classic’s Library?
Why do black areas show blue and white areas show red in Lightroom Develop mode?
Where is Lightroom Classic’s “Eject after Import” option, and why might it be missing?
Why does Photoshop show banding that I don’t see in Lightroom?
Why do I see color banding in Lightroom Mobile and how can I reduce it?