Bulk-add contains-synthetic-performer metadata
The AssetDisclose batch XMP tagger processes up to 100 supported images locally, appends the exact disclosure keyword, verifies each generated file, and packages completed outputs with a CSV manifest.
Why batch verification matters
A large listing or A+ content refresh can contain a mix of already tagged, untagged, duplicated, and unsupported files. Per-file status prevents one failure from hiding the result of the rest of the batch.
What the manifest records
- Original filename and media format
- Action taken for the file
- Exact-tag verification result
- Policy date associated with the workflow
- Original and generated file hashes
Safe operating practices
Keep originals outside the batch ZIP, verify again after any later image optimization, and use the decision assistant before writing. A bulk tool accelerates a confirmed decision; it should not turn uncertain provenance into an automatic legal conclusion.
Evidence behind this guide
Policy guidance can change. Confirm the current Seller Central instruction before a production upload.
Common questions
Will one bad file stop the whole batch?
No. Each file receives its own result so supported files can complete while unsupported or damaged files show an error.
Can the batch tool process folders?
Browser capabilities vary, but multiple file selection is supported. Folder workflow improvements are planned.
Is the batch sent to a server?
No. The current image workflow runs locally and creates the ZIP in your browser.
Amazon AI media tagging resources
Move from policy interpretation to writing, verification, batch processing, and provenance.