Lightroom Catalog and Import Shortcuts

Import (Ctrl+Shift+I / Cmd+Shift+I) opens Lightroom's Import dialog, which handles bringing photos in from a memory card, an existing folder on disk, or a connected camera, while also offering to apply an initial set of settings during the import itself — a starting develop preset, keyword tags, a copyright watermark, or a specific file-renaming scheme — all of which can save considerable time compared to applying these individually to hundreds of images after the fact. A detail that surprises photographers new to Lightroom's catalog model: importing a photo into Lightroom does not duplicate or move the actual image file into some internal Lightroom-only storage by default (though the Import dialog does offer a 'Copy' option that does exactly that) — instead, Lightroom typically just records a reference to wherever the file already sits on disk, meaning the underlying file structure on your hard drive matters and moving or renaming files outside of Lightroom's own interface can break that reference, showing up as a 'missing file' warning with a question-mark icon on the affected thumbnail. Understanding this catalog-as-reference-database model (rather than catalog-as-file-storage) is foundational to avoiding a common and frustrating class of Lightroom problems, where photographers who reorganize their photo folders using their operating system's file explorer, rather than through Lightroom's own Library module folder panel, end up with a catalog full of broken links pointing to files that have since moved. Sync Settings addresses a genuinely common repetitive task: once you've dialed in a careful edit on one representative image from a shoot — correcting for a specific lighting setup, or placing Spot Removal points for known sensor dust locations — selecting every other similarly-shot image and using Sync Settings applies that same adjustment recipe across all of them simultaneously, with a dialog letting you choose exactly which adjustment categories (exposure, but not crop, for instance) actually get copied rather than blindly applying everything. For photographers managing a large, multi-year archive, maintaining multiple separate catalog files — one per year, or one per major client — rather than a single monolithic catalog is a common organizational strategy, and Ctrl+Alt+O (Cmd+Option+O) opens the catalog picker for switching between them. This tradeoff is worth understanding: a single unified catalog makes cross-year searching and comparison trivial, while separate catalogs keep each individual catalog file smaller and faster to open, with the right choice depending heavily on shoot volume and how often cross-referencing older work against new work actually comes up in practice. A final catalog-health habit worth building: Lightroom's File menu includes an Optimize Catalog command that should be run periodically, particularly after a large import or a long editing session, since catalog performance can degrade gradually as its internal database grows without this maintenance step, something photographers with catalogs spanning tens of thousands of images notice far more than those with smaller, newer catalogs. One more catalog fundamental worth flagging for anyone new to Lightroom's architecture: the catalog file itself (the .lrcat database) is entirely separate from your actual image files, meaning backing up only your photos folder without also backing up the catalog file loses all of your ratings, flags, keywords, and edit history even though the original images remain intact. Lightroom's Catalog Settings includes an option to prompt for a backup of the catalog file on a schedule, and enabling that, rather than relying purely on whatever general file backup system protects the image files themselves, is a cheap insurance policy against losing weeks or months of organizational and editing work to a corrupted or lost catalog file. For anyone migrating an existing library into Lightroom for the first time, it's worth doing that initial import in smaller batches rather than pointing the Import dialog at an enormous existing folder structure all at once, since a very large first import can take a long time to process previews and is harder to troubleshoot if something in the folder structure causes an unexpected issue partway through.