Lightroom Previews.lrdata Is Huge: Why, and Is It Safe to Delete?

If you have ever run a storage audit on your Mac and watched the bar graph explode, there is a good chance a single folder called Lightroom Previews.lrdata delete-worthy or not-was sitting near the top of the list. Photographers routinely find this bundle consuming 30, 50, even 100 GB alongside their actual catalog, and many have no idea what it contains or whether removing it will wreck their library. This guide explains exactly what lives inside that folder, how Lightroom generates and uses the data, and how to safely reclaim the space whether you are on Apple Silicon or Intel, running macOS Sequoia or the newly released Tahoe.

What Exactly Is Previews.lrdata?

Lightroom Classic stores its catalog in a .lrcat file-a SQLite database-and keeps all rendered preview images in a companion bundle named Previews.lrdata. The two files always live in the same folder, which by default is:

The bundle is technically a macOS package (you can right-click it and choose Show Package Contents to browse inside). Inside you will find thousands of JPEG tiles at several resolutions-typically 1:1 full-resolution previews, Standard previews at your configured pixel size, and small thumbnails. Lightroom generates these the first time you import photos or when you manually select Library > Previews > Build Standard-Sized Previews. They exist so the app can display images at full quality without re-reading your raw files from disk every time you scroll.

Why Does It Get So Large?

The size grows for three compounding reasons:

• 1:1 previews are full-resolution JPEGs. A 45 MP Sony or Nikon raw file can generate a 1:1 preview that is 20–40 MB on its own. A library of 10,000 such images will produce previews that dwarf the raws themselves.
• Lightroom never auto-purges by default. Unless you explicitly configure automatic deletion or run a manual purge, previews accumulate indefinitely-including for photos you have already culled, exported, or moved to a different folder.
• Each catalog has its own bundle. If you maintain multiple catalogs (one per year, one per client, one for mobile sync), each gets its own Previews.lrdata alongside it.

There is also a sibling bundle called Smart Previews.lrdata in the same directory. Smart Previews are lossy DNG files that let you edit photos without the original raws attached. They are smaller individually but can still add up to several gigabytes in a large library.

Size Breakdown: What You Are Actually Storing

Is It Safe to Delete Previews.lrdata?

Yes-with important caveats. Previews are a cache. Deleting the entire Previews.lrdata bundle will not delete your photos, your edits, your metadata, or your catalog. Your .lrcat file holds all of that. What you lose is the pre-rendered cache, so the next time you open Lightroom it will need to regenerate previews as you browse-which takes CPU time and may feel sluggish until the new cache is warm.

Smart Previews are a different story if you frequently work without your external drives attached. If you delete Smart Previews.lrdata and then go offline, images stored on disconnected drives will appear as low-resolution proxies until you reconnect and rebuild. As long as your original files are accessible, deleting Smart Previews is safe; rebuilding them is a menu option away.

How to Delete or Purge Lightroom Previews (Step by Step)

There are two approaches: the controlled in-app purge, and the manual bundle delete. The in-app method is always preferable.

Option 1: Use Lightroom's Built-In Purge

1. Open Lightroom Classic and make sure the catalog you want to clean is active.
2. Go to Library > Previews > Discard 1:1 Previews. This removes only the large 1:1 cache and leaves Standard previews intact for comfortable browsing.
3. Optionally, go to Library > Previews > Discard All Standard Previews if you want a more aggressive purge. Lightroom will rebuild thumbnails automatically next time you browse.
4. To remove Smart Previews you no longer need, select the affected photos in the Library, then go to Library > Previews > Discard Smart Previews.
5. Quit Lightroom fully (Cmd-Q) and wait a moment; the app sometimes defers disk writes until exit.

Option 2: Delete the Bundle Manually in Finder

1. Quit Lightroom Classic completely before touching any catalog files.
2. Open Finder and navigate to the folder that contains your .lrcat file. By default:
   ~/Pictures/Lightroom/
3. Locate Lightroom Catalog Previews.lrdata (the exact name depends on your catalog name). Move it to the Trash.
4. Empty the Trash to release the disk space.
5. Reopen Lightroom. It will create a fresh Previews.lrdata bundle and rebuild thumbnails as you browse. A background render of Standard previews can be triggered via Library > Previews > Build Standard-Sized Previews.

Preventing the Folder from Growing Back

A one-time delete helps today, but the folder will balloon again unless you configure automatic maintenance. Lightroom Classic has a setting that auto-discards 1:1 previews after a period of time:

1. Open Lightroom Classic > Preferences (Cmd-,) and click the Catalog Settings button, or go to Edit > Catalog Settings.
2. Under the File Handling tab, find Automatically Discard 1:1 Previews.
3. Set it to After 30 Days or After One Week depending on your workflow. This keeps 1:1 previews available for recent work while preventing unlimited accumulation.
4. Reduce the Standard Preview Size if your monitor resolution allows it-2048 px is usually sufficient for a 27-inch display and produces much smaller preview files than 4096 px.

Other Hidden Lightroom Files That Eat Space on macOS

While you are auditing the catalog folder, a few more items deserve attention:

• ~/Pictures/Lightroom/Backups/ — Lightroom backs up its catalog on a schedule you set. It never auto-deletes old backups, so this folder can contain dozens of compressed .lrcat.zip copies. Keep the last two or three and delete the rest.
• ~/Library/Application Support/Adobe/Lightroom/ — stores plug-in data, presets, and some cache fragments. Rarely large, but worth a look.
• ~/Library/Caches/com.adobe.LightroomClassicCC7/ — macOS cache for the app itself. Safe to delete; Lightroom will rebuild it on next launch.

If you maintain several applications with similar hidden caches-Capture One, DaVinci Resolve, Final Cut, Xcode-a storage audit tool can surface all of them in one scan rather than requiring you to hunt each folder individually. A tool like Crumb can audit all of these at once and show what's safe before you delete, which reduces the risk of accidentally removing something you still need.

Apple Silicon vs. Intel: Does Architecture Matter?

The Previews.lrdata bundle itself is architecture-neutral JPEG data, so the content and behavior are identical on M1/M2/M3/M4 Macs and older Intel machines. What does differ is performance. Apple Silicon Macs with a fast NVMe controller and the Neural Engine-accelerated JPEG codec regenerate previews significantly faster than older Intel hardware, so the "cold start" penalty after a purge is much less painful. On a MacBook Pro M4 Max, Lightroom can render Standard previews for a thousand raw files in roughly half the time an equivalent Intel Mac requires. This means more aggressive purge schedules are practical on Apple Silicon without noticeably disrupting your workflow.

Quick Summary: Should You Delete It?

If your Mac is running low on storage and you have not touched certain catalogs in months, deleting or purging Previews.lrdata for those catalogs is one of the highest-yield, lowest-risk cleanup moves available. Your photos and all edits are safe inside the .lrcat file. The worst outcome is a slower first browse session while Lightroom rebuilds. For active catalogs, the in-app 1:1 purge combined with a 30-day auto-discard setting is the better long-term habit. To understand what else is contributing to your storage use beyond Lightroom, see our guide to cache files on macOS.