Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
1

Lightroom catalogue gets huge due to denoise data

Explorer ,
Jul 06, 2025 Jul 06, 2025

In the latest updated of Lightrrom the denoise feature has gotten much smoother. Instead of saving a new DNG-file next to the originial image it does some internal magic.

 

I have noticed thet the catalogue get huge though. It grows very rapidly. Mines has double the last few days of editing. This is a problem as the backups is also getting very large. I prefered haviing the DNG-file together with the picture not being backuped all the time.

 

Why is this? Is there any way to get around this? Like removing some denoise data for older photos and being able to recreate it later if needed? Why does all this data gets saved into the backup?

TOPICS
macOS , Windows
208
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 06, 2025 Jul 06, 2025

Why is this?


Because that's how Adobe designed it.

 

Is there any way to get around this?

 

No. (Unless you want to downgrade to 14.3)

 

Like removing some denoise data for older photos and being able to recreate it later if needed?

 

You can remove the data from the catalog by going into the history panel and selecting the last edit BEFORE the denoise, right click on it and the select "Clear History Above This Step"

 

Why does all this data gets saved into the backup?

 

Everything gets backed up. There is no partial backup.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jul 06, 2025 Jul 06, 2025

You may be the victim of a bug in Adobe's software.  You should read the posts by @johnrellis in this thread: https://community.adobe.com/t5/lightroom-classic-ideas/p-bring-back-the-ability-of-enhance-to-create... 

Ellis' posts are always very carefully explained and supported by very thorough testing.

The way to avoid it is to make sure you have Catalog Settings > Metadata > Automatically Write Changes Into XMP unchecked.

I hope that is the solution to your problem.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 06, 2025 Jul 06, 2025

Changing the XMP settings will not affect catalog size.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jul 06, 2025 Jul 06, 2025

Hmmm.....did you read the linked thread?

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 06, 2025 Jul 06, 2025

"I have noticed thet the catalogue get huge though. It grows very rapidly. Mines has double the last few days of editing."

 

Look in the catalog folder. There are two files, <catalog>.lrcat (the main database file) and <catalog>.lrcat-data. 

 

In LR 14.4, denoise, raw details, and super resolution data has been moved from DNG files into the .lrcat-data file.  That's by design, and you will see that file grow by typically 5 to 50 MB for each denoised photo (more for super resolution).

 

But if you see the .lrcat file (the main database file) grow quickly, that's due to the bug @DClark064 linked to.  As a workaround until it's fixed, turn off Catalog Settings > Metadata > Automatically Write Changes To XMP. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Jul 07, 2025 Jul 07, 2025

Optimising Catalog gets rid of the XMP stored inside it.

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 07, 2025 Jul 07, 2025

"Optimising Catalog gets rid of the XMP stored inside it."

 

Be sure  to clear all references to denoise/raw details/super resolution from the Develop History panel before File > Optimize Catalog will get get of the incorrect copies of the AI data from the photo's XMP in the catalog.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Jul 07, 2025 Jul 07, 2025

@johnrellis also clear Enhance from snaphsots.

I find this is the hardest to do for users.

 

Removing Enhance form the photos that have it was simple via the SDK but for snaps one needs to check one by one.

 

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 07, 2025 Jul 07, 2025
LATEST

Very much agreed.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines