Why Lightroom Classic folders fail photographers with large catalogs

By David · May 6, 2026 · 10 min read

The Folders panel in Lightroom Classic looks like a filing cabinet. It is a filing cabinet — every folder you see maps to a real directory on your hard drive, and every move you make there changes something on disk. That's fine at 2,000 photos. At 20,000, it starts to feel constricting. At 80,000, it breaks.

The problem isn't photo volume. It's that folders are a one-to-one system trying to handle a many-to-many world.

What folders actually do — and where they stop

Every entry in the Folders panel corresponds to a real directory on disk. That makes the Folders panel useful as a safety net: you always know exactly where a file lives, and if a drive gets disconnected or a folder gets renamed outside Lightroom, you can reconnect it without data loss.

But folders carry one constraint with no workaround: each photo exists in exactly one folder. Think about what that means in practice. You shoot a week in Iceland. The files land in /Photos/2025/Iceland/. A few months later you want to pull together your best landscape shots — Iceland, Norway, Patagonia, Japan — for a portfolio review. With folders, you navigate each country directory separately, make temporary selections, and either duplicate files or work from four scattered screens simultaneously.

The Folders panel also disappears the moment you leave the Library module. Switch to Develop to edit a photo and your folder tree is gone. You'd have to go back to Library, find the folder, select the photo, then switch back to Develop. The Collections panel appears in every module: Library, Develop, Map, Book, Print, Slideshow, and Web.

There's also a safety issue. Removing a photo from a folder in Lightroom prompts you to delete the actual file. One misclick on 80,000 photos is a real problem. Removing a photo from a collection never touches the file.

Collections: virtual groupings that leave your files alone

Think of a collection as a playlist. When you add a song to a playlist you're not copying the audio file — you're saving a pointer to it. Collections work the same way. The Iceland shot, the Norway shot, and the Japan shot can all be in a "Landscapes - portfolio" collection. The originals are still in their folder directories. The collection is just a list of references to them.

The same photo can be in ten collections simultaneously with no storage penalty and no duplicated files. A wedding shot that also happens to be a strong portrait and a good black-and-white candidate can sit in "Wedding - Chen 2025", "Portraits 2025", and "B&W shortlist" at the same time, all pointing at the same original RAW file.

Lightroom Classic has four collection types, each serving a different purpose.

Regular collections are manually curated. You drag photos in, or right-click any collection to set it as the Target Collection, then tap B to add any selected photo instantly. This is the fastest culling method I know: no star rating system, just tap B on anything worth keeping. It forces a binary decision and you move through a shoot much faster.

Quick Collections are Lightroom's scratch pad. Tap B on a photo before you've set a Target Collection and it lands here. Quick Collections are temporary by design. Use one for a first pass on a freshly imported shoot, then convert it to a named regular collection once you know what the group is.

Collection Sets are containers for collections, not for photos. A set called "Client Work 2026" can hold twelve collections inside it, one per client. Sets can be nested up to five levels deep, though two or three is usually enough before the hierarchy becomes its own navigation problem.

Smart Collections are the type that actually change how a catalog scales at volume. They get their own section below.

Smart collections: the part that actually scales

A smart collection has no manual curation. You define rules and Lightroom populates it, forever. Set one rule — "Rating is greater than or equal to 4 stars" — and every photo in your entire catalog that meets that threshold appears immediately, including shots from five years ago you rated last week. Change a photo's rating and it drops in or out of the collection in real time.

Lightroom ships with five built-in smart collections: Colored Red, Five Stars, Past Month, Recently Modified, and Without Keywords. Most people notice Five Stars and ignore the rest. Without Keywords is probably the most actionable: it shows every untagged photo in your catalog at a glance, which tells you exactly how much organizational debt you're carrying before you even start.

You can build your own from around 25 criteria: star rating, pick flag, color label, keyword, date captured, GPS data, camera model, lens, ISO, file type, publish status, face recognition status, and more. You can require all rules to match or any rule, and some criteria support nested AND logic.

Here are six smart collections actually worth building:

Once these are in place, navigating by folder becomes almost optional. Your working collection stays one click away, and everything else is findable through rules rather than memory.

Folders vs collections vs smart collections

Here's how the three systems compare across the features that matter most in day-to-day use:

The last row is worth noting if you use any Lightroom plugins. The Lightroom SDK lets plugins create, populate, and update collections programmatically. Folders are read-only from the plugin side, which is why most plugin output ends up in collections rather than being filed to disk.

Three scenarios where the folder system breaks down

80,000 photos, five years of wedding work. A recurring family has appeared as guests at three different weddings across five years. Their photos are split across three date folders: 2021/Chen-Wedding, 2023/Reyes-Wedding, and 2025/Kim-Wedding. With folders, finding every photo of this family means navigating three directories and working from separate, non-contiguous selections. With a collection, you drag in the relevant shots from all three events once, name it "Guest family - Martinez", and it's done. When they show up at a fourth wedding in 2027, you add those shots in 30 seconds.

140,000 photos, ten years of travel. You want to pull together all your night sky shots — Iceland, Namibia, New Zealand, Joshua Tree — for a gallery print series. The photos span ten years of folder hierarchies across four continents. A smart collection with two rules ("Keyword contains 'stars'" and "Rating is 4 stars or higher") surfaces every qualifying shot in under a second. The catch: you need consistent keywording going back through the catalog. Collections reward that consistency in a way folders never will, because the payoff compounds with every photo you add.

90,000 photos, seven years of family life. Your kids have grown from toddlers to teenagers across your catalog, and every year folder has the same faces. A smart collection keyed to a name keyword — applied consistently each time you keyword a shoot — pulls every photo of one child from 2019 through today into a single view, sorted however you like. That view is immediately useful for a birthday slideshow, a school project, or a photo book. The folder-based equivalent means opening seven year folders manually, which usually means it never happens.

One photo, many collections — the unlock

This is the concept that takes the longest to internalize, especially if you've spent years in a folder-first workflow. A folder system is zero-sum: each photo belongs to exactly one place, so every filing decision is also a prioritization decision. You're always picking the one category that matters most and throwing away the rest.

Collections are not zero-sum. A shot of my daughter at her grandmother's kitchen table in Tel Aviv is simultaneously a portrait, a family memory, a travel photo, a Rosh Hashana shot, and a potential print. In a folder I'd pick one. In collections, all five exist — each with zero storage overhead, each showing the same original file.

For photographers who license work, this becomes a business tool rather than a convenience. A "Licensed to Getty" collection, a "Submitted to agency" collection, and a "Available for re-licensing" collection can all contain the same image at the same time with different status meanings. Tracking that in a folder system would require duplicate files or a spreadsheet maintained alongside Lightroom, both of which are their own form of organizational debt.

Setting up a collection system this week

You don't need to reorganize your hard drive to get started. Keep your existing folder structure exactly as it is — it's doing its job as a file-location record. Build collections on top of it.

A setup that works for most photographers: one top-level Collection Set per year (2024, 2025, 2026). Inside each year, one Collection per major shoot or project. For themes that span years — portfolio work, a specific client, a personal project — create a top-level Collection Set for that theme with individual collections inside it, regardless of which year the photos were shot.

Then build five smart collections from scratch. Start with Five Stars (your best work, across all time), Flagged-no-label (your current edit queue), Without Keywords (your organizational backlog), Last 30 Days (your recent import window), and one project-specific rule that fits what you're working on right now.

Right-click the collection you use most and set it as your Target Collection. From that point, B is your one-key add shortcut — any selected photo drops in instantly, from anywhere in Lightroom, regardless of which module you're in or which folder contains the file.

Give this setup 30 days. The Collections panel will have more of your actual working workflow in it than the Folders panel ever did.

When plugins auto-populate collections

This is where the collection system becomes genuinely interesting from a tooling perspective. When I built the Face Tagger plugin for Lightroom Classic, the entire output layer is collection-based. Not because folders wouldn't have worked conceptually, but because the Lightroom SDK lets plugins create and populate collections programmatically. Folders are read-only from the plugin side — there's no API to file a photo into a directory.

After Face Tagger scans a catalog, it creates a "Face Tagger Results" Collection Set. Inside it: one collection per recognized person (named after them), a "No Face Detected" collection for photos that found no face, and a "People Detected - No Face" collection for shots where someone appears from behind or too far away to identify. A scan of 3,000 family photos typically produces 6 to 10 named collections with no manual dragging.

Combine that with a smart collection keyed to a person's name keyword — which Face Tagger applies during the scan — and the two systems reinforce each other. The plugin populates the named collection per person; the smart collection picks up any additional shots keyworded later. Add more photos, run another scan, and both update.

That feedback loop is what makes a large family catalog actually searchable rather than just technically organized. The photos are in folders because they have to be. The catalog is in collections because that's where the work happens.