What metadata management should do
Metadata management means keeping useful information about an image accurate, available and appropriate for its destination. A photographer needs enough context to find the original, identify a delivered version and explain how it may be used. A client does not necessarily need the studio’s entire internal record.
Separate three places where information can live: your editing catalog, the image file or its sidecar, and the delivery platform. A value visible in one place is not proof that it exists in the others. Exporting, resizing or downloading can change which fields remain.
The practical goal is not to fill every field. Choose a small set you can maintain, decide what belongs in a public copy, and inspect the file that actually reaches the recipient.
EXIF, IPTC and XMP are related, not three separate boxes
EXIF commonly contains capture information such as camera model, exposure and date. Some files also contain GPS coordinates. Treat these as recorded values to inspect, not unquestionable facts: camera clocks and settings can be wrong.
IPTC defines descriptive and administrative properties such as creator, description, keywords and rights information. XMP is a metadata format that can carry IPTC properties as well as other information. It is not simply a third, unrelated category alongside IPTC.
Some workflows store information in an XMP sidecar beside a camera raw file. Others embed it in a supported image format. Catalog-only changes may not accompany a file copied outside the application. Keep required sidecars with their matching originals and back up the catalog as well.
The IPTC user guide explains these relationships and the meanings of individual fields. Field names in your editor may differ from their technical names; check the tool’s documentation before making a batch change.
Choose a small, repeatable field set
Start with creator and a business contact route that you are comfortable distributing. Add an accurate description and a few useful keywords for retrieval in software that reads them. Keep spelling and naming consistent across a job.
For example, a studio could describe a frame as “Couple walking beside the vineyard after the ceremony” and use wedding, vineyard and portraits as keywords. This is a naming example, not a claim that every client-gallery search will index those words.
Use credit and rights-related fields where they fit the agreed delivery. Metadata can communicate attribution and usage information, but it is not an access control and should not be your only record of an agreement. Keep the relevant project records separately.
Avoid putting unnecessary personal information into a reusable preset. Client names, addresses, private venue details and internal notes deserve a per-job decision, not automatic copying into every exported file.
Do not equate a complete form with a correct record. An empty field can be better than a confident but inaccurate location, identity or description.
Apply shared facts on import, then add image-specific context
Create an import preset for information that is genuinely shared: creator, suitable contact details and any consistent attribution information. Check that an old preset has not carried over the previous client, campaign or year.
Add scene-specific descriptions and keywords after you have reviewed the photographs. A batch labeled ceremony should not silently include preparation or reception images. Apply changes to a small selection first and inspect the result before continuing.
Agree what ratings, labels and flags mean within your team. A five-star rating might mean a strong candidate, while a separate record identifies the client’s confirmed selections. Do not assume every tool exports those application-specific decisions in the same way.
Keep stable identifiers between originals, proofs and finals. If a filename changes, maintain a clear mapping so that metadata edits and client instructions refer to the right photograph. A tidy keyword list cannot fix a mismatched final file.
Export for the destination, not with one universal preset
Keep a richer archive version when appropriate and create a separate delivery copy. Decide which creator, contact and descriptive fields the recipient needs, and which personal or operational details should remain internal.
Adobe documents metadata options in Lightroom Classic’s Export dialog, including copyright-focused options and a Remove Location Info option for GPS metadata. The documented options have format-specific limits, including restrictions for DNG. Check the settings for the file type you are actually exporting.
Removing GPS coordinates is not the same as removing every location clue. A city field, caption, filename, keyword or visible address in the photograph can still identify a place. Review those separately.
After export, inspect the exported file rather than relying on what the editing catalog displays. If you resize it, pass it through another tool or offer a different download size, inspect that derivative too.
A small, tested example: archive copy versus delivery copy
We tested a local copy of SendPhoto’s logo PNG with fictional metadata using ExifTool 13.55. It was not a client photograph, and this was not a Lightroom export or a SendPhoto upload test.
The archive sample contained Creator “SendPhoto demo,” Description “Fictional metadata test, not a client photo,” Subject “demo,” and City “PRIVATE TEST CITY.” The delivery copy started with the same values.
After removing the XMP City field from the delivery copy, a fresh read still showed Creator, Description and Subject, but no value for that City field. The archive copy retained the city. This demonstrates checking a specific changed field while retaining selected others, not a complete privacy scrub.
To inspect your own file without changing it, run the read-only command exiftool -G1 -s "delivery.png", substituting its actual path. IPTC publishes an ExifTool guide covering full-file reads and specific metadata properties. Review the output locally; do not paste a client’s metadata dump into a public issue or article.
Use a disposable copy for experiments. A successful operation should be followed by another read of the resulting file. If a tool reports an unknown or unwritable field, stop and resolve that warning rather than treating the attempted change as successful.
What metadata does and does not do in SendPhoto
SendPhoto’s client-gallery folder filter matches displayed folder names. Adding keywords, captions or ratings to image metadata does not turn that control into photo-level metadata search. Use clear collection names for navigation and your archive software for its supported metadata searches.
Likewise, do not assume that a field will be visible in the gallery interface just because it is embedded in an uploaded file. Display, retention and search are different capabilities.
For a delivery check, start with a non-sensitive test image containing distinctive fictional values. Inspect the upload copy, then download the exact type you intend clients to receive and inspect that file separately. Repeat for other offered sizes rather than assuming the original and resized download are identical.
This guide does not claim a verified metadata-retention result for SendPhoto uploads. Keep your authoritative originals and archive records independently of a gallery link. If a recipient requires particular embedded fields, verify that delivery path before sending the real set.
Keep automation useful without spreading mistakes
Automate stable facts, not uncertain judgments. A preset can save repeated typing, but it can also replicate the wrong contact details across a whole shoot. Check it when your business information changes and before using it for a new type of job.
Treat automated descriptions and keywords as suggestions to review. Check the people, objects, location and purpose against the photograph and the job. Remove terms that are inaccurate or inappropriate to share.
When a colleague updates metadata, agree which copy is authoritative. Avoid editing two catalogs independently and expecting their descriptions or ratings to merge without checking. Keep a short record of the chosen naming conventions and handoff process.
If the archive has years of inconsistent labels, start with the jobs you revisit most. Correct a manageable group and verify retrieval before changing the entire library.
A final delivery check
Check the image identifier, creator and intended descriptive fields. Look for stale client details, internal notes and location information. Confirm that the recipient’s actual file contains what you intended and omits the fields you deliberately removed.
Keep a copy of the export settings or a short delivery note so that another team member can repeat the process. If the client needs a caption or credit prominently displayed, include it in the agreed handoff rather than depending solely on embedded metadata.
Use metadata to maintain a useful archive, clear folder names to support gallery navigation, and a confirmed file list to keep client selections unambiguous. These are complementary tasks, not interchangeable features.
References and related guides: IPTC Photo Metadata User Guide; Adobe’s Lightroom Classic export documentation; IPTC’s ExifTool guide; SendPhoto folder search; confirming proofing selections; gallery delivery.