Text: no public check
OpenAI's public provenance documentation does not provide a tool where you paste ChatGPT text and test for an official watermark.
The important answer depends on the format. Text, images and audio do not use the same public verification system.
Three facts prevent the most common misunderstandings.
OpenAI's public provenance documentation does not provide a tool where you paste ChatGPT text and test for an official watermark.
Supported images can be checked for signed C2PA Content Credentials and an embedded SynthID watermark.
Supported audio can be checked for an embedded SynthID signal. A result is evidence of a signal—not a complete history.
One travels as signed information in an image file. The other is embedded in the media itself.
OpenAI says SynthID can mark supported images and audio. The signal is part of the media and may survive some transformations.
It is not a visible logo and cannot be found by reading image metadata alone.
Content Credentials can carry signed information about an image's origin. The verifier also checks whether the record is cryptographically valid.
Editing, conversion or sharing can remove this metadata.
The verifier looks for supported OpenAI signals. It does not guess from whether the file “looks like AI.”
Use an image or a short audio file. The original is best because screenshots, exports and conversions can lose information.
For images, the result can include both C2PA and SynthID. For audio, the documented check is SynthID.
If an image has Content Credentials, the verifier checks the issuer and signature. Model or generation time may be present, but can also be unavailable.
The detector looks for an embedded OpenAI-supported signal. It returns detected, not detected or an error—not the identity of a person.
These systems answer different questions. C2PA is a signed manifest attached to an image file. SynthID is an embedded watermark that OpenAI says can be detected in supported images and audio. OpenAI's verifier reports each applicable signal separately.
The verifier parses the image's Content Credentials, validates its cryptographic signature and reports the issuer. Optional details such as model and generation time may be missing.
The detector examines the media for an OpenAI-supported watermark. Because it is embedded rather than stored only as metadata, it may survive some transformations—but edits can still weaken it.
The Content Provenance API accepts one file per request, up to 50 MiB. Audio must be no longer than 60 seconds. Results are not a universal AI-origin verdict.
Images: PNG, JPEG and WebP, with C2PA and SynthID results where applicable.
Audio: MP3, Opus, AAC, FLAC, WAV and PCM, with a SynthID result.
Why use both? C2PA can carry useful signed context, but metadata is easy to lose. An embedded signal can be more durable, but it carries less human-readable context and can degrade after transformation. Together they provide stronger evidence than either one alone.
A provenance result is useful evidence, but it is not a verdict about authorship, truth or misconduct.
Check which signal was detected and, for C2PA, whether the issuer and signature are valid.
It also does not prove the file is true, unchanged in every way or entirely generated by AI.
The result describes this file and the signals the verifier currently supports.
The signal may be absent, removed, degraded, unsupported or created by another provider.
Remember: “Not detected” is not the same as “made by a human.”
Use OpenAI's own verifier for supported files. Do not confuse it with a writing-style detector.
Checks supported OpenAI provenance signals in image and audio files.
Usually guesses from writing style or statistical patterns. It is not an official OpenAI provenance check.
C2PA metadata and an embedded SynthID watermark fail in different ways.
The public documentation defines formats and limits, not a promise that every OpenAI model or output is marked.
PNG, JPEG and WebP files can be checked. Results may include C2PA and SynthID.
MP3, Opus, AAC, FLAC, WAV and PCM files can be checked for SynthID. Audio is limited to 60 seconds.
The public provenance guide and verifier do not document a pasted-text watermark check. Do not turn that absence into a stronger claim.
Use provenance as one piece of evidence and match the response to the situation.
If you only want to understand an image or audio file, start with the original and read each signal separately. A missing signal is not proof of human origin.
Do not use a generic text detector as proof that ChatGPT wrote an assignment or email.
Machine-readable provenance and visible disclosure are separate questions. EU rules can require providers to mark output and can also require visible disclosure in specific public-interest uses.
The Content Provenance API can automate supported checks, but OpenAI says results should be combined with context, human review and clear uncertainty.
Paste your Danish text into SkrivSikkert and correct common mistakes.
Correct my Danish textOpenAI's public provenance documentation does not provide a pasted-text watermark check. That does not prove that no internal, experimental or future text signal exists; it means users do not currently have that public documented check.
Yes. OpenAI provides a public Verify page and a Content Provenance API for supported image and audio formats.
C2PA Content Credentials are signed provenance metadata in an image file. SynthID is an embedded watermark used in supported images and audio. Metadata can be removed more easily; an embedded signal may survive some transformations.
No. It means the verifier found a supported OpenAI provenance signal. It does not identify a person, account or prompt, and it does not provide the file's complete history.
No. A signal may have been removed or degraded, the output may be unsupported or older, or the file may come from another AI provider.
Screenshots, re-exports, format changes, cropping and compression can remove C2PA metadata or weaken an embedded watermark.
No. OpenAI's documentation says results should not be used to infer the prompt, account or person behind the content.
No. Provider-side machine-readable marking and user-facing visible disclosure are separate obligations. Visible disclosure depends on the content and how it is used.
OpenAI's own documentation comes first. EU and C2PA sources explain the legal and technical context.