Open Activity Monitor while Lightroom Classic is running and you will see a single process sitting anywhere from 2 GB to well above 8 GB, depending on what you are doing. For most photographers this lands in the "huh, that's a lot" category rather than the "something is wrong" category. Lightroom is a memory-hungry application by nature, and understanding why makes it much easier to decide when to act and when to leave it alone.
Adobe's own Lightroom Classic system requirements page lists 16 GB of RAM as the recommended amount, with 8 GB as the stated minimum. In practice, those numbers reflect a real boundary: below 16 GB, Lightroom's behavior changes noticeably during memory-intensive operations.
Where Lightroom's memory goes
Lightroom Classic does not use a single pool of memory for everything. Its footprint is made up of several distinct caches and subsystems, each of which can grow independently.
Catalog cache. Lightroom keeps a working copy of your catalog database in memory. For small catalogs this is modest, but large catalogs with tens of thousands of images and extensive metadata carry a proportionally larger in-memory footprint. The catalog cache is loaded on launch and stays resident throughout the session.
Smart Previews. Smart Previews are compressed DNG files Lightroom generates alongside your catalog, sized to allow editing without the original raw file present. When you work in the Develop module with Smart Previews active, Lightroom loads these into memory. On a catalog with many Smart Previews enabled, this adds up quickly.
GPU preview compositing. Lightroom uses the GPU to composite the Develop module panels, histogram, and canvas. The GPU VRAM usage is separate from the main RAM figure in Activity Monitor, but Lightroom also allocates system RAM to manage the GPU pipeline. Enabling GPU acceleration (the default) shifts some display work off the CPU, but it still has a system RAM cost.
Develop module history. Every slider adjustment you make in the Develop module is stored as a history state. Lightroom holds these in memory so that stepping backward through the history panel is instant rather than a re-render. After a long editing session with many adjustments across many images, the accumulated history cache is a meaningful share of Lightroom's total footprint.
The 23GB anecdote explained
The specific number - 23 GB on a 32 GB Mac - comes from a catalog rebuild, not from normal editing. It represents a genuinely different category of memory use.
Catalog rebuilds. When Lightroom rebuilds a large catalog, it reads every record in the database, processes metadata for each image, and rewrites the catalog file. Large chunks of the catalog are loaded into RAM simultaneously. On a catalog with 100,000 or more images, this is legitimately heavyweight. The 23 GB figure is plausible on a catalog of that scale: the catalog itself, the preview cache, the metadata processing buffer, and macOS's own working set all competing for the same 32 GB.
Smart Previews during rebuild. If Smart Preview generation is running concurrently, the memory load multiplies. Each Smart Preview is a compressed DNG file that must be decoded and re-encoded, which is both CPU and RAM intensive.
Library module previews. During a rebuild, Lightroom may regenerate 1:1 previews across the catalog. A 1:1 preview for a 45-megapixel raw file is several hundred megabytes of uncompressed image data. Lightroom holds many of these in its preview cache simultaneously during the operation.
Seeing memory use climb to 20 GB or more during a rebuild is not Lightroom misbehaving. It is Lightroom doing exactly what was asked of it, at full effort.
Realistic numbers
Outside of catalog rebuilds, here is what to expect in normal use:
- Idle, catalog open, no images selected: 1.5-3 GB. The catalog is loaded, the preview cache is warm, but Lightroom is not actively decoding anything.
- Library module, browsing a grid of 200 images: 3-5 GB. Thumbnail previews for the visible grid are loaded, and Lightroom prefetches previews for adjacent images as you scroll.
- Develop module, editing a single raw file: 4-7 GB. The full-resolution raw is decoded, the GPU pipeline is active, and develop history is accumulating. Higher-megapixel cameras (45 MP and above) push toward the top of this range.
- Batch export, 500 images to JPEG: 6-10 GB. Lightroom decodes multiple raw files simultaneously to keep the export queue fed, which spikes memory use well above the single-image editing figure.
These numbers assume Lightroom Classic on an Apple Silicon Mac with 16-32 GB of unified memory. On Intel Macs, the figures tend to be slightly higher because the unified memory architecture handles the GPU-CPU boundary differently. For a broader look at how 8 GB compares to 16 GB for creative work, the differences matter most in exactly these batch operations.
Settings that actually reduce memory
Lightroom exposes several settings that have a direct and measurable effect on memory use. Not all of them are obvious.
Preview cache size. This is the most impactful setting. Go to Lightroom Classic Preferences, then Catalog Settings, then File Handling. The "Standard Preview Size" option controls the resolution of the previews Lightroom generates for the Library module. Setting this to match your monitor resolution rather than the highest available option significantly reduces how much RAM the preview cache consumes. The default is often set too high. Dropping from 2880 px to 1440 px on a standard display halves the memory needed per preview.
Automatically discard 1:1 previews. In the same Catalog Settings panel, find "Automatically Discard 1:1 Previews" and set it to "After One Day" or "After One Week". Full-resolution 1:1 previews are large and Lightroom generates them whenever you zoom in on an image in the Develop module. Left unchecked, they accumulate. This setting clears them automatically so the preview cache stays bounded.
Smart Preview generation. If you do not edit away from your originals (that is, your raw files are always connected), you do not need Smart Previews. In the Import dialog, leave "Build Smart Previews" unchecked. For an existing catalog with Smart Previews already generated, you can remove them from Library, Previews, Discard Smart Previews. This frees both disk space and reduces the memory Lightroom needs to manage the Smart Preview index.
GPU acceleration. Lightroom Preferences, Performance tab. GPU acceleration is beneficial for most users: it makes the Develop module more responsive and reduces the CPU load during panel adjustments. Disabling it does not meaningfully reduce RAM use in most cases, and makes Lightroom feel slower. Leave it enabled unless you are experiencing rendering glitches or crashes, which can indicate a GPU driver conflict.
If your Mac is also running Photoshop alongside Lightroom, the memory competition between the two is covered in the Photoshop on 8 GB Mac guide. The short version: Lightroom and Photoshop should not both be running at full effort simultaneously on anything less than 32 GB.
Lightroom Classic vs Lightroom (cloud) memory differences
Adobe sells two products under the Lightroom name, and they behave very differently with respect to memory.
Lightroom Classic is the local-catalog application. It stores everything on your Mac: the catalog database, the preview cache, the original raw files (if you choose), and the Smart Previews. All of this lives in RAM when Lightroom is running and the data is needed. This is why Classic can hit 8 GB or more during normal editing sessions.
Lightroom (cloud-based, sometimes called just "Lightroom") is a different application. It does not maintain a local catalog in the same way. Originals are stored in Adobe's cloud, and the local application manages a subset of cached images for offline work. Because the local preview cache is smaller and the catalog management overhead is handled server-side, memory use is significantly lower. Typical sessions run in the 1-3 GB range.
The trade-offs are real. Lightroom Classic gives you full local control: your catalog is yours, offline access to everything, compatibility with the full Lightroom plugin ecosystem, and no dependency on cloud sync. Lightroom (cloud) gives you lighter hardware requirements and seamless multi-device sync, at the cost of always needing Adobe's infrastructure for your full library.
For photographers on an 8 GB Mac who find Classic uncomfortably slow, switching to Lightroom (cloud) is a legitimate option rather than a compromise. For photographers with large existing catalogs, custom plugin workflows, or a need to work fully offline, Classic is the only real choice, and the memory cost is the price of that control. Understanding what memory pressure means on Mac helps you read whether Lightroom is actually causing a problem or just using what macOS has made available to it.