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 slipped past your import preset |
| In Progress | Label is Yellow | Your live edit queue across all clients |
| Ready to Export | Label is Green AND Rating >= 2 | One click before every delivery |
| Portfolio Candidates | Rating is 5 | Website and print reviews without hunting |
| This Season | Capture Date is in the last 6 months | Fast access to active jobs |
| Missing Files | File is missing | Early warning that a drive path broke |
| Untouched RAWs | Has Adjustments is false AND Pick flag is flagged | Finds selects you forgot to edit |
| Rejects to Purge | Pick flag is rejected | Quarterly disk space recovery |
Tip: smart collections can be exported and imported. Build them once, then drop the same set into any future catalog.
Step 5: A Keyword Taxonomy You Will Actually Maintain
Most photographers abandon keywording because they try to describe everything. The trick is a small, hierarchical, controlled vocabulary: five top-level branches, nothing deeper than three levels, and no synonyms.
The five branches
People ├── Clients │ ├── Dupont-Lefevre 2026 ├── Vendors │ ├── Planner - Maison Belle │ └── Venue Coordinator Event ├── Getting Ready ├── First Look ├── Ceremony ├── Portraits ├── Reception │ ├── Speeches │ ├── First Dance │ └── Cake └── Send Off Subject ├── Details │ ├── Rings │ ├── Dress │ ├── Invitations │ └── Florals ├── Candid ├── Group Photo └── Venue Exterior Location ├── Paris ├── Provence └── Tuscany Style ├── Black and White ├── Golden Hour ├── Backlit ├── Rain └── Night Flash
How to apply keywords in under five minutes per wedding
- Apply Client + Location + year to the entire import at once, in the import dialog’s Keywords field.
- After culling, select each chapter of the day in the grid (they are already chronological) and apply the matching Event keyword with a keyword set shortcut.
- Use the Painter tool (the spray can in the Library toolbar) to dust Subject and Style keywords onto the 40 or 50 images that deserve them.
- Ignore the rest. Keywording every frame is a trap. Keyword the images you may want to find again.
Rules that keep the vocabulary clean
- Turn on Include on Export for public terms, and turn it off for private terms like client surnames if you publish images.
- Use the Synonyms field instead of creating duplicate keywords. “Bouquet” as a synonym of Florals, not a second keyword.
- Enable Person keywords for face recognition, but keep faces in the People branch only.
- Periodically open the Keyword List panel, sort by count, and merge the ones with a count of 1 or 2. Those are typos.

Step 6: Flags, Stars and Color Labels, One Job Each
Overlapping meaning is what makes a big catalog unsearchable. Lock this table to your wall and never deviate.
| Marker | Meaning | When applied |
|---|---|---|
| Pick flag (P) | Keep | First culling pass |
| Reject flag (X) | Delete at the end of the season | First culling pass |
| 2 stars | Goes in the client gallery | Second pass |
| 4 stars | Blog, socials, vendor submission | After editing |
| 5 stars | Portfolio grade | Rare, after editing |
| Red label | Needs Photoshop or heavy retouch | Any time |
| Yellow label | Editing in progress | Develop module |
| Green label | Approved, ready to export | Final review |
| Blue label | Delivered to client | After export |
| Purple label | Album spread candidate | Design phase |
Colors are the status layer, and because Lightroom lets you filter by label with a single keystroke (6 through 9), your entire pipeline becomes visible at a glance.
Step 7: Keep It Fast, Not Just Organized
Structure alone will not fix sluggishness. These settings do:
- Standard previews: set the size to match your display resolution, quality Medium. Oversized previews inflate the preview cache into hundreds of gigabytes.
- Discard 1:1 previews after 30 days. Regenerating them for an old job takes minutes. Storing them forever costs you a drive.
- Build Smart Previews for jobs you edit on a laptop while the archive drive stays home. Smart previews also speed up the Develop module noticeably.
- Catalog Settings > Optimize Catalog once a month. It rebuilds the database indexes.
- Back up on exit, weekly, keep the last three backups, and store them on a different drive from the catalog. Tick “Test integrity before backing up”.
- Limit the Camera Raw cache only if disk space is tight. On a spacious SSD, 40 GB or more makes browsing snappier.
- In the Library Filter, keep Folders panel view collapsed. Hold Alt or Option while clicking a triangle to collapse every folder at once.
Migrating a Messy Catalog Without Breaking Your Edits
This is the part that scares people, and rightly so. Edits live in the catalog database, linked to file paths. Break the path and Lightroom shows question marks. Follow this order and nothing breaks.
Before you touch anything
- Back up the catalog manually: File > Backup Catalog on exit, or copy the .lrcat file to another drive.
- Write metadata to files: select all images, then Metadata > Save Metadata to Files (Ctrl/Cmd+S). This writes keywords, ratings, labels and develop settings into XMP sidecars or DNG headers as a safety net.
- Note your total image count so you can verify nothing disappeared.
The golden rule
Move folders and files inside Lightroom’s Folders panel, never in Finder or Windows Explorer. Drag and drop inside Lightroom moves the actual files on disk and updates the database in the same operation. Moving files outside Lightroom is what produces the dreaded missing photo icon.
The migration sequence
- Create the new structure first. In the Folders panel, right click your drive and add the parent folder, then year subfolders. Nothing has moved yet.
- Consolidate stray root folders. If your Folders panel shows a dozen top-level entries scattered across the drive, drag each one into the parent folder inside Lightroom. Do it in batches of one folder at a time and let each move finish.
- Rename job folders to the date-first convention. Right click the folder in Lightroom, choose Rename. Lightroom renames on disk and keeps the link.
- Sort loose images. Use the Library Filter with Metadata > Date to identify orphan images, then drag them into the correct job folder.
- Reconnect anything already missing. Right click the folder with the question mark, choose Find Missing Folder, and point at its new location. Reconnecting one parent folder repairs all its children.
- Rebuild the collection layer. Do not migrate old collections. Create the new collection sets for the last two years only, then let new jobs follow the system going forward. Older archives are found by folder and keyword, and that is enough.
- Retro-keyword in bulk. Select a whole job folder, apply the client, location and year keywords in one action. Ten seconds per wedding. Do not attempt shot-level keywording on old archives.
- Purge rejects. Use the Rejects to Purge smart collection, review, then Photo > Delete Rejected Photos. Expect to recover a serious amount of space.
- Optimize the catalog and run a fresh backup.
Common migration traps
- Duplicates: if the same wedding got imported twice from different card copies, use a duplicate finder plugin or filter by filename before merging. Deleting from the catalog only removes the reference unless you choose Delete from Disk.
- Drive letters on Windows: assign a fixed letter to your archive drive in Disk Management, otherwise every reconnection breaks when you plug into a different port.
- Network drives: Lightroom Classic does not officially support catalogs on a NAS. Photos on a NAS are fine, the catalog is not.
- Virtual copies and snapshots live only in the catalog. Another reason the catalog backup matters more than the sidecars.

Your One Afternoon Checklist
| Time | Task |
|---|---|
| 0:00 to 0:20 | Back up catalog, save metadata to files, move catalog to internal SSD |
| 0:20 to 1:00 | Build the parent + year folder structure, consolidate stray folders |
| 1:00 to 2:00 | Rename job folders to date-first convention |
| 2:00 to 2:30 | Create keyword hierarchy and keyword sets |
| 2:30 to 3:00 | Build the 8 smart collections and portfolio collection sets |
| 3:00 to 3:30 | Create the import preset with renaming and base keywords |
| 3:30 to 4:00 | Purge rejects, optimize catalog, run a fresh backup |
What Changes When You Work in Lightroom (Cloud) Instead
The cloud version has no folders panel, so the structure moves entirely to albums and album folders, plus keywords and its automatic search by content. If you shoot high volume weddings, Lightroom Classic remains the safer archive because you keep control of the original files and the folder structure. A common hybrid: archive and edit in Classic, then sync only your Portfolio collections to the cloud so they are searchable on your phone.
FAQ
How many Lightroom catalogs should I keep?
One master catalog for your entire archive. Search, smart collections and keyword filtering only work within a single catalog, so splitting them cripples your ability to find anything. The only justified exception is a temporary travel catalog on a laptop that you merge back with File > Import from Another Catalog.
Where should I keep my Lightroom catalog file?
On your fastest internal drive, ideally an internal SSD, in its own folder alongside the previews. The photos themselves can live on an external drive or RAID. Never place the catalog on a NAS or network share, and never run it from a cloud sync folder like Dropbox while Lightroom is open, as this can corrupt the database.
How do I clean up a bloated Lightroom catalog?
Work in this order: delete rejected photos from disk, remove duplicate imports, discard 1:1 previews older than 30 days, merge duplicate and single-use keywords, delete unused collections, then run Catalog Settings and Optimize Catalog. Finish with a fresh backup with integrity testing enabled.
What is the difference between folders and collections (or albums)?
Folders mirror where files physically sit on your hard drive, so an image can only exist in one folder. Collections (called albums in the cloud version) are virtual: the same image can appear in your Selects, Portfolio and Album collections at the same time without duplicating the file. Removing a photo from a collection does not delete it, removing it from a folder can.
Will reorganizing my folders lose my edits?
No, as long as you move and rename folders inside Lightroom’s Folders panel. Edits are stored in the catalog and linked to file paths, so moving files in Finder or Explorer breaks that link and shows missing photo icons. If that already happened, right click the folder and choose Find Missing Folder to reconnect everything at once.
Should I keyword every single photo from a wedding?
No. Apply client, location and year keywords to the whole import in one action, event chapter keywords to each block of the day, and detailed subject or style keywords only to the 40 to 60 images you might want to find again for a portfolio, a blog post or a vendor submission. Anything more is time you will not recover.
How large can a Lightroom catalog get before it slows down?
Catalogs with 300,000 to 500,000 images run fine when the catalog file sits on an SSD, previews are sized sensibly and the catalog is optimized regularly. Slowdowns almost always trace back to a mechanical hard drive, oversized 1:1 previews, or hundreds of history steps per image rather than the raw number of photos.
Final Word
The value of a system is not the folders, it is that you stop making decisions. Every import lands in the same place, every keyword comes from the same list, every color means the same thing in 2026 as it will in 2031. Spend one afternoon to organize your Lightroom catalog around these five layers, and the archive stops being a liability and becomes what it should be: a searchable body of work you can mine for portfolio pieces, reprints and marketing for the next decade. Learn how to organize your photos in Lightroom tackles the same question from another angle.





