Lightroom Classic Cache on Mac: Previews, RAW and Backups

Lightroom Classic can fill a disk with previews even when the photo originals live on another drive. Before deleting anything, separate the working catalog, previews, Camera Raw cache and old catalog backups, then change only the store that accounts for the space.

Find the Active Catalog First

Adobe's catalog management guide documents Lightroom Classic › Catalog Settings › General, where Show reveals the active catalog in Finder. Start there instead of assuming the largest Lightroom folder is the one you use.

Record its location and inspect nearby items. Adobe's file-location reference distinguishes the catalog, preview stores and backups. Names below describe file types, not instructions to remove the entire folder.

Do not delete original photos, presets or catalog companion files just because they sit beside a large preview store. In particular, Adobe says the catalog journal is used for incomplete database records and should not be deleted independently.

Reduce Ordinary Previews First

In the catalog settings, review preview size, quality and automatic disposal of 1:1 previews. These controls affect rendered previews, rather than deleting original photographs. Note your current settings before making a change so you can restore them.

Current Adobe documentation also describes a preview-cache limit. If your installed version offers it, choose a budget there, but do not expect immediate removal: recent previews are retained and cleanup runs when the app is idle. A limit is not an instant disk-space button.

Change one setting, continue your usual browsing, and compare the same preview store later. If viewing becomes too slow, restore the previous setting. Smaller storage and faster browsing are a trade-off, not two guaranteed outcomes of clearing previews.

Rebuild Previews Only With Sources Available

For a preview-cache error or gray thumbnails, Adobe's preview repair instructions give a narrower Mac procedure:

1. Quit Lightroom Classic.
2. Open the active catalog's folder recorded earlier.
3. Move only the matching Previews.lrdata item to the Trash, leaving the catalog and Smart Previews intact.
4. Reopen that catalog and check the affected photographs.

Adobe warns that browsing can be slower while previews rebuild. Have the originals available first, particularly for archived or disconnected photographs, because deleting a preview does not recreate its missing source.

Keep the removed item in the Trash while you check the result, and do not permanently delete it until you have decided whether rebuilding worked. Recovery requires that the removed item still exists, so keep the original photographs and catalog backed up independently as well.

Treat Smart Previews as an Offline Choice

Adobe's Smart Previews guide explains their separate role when originals are unavailable. They are not the ordinary preview cache, and removing them can take away your ability to edit those photographs with the originals disconnected.

Reconnect the original drive and verify the needed photographs before removing Smart Previews. Select only photographs that no longer need this offline copy, then use Library › Previews › Discard Smart Previews. Keep the rest.

To reverse that choice, reconnect the originals, select those photographs and use Library › Previews › Build Smart Previews. Rebuilding takes work and requires accessible sources, so do not discard your only usable editing copy on the assumption it will appear again automatically.

Set the Camera Raw Cache Budget and Location

Adobe's performance guide places Camera Raw cache controls in Lightroom Classic › Preferences › File Handling. Record the shown location and maximum size before changing either, rather than deleting a guessed Adobe folder.

Use Purge Cache for that cache, or adjust Maximum Size to your storage budget. Choose changes its location. A smaller cache can mean more processing during later Develop work, and relocating it changes which disk holds the data rather than eliminating the need for storage.

Check the same cache location afterward, then open a raw photograph in Develop. If performance suffers, restore the earlier budget or choose a suitable available location. Purging does not provide a Trash-based undo, and rebuilding depends on having the source photographs.

Review Catalog Backups Separately

Adobe's backup guide describes dated backups under a Backups folder and allows another destination. Check the configured location instead of assuming every catalog uses the default.

Lightroom Classic 14.2 and later provide a Backups panel in catalog settings. Its Delete action removes backups from disk, whereas Remove only removes entries from the list. Keep a recent verified recovery point and older versions you still need before deleting selected backups.

A catalog backup is not a backup of the original photographs. Preserve those separately, preferably keeping recovery copies away from the working disk. To check a catalog backup, follow Adobe's restore procedure using a separate copy, without replacing your working catalog merely to test it.

Shared installer and Creative Cloud data are a different task, covered in Creative Cloud leftovers. For the broader storage picture, see Mac System Data.

Where Mole Fits

Mole Mac has no dedicated Clean catalog entry for Lightroom catalog previews or catalog backups. Its generic sweep can offer eligible Adobe folders under ~/Library/Caches, so a Camera Raw cache there may appear, but this does not cover every custom location or make every Lightroom file disposable. Use Adobe's controls for this distinction.

FAQ

Can I Delete the lrcat File to Clear Cache?

No. Keep the working catalog and its associated data, and identify the separate preview store or Camera Raw cache instead.

Can Smart Previews Be Rebuilt?

Yes, with the original photographs accessible. Keep them while they are needed for editing without the original drive.

Why Did the Space Not Return Immediately?

Check whether the removed preview item is still in the Trash, whether a different cache location was measured, or whether previews were generated again during browsing.