A Lightroom Classic catalog lives in a file ending in .lrcat, and at some point many photographers need to look inside one without opening Lightroom. Maybe you are planning a migration, recovering data from an old drive, or simply curious about what Lightroom has been storing about your photos for all these years. The good news is that the format is readable, and you do not need an Adobe subscription to inspect it. This guide explains what a .lrcat file is, how to open one safely, what you can and cannot find inside, and the easier path if your real goal is to use that data rather than just read it.
This article is part of our larger guide on how to migrate from Lightroom Classic, which covers the full move in detail.
What a .lrcat file actually is
A Lightroom catalog is not a folder of photos. It is a database. Specifically, a .lrcat file is a SQLite database, one of the most widely used database formats in the world, which is exactly why it can be read by tools other than Lightroom. The catalog records where each photo lives on disk, plus the metadata and edit instructions you have added over time. The image pixels themselves stay in your original files wherever they already sit.
Because the catalog is a standard SQLite file, any program that can open SQLite can open a Lightroom catalog. That does not mean every value inside is easy to interpret, but the structure is open and inspectable rather than locked.
Open a .lrcat file with a SQLite browser
The simplest way to look inside is a free tool called DB Browser for SQLite. It is a graphical application available for Windows, macOS, and Linux that lets you open a database and browse its tables without writing any code.
Step by step
- Make a copy first. Never open your only catalog directly. Copy the .lrcat file to a separate folder and work on the copy. Make sure Lightroom is closed so the catalog is not locked.
- Open the copy in DB Browser for SQLite. Use File, then Open Database, and select your copied .lrcat file.
- Browse the tables. Switch to the Browse Data tab and look through the tables. The names are technical but readable once you know what to expect.
Useful tables to look at
- AgLibraryFile and AgLibraryFolder: the file names and folder paths of your photos.
- Adobe_images: core records for each image, including capture time and rating.
- AgLibraryKeyword and related tables: your keyword list and how keywords map to images.
- AgHarvestedExifMetadata: camera and exposure information pulled from the files.
What you can find, and what stays hidden
Reading the catalog this way reveals the organizational layer of your library: file locations, ratings, flags, labels, keywords, titles, captions, and capture dates. That is the work that took you the most time, and it is all there in a structured form.
What is not human friendly is your develop edits. Lightroom stores adjustments as encoded instructions in Adobe's own format, so even though you can see that an image has edits, you cannot read them as simple slider values, and you certainly cannot see a finished, edited photo inside the catalog. Remember that the catalog never contained your edited pixels in the first place. It only stores instructions that Lightroom re applies when it renders an image.
Important safety rules
- Always work on a copy. Treat the original catalog as read only so you cannot accidentally corrupt it.
- Close Lightroom before copying. An open catalog may be locked or mid write.
- Do not save changes from a SQLite editor back into a live catalog. Editing the database by hand can break it in ways Lightroom cannot repair.
- Keep a backup of your photos as well as the catalog. They are separate things, and you want both protected.
The easier path: let a tool read it for you
Browsing tables is useful for understanding or recovery, but if your actual goal is to use your catalog data, for example to keep searching and organizing your library outside Lightroom, you do not want to read SQLite tables by hand. A photo manager can do it for you.
Memora reads Lightroom Classic catalogs directly. You point it at your .lrcat file and it maps your folders, ratings, and keywords automatically, then builds a local AI index so you can search your library by describing what is in a photo. Your catalog is opened read only and your original files are never modified. You can see how the catalog reading works on the Lightroom integration page, and the full process is covered in our Lightroom migration guide.
Frequently asked questions
Can I open a .lrcat file without Adobe software?
Yes. A .lrcat file is a SQLite database, so a free SQLite viewer can open it, and tools like Memora can read it directly. You do not need a Lightroom subscription to access the data.
Will opening the catalog damage it?
Not if you work on a copy and open it read only. Avoid editing the database by hand, since manual changes can corrupt a catalog Lightroom still relies on.
Can I see my edited photos inside the catalog?
No. The catalog stores edit instructions, not edited pixels, and those instructions are in Adobe's proprietary format. To see finished edits you either render them in Lightroom or export them as standard image files.
Next steps
Now that you know a Lightroom catalog is just a readable database pointing at your photos, the move off Lightroom feels far less risky. If you want to put that data to work, download Memora free and let it read your catalog, or read the complete guide to migrating from Lightroom Classic.