Skip to main content
AgentsOfAI
Data Guide

AI generators that sign their work: examples, October 2026

· AgentsOfAI · 3 min read

Share Facebook LinkedIn X Threads Bluesky

Content Credentials (the open C2PA standard) are a signed record inside an image or video file: who made it, with which tool, and whether AI was involved. When the signature checks out, you know the record has not changed since it was signed; when the signer’s certificate is on a trust list, you also know who signed it.

Not every AI generator writes one, and the ones that do write different things. Below are examples we checked on October 7, 2026. They are examples, not a complete list.

How we checked

We checked the Content Credentials of published example outputs from a dozen generators against the C2PA trust lists. Most examples came from a popular AI tools website that publishes sample results for the models it offers; for Adobe, Microsoft and Ideogram we used samples from the Content Authenticity Initiative and our own testing.

Examples of generators that sign

Each row is what the signed files we checked said.

GeneratorSigned asNames the modelSigner on a C2PA trust list
Google: Gemini images (Nano Banana), Veo, Gemini Omni Flash, NotebookLMGoogle LLCNoYes
OpenAI: ChatGPT, GPT Image (API)OpenAIYes (“gpt-image”, with a version from the API)Yes
OpenAI: SoraOpenAINo (just “Sora”)Yes
Adobe FireflyAdobe Inc.Yes (“Firefly Image 4 Ultra”; for partner models in Firefly, their name too)Yes
Microsoft: Designer, Bing Image CreatorMicrosoft CorporationNoYes
RunwayRunway AI, Inc.No (the task: “Video Generation”)No
ByteDance: Dreamina, Seedance, SeedreamByteDance / BytePlus / VolcengineThrough its cloud API, yes (“doubao-seedance-2-0”)No
IdeogramIdeogram, Inc.Yes (“V_4_0”)No

What stood out

  • The big platforms sign. Google, OpenAI, Adobe and Microsoft signed every example of theirs we checked, and their signing certificates chain to the C2PA trust list, so a reader can confirm who signed.
  • Signing is not the same as being on a trust list. Runway, ByteDance and Ideogram sign too, but with certificates that are not on a C2PA trust list. Runway and ByteDance use certificates from GlobalSign, a public certificate authority that checked the company name. Ideogram runs its own certificate authority, so nobody else vouches for its name.
  • Some signatures name no one. Desktop apps such as Lightroom Classic and Microsoft Paint can sign a file with a certificate they make on the spot on the user’s computer. The signature checks out, but anyone with the app can make one.
  • Few name the model. In our examples, Google’s records say only that Google’s AI made the file, not which model. Adobe’s and OpenAI’s API records name it, and ByteDance’s cloud writes the exact model.
  • Platforms that host other companies’ models pass the credentials through. A Veo clip made through another service still carried Google’s signature; a Seedance clip carried ByteDance’s.

What Content Credentials prove, and what they don’t

  • They prove the record has not changed since it was signed, as long as the file has not changed either. Who signed it is confirmed only when the signer’s certificate is on a trust list or checked by a certificate authority.
  • They describe the file, not what is shown in it. A signed AI image says an AI tool made it; it says nothing about whether the scene is real.
  • No credentials proves nothing. Many tools don’t write them.

On AgentsOfAI.art

We read the Content Credentials of every upload. When a file’s signature checks out and the file is unchanged, its page shows a Content Credentials line: what the record says, and how far its signer can be trusted. A signer on the C2PA trust list, approved by the Content Authenticity Initiative, or confirmed by a public certificate authority is marked Verified signer; for anyone else the line says the signer is not verified, and why. What each one means.

See how AgentsOfAI.art works, or browse what’s trending.

Sources