Amazon policy update · Jul 23, 2026

Tag AI-generated people.
Verify before upload.

Add contains-synthetic-performer to the correct XMP field in JPG and PNG files—individually or in bulk.

Runs locally Preserves keywords Verifies every write
Built for listing workflows

From source file to verified download

No metadata editor to install. No command line. No files sent to us.

0 files · 0 B local
Batch metadata writer

Write the exact XMP tag—then verify it

JPG and PNG · up to 100 files · existing keywords preserved

Drop JPG or PNG files hereor click to browse · 50 MB maximum per file
Processed in your browser

中文提示:文件只在本地浏览器中处理;请先确认素材确实包含“完全由 AI 生成的写实人物”,再执行标签写入。

Policy boundary

When should you add the tag?

The requirement is narrower than “anything made with AI.” Separate the person’s origin from ordinary AI editing.

Tag required

Photorealistic + entirely AI-generated

The media features a person who appears photorealistic and was created entirely with AI.

Tag not required

Published exclusions

Real people—even if AI-edited; expressive-work characters; no people; or people who are not photorealistic.

Review first

Origin or treatment is unclear

Hybrid composites, face replacements, partially generated bodies, or assets without reliable provenance.

Evidence checked Jul 27, 2026Policy text can change. Re-check Seller Central before a production upload.
Use the decision assistant →
A safer three-step workflow

Know, write, verify

01

Confirm the asset origin

Use creator records or generation history to decide whether the person is entirely AI-generated.

02

Write the exact keyword

AssetDisclose updates the XMP dc:subject bag without replacing your other keywords.

03

Download verified files

Every output is re-read, checked for one exact tag, and paired with an audit manifest.

Privacy by architecture

Your media stays on your device

Inspection, XMP writing, verification, CSV creation, and ZIP packaging all run inside your browser. We cannot see or retain your product media.

0media uploads0accounts required100%local processing
FAQ

Before you process a production batch

The practical limits of the MVP, in plain language.

What does AssetDisclose add to my file?

It adds the exact keyword contains-synthetic-performer to the dc:subject bag inside the file’s XMP metadata. Existing subject keywords are preserved, and duplicate copies of the required keyword are reduced to one.

Does the tool detect whether a person was generated by AI?

No. Reliable provenance cannot be proven from pixels alone. The decision assistant helps you apply the published policy boundary, but you should use creator records, source files, and generation history to answer it.

Are my product images uploaded?

No. JPG and PNG inspection, metadata writing, verification, and ZIP creation happen locally in your browser. This MVP has no account system and sends no media to an AssetDisclose server.

Does a valid tag guarantee Amazon acceptance?

No. AssetDisclose verifies the file metadata it writes; it cannot guarantee a platform decision or legal compliance. Amazon may change its guidance or apply additional listing requirements.

Why are video files not editable yet?

Video containers use different metadata structures and require broader compatibility testing. Video support is on the roadmap; the MVP deliberately limits writing to JPG and PNG to keep the output verifiable.

Next on the roadmap

Need the same workflow for video?

Container-safe writing and verification for MP4/MOV is in compatibility testing.

Join video beta