
Choose export metadata according to what the recipient needs, then inspect the actual outgoing file. Lightroom desktop documents choices including all metadata or copyright only in its export options. Adobe's guide does not make every export edition identical to the information visible in your library.
Key Takeaways
- Define required credit and descriptive fields before exporting.
- Keep private source information separate from the public delivery.
- Check the exported copy rather than relying on a setting label alone.
Write a field-level delivery requirement
For a proposed client portrait handoff, the recipient may need the photographer's credit while not needing the full camera record. A publication may also need a caption or other descriptive information. State those needs explicitly; ‘keep the metadata’ is too vague to approve a deliverable.
Inspect the source entries for accuracy before export. A copyright field copied from an old template can be inappropriate for a different photographer or project. A retained field is not necessarily a correct field. Do not add ownership or licensing claims that the responsible person has not approved.
Select the export scope deliberately
Use the relevant options for Lightroom desktop and the intended output. Adobe documents metadata scope alongside file type, dimensions, naming, sharpening and color space. Those controls serve different parts of the handoff. A smaller JPEG or a different filename does not demonstrate that its metadata scope changed.
Keep a separate export candidate and preserve the original library information. If a required field is not available through the chosen scope, identify a supported way to deliver it rather than assuming that every application will reconstruct it from the filename or watermark. Visible credit, embedded metadata and licensing instructions can be separate artifacts.
Inspect the same copy the client receives
A proposed acceptance check reads the exported file's relevant fields and compares them with the agreed requirement. Then transfer it through the intended delivery route and inspect the received copy where possible. A system between export and receipt may process the file. Do not claim a universal removal or preservation result without checking that route.
Record the export settings, filename and fields actually verified. This guide does not certify that a copyright-only option removes every possible identifying trace. Accept the delivery when required, approved information is present in the outgoing edition and unwanted information has been assessed using an appropriate inspection method.
Compare two controlled metadata candidates
For a proposed field check, export separate copies of one authorized image using All Metadata and Copyright Only where those choices are offered in the current Lightroom desktop interface. Do not infer a particular field's result from those labels alone. If ExifTool is already available, use the officially documented extraction flags for a read-only inspection of each candidate:
exiftool -a -G1 -s "client-all.jpg"
exiftool -a -G1 -s "client-copyright.jpg"
Replace these example names with the two actual exported files, including their paths when needed. There are no assignment arguments here: these commands display metadata rather than edit it. -a includes duplicate tags, -G1 shows their family-1 locations, and -s prints tag names. Compare copyright/creator, description and any location-related entries against the delivery requirement, recording group and tag together so a same-named value in another metadata group is not overlooked. This is a proposed inspection, not a claim that either example file exists or was checked. A focused field list is not proof that every identifying trace was removed.
| Field to inspect | Agreed delivery purpose | Acceptance question |
|---|---|---|
| Copyright or creator information | Approved credit | Is the expected value accurate and retained? |
| Caption or descriptive text | Publication context | Did the chosen edition retain the required text? |
| Location or camera-related entries | Assess recipient need | What is present, and should that information be supplied? |
The table is a verification plan, not a claimed result for either setting. If a required caption disappears, choose another supported route or supply a clearly associated caption record. If information remains that should not be shared, investigate the actual field and delivery route; do not announce blanket privacy cleaning.
Use the export-settings distinction to record reproducible candidates, and the XMP caption-language check when multilingual descriptions matter. The published-image licensing-link guide concerns a separate public-page requirement: embedded credit does not establish that the eventual webpage exposes the required source or license links.
Related tasks
- Why Did Export With Previous Use My Last Test Settings?
- Change an XMP Default Caption Without Deleting Translations
- How Do I Tell Google Images Who Created a Photo and How It May Be Used?
Sources and scope
- Export, share, and invite people to contribute to your albums in Lightroom desktop, Adobe: Lightroom desktop offers export metadata choices including all metadata or copyright only.
- ExifTool FAQ: Read-only metadata extraction and group-aware field interpretation.
Documentation-based guidance reviewed October 31, 2026. No private photograph or exported metadata was inspected, and no blanket privacy-cleaning guarantee is made.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.