Skip to main content
Participant
June 4, 2025
Answered

Lightroom Catalog corrupt : in develop mode, no edits/crop/masks are visible anymore

  • June 4, 2025
  • 1 reply
  • 216 views

Lightroom Classic 14.3.1

Windows 11 Pro 24H2


Since some weeks, my Lightroom library seems to have hiccups.

When opening a picture in Develop mode, it is often not shown. There is only an empty screen.
When I select another picture in the bottom bar and then select the first one again, in the end it is shown.
However, when I select the other picture again, the first picture remains shown.
None of my edits (edits, crop overlay, remove, masking) are shown in the right sidebar anymore. Everything seems to be reset.


Some pictures indicate a mismatch between the Lightroom catalog and the file on disk, but for most pictures this is not the case.


All XMP files are still there.


Trying a backup catalog does not resolve the problem. Clearing disk space (used to be 25 GB; is now 125 GB) does not resolve the problem.

Do I need to remove some of the .lrcat-data files (and is it a destructing operation)? Any advice on how to repair my library is appreciated.

Correct answer Koditech

In the meantime I have had support from Adobe using screen share.

 

The first support agent suggested to go to Lightroom -> Edit -> Preferences -> Performance. For Camera Raw, the "Use Graphics Processor" was "Auto" and he suggested to select "Custom" instead. The Camera Raw Cache Settings had a maximum size of 5,0 GB ; he suggested to set it to 30 GB. Had to free up disk space first. Finally I had to purge caches for camera raw cache settings as well as video cache settings.

 

It has become clear that my catalog was corrupt for some reason. We have been able to trace the last catalog backup which was not corrupt and contained all edits I needed.

 

Restored the backup catalog, removed all .lrcat-data files and let Lightroom build all (smart) previews again. On a sample basis, the problem appears to have been resolved. There are quite some photos though that indicate a metadata conflict between the data in the catalog and the data on disk.

 

In case I didn't have the necessary backups, Adobe could have been able to do a full catalog repair on their side, but I have no details what the outcome would be in that case.

1 reply

dj_paige
Legend
June 4, 2025

When opening a picture in Develop mode, it is often not shown. There is only an empty screen.
When I select another picture in the bottom bar and then select the first one again, in the end it is shown.
However, when I select the other picture again, the first picture remains shown.

 

I would first try resetting your preference file https://www.lightroomqueen.com/how-do-i-reset-lightrooms-preferences/

 

None of my edits (edits, crop overlay, remove, masking) are shown in the right sidebar anymore. Everything seems to be reset.

 

This sounds like a completely different problem. Please show us a screen capture of your History Panel in the Develop module. Use the "Insert Photos" icon to include screen captures in your reply. Do not attach files.

KoditechAuthorCorrect answer
Participant
June 5, 2025

In the meantime I have had support from Adobe using screen share.

 

The first support agent suggested to go to Lightroom -> Edit -> Preferences -> Performance. For Camera Raw, the "Use Graphics Processor" was "Auto" and he suggested to select "Custom" instead. The Camera Raw Cache Settings had a maximum size of 5,0 GB ; he suggested to set it to 30 GB. Had to free up disk space first. Finally I had to purge caches for camera raw cache settings as well as video cache settings.

 

It has become clear that my catalog was corrupt for some reason. We have been able to trace the last catalog backup which was not corrupt and contained all edits I needed.

 

Restored the backup catalog, removed all .lrcat-data files and let Lightroom build all (smart) previews again. On a sample basis, the problem appears to have been resolved. There are quite some photos though that indicate a metadata conflict between the data in the catalog and the data on disk.

 

In case I didn't have the necessary backups, Adobe could have been able to do a full catalog repair on their side, but I have no details what the outcome would be in that case.