Why Lightroom Classic Culling Is So Slow and How to Fix It

You just got back from a shoot with 2,000 photos on your card. You fire up Lightroom Classic, import everything, and start flagging keepers. Then you hit the right arrow key. And wait. You hit it again. More waiting. The preview loads in a blurry mess before slowly sharpening, and by the time it's sharp, you've already lost your momentum. Sound familiar?

Lightroom Classic is an incredible tool for organizing and editing photos, but its culling workflow has a well-known problem: it's painfully slow. For photographers who need to sort through hundreds or thousands of images quickly, that lag adds up fast. A session that should take 20 minutes stretches into an hour. Your creative flow breaks. You start second-guessing picks because you can't compare images side by side without buffering.

This article breaks down the five most common reasons Lightroom Classic lags during culling and gives you concrete fixes for each one. And if you've already tried everything and still feel stuck, there are faster alternatives like Photopicker that use AI to score and rank your photos instantly, no catalog setup required.

Let's dig into what's actually going on under the hood.

The Preview Problem: Why Lightroom Renders So Slowly

The single biggest culprit behind Lightroom's culling lag is its preview system. Understanding how it works explains most of the frustration photographers experience.

When you import photos into Lightroom Classic, it doesn't display your actual RAW files in the Library module. Instead, it generates preview images, essentially JPEG renderings stored in a preview cache alongside your catalog. There are several types of previews: minimal, embedded, standard, and 1:1. Each serves a different purpose, and the type you're working with has a massive impact on how responsive culling feels.

Minimal and Embedded Previews

If you import with "Minimal" previews selected (which is the default for many photographers), Lightroom pulls the tiny thumbnail embedded in your camera's RAW file. These load fast, but they're low resolution. The moment you zoom in or even try to evaluate sharpness at the Library level, Lightroom has to render a higher-quality preview on the fly. That's the lag you feel when flipping through images.

"Embedded & Sidecar" previews are slightly better. They use the larger JPEG preview your camera writes into the RAW file, which is often good enough for initial culling decisions. But they still aren't full-resolution, and Lightroom may still need to re-render when you zoom.

Standard and 1:1 Previews

Standard previews are Lightroom's own rendered JPEGs at a resolution you configure in your catalog settings. They're great for culling at the Library view level, but rendering them for 2,000 images takes time. The real power move for culling is building 1:1 previews before you start. These are full-resolution renderings that let you zoom in without any lag at all.

The catch? Building 1:1 previews for a large import can take 30 minutes to over an hour depending on your hardware. Many photographers skip this step because they want to start culling immediately, and that's where the cycle of frustration begins.

The fix: After importing, go to Library > Previews > Build 1:1 Previews, select all your imported images, and let Lightroom render them before you start culling. Yes, it means waiting upfront. But the culling experience afterward is dramatically smoother. If you're working with a fast SSD (more on that below), this process goes faster than you might expect.

Another tip: in your Catalog Settings under the File Handling tab, set your Standard Preview Size to match your monitor resolution. If you're on a 2560px-wide display, set it to 2560. Setting it lower means Lightroom has to upscale, and setting it higher wastes rendering time.

According to Adobe's own performance optimization guide , keeping your preview cache size manageable and matched to your display is one of the most impactful tweaks you can make.

Hardware Bottlenecks That Tank Culling Performance

Lightroom Classic is more hardware-dependent than many photographers realize, and the bottlenecks aren't always where you'd expect. You might assume a faster CPU or more RAM is the answer, and while those help, the most common hardware limitation during culling is actually your storage setup.

Your Catalog Belongs on an SSD

Lightroom's catalog file (.lrcat) is essentially a database, and every time you navigate between photos, flag an image, or render a preview, Lightroom reads from and writes to this database. If your catalog is sitting on a spinning hard drive (HDD), every one of those operations is bottlenecked by the drive's mechanical read/write speed.

Moving your catalog and preview cache to a solid-state drive (SSD), ideally an NVMe SSD, is the single most impactful hardware change you can make. The difference is night and day. Photo-to-photo navigation that took 2-3 seconds on an HDD often drops to near-instant on an NVMe drive.

Your actual photo files can stay on a larger, slower external drive if needed. Lightroom reads the RAW files when generating previews but relies on the preview cache and catalog for day-to-day culling. As long as those two things live on fast storage, your culling experience improves dramatically.

RAM and the Camera Raw Cache

Lightroom Classic benefits from having at least 16GB of RAM, and 32GB is even better for large catalogs. But beyond raw memory, there's a hidden setting that makes a noticeable difference: the Camera Raw Cache.

Go to Edit > Preferences > Performance (or Lightroom Classic > Preferences on Mac). You'll find a setting for Camera Raw Cache Size. The default is often set to 1GB, which is absurdly small for photographers working with modern RAW files. Bump this to at least 20GB, or even 40GB if you have the SSD space. This cache stores processed versions of your RAW data, and a larger cache means Lightroom doesn't have to re-process images you've already viewed.

GPU Acceleration

In the same Performance preferences panel, you'll find GPU settings. Lightroom can use your graphics card to accelerate image rendering, but this feature is hit-or-miss depending on your hardware. If you have a modern dedicated GPU (NVIDIA GTX/RTX series or AMD equivalent), enabling "Full" GPU acceleration usually helps. If you're on integrated graphics or an older card, it can actually make things worse. Try toggling it and see if culling feels snappier with it on or off.

The point here is that Lightroom's lag during culling often isn't a software bug. It's a resource problem. The application is doing genuinely heavy work, rendering and caching high-resolution previews from enormous RAW files, and it needs fast storage and sufficient memory to do it without choking.

Catalog Bloat, Smart Previews, and Workflow Mistakes

Even with fast hardware and properly built previews, there are workflow habits and catalog issues that gradually slow Lightroom to a crawl. These are the sneaky performance killers that accumulate over time.

Oversized Catalogs

Lightroom Classic doesn't impose a hard limit on catalog size, and Adobe says it can handle hundreds of thousands of images. In practice, though, catalogs with over 100,000 images start showing noticeable sluggishness, especially during Library operations like filtering, searching, and yes, culling.

Every image in your catalog adds metadata, keywords, develop settings, and collection memberships to the database. The larger that database gets, the longer every query takes. If you've been dumping every photo from every shoot into a single catalog for years, that accumulated weight drags down performance across the board.

The fix: Consider splitting your catalog by year or by project. Go to File > Export as Catalog to create a separate catalog for archived work. Keep your active working catalog lean. Many professional photographers maintain a "current year" catalog for active work and archive older catalogs that they only open when needed.

Smart Previews: Friend or Foe?

Smart Previews are compressed DNG files that let you edit photos even when the original files are offline (like on a disconnected external drive). Some photographers build Smart Previews for everything, thinking it will speed up culling. It can, but with a trade-off.

Smart Previews are great for the Develop module because they let you make adjustments without accessing the full RAW file. But in the Library module during culling, they add another layer of data that Lightroom has to manage. If you've built Smart Previews, 1:1 Previews, AND Standard Previews for the same set of images, your preview cache balloons in size and Lightroom spends more time managing it.

For culling specifically, Standard or 1:1 Previews are what you want. Build Smart Previews later when you move into editing.

Embedded Preview Culling Trick

There's a lesser-known workflow that some photographers swear by: culling using only embedded previews before Lightroom renders anything else. During import, select "Embedded & Sidecar" previews. Then immediately start culling in the Library module using Loupe view. Because Lightroom is displaying the camera-generated JPEG (which loads almost instantly), you can flip through photos at full speed.

The downside is that you're evaluating a JPEG interpretation of your RAW file, not Lightroom's rendering. Colors and exposure might look slightly different from what your final edit will produce. For rough first-pass culling (keep vs. reject), this is usually fine. For critical sharpness evaluation, you'll still want 1:1 previews.

Another common mistake: having too many panels open in Library mode. Every open panel (Histogram, Quick Develop, Keywording, Metadata) refreshes as you move between photos. Collapse panels you don't need during culling. Use Tab to hide side panels entirely and give Lightroom fewer things to update per image.

If your catalog has gotten bloated with duplicates over years of importing, that's another source of drag. Identifying and removing near-duplicate photos can meaningfully reduce catalog size. Photopicker's duplicate detection uses perceptual hashing to automatically cluster similar images and flag redundancies, which can help you clean up before or after a Lightroom session.

When Fixes Aren't Enough: Rethinking the Culling Workflow

Here's the uncomfortable truth that many photographers eventually arrive at: even with every optimization applied, Lightroom Classic's culling workflow is fundamentally limited by its architecture. It was designed as a comprehensive photo management and editing suite, not a purpose-built culling tool. Preview rendering, catalog database queries, and module switching all add overhead that pure culling tools don't have.

If you've moved your catalog to an NVMe SSD, built 1:1 previews, bumped your Camera Raw Cache to 40GB, and you're still watching previews stutter as you flip through photos, the problem isn't your settings anymore. It's the tool.

What a Faster Culling Workflow Looks Like

The fastest culling workflows separate the selection phase from the editing phase entirely. Instead of importing into Lightroom, waiting for previews, culling, and then editing all within the same application, you cull first in a lightweight tool and only bring your selections into Lightroom for editing.

This is where AI-powered scoring changes the game. Rather than manually flipping through every image and making subjective keep/reject decisions while fighting preview lag, you can upload a batch of photos and let an AI evaluate quality, sharpness, composition, and exposure across every image simultaneously.

Photopicker does exactly this. You drag and drop up to 500 photos (or import from Google Drive), and its AI scores each image across five dimensions: quality, aesthetics, composition, sharpness, and exposure. Photos are ranked into tiers, S-tier (top 10%), A-tier (top 30%), B-tier (top 60%), and Pass, so you immediately see which shots are your strongest without touching a single preview render.

The duplicate detection is particularly useful for photographers. If you shot 15 nearly identical frames of the same pose, Photopicker clusters those duplicates using perceptual hashing and selects the sharpest, best-composed winner from each group. That alone can cut your Lightroom import in half.

A Hybrid Workflow

The most efficient approach for many photographers is hybrid:

1. Upload your shoot to Photopicker directly from your card or drive
2. Review the AI rankings to identify your top-tier images and reject obvious misses
3. Download your curated set (Starter and Pro plans at photopicker.com/pricing include full ranked ZIP downloads)
4. Import only the keepers into Lightroom for editing and final delivery

This workflow eliminates the two biggest time sinks: waiting for Lightroom previews and manually evaluating every single frame. You still use Lightroom for what it does best, developing and exporting final images, but you skip the part where it struggles most.

For photographers who want even deeper reading on breaking free from Lightroom's culling bottleneck, there's a full breakdown of AI alternatives for photo culling that covers the topic in more detail.

Quick-Reference Fix Checklist

Before you go, here's everything covered in this article as a scannable checklist:

• Build 1:1 or Embedded & Sidecar previews before culling
• Set Standard Preview Size to match your monitor resolution
• Move your catalog (.lrcat) and preview cache to an NVMe SSD
• Increase Camera Raw Cache to 20-40GB in Preferences > Performance
• Test GPU acceleration (enable or disable based on your hardware)
• Keep your working catalog under 100K images by archiving old shoots
• Collapse unused Library panels during culling sessions
• Skip Smart Previews for culling (build them later for editing)
• Consider AI-powered pre-culling to reduce what you import into Lightroom

Lightroom Classic isn't going anywhere, and for editing, it remains one of the best tools available. But culling thousands of photos doesn't have to mean fighting with preview rendering and catalog lag. Fix what you can, and for everything else, let AI handle the heavy lifting.