Skip to main content
felipea51223863
Participant
October 1, 2025
Question

Overlay Masks do not appear after LRC Catalog is exported

  • October 1, 2025
  • 2 replies
  • 140 views

Hi! 

 

I am a professional photographer who sometimes outsources my editing. I provide reference photos to my editor, all of them include overlay masking.

I zip my LRC Catalog (including 1) Smart Previews.lrdata,
2) Previews.lrdata 3) .lrcat and 4) .lrcat-data) and send it to my editor. 

When they open the file, they can see my masks. They edit on their end, zip the file, send it my way. When I export their file, I can see my Overlay Masks, but theirs don't work. I can see it's been created, I can see which cursors were modified in this mask, but it doesn't show on the image. I tried duplicating it: not working.

Any spot removing/healing is also not working: I can see there was healing done, but it has an orange ! and is not changing anything of the photo aspect. 

 

How can I fix this issue? Has anyone ever experienced this? 

 

Thank you. 

2 replies

Community Manager
October 17, 2025

Hi @felipea51223863!

Just checking in to see if you're still running into that issue. Let me know when you get a chance!
Thanks so much,
Alek

*(If you mention me with an @, like @Aleke, I’ll get a notification and can respond faster.)*
Claire H.
Community Manager
Community Manager
October 1, 2025

Hi @felipea51223863, welcome to the Lightroom Classic Community Forums. This issue can be related to how Lightroom Classic handles AI masks and healing data across machines.

1. Close Lightroom.

2. Move the .lrcat-data file to your desktop (don’t delete it).

3. Reopen the catalog in Lightroom.

4. In Grid View, select all photos and go to: Photo > Develop Settings > Update AI Settings


This should restore visibility to your editor’s masks and healing edits. Also, make sure both systems have matching Lightroom versions and full read/write permissions on the catalog files. Try these things and let me know if they work. If not, we can continue to troubleshoot the issue. ^CH