Metadata that vanishes between your catalogue and the agency almost always traces to one of five causes: it was never written out of the catalogue, the export preset was set to keep only copyright fields, a raw file was uploaded without its sidecar, individual keywords were flagged not to export, or something downstream re-saved the file and dropped what it did not carry.
Each of those has a specific named setting behind it, which is useful, because it means this is a diagnosable problem rather than a mysterious one. The sequence below moves from the most common cause to the least, and each step tells you how to confirm it before you change anything.
The five places metadata actually goes missing
1. It was never written to the file
In Lightroom Classic, what you type into the Keywording and Metadata panels goes into the catalogue first. It reaches the file only when something writes it there. Adobe's own documentation points to two mechanisms: a setting under Catalog Settings called Automatically write changes into XMP, which saves continuously as you work, and a manual command at Photo > Save Metadata to File. If neither has run, the catalogue looks complete and the file is bare. That difference between catalogue state and embedded metadata is the single most common reason a contributor is certain the keywords exist and the agency is certain they do not.
The quick test is to open the original in a second application that reads the file rather than the catalogue. If the fields are empty there, you have found it.
2. The export preset is throwing it away
The Metadata section of Lightroom Classic's export dialog is not a toggle; it is a choice between levels. Adobe documents four: Copyright Only, which keeps only the IPTC copyright metadata; Copyright & Contact Info Only, which keeps the IPTC contact and copyright metadata; All Except Camera Raw & Camera Info, which keeps everything except the EXIF camera fields like exposure, focal length and date; and All, which keeps everything.
The first two are the trap. They are reasonable defaults for a photographer sending files to a client who does not need a keyword set, and catastrophic for a contributor uploading to an agency that searches on exactly that keyword set. A preset built years ago for a different purpose will keep doing its job quietly for as long as you let it.
Two more controls sit alongside those options. Remove Location Info strips GPS data even when All is selected, which matters for travel and editorial work where location is part of the value. Write Keywords As Lightroom Classic Hierarchy writes parent and child relationships using a pipe character, producing terms like Names|Maria. That is useful inside Adobe's ecosystem and usually wrong for an agency field that expects flat, comma-separated keywords.
3. The raw file left its sidecar behind
Raw formats generally do not hold your metadata inside the file. Lightroom Classic supports external sidecars for raw images and a few non-raw formats, normally an XMP file saved next to the original. From version 15.0 it also writes an ACR sidecar for heavy edits, masks and AI settings, keeping the XMP sidecar lightweight. You can confirm what exists by selecting the photo in the Library module and checking the Sidecar Files field in the Metadata panel.
The practical consequence is simple: a sidecar is a separate file, and separate files get left behind. Copy the raw to an upload folder without its companion and the metadata never travels. Exporting a JPEG or TIFF sidesteps this entirely, because the metadata is embedded in the derivative, which is why most contributors deliver a derivative rather than the original capture.
4. Individual keywords are flagged not to export
This is the cause that produces the most confusing symptom, because the loss is partial. Some keywords arrive, others do not, and the export preset looks innocent. The explanation is that keyword tags carry their own switches. Adobe's keyword documentation describes three, available in both the Create Keyword Tag and Edit Keyword Tag dialogs.
- Include On Export includes the keyword when exporting photos. Deselected, the keyword is not included at all.
- Export Containing Keywords includes the higher-level keywords that contain the keyword. Off, a child term arrives without its parents, so a photo tagged only with a leaf term loses the broader concepts a buyer might search for.
- Export Synonyms includes the related terms attached to a keyword. Off, a carefully built synonym set stays in the catalogue.
Contributors usually hit this one by inheritance rather than by choice: a keyword tag created for private organisation years ago, deliberately excluded from exports at the time, still sitting in the hierarchy doing what it was told. The Keywording panel can be set to show what will actually be written, which is a faster check than auditing tags one at a time.
5. Something downstream re-saved the file
If the file sitting in your export folder inspects as complete and the copy the agency received does not, nothing in your export settings is at fault. The loss happened in between. Any step that re-encodes the image is a candidate: a resizing script, a format converter, an image optimiser, a compression pass, a sync client that generates its own derivative. None of these are obliged to carry metadata forward, and many do not.
The diagnostic is to inspect the same frame at each hop rather than only at the ends. Whichever hop turns a full file into a bare one is the step to replace or configure, and that is almost always cheaper than rebuilding your keyword workflow on a suspicion.
Where did your metadata go?
A four-question walk through the five documented causes of metadata loss on export: catalogue-only metadata not yet written to the file, an export preset limited to copyright fields, a raw file separated from its XMP sidecar, keyword tags with Include On Export disabled, and stripping by a downstream step that re-saves the file.
The tools people use for this, and what each is actually good at
No single tool prevents every version of this problem, because the five causes sit at different points in the chain. What follows is where each commonly used option is strong and where it is not.
Adobe Lightroom Classic
- Best for: photographers who already edit there, with a keyword hierarchy and synonym structure worth maintaining.
- Pricing model: part of an Adobe subscription rather than a standalone purchase.
- Main limitation: three of the five causes above are Lightroom behaviours. The catalogue-versus-file split, the export preset levels and the per-keyword export switches are all working as designed, which is precisely why they surprise people.
Adobe Bridge
- Best for: inspecting and editing metadata on files directly, with no catalogue in the way. Its IPTC Core panel is split into Content, Contact, Image and Status areas, and a Raw Data tab shows the underlying XMP text, which makes it a genuinely useful verification step.
- Pricing model: bundled with Adobe accounts rather than sold per seat.
- Main limitation: Adobe's own documentation warns that any information you enter in a field overrides existing metadata. A batch write across a selection replaces rather than merges, so it repairs well and can also erase quickly.
ExifTool
- Best for: proving what is actually in a file, and scripted repair across thousands of them. For the hop-by-hop diagnostic described above, nothing beats reading the raw tags.
- Pricing model: free and open source.
- Main limitation: it is a command-line tool with no confirmation step. It will do exactly what you asked across a whole directory, including the wrong thing, so it belongs in the hands of someone comfortable testing on copies first.
Photo Mechanic
- Best for: fast ingest and captioning at volume, which is why it is long established in news and sport workflows where metadata is written at the point of import.
- Pricing model: a commercial licence bought directly from the vendor.
- Main limitation: it writes metadata extremely well and is not a multi-agency delivery layer, so the handoff to each destination remains yours to arrange.
Capture One
- Best for: contributors who prefer its raw processing and work in sessions rather than one large catalogue.
- Pricing model: commercial raw workflow software sold directly by the vendor.
- Main limitation: changing editor does not remove the underlying issue. Any catalogue-based application keeps a working copy of metadata that has to be written out deliberately, so the first cause on this list applies there too under different menu names.
Rastock AI
- Best for: holding one canonical metadata record per asset and delivering it to the agencies in your rotation in the shape each one expects, so a mis-set export preset is not sitting between your keywords and ten destinations.
- Pricing model: subscription, with a 14-day free trial that does not ask for a card. No revenue share, no ownership claim over your files, and IPTC, CSV and XML export stay open so nothing is trapped.
- Main limitation: it is a metadata and delivery layer, not a raw editor. You still cull and process in Lightroom, Capture One or whatever you use today, and it cannot recover metadata that a downstream optimiser strips after delivery.
When to use which
Use ExifTool when the question is what is in this file, because every other answer is a guess until someone reads the tags. Use Bridge when you want the same answer with a visual field-by-field view, and when you need to repair a handful of files rather than script a thousand.
Stay in Lightroom Classic when the keyword hierarchy itself is the asset you have invested in, and fix the three settings named above rather than migrating away from them. Reach for Photo Mechanic when metadata needs to be written at ingest, on a deadline, at a volume that makes any catalogue step feel slow.
Add a dedicated delivery layer when the problem is not one file but the multiplication: several agencies, each with its own field expectations, each a separate chance for a preset to quietly drop something. If you are weighing the two Adobe options against each other for everyday metadata work, the Bridge and Lightroom comparison goes further into where each one fits.
The sixth case: the file is full and the agency still shows nothing
Occasionally every check passes and the agency form still arrives blank. That is not a loss, it is a mismatch. The same human-readable idea can live in more than one field, and two applications can disagree about which one counts as the title or the caption. Bridge makes this visible: its IPTC Core panel shows the structured fields while the Raw Data tab shows the XMP text underneath, and the two views do not always look like the same file. The fix is not to rewrite the metadata but to map your fields to what each agency actually reads before delivery.
A standing check worth building in
Most contributors discover this problem retroactively, after a batch has already gone out bare and the downloads never came. The cheap habit is to pull one file back out of every delivered batch and read its tags, the same way you would check one print off a run. Thirty seconds per batch catches a broken preset on the day it breaks rather than a quarter later, and it pairs well with a settled routine for writing metadata in the first place.
Rastock.ai takes the multiplication problem off the table: one metadata pass per asset, then delivery over FTP or SFTP to the 10+ agencies it supports, with policy-aware keywords, banned and mandatory term handling, rollback when a batch goes wrong, and per-agency status you can read at a glance. You can see what the workflow covers or look at the plans — the trial runs 14 days and does not ask for a card.
Frequently asked questions
Why are my keywords missing after I export from Lightroom Classic?
The most common cause is the Metadata option in the export preset. Copyright Only and Copyright & Contact Info Only keep just the IPTC copyright and contact fields, so titles, descriptions and keywords never reach the exported file. Setting that option to All keeps everything. The second most common cause is keywords flagged with Include On Export turned off.
Does metadata live in the file or in the Lightroom catalogue?
Both, but not automatically. Edits you make in Lightroom Classic are held in the catalogue until they are written out. Catalog Settings has a Metadata option called Automatically write changes into XMP, and there is a manual equivalent at Photo > Save Metadata to File. Until one of those runs, another application reading the original file sees nothing.
Why does my raw file arrive at the agency with no keywords?
Raw formats generally keep their metadata in an XMP sidecar file saved next to the original rather than inside it. Upload the raw on its own and the sidecar stays on your drive. Exporting a JPEG or TIFF embeds the metadata in the file itself, which is why most contributors deliver a derivative rather than the raw.
Why do only some of my keywords survive the export?
Keyword tags carry their own export switches. In the Create Keyword Tag and Edit Keyword Tag dialogs, Include On Export decides whether a keyword is written at all, Export Containing Keywords decides whether its parent keywords come with it, and Export Synonyms decides whether synonyms are included. A partial loss usually means one of those is off.
Can a tool strip metadata after I have exported correctly?
Yes. Anything that re-saves, resizes, converts or optimises a file between your export folder and the agency can drop fields it does not carry forward. If the exported file in your own folder has full metadata and the delivered copy does not, the loss is in that chain rather than in your export settings.
Why does an agency show empty fields when my file clearly has metadata?
Different fields can hold what looks like the same information. A title may sit in one namespace while the agency reads another, and keywords can be stored in more than one place. When the file inspects as full but the agency form arrives blank, the mismatch is usually in which field each side is reading rather than in whether data exists.