Photorealistic + entirely AI-generated
The media features a person who appears photorealistic and was created entirely with AI.
Add contains-synthetic-performer to the correct XMP field in JPG and PNG files—individually or in bulk.
No metadata editor to install. No command line. No files sent to us.
JPG and PNG · up to 100 files · existing keywords preserved
中文提示:文件只在本地浏览器中处理;请先确认素材确实包含“完全由 AI 生成的写实人物”,再执行标签写入。
The requirement is narrower than “anything made with AI.” Separate the person’s origin from ordinary AI editing.
The media features a person who appears photorealistic and was created entirely with AI.
Real people—even if AI-edited; expressive-work characters; no people; or people who are not photorealistic.
Hybrid composites, face replacements, partially generated bodies, or assets without reliable provenance.
Use creator records or generation history to decide whether the person is entirely AI-generated.
AssetDisclose updates the XMP dc:subject bag without replacing your other keywords.
Every output is re-read, checked for one exact tag, and paired with an audit manifest.

Inspection, XMP writing, verification, CSV creation, and ZIP packaging all run inside your browser. We cannot see or retain your product media.
The practical limits of the MVP, in plain language.
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.
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.
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.
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.
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.
Container-safe writing and verification for MP4/MOV is in compatibility testing.