Why Lightroom is slow for culling (and what to do instead)

Lightroom Classic is an excellent photo editor. It's also one of the slowest tools you can use for culling. This isn't subjective. It's architectural. The same design decisions that make Lightroom powerful for editing, organizing, and managing a 200,000-image catalog across multiple drives make it fundamentally sluggish when all you want to do is flip through 2,000 images and decide which ones to keep. If you've ever felt like Lightroom is fighting you during a cull, it's not your computer. It's the software doing exactly what it was designed to do, which is a lot more than you need at that stage of your workflow.

The catalog model: power and overhead

Every action you take in Lightroom writes to a SQLite catalog file. Flag an image as a pick? That's a database write. Move to the next image? Lightroom pre-fetches metadata and checks the catalog. Reject a frame? Another write, plus it updates the filter counts in your Library view. For editing, this catalog model is brilliant. It means every adjustment is non-destructive, searchable, and reversible. For culling, it's dead weight. When you're pressing P and X at speed on 2,000 images, you're generating thousands of small database transactions. On a spinning hard drive, this is painfully slow. On an SSD, it's better but still measurably slower than a tool that just reads files from disk without maintaining a database. The catalog also locks the file while writing, which means Lightroom can't load the next image preview while it's still committing the flag you just set on the current one. That tiny lag, maybe 200 to 500 milliseconds, doesn't sound like much. But at 2,000 images, those half-second pauses add up to 15 or 20 minutes of just waiting.

Preview generation: the hidden bottleneck

Before you can cull in Lightroom, you need to import your images. And during import, Lightroom generates previews. You have four options: Minimal, Embedded & Sidecar, Standard, and 1:1. Minimal previews load fast but look terrible. You'll be staring at pixelated thumbnails that re-render every time you click on an image, which defeats the purpose of culling quickly. Embedded previews use the JPEG that your camera wrote into the RAW file. These are decent quality and relatively fast to extract, but Lightroom still needs to read each RAW file and pull out the embedded data. For 2,000 Canon CR3 files at 30MB each, that's 60GB of file reading just to generate previews. Standard previews render the RAW data at a resolution you configure (usually 2048px on the long edge). These look good in the Library module and render from cache when you navigate. But generating them takes 15 to 45 minutes for a 2,000-image shoot, depending on your CPU. And 1:1 previews? These are full-resolution renders of every single RAW file. They look perfect. They also take an hour or more to generate and consume gigabytes of disk space. No matter which option you choose, you're spending significant time on preview generation before you even start evaluating images. A dedicated culling tool skips this entirely by reading and decoding images on the fly, using GPU-accelerated rendering to display each file in real time as you navigate to it.

Import before cull: the wrong order

Lightroom's workflow assumes you import first, then organize, then edit. Culling happens inside this pipeline, after import, inside the catalog. This means every image you ultimately reject was imported, previewed, cataloged, and stored. For a wedding shoot where you reject 50% of your frames, you just imported and previewed 1,500 images you're going to throw away. That's not just wasted time. It's wasted disk space (preview cache), wasted catalog bloat (1,500 database entries you'll later delete), and wasted organizational overhead (those rejected files show up in your folder structure, your smart collections, and your date-based filters until you explicitly remove them). The alternative is culling before import. Review your images in a lightweight tool that reads directly from your card dump folder, make your pick and reject decisions, then import only your selects into Lightroom. Your catalog stays lean. Your previews are only generated for images you'll actually edit. And your Lightroom experience is faster for everything else because the catalog is smaller.

The Library module wasn't built for speed

Lightroom's Library module is a photo management interface. It handles folders, collections, smart collections, keyword hierarchies, face recognition, map views, and publish services. All of those features load data, update the UI, and consume resources while you're trying to cull. When you press the right arrow key to move to the next image, Lightroom isn't just loading a preview. It's updating the metadata panel, refreshing the histogram, checking keyword suggestions, and potentially running face detection in the background. Each of those operations is lightweight on its own, but together they create a noticeable drag on navigation speed. Lightroom also doesn't have a true auto-advance option built into its core workflow. You can toggle Caps Lock to enable auto-advance for flagging, but it's a modal toggle that's easy to forget, and it doesn't work with all rating methods. Compare this to a purpose-built culling tool where auto-advance is the default behavior, there's no metadata panel updating between frames, and the entire interface is optimized for one thing: showing you the next image as fast as possible.

What about Lightroom CC (cloud)?

Lightroom CC (the cloud-based version, as opposed to Classic) is even worse for culling. It uploads your original files to Adobe's cloud before you can work with them, which means your culling speed is now limited by your upload bandwidth. For a 60GB wedding shoot on a typical home connection, you could be waiting hours before all your images are available at full quality. Lightroom CC's strength is accessibility across devices and automatic cloud backup. Those are real benefits for some photographers. But for the specific task of sitting down after a shoot and quickly sorting 2,000 to 5,000 images, it adds latency at every step.

The modern workflow: cull first, Lightroom second

The photographers who have the smoothest Lightroom experience are often the ones who don't cull in Lightroom at all. Their workflow looks like this: dump cards to an SSD folder, open the folder in a dedicated culling tool (Selekt, Photo Mechanic, or similar), cull at speed with keyboard shortcuts and instant image loading, export selections with XMP sidecar files that carry star ratings, then import only the selects into Lightroom. When they open Lightroom, they're looking at 600 to 800 curated images instead of 3,000 raw frames. Preview generation is 3x faster because there are 3x fewer files. The catalog is smaller and more responsive. Every image in the Library module is one they actually plan to edit. This isn't a workaround. It's how high-volume professionals have worked for years, going back to the Photo Mechanic plus Lightroom combination that wedding photographers standardized a decade ago. The difference now is that you don't need to choose between Photo Mechanic's speed and a modern interface. Tools like Selekt give you the same instant-loading, keyboard-driven culling workflow with an interface that doesn't feel like it's from 2006.

Making Lightroom faster if you must cull there

If you prefer to keep your entire workflow inside Lightroom, there are things you can do to reduce the friction. Build 1:1 previews before you start culling and go do something else while they render. Use the Embedded & Sidecar preview option during import for faster initial loading, then build Standard or 1:1 previews in the background. Turn off face detection during import (it competes with preview generation for CPU time). Close every panel you don't need: Map, Book, Print, Web. Keep only Library open with the Navigator, Metadata, and Filmstrip panels. Use Caps Lock to toggle auto-advance when flagging. Work from an NVMe SSD, not a hard drive or network share. Keep your catalog file on the SSD too, not on the same drive as your images. These optimizations help. They can take Lightroom from genuinely painful to merely adequate for culling. But they're optimizations around a fundamental architecture that wasn't designed for rapid image triage. At some point, the faster solution is to use the right tool for the right job: a culling tool for culling, Lightroom for editing.