LeCoqRoti
Import: organise the day's shoot
A photographer returns with a memory card full of raw files. Lightroom Classic reads the card directly from the desktop, copying images to a chosen drive while building previews. The import dialog offers file renaming, copyright metadata and a destination folder — all set before a single frame appears in the library.
Develop: local adjustments with new masking control
In the Develop module, one portrait is pushed further: a radial mask lifts the face from a flat background. The current version introduces Feather and Edge controls, so the transition between masked and unmasked areas can be softened or sharpened with precision — no halos, no guesswork.
Export: a rendered DNG for the archive
Rather than a routine JPEG, the edited file is saved as a rendered DNG. The Render to DNG command bakes adjustments into a linear raw container, preserving latitude for future proofing while locking in the look. The file goes straight into the archive, clean and self-contained.
Preview size and colour space: two early changes that shape performance
Lightroom Classic ships with defaults that favour caution: conservative previews, automatic writing to the catalog, a colour space that fits screens but not prints. A few early adjustments make the application feel responsive and predictable.
Begin with preview size and quality. Under Catalog Settings > File Handling, set the standard preview size to match the longer edge of the display — 2560 pixels or above for a modern monitor. Preview quality set to High slows the initial build but removes the soft, waiting-for-render flicker when stepping through images in Loupe view.
Turn off automatically write changes into XMP unless a second application needs to read the edits. The catalog stores everything internally; writing sidecar files on every adjustment adds disk chatter for no immediate gain. Enable it only before a handoff to Photoshop or a collaborator.
Under Preferences > Performance, increase the Camera Raw cache to at least 20 GB and place it on the fastest internal drive available. This is the working space where Develop module renders live, and a generous cache keeps the sliders fluid. If the machine has an Apple Silicon chip, confirm that Use GPU for image processing is set to Auto — the current version leans on the Neural Engine for masking and noise reduction, and an incorrect setting here robs performance silently.
One more overlooked checkbox: File Handling > Replace embedded previews with standard previews during idle time. Uncheck it if disk activity between edits feels distracting. Lightroom will still build the previews it needs on demand.
A workflow: culling and editing an event shoot
Picture a morning after a gallery opening: 800 frames on the card, mixed lighting, white walls that fool the meter. The goal is forty final images, colour-corrected and cropped, delivered by midday.
The import is set to Embedded & Sidecar previews — fast to display, good enough for culling. A metadata preset stamps the copyright and event name. The files land in a folder named by date, inside a year catalogue that already holds previous exhibitions.
Culling runs in the Library module with auto-advance on: the right arrow key moves through frames, the P key flags keepers, X marks rejects. Caps Lock auto-advances after each flag, so the left hand rests. A first pass takes fifteen minutes and reduces 800 frames to about 120.
Then a filter isolates the flagged images. Quick Develop on the toolbar pushes exposure up a third of a stop across all — the camera's meter had been fooled by those white walls. A second, slower pass in Loupe view winnows the set to sixty, checking focus at 1:1. The rejected frames get deleted from disk with Command-Delete.
A colour reference shot taken with a grey card at the start of the evening becomes the baseline. In Develop, a white-balance click on the grey card fixes the tungsten-spiked ambient. This correction is copied and pasted across every image from that room using Shift-Command-C and Shift-Command-V, skipping only the flash-lit frames near the bar. Those receive their own reference correction from a different grey card shot.
Individual edits are quick: a slight S-curve for contrast, the new Feather control on a subject mask to lift faces without haloing the dark walls behind, a gentle vignette to close the edges. Cropping uses the opacity slider introduced in version 15.5 — dragging a crop while seeing the discarded area at reduced opacity helps avoid cutting through a hand or the edge of a painting.
Export runs a preset: JPEG at 80% quality, long edge 2048 pixels, sharpening for screen, sRGB profile. The rendered DNG command saves the hero shots — five frames that might print later — into an archive folder with adjustments baked into the linear container. The whole session closes in under two hours, and the catalogue is backed up to an external drive before lunch.
Skipping the import dialog: editing outside a catalogue vanishes later
The first mistake is treating the catalogue as optional. A photographer who skips the import dialog and browses files directly from a memory card is not building a catalogue at all — the edits exist only in a temporary session. One ejected card and the work disappears. Lightroom Classic is built around the catalogue; fighting that structure leads to lost adjustments and duplicate files scattered across the drive.
Moving folders outside the application is another common slip. Renaming or relocating an image folder in the Finder breaks every link in the catalogue. The repair requires right-clicking the missing folder in Lightroom's Folders panel and pointing to its new location — simple, but panic-inducing the first time a photographer sees question-mark thumbnails across the grid.
Over-sharpening at the capture stage, then sharpening again on export, creates brittle edges that no screen can soften. The sharpening panel in Detail works on the raw data; output sharpening in the Export dialog is a second pass tuned for the final medium. Applying both without understanding the cumulative effect produces halos that print badly.
The Vibrance and Saturation sliders are confused more often than not. Vibrance protects skin tones and already-saturated colours; Saturation pushes everything equally. A portrait pushed to +40 Saturation looks sunburnt. The same adjustment on Vibrance lifts the muted background without turning the subject orange.
Finally, ignoring the history states in Develop invites frustration. Lightroom Classic stores every slider move as a named step, and clicking any earlier state temporarily reverts the image — but a subsequent adjustment erases all states after that point. Saving a snapshot before a major branch in editing preserves the option to return without losing later work.
Photoshop handoff: how Lightroom Classic sends a file outward
Lightroom Classic sits at the centre of a desktop workflow, and its connections outward are deliberate rather than automatic. The most immediate link is to Adobe Photoshop: right-clicking an image and choosing Edit In hands off a rendered file — TIFF or PSD — with the Lightroom adjustments applied. When the file returns from Photoshop and is saved, it appears stacked beside the original raw in the catalogue. The round-trip preserves layers if the format allows, and the edited file inherits the collection membership of its parent.
Plug-ins extend the reach further. The export system can run a post-processing action after every file: a droplet that compresses a JPEG further with ImageOptim, a script that uploads to a CMS, a preset that hands a TIFF to Helicon Focus for stacking. These are configured once in the Export dialog and triggered by a single preset selection.
On macOS, the integration is quieter but useful. The Photos app does not read the Lightroom catalogue, but exported JPEGs dropped into a Photos album sync across iCloud to an iPhone for quick sharing. Finder tags applied to exported files survive the round-trip as metadata that Spotlight can search — tagging a set of final selects with a client name makes them retrievable outside the catalogue.
Time Machine deserves a note of caution: it backs up the catalogue file and the previews folder, but if it grabs the catalogue mid-write, the backup is corrupted. A better approach is to close Lightroom Classic at the end of a session and let Time Machine catch the stable file, or to use Lightroom's own catalog backup dialog — set to run weekly, verifying integrity after each copy — and store the backup on a volume that Time Machine excludes. The two systems complement each other without overlapping.
For photographers who also shoot tethered, the Hot Folder feature in the Auto Import settings watches a folder on disk. Any image that lands there — from a wireless transmitter, a watched Dropbox share, or a scanning script — gets pulled into the catalogue with a chosen develop preset applied. It turns a folder into an inbox that Lightroom Classic monitors without the photographer needing to click Import again.
In short: the application works best when it is the hub, not an island. Every connection — to Photoshop, to a watched folder, to the Finder — reinforces the catalogue as the single source of truth for the image library.
Correspondence 0
Take a chair or join the table to send a letter.
No correspondence on this note yet. Letters are read before they appear.