2 Replies Latest reply on May 17, 2018 2:18 AM by Jim Wilde

    Lightroom Classic CC Smart Previews Timestamp Doesn't Update?


      Hi, so I am trying to copy over my lightroom catalog to an external hard drive, the main catalog file and the previews file have the time stamp updated to the most recent time but the smart previews catalog shows that it was modified on September 19, 2016. Is this the correct smart preview catalog to copy over when backing up my catalog? I don't see any other smart preview files to copy over. Screen Shot 2018-05-17 at 2.16.10 AM.png

        • 1. Re: Lightroom Classic CC Smart Previews Timestamp Doesn't Update?
          kellyz63546565 Level 1

          Ok i have figured out the answer to this after doing some research, what you need to do is right click on the SmartPreviews.lrdata file (on a mac) and click on "Show Package Contents" you will then be able to see all of your smart previews with the correct time stamp! Not sure what the lrdata file doesn't update but good to know all the recent smart previews are there!

          • 2. Re: Lightroom Classic CC Smart Previews Timestamp Doesn't Update?
            Jim Wilde Adobe Community Professional

            I think the explanation for the Previews.lrdata showing an updated modified date, while the Smart Previews.lrdata does not, is because folders (and the "package" operates like a regular folder, which is the way it appears under Windows) only show an updated modified date when root-level files within the folder are themselves updated. If you look at Previews.lrdata, you'll see two root-level files ("previews.db" and "root-pixels.db") which are database files which manage the constantly changing previews in the 0-F sub-folders. These two files are updated every time you use Lightroom, so the modified date is updated every time, and that reflects in the parent "folder" when you examine that.


            Smart Previews.lrdata, OTOH, has no root-level files. Database files aren't apparently needed in the same way, presumably because there's not a lot of change in those sub-folders, just additions and deletions and no other churn, so I guess the name and location of an individual images's Smart Preview is stored in the catalog. As a result, there are no root-level files, so nothing to force a change of the package's modified date.