Loading...
Loading...
Which file formats get AI-disclosure metadata and a signed C2PA manifest today, which do not, and what is planned.
Free to start. No card needed.
Numonic signs JPEG, PNG and WebP exports with a C2PA manifest, up to 50 MB. When Numonic knows a file is AI-generated, it also writes IPTC 2025.1 AI-disclosure fields. GLB 3D files get the disclosure fields but no signature. Video, audio and GIF exports get neither yet.
| Format | AI-disclosure metadata (IPTC 2025.1) | C2PA signature | Credentials already in the file |
|---|---|---|---|
| ImagesPNG, JPEG, WebP | TodayFor files known to be AI-generated | TodayUp to 50 MB | Kept as a linked ingredient of Numonic's manifest |
| 3D modelsGLB | TodayFor files known to be AI-generated | Not yetPlanned, not scheduled | A GLB that already carries a signature exports unchanged, with no fields added |
| VideoMP4, MOV, WebM, MKV | Not yetPlanned, not scheduled | Not yetPlanned, not scheduled | The file passes through unchanged, so credentials stay intact |
| AudioMP3, WAV, OGG, FLAC | Not yetPlanned, not scheduled | Not yetPlanned, not scheduled | Credentials in MP3 files stay in the export on every preset |
| Animated imagesGIF | Not yetPlanned, not scheduled | Not yetPlanned, not scheduled | The file passes through unchanged |
Numonic writes AI-disclosure fields only for files its provenance records identify as AI-generated. Signing does not depend on the export preset. Presets decide which metadata is removed, not whether a file is signed.
Last checked against the export code on .
The open-source C2PA tools cover more formats than Numonic signs today: images such as JPEG, PNG, WebP, GIF and TIFF, MP4 and MOV video, and WAV, M4A, MP3 and FLAC audio. Numonic's coverage is narrower, as the table above shows. The limit is in our export pipeline, not in the tools. See the C2PA supported-formats list.
A signed export carries a C2PA manifest that records:
If signing cannot run, the file still exports and Numonic marks it as unsigned. You are never left to assume a signature that is not there.
Numonic signs with its own certificate today. A verifier confirms the signature is valid and the file has not changed since, then lists the issuer as unrecognised. That is accurate: no recognised authority has issued the certificate yet.
A certificate from a recognised authority is planned, not scheduled. Until then, treat Numonic's signature as proof of what Numonic recorded and that the file is unaltered, not as a third-party endorsement.
If a client or platform asks for disclosure on these formats, label them yourself or ask us how we handle your case.
All items below are planned, not scheduled, and listed in no particular order. We publish no dates. We move an item to Today only after it ships and we have tested a real export.
No. Video exports pass through unchanged today, so a credential already in the file stays valid, but Numonic adds no signature or disclosure fields. Video marking and signing are planned, not scheduled.
Not yet. Audio exports carry no Numonic disclosure fields or signature. An existing C2PA manifest in an MP3 stays in the exported file.
No export can prove that by itself. This page lists what the files carry. Your obligations under Article 50 depend on your role. See our Article 50 guide for creators and the AI disclosure generator.
All of them. The Share, Portfolio, Client and Archive presets differ in what metadata they remove. Signing and disclosure marking run on every preset for the formats in the table.
The export tells you. A file Numonic could not sign, such as one over 50 MB, is marked unsigned instead of failing silently.
Read our guide to C2PA and Content Credentials, or the post on IPTC 2025.1 and C2PA.
Tell us which formats you deliver and who asks for disclosure. We will say plainly what Numonic covers today.