There are basically two different types of local image management software – databases (catalogs) and file browsers. So what’s the difference? What actually is a Lightroom catalog? Let’s compare to a physical library of books to illustrate.
File Browser
A file browser (for example Explorer or Finder) looks at the files directly on the hard drive and organizes photos by the folder you place them in. This is like walking straight into the library and looking round the shelves of books organized by topic. If someone’s borrowed a book, you won’t even know it exists.
Database
A database is a series of text records. This is like the library’s catalog of books. In the old days, it was made up of drawers full of cards, but these days it’s all computerized. Each card – or computerized record – contains information about the book, who wrote it, a description, its ISBN number, perhaps a picture of the cover, and most importantly, which shelf the book is stored on. The books themselves are still on the shelves. They’re not IN the catalog. If someone’s borrowed a book so it’s no longer on the shelf, you can still see the information describing the book, but you can’t read the book until it’s returned to its shelf. If someone moves the book to a new shelf, the information on the card is incorrect and you’ll be looking in the wrong place until the record is updated.
Lightroom’s catalog works in the same way. Photos are never IN the catalog. The Lightroom catalog contains text records of information describing the photos, with small previews stored nearby, and most importantly, a note of where each photo is stored on the hard drive. If the hard drive is disconnected or a photo is moved to a new location, you can still see the information describing the photo and a small preview in the catalog, but you can’t work with the photo until the original file is found.
Why does understanding the catalog matter?
We’re very familiar with working in file browsers. Windows Explorer and Mac Finder are used on every single Windows and Mac computer, so handling files in a browser comes naturally to most computer users.
Catalogs are different. If you move, rename or delete a file outside of Lightroom, the records in the catalog won’t get updated to match. It’d be like moving a book in the Library without telling the Librarian! Lightroom will still be looking in the old location on the hard drive for the file, and won’t be able to find it. When this happens, you’ll be left with exclamation points on the photos, and you won’t be able to edit or export the photos (just like you can’t read a library book until you find the book itself).
As well as the information about the original image files, the catalog contains all of the work you’ve done to the photos. This includes flags, stars, keywords, captions, stars, flags, collection membership, and more. Even your Develop edits are stored as a series of text instructions in the catalog itself. While it is possible to store some of this metadata with the files (in a format called XMP), by default it’s only stored in the catalog. If you remove the photos from the catalog, all of your Lightroom edits will be gone. Even if you reimport the photos later, you won’t get this information back.
What do you need to remember?
- Always rename photos within Lightroom, using the Library menu > Rename command. If you don’t, you have to fix the links one at a time. BIG job!
- Move photos within Lightroom by dragging and dropping them on another folder – or if you move them using Explorer/Finder/other software, update Lightroom’s records immediately, before you forget where you put them.
- Don’t remove photos from the catalog unless you’re also intentionally deleting the original photos (e.g. the fuzzy ones).
- Back up your catalog regularly. It contains a lot of essential information!
So should you have one catalog or multiple catalogs? That’s up for discussion in the next post in the series.
For extensive information on Lightroom Classic, see Adobe Lightroom Classic – The Missing FAQ.
If you have the Photography Plan, then as well as Classic you have access to the Lightroom cloud ecosystem including the mobile apps and web interface. For more information on these apps, see Adobe Lightroom – Edit Like a Pro.
Note: purchase of these books includes the first year’s Classic or cloud-based Premium Membership (depending on the book purchased), giving access to download the latest eBook (each time Adobe updates the software), email assistance for the applicable Lightroom version if you hit a problem, and other bonuses.
We also have a special bundle offer for the two books. This includes Premium Membership for the first year as described above for the whole Lightroom family!
Originally posted 28 November 2016, updated for latest Lightroom versions February 2020.
Hello Victoria, I trust this note finds you well.
Ref this article, It states at the end – That’s up for discussion in the next post in the series.
1. Has this been done?
2. How can I access this, If done?
Pse advise. Thx.
G
Hi Gary
Victoria did indeed write that and further follow-up posts:
https://www.lightroomqueen.com/one-or-multiple-catalogs/
Paul
Victoria, I have pretty much decided to convert my raw NEF files to DNG for use with Adobe products. The problem is Bridge is terrible at this and it seems the best way to do this and import to Lightroom is with Classic. However I am trying to be cloud centric but Lightroom CC doesn’t offer a DNG conversion, wouldn’t it be great if this was done automatically in the cloud with cloud resources instead of a PC or iPAD, but I digress. My thought was I would use Classic and COPY AS DNG and target a folder in “FROM LIGHTROOM” to get them to the cloud. So my two questions are: 1 Will Classic upload the RAW file like I want and 2 Will it still put a copy in the Classic catalog that I have to be careful not to move and screw up my catalog? If you feel it a worthy topic would you consider a blog post about how to manage a cloud centric Lightroom workflow?
If you’re going to be using the cloud, I wouldn’t bother with DNG TBH. It’ll just complicate your workflow.