Did Your Image Metadata Survive the Upload? A 5-Minute Test

Why metadata disappears after upload

Image metadata lives inside the file container, so anything that re-encodes the file can drop it. Platforms re-encode for three reasons: to generate thumbnails and responsive variants, to strip potentially sensitive data such as GPS, and to normalise formats for their CDN. Some pipelines copy the fields deliberately; many simply do not.

The result is that your local file and the file the platform serves are different files. Checking properties on your desktop proves nothing about what shoppers — or search engines — receive.

This matters because metadata is a supporting signal, not a magic ranking switch. If a marketplace strips it, the listing still ranks on title, tags, photos and engagement. But if you are relying on embedded keywords as part of your workflow, you need to know whether they survive.

The 5-minute round-trip test

Run this once per platform, with a throwaway listing, and write down the result. You will never have to guess again.

• Create a small test image, 1200 px wide, named with an obvious marker such as metadata-test-amber-mug.jpg.
• Inject four unmistakable values: Title = METADATA TEST TITLE, Subject = METADATA TEST SUBJECT, Tags = amber-mug-test, Comments = uploaded 2026-10-22.
• Verify the file locally with the metadata inspector before uploading. If the fields are empty here, stop — the upload is not the problem.
• Upload to a draft or hidden listing, then open the listing in a private window.
• Right-click the served image → Save image as… (or use the browser's copy image address and download that URL).
• Inspect the downloaded file, not your original. Compare all four fields.
• Record the result: all four survived, some survived, or none. Then repeat with a PNG to see whether the text-chunk path behaves differently.

What the inspector should show

For JPEG, the four fields are Windows XP tags: XPTitle, XPSubject, XPKeywords and XPComment. In a file-properties dialog they appear as Title, Subject, Tags and Comments. For PNG, they are text chunks named Title, Subject, Keywords and Comment.

If the served file is now WEBP or AVIF, the platform converted it. Some converters preserve EXIF/XMP, many do not; the inspector will show you which. A file with no metadata after conversion is normal, not a bug in your injector.

One caveat: some viewers show only EXIF and hide XMP. If you injected XMP-based fields and the inspector shows nothing, check a second tool before concluding the data is gone.

What to expect per platform (verify on your account)

Platforms change their pipelines without announcement, so treat this table as a starting hypothesis to test, not as a specification.

When the fields are empty

Work backwards from the served file, not forwards from your intention. If the local file was correct and the served file is empty, the platform stripped it — no amount of re-injecting will change that. Move the keywords into the fields the platform actually reads: title, tags, description and alt text where available.

If the local file was already empty, the problem is upstream. Check four things in order: the source format (some formats cannot hold the field), whether another tool re-saved the file after injection, whether the field was disabled in the batch settings, and whether the exported ZIP was generated before the injection finished.

• Local file empty → fix the injection step first.
• Local file correct, served file empty → platform strips it; use platform fields.
• Local file correct, served file is a different format → conversion dropped it.
• Some fields survive, others do not → field-level differences in the pipeline.

Keep a verifiable archive

Store three things per batch: the untouched originals, the injected masters, and a small text file listing what was written into each image. When a platform strips metadata or a colleague asks what was published, the archive answers in seconds.

Name the archive folder by date and batch size, not by product name. Product names change; batches do not. A folder called 2026-10-22_batch-50 tells you more a year later than autumn-mugs-final-v3.

Why bother if marketplaces strip it

Because not every destination strips it, and because the same files often travel: your own store, a newsletter, a press kit, a stock library. Metadata is also how you keep a catalogue searchable on your own disk years later, when filenames alone are not enough.

Treat embedded keywords as one layer of a stack — filename, metadata, alt text, page context — and verify each layer where it is actually consumed.

Frequently asked questions

Does Etsy read EXIF keywords for ranking?

Etsy ranks primarily on title, tags, listing quality and engagement. Embedded metadata is not a documented ranking input, and Etsy may strip it on upload. Use it as a supporting signal, not a strategy.

Why did my keywords disappear after uploading?

The platform re-encoded the image to create display variants. Re-encoding can drop EXIF and XMP. Run the round-trip test to confirm on your account.

Does converting to WEBP remove metadata?

It can. WEBP supports EXIF and XMP, but many converters do not copy them. Inspect the output file rather than assuming.

Should I inject metadata into PNG or JPEG?

JPEG if the destination reads Windows XP tags; PNG if it reads text chunks. For photographs, JPEG is the more portable choice.

How do I check metadata on a phone?

Use a metadata viewer app, or download the served image to a desktop. Mobile galleries rarely expose the fields you need.