A Metadata-First Photo Workflow: Fix in ExifToolGui, Finish in Lightroom
Most photo workflows start in the editor and treat metadata as an afterthought — which is how wrong dates, missing credits and stray GPS coordinates survive into finished, exported, shared files. This workflow reverses the order: a short, deliberate metadata pass in ExifToolGui first, then editing and organising in Lightroom with clean files. ExifToolGui (Bogdan Hrastnik’s GUI, continued as V6 by Frank Bijnen) handles the forensic work through Phil Harvey’s ExifTool; Lightroom does what it is for — developing and managing the corrected library. The workflow lives in the Workflows & Buying Guides hub with the backup workflow and AI editing after metadata. Tools start at the download page.
Why metadata first, in one argument
Editors trust embedded metadata. Import order, timeline views, smart collections and export naming all read capture time; search and filtering read keywords and captions; clients and stock pipelines read credit and rights fields. If those fields are wrong at import, every downstream convenience quietly automates the error — the trip sorts wrong, the wrong name is credited, the location you meant to keep private is embedded in the export. Fixing the fields at the file level, before import, means every tool that touches the file afterwards inherits the truth. ExifToolGui is the right instrument for that pass because it shows everything ExifTool recognises and writes at that depth — not just the fields an import dialog happens to surface.
Step 1: the fix pass in ExifToolGui
- Verify capture times. Sort by DateTimeOriginal; fix a wrong camera clock with Modify → DateTime shift, set exact dates where a single value is wrong, then run DateTime equalize so EXIF and XMP agree.
- Write credit once. In the Workspace, set Artist and Copyright on the whole selection — the values every later export should carry.
- Keyword the keepers. Apply the shared event/place keywords to the batch, then add per-photo terms to the standouts.
- Decide location deliberately. Keep GPS in your masters if it serves your archive; plan to strip it from sharing copies later, not from the masters by accident.
- Re-read to verify. Click away and back; the stored values, not the typed ones, are what Lightroom will inherit.
Work on copies until the pass is routine, as with every batch write on this site. The detailed mechanics live in the Tutorials cluster — date shifting, batch editing and Workspace building are each covered step by step — but the pass itself takes minutes once the Workspace panel for it exists.
Step 2: import and finish in Lightroom
Import the corrected files and let the library work on true data: the timeline is right on day one, and the credits and keywords you wrote at file level are the starting point rather than a repair job. From here the workflow is the familiar one — organise, develop, export — with one discipline added: when an export needs different metadata behaviour (location removed for a public copy, for example), make that copy deliberately and keep the master untouched. If you later edit in Lightroom or Photoshop and do not yet have them, the route for readers is Adobe Photography (Lightroom and Photoshop). Some links on this page are affiliate links — see our affiliate disclosure. How Bridge-style library management compares with the specialist pass is covered in ExifToolGui vs Adobe Bridge.
Step 3 (optional): rescue the problem frames
Every shoot has a few frames that matter and are technically poor — noisy, soft, low-resolution. Those belong to a different tool class than metadata editors: AI photo editors and denoisers. Where readers ask for an option, the one linked from this site is Topaz Photo, used for denoise and upscale work on selected frames rather than whole folders. Keep the order: rescue after the metadata pass, and re-check the rescued file’s metadata afterwards (exports from any editor can rewrite fields), because the file that returns to the library should still carry the dates and credits you fixed in step 1. The fuller tour of this step is After the Metadata: AI Denoise and Upscale Options.
The habit that holds it together
Metadata-first is a habit, not a project: fix, then finish, every time, in that order. Pair it with the companion discipline in Back Up the Photo Library You Just Cleaned — a cleaned library is worth protecting properly — and a folder of camera files becomes an archive whose contents you can assert, not merely assume.
Frequently Asked Questions
Why not just fix metadata inside Lightroom after import?
Because import builds order, collections and exports on the embedded values from the first minute, and library-level fixes do not always rewrite the file-level fields other tools will read later. A file-level pass in ExifToolGui fixes the source every tool inherits.
Does ExifToolGui edit photos like Lightroom does?
No. ExifToolGui views and edits metadata only — it develops nothing. That division is the workflow: ExifToolGui for the data about the photo, Lightroom for the photo itself.
What if an editor’s export changes my metadata?
It can — exports may rewrite or drop fields depending on settings. Re-open exported keepers in ExifToolGui and re-read the key fields; restoring a field on the export copy takes seconds once checking is a habit.
More workflows are collected in the Workflows hub; the metadata tools themselves are on the download page.
