Check if the contains-synthetic-performer tag is still there
Drop in an image or a video and see immediately whether contains-synthetic-performer is still embedded. Tagging is something you do once; verifying is something worth doing before every upload — creative files usually pass through retouching software, compression tools, asset libraries and agency portals on their way to Seller Central. We measured how often that costs you the tag: not one of seven processing steps kept it on both JPEG and PNG.
Drop an image or video here
JPG · PNG · MP4 · MOV · WebM — read only, never modified, never uploaded
Results appear here instantly. Files never leave your browser.
What each result means
| Result | Meaning | What to do |
|---|---|---|
| Tag present | A compliance tag was read from XMP dc:subject (container tags for video) | Safe to upload |
| No tag | The file carries metadata, but none of it is a compliance tag | Add the tag if the image contains a fully AI-generated photorealistic person |
| No metadata | Nothing was read at all — typical of files that went through a compression or export step | Go back to the source file, or tag it again |
This tool tells you whether the tag is there, not whether the image needs one. That depends on what is in the frame: fully AI-generated photorealistic people need the tag; real people (even after AI retouching), cartoons and illustrations, characters from film, TV or games, and images with no people at all do not.
How a tag goes missing
Almost always the same way: something re-encoded the image. Opening a file in an imaging library and saving it again is enough — no cropping, no compression setting, no export dialogue. We measured eight processing steps and not one kept the tag on both JPEG and PNG.
So the useful question about any step in your workflow is not which app it is, but whether it re-encodes the picture. Compressing, resizing, converting format and editing all do. Copying, zipping and sending a file as a file do not — and those leave the bytes, and the tag, untouched.
A file can carry metadata and still fail. Some tools do not delete the XMP packet, they overwrite it with their own. The export still looks like it has metadata while the field Amazon reads is empty — which is why the result above distinguishes “no tag” from “no metadata”.
What this checker does and does not do
- Reads XMP
dc:subjectfor images, and container tags for video - Never modifies the file — it is opened read-only and nothing is written back
- Never uploads anything; parsing happens in your browser
- Tells you whether the tag is present, not whether the image needs one
That last point matters. Whether an image needs the tag depends on what is in the frame, and only a person can judge that — see what needs tagging.
Checking a whole batch
Drop in as many files as you like — the checker reads them all and counts how many carry a tag. For a catalogue audit that is usually enough: you want the number of files missing a tag, and their names, not a report per image.
If some of them turn out to need tagging, the workspace writes tags in bulk and skips the files that already comply, so you are not rewriting what is already correct.
What video checking can and cannot tell you
Video is read from container tags — the fields a muxer writes alongside the stream. MP4, MOV and WebM are all parsed, and a tag written by this site or by ffmpeg will be found.
The honest limitation: Amazon has published the metadata field for images only. Which field it reads for video, if any, has not been stated. So a video reading “tag present” here means the container carries the keyword — it does not mean Amazon will read it from there. Video results are marked experimental for that reason, and the same caveat applies to any tool claiming otherwise.
Two things people expect this to do, and it does not
- It does not look at the picture. Whether an image contains an AI-generated person is a judgement about content; this reads metadata only. A product shot with no people in it will report “no tag” exactly like a mis-tagged AI model shot.
- It does not fix anything. Files are opened read-only. Nothing is written back, and the file you dropped in is byte-for-byte the file still on your disk.
Need to tag a whole folder?
The workspace takes an entire folder, writes tags in bulk and exports a ZIP with a compliance report — also entirely in your browser.
Open the workspace →