Why Adobe Stock doesn't read your JPG metadata
You embedded XMP, verified it in ExifTool — all present. You upload to Adobe Stock — empty fields. This is a common, poorly documented problem. Here's what's going on.
The symptom
The JPG contains a valid XMP packet (dc:title, dc:subject, dc:description), ExifTool and Photoshop see it, but the Adobe Stock upload doesn't fill the card. The file is valid, opens everywhere, throws no errors.
The cause: a missing JFIF APP0
A standard JPG starts with an APP0 (JFIF) marker. Adobe Stock's parser expects the classic segment layout: APP0, then APP1 with XMP. Some generators, converters and metadata libraries save files without APP0, or put XMP as the first segment — technically valid, but Adobe silently skips the metadata.
This happens a lot with files re-saved by certain Python/Node libraries and AI pipelines.
How to check your file
Drop the JPG into our free metadata checker: it shows not just the XMP fields but also whether the JFIF marker is present. Or inspect the first bytes: after FF D8 there should be FF E0 (APP0, “JFIF”).
How Stock Metadata Tagger fixes it
When embedding metadata the service checks the segment layout and, if APP0 is missing, inserts a minimal JFIF header before the XMP. The result is a file Adobe Stock reads reliably — a fix born from our own empty cards on real uploads.
Why does ExifTool see the metadata but Adobe doesn't?
ExifTool tolerates segment order and scans the whole file for XMP. Adobe Stock's parser is stricter: without APP0 before APP1 it can skip the XMP entirely.