Image Metadata Embedder for JPG, PNG and SVG
Keep reviewed descriptive metadata with a supported image file. CSV Metadata can write an XMP packet to JPEG, PNG and SVG outputs, while contributor CSV export remains available when a marketplace requires a separate table.
What this metadata writer adds
The embedded output contains descriptive XMP fields for a title, description and keyword list, with category and platform information where supplied by the workflow. XMP is a metadata format used to carry these values; it is not the same as changing the visible artwork. Generate and review the text first, then select Embed Metadata as the output mode in Metadata Studio.
Supported file formats and limits
The current embedding implementation supports JPEG/JPG, PNG and SVG files. JPEG output stores the XMP packet in an application metadata segment, PNG output uses a text metadata chunk, and SVG output includes a metadata element. Do not assume that every application or stock platform reads all of these containers in the same way. Other input formats may be usable for visual analysis without supporting direct metadata embedding.
Preserving image content and transparency
For supported formats, the embedding step adds metadata rather than rendering a new background into the artwork. Review a downloaded sample to confirm that the image still opens correctly and that a transparent PNG remains transparent. Keep the source file as your reference copy. If another application later re-exports the file, check again: editors and upload pipelines may remove or rewrite metadata during their own processing.
XMP, IPTC and EXIF describe different things
Contributors often search for an IPTC metadata editor when they want descriptive titles and keywords. CSV Metadata writes those descriptive values through XMP; it does not claim to write every IPTC-IIM field or to recreate camera EXIF data. Camera settings, capture times, GPS coordinates, copyright evidence and release permissions should never be invented from an AI image description. Check the receiving application's supported fields before relying on an embedded export.
Choose embedded metadata or CSV deliberately
Use an embedded copy when you want supported descriptive values to travel with a compatible image. Choose contributor CSV when the receiving marketplace expects rows matched to uploaded filenames. For an Adobe Bridge workflow, open a small exported sample and inspect the relevant metadata fields before preparing the full batch. Whether metadata is embedded or exported separately, check the final contributor submission form because acceptance and field interpretation are controlled by the destination.
Frequently asked questions
Does this write all EXIF camera information?
No. The tool writes descriptive XMP metadata. It does not reconstruct real capture settings, dates or GPS information.
Can I embed metadata in a PNG without adding a white background?
The metadata embedding step adds a metadata chunk; it does not flatten PNG pixels. Check your downloaded sample and any later re-exports.
Can I embed directly into every vector format?
No. Direct embedding currently supports JPG/JPEG, PNG and SVG. Use a contributor CSV for other supported analysis workflows.