How to Organize Your Lightroom Catalog for Large Photo Libraries: Folders, Collections, and Keywords
If you shoot weddings or events, your library grows by 3,000 to 8,000 frames per job. After three or four seasons, most photographers hit the same wall: scrolling takes forever, search returns nothing useful, and finding “that one detail shot of the ring box from 2023” turns into a 20 minute archaeology dig. The problem is almost never the software. It is the structure. This guide gives you a complete, repeatable way to organize your Lightroom catalog so it stays fast and searchable past 100,000 images, and you can set it up in a single afternoon. See mitchellens.ink for their take. Everything below is written for Lightroom Classic (the folder-based version professionals use for large archives). Where the cloud version of Lightroom behaves differently, we flag it. The 30 Second Version: The System at a Glance Layer What it does Rule of thumb Folders Where files physically live on disk One parent folder, then Year > Date_Client. Never change again. Collections Virtual groupings for delivery stages One collection set per job: Selects, Retouch, Delivered, Portfolio. Smart Collections Auto-updating saved searches Build 8 to 10 once, use them forever. Keywords Cross-catalog search across all years Hierarchical, controlled vocabulary, max 5 top-level branches. Flags, stars, colors Speed of culling and status tracking Flags = culling. Stars = quality. Colors = workflow status only. Each layer has exactly one job. The single biggest mistake in large catalogs is asking folders to do the work of keywords, or using stars to mean five different things depending on the year. Step 1: One Catalog, One Parent Folder Use one catalog, not one per wedding Splitting your archive into a catalog per year or per client feels tidy but destroys the thing that makes Lightroom valuable at scale: search across everything. Lightroom Classic handles hundreds of thousands of images comfortably when the catalog file sits on an internal SSD. Speed problems in big catalogs come from preview settings, spinning drives, and bloated history steps, not from image count. Keep a second, temporary catalog only for one situation: shooting on a laptop on location, then merging back into the master catalog with File > Import from Another Catalog. Much the same conclusion turns up on photoshopcafe.com. Separate the catalog from the photos These are two different things and they belong on two different drives: Catalog file (.lrcat) and previews: internal SSD, in a folder like /Users/you/Lightroom/. This is what determines whether browsing feels instant. Photos: a large external SSD or RAID, with one single parent folder named something boring and permanent like PHOTO_ARCHIVE. Backups: a separate drive plus offsite or cloud. Your catalog is a database. If it dies without a backup, every edit, keyword and collection dies with it. The parent folder rule matters more than it looks. When every image lives under one root, moving your archive to a new drive later means Lightroom asks you to relink once, not 400 times. Step 2: A Folder Hierarchy That Never Needs Rethinking Folders should answer one question only: when and for whom was this shot? Nothing about content, nothing about status. PHOTO_ARCHIVE/ ├── 2026/ │ ├── 2026-05-16_Dupont-Lefevre_Wedding/ │ │ ├── 01_RAW/ │ │ ├── 02_Exports_Web/ │ │ └── 03_Exports_Print/ │ ├── 2026-06-06_Nakamura_Engagement/ │ └── 2026-06-20_ACME-Corp_Gala/ ├── 2025/ └── 00_Personal/ Why the date comes first Starting each folder with YYYY-MM-DD means the operating system and Lightroom both sort chronologically without any effort, and two clients with the same surname never collide. Adding the client name and job type after the date makes the folder readable in a file browser even if Lightroom is not open, which matters when a client emails you in four years. Folder naming rules to lock in today Use ISO dates: 2026-05-16, never 16-05-26 or May16. No spaces. Use hyphens or underscores. Cloud sync tools and web servers will thank you. No accents or special characters in folder or file names. Job type suffix from a fixed list: Wedding, Engagement, Elopement, Gala, Corporate, Portrait, Personal. Two-shooter jobs go in the same folder, not separate ones. Sort by capture time after syncing camera clocks. File renaming on import Never keep IMG_4471.CR3. Duplicate file names across years cause chaos in exports, client galleries and album design software. Build one import preset with a filename template: Template Result {Date YYYYMMDD}_{Custom Text}_{Sequence 0001} 20260516_Dupont-Lefevre_0001.CR3 One import preset, one custom text field to fill per job, and every file in your archive becomes globally unique and self-describing. Step 3: Collections Do the Work Folders Should Not Folders are physical and permanent. Collections are virtual, so an image can live in ten of them without duplicating a single byte on disk. This is where your delivery workflow lives. The per-job collection set For every wedding, create a collection set named exactly like the folder, inside a year-level collection set. Inside it, four collections: 01 Selects – everything that survived culling, in delivery order. 02 Retouch – the 30 to 60 frames needing skin work, composites or sky replacement. 03 Delivered – the exact final set sent to the client. This is your legal and reprint reference. 04 Album – the spread selection, set as a target collection while designing. Add two global collection sets sitting above the years: PORTFOLIO with sub-collections per category (Ceremony, Reception, Details, Couple, Dance Floor, B&W). This is how you rebuild a website in 20 minutes instead of two days. BLOG & SOCIAL for content queues and vendor submissions. Set a target collection Right click any collection and choose Set as Target Collection. Now pressing B on any image anywhere in the catalog throws it into that collection. During portfolio review sessions this is the single fastest tool in Lightroom. Step 4: Smart Collections, Your Automated Assistant Smart collections are saved searches that update themselves. Build these once and your catalog starts telling you what needs attention instead of the other way around. Smart collection Rules Why it saves you Needs Keywording Keywords are empty AND Pick flag is flagged Catches every image that









