Catalog Setup and Storage for Lightroom Classic: Folders, Backups, and Previews

Choosing or Creating a Catalog (and Why It Matters)

A Lightroom Classic catalog (.lrcat) is a database that stores edits, ratings, keywords, collections, and the links to where your photo files live on disk. Your original photos are not stored inside the catalog; Lightroom references them by their path (drive + folders + filename). This is why a predictable storage plan is essential: if the path changes outside Lightroom, the catalog can’t find the files.

One Catalog vs Multiple Catalogs

• One main catalog is usually best for most photographers: easier searching, consistent keywords, and fewer duplicated previews.
• Multiple catalogs can make sense if you must separate work (e.g., different businesses, strict client separation, or very large archives on separate drives). If you choose multiple catalogs, keep the same folder naming rules across all of them.

Step-by-step: Create or choose a catalog

1. Decide the scope: “Main Catalog” (recommended) or separate catalogs by business/year.
2. Create the catalog: In Lightroom Classic, use File > New Catalog… and name it clearly (e.g., Main Catalog.lrcat or Studio_2026.lrcat).
3. Set a predictable home: choose a location you will not casually reorganize later (details below).
4. Open the correct catalog by default: in Preferences, set Lightroom to open your main catalog on launch to avoid accidentally importing into the wrong one.

Where to Store the Catalog (Speed, Safety, and Portability)

The catalog benefits from fast random access. In practice, that means storing it on a fast internal SSD (or a very fast external SSD if you move between computers). Your photos can live elsewhere, but the catalog and previews should prioritize speed.

Recommended storage layout

Practical rule

Don’t store the catalog on a network share (typical NAS/SMB locations) because database catalogs can become unstable or slow over network file systems. If you use a NAS for photos, keep the catalog local and let Lightroom reference the photos over the network only if performance is acceptable.

How Lightroom References Files (and Why “Missing” Happens)

Lightroom stores a record for each photo that includes the file’s location on disk. If you move, rename, or delete files/folders outside Lightroom (Finder/Explorer), the stored path no longer matches reality. Lightroom then marks them as missing (often shown with a question mark on folders or an exclamation mark on thumbnails).

Common causes of missing files

• Renaming a top-level photo folder in Finder/Explorer
• Moving a folder to a different drive letter (Windows) or volume name (macOS)
• Importing to one drive, then later consolidating files manually
• Disconnecting an external drive that contains originals

Best practice

Do all moves/renames inside Lightroom’s Folders panel. Lightroom will update the database paths as it moves files, preventing missing links.

Continue in our app.

• Listen to the audio with the screen off.
• Earn a certificate upon completion.
• Over 5000 courses for you to explore!

Or continue reading below...

Download the app

Designing a Predictable Photo Storage Structure on Disk

A good structure is: (1) consistent, (2) scalable for years, (3) easy to navigate without Lightroom, and (4) resistant to “where did I put that job?” confusion. You can organize primarily by date, by client/project, or by location/event. The key is choosing one primary axis and using subfolders for the rest.

Choose a “root” photo folder

Pick one top-level folder that will contain everything you import going forward. Examples:

• Photos (simple)
• Photo Archive (explicit)
• Lightroom Photos (clear purpose)

Inside Lightroom, add this folder as your main parent folder so you always see the full structure in one place.

Step-by-step plan: Folder naming conventions

Use a naming pattern that sorts correctly and stays readable. Avoid special characters that can cause cross-platform issues. Prefer ISO-style dates (YYYY-MM-DD) so folders sort chronologically.

Option A: Date-based (best for personal, travel, ongoing shooting)

1. Create year folders: 2026, 2025, etc.
2. Inside each year, create shoot folders named: YYYY-MM-DD_Description
3. If needed, add subfolders for camera cards or segments: A-Cam, B-Cam, Edits, Exports

Photos/  2026/    2026-01-20_Winter-Hike_Mt-Rainier/      RAW/      Selects/      Exports/    2026-02-03_Family-Session_Smith/      RAW/      Exports/

Why it works: predictable, chronological, and easy to maintain. The description keeps it human-readable.

Option B: Client → Project (best for commercial/client work)

1. Create a Clients folder under your root.
2. Create one folder per client: ClientName.
3. Inside each client, create project folders with date + project name: YYYY-MM_ProjectName or YYYY-MM-DD_ProjectName.
4. Use consistent subfolders: RAW, Deliverables, Exports, Working.

Photos/  Clients/    Acme-Co/      2026-01_Product-Shoot_Spring/        RAW/        Deliverables/        Exports/    Rivera-Weddings/      2026-06-14_Rivera-Wedding/        RAW/        Exports/

Why it works: mirrors how you think about paid work and makes it easy to locate all shoots for a client.

Option C: Location/Event (best for documentary, travel libraries)

1. Create a Locations folder under your root.
2. Use country/state/city as nested folders.
3. Name shoots with date + event descriptor.

Photos/  Locations/    USA/      Washington/        Seattle/          2026-03-10_Pike-Place/          2026-03-11_Waterfront/

Why it works: browsing by geography is intuitive, but be careful: the same trip may span multiple locations, so you must be consistent about where it “belongs.”

Rules that keep storage predictable

• One root folder for all Lightroom-managed photos (or one per drive if you must split).
• ISO dates (YYYY-MM-DD) for sorting.
• Keep names stable: avoid renaming folders after you’ve edited and delivered.
• Separate “Exports” from originals: don’t mix JPEG deliverables into RAW folders unless you have a clear reason.
• Don’t over-nest: deep folder trees slow human navigation and increase the chance of misplacing files.

Catalog Backups: Frequency, Location, and Integrity Checks

Catalog backups protect your Lightroom work (edits, organization, metadata stored in the catalog). They do not automatically back up your original photos. You need both: a catalog backup plan and a photo backup plan.

Set backup frequency

In Lightroom Classic, you can choose how often to back up the catalog when exiting. A practical approach:

• Daily/Every exit if you edit frequently or do client work.
• Weekly if you edit occasionally and changes are minimal.

More frequent backups are useful, but they can accumulate quickly; plan to prune older backups.

Choose a safe backup location

• Never back up to the same drive that holds the catalog. If that drive fails, you lose both.
• Use an external drive dedicated to backups, or a reliable backup destination that is physically separate.
• Consider keeping an additional copy offsite (separate from Lightroom’s built-in backup) as part of your broader backup strategy.

Step-by-step: A practical catalog backup routine

1. Set Lightroom to back up on exit at your chosen frequency.
2. Point the backup folder to a different physical drive (e.g., BackupDrive/Lightroom Catalog Backups/).
3. Enable the option to test integrity during backup when available; this helps detect catalog issues early.
4. Periodically prune backups: keep a rolling set (e.g., last 10 backups, plus one per month).
5. Once a month, perform a restore test: copy a backup catalog to a temporary location and open it to confirm it launches and your recent work is present.

What “verifying backup integrity” means in practice

• Integrity check: Lightroom validates the database structure to catch corruption.
• Restore test: you actually open a backup copy to ensure it’s usable (the most reliable verification).

If a backup won’t open, try an older one immediately and investigate disk health before continuing heavy work.

Previews Explained: Standard vs 1:1 vs Smart Previews

Previews are Lightroom’s cached representations of your photos used for browsing and, in some cases, editing responsiveness. Preview choices affect speed and disk usage.

Standard Previews

• What they are: medium-resolution previews sized to your screen settings.
• Best for: fast grid browsing, culling at “Fit” view, general library work.
• Disk impact: moderate.

Guidance: Set Standard Preview size to match (or slightly exceed) your typical display resolution. Oversizing wastes disk; undersizing can make loupe viewing feel sluggish as Lightroom regenerates previews.

1:1 Previews

• What they are: full-resolution previews that allow instant 100% zoom without waiting.
• Best for: critical sharpness checks, noise inspection, detailed retouch decisions during culling.
• Disk impact: high (can grow quickly on large shoots).

Guidance: Build 1:1 previews when you know you’ll zoom to 100% repeatedly (e.g., selecting the sharpest frames). Set them to discard after a reasonable time (e.g., 30 days) to control disk usage.

Smart Previews

• What they are: smaller, high-quality DNG-based previews that let you edit even if the originals are offline.
• Best for: laptop workflows, travel editing, working with external drives you don’t always connect, and sometimes improving responsiveness on slower storage.
• Disk impact: moderate (usually less than 1:1 previews, more than minimal standard-only setups).

Guidance: Build Smart Previews for shoots you want to edit on the go or when your originals are on an external drive. When the originals reconnect, Lightroom applies edits to the full files automatically.

Preview strategy examples

• High-volume culling day: Build Standard + 1:1 previews for the new import; discard 1:1 after culling is done or after a set period.
• Travel editing on a laptop: Build Smart Previews before leaving; you can edit without carrying the full archive drive.
• Limited SSD space: Use Standard previews only; build 1:1 selectively for critical folders.

Troubleshooting: Missing Files, Moved Folders, and Slowdowns

Issue: You moved folders outside Lightroom (now they show “?”)

What happened: Lightroom’s stored folder path no longer matches the actual location.

Fix (recommended): Reconnect the top-level missing folder so Lightroom updates everything beneath it.

1. In the Library module, go to the Folders panel.
2. Right-click the folder with a question mark and choose Find Missing Folder (or equivalent option).
3. Navigate to the folder’s new location and select it.
4. Confirm that subfolders and images relink correctly.

Tip: Relinking the highest-level missing folder is faster than fixing individual images.

Issue: Individual photos show an exclamation mark (missing file)

1. Click the exclamation mark on the thumbnail.
2. Choose Locate and point Lightroom to the correct file.
3. If prompted, enable the option to find nearby missing photos so Lightroom can relink others in the same folder automatically.

Prevention: Avoid renaming files after import. If you must rename, do it in Lightroom so the catalog stays in sync.

Issue: External drive letter/name changed (common on Windows)

What happened: The drive path changed (e.g., from E: to F:), so Lightroom thinks the folders are missing.

Fix: Either restore the original drive letter in your OS, or use Find Missing Folder on the top-level folder to point Lightroom to the new drive path.

Issue: Performance slowdowns (laggy browsing, slow zooming, sluggish Develop)

Performance issues usually come from storage speed, preview strategy, catalog size/health, or background tasks.

• Catalog on slow drive: Move the catalog and previews to an internal SSD for a noticeable improvement.
• Previews not built: If zooming is slow during culling, build 1:1 previews for that folder.
• Too many 1:1 previews: If disk space is tight, discard older 1:1 previews to reduce load and free space.
• Originals on slow external HDD: Consider Smart Previews for active projects; editing can feel faster because Lightroom can rely on Smart Previews.
• Catalog health: Run an integrity check via the backup process; if issues persist, test opening a recent backup catalog copy.
• Background tasks: Large imports, preview building, or syncing can slow the system; let them finish before judging performance.

Quick diagnostic checklist

• Is the photo drive connected and mounted with the same name/letter?
• Are missing items at the folder level (question mark) or file level (exclamation)?
• Is the catalog on SSD and the previews alongside it?
• Do you actually need 1:1 previews for this stage, or would Standard/Smart be better?