DALL·E 3 / OpenAI provenance

Inspect OpenAI image provenance locally

Read C2PA separately from ordinary text, EXIF and XMP. Create a derivative without supported embedded sections while keeping the original intact.

Reviewed August 12, 2026 by ClearTags EditorialMethodology and corrections

CONTEXT / EVIDENCE

OpenAI documents provenance, not a guaranteed prompt field

OpenAI says images generated with ChatGPT, Codex and its API include C2PA metadata. The signed claim is a provenance signal and can be removed accidentally or intentionally, so its absence does not establish how an image was made.

C2PA does not mean that a complete private prompt or seed is guaranteed to be stored as readable text. ClearTags reports what this particular file contains and can remove supported embedded metadata from a new publishing copy.

TESTED FILE / CHATGPT

One real ChatGPT export, checked end to end

See the file, license and hashes

Our Lab includes a redistributable ChatGPT / GPT-4o PNG from the Content Authenticity Initiative example corpus. The upstream record does not state the exact ChatGPT build or generation settings, so neither do we.

Test file

ChatGPT / GPT-4o · PNG

The original PNG contains an OpenAI provenance manifest that the official C2PA reader can parse.

Version
Not provided by upstream
SHA-256
7cd57b4a33f0…
Verified result

The production cleaner removed the supported metadata, reinspected the copy and kept the PNG image payload hash unchanged.

ClearTags Lab documents each fixture's scope and publishes its complete hashes.

Keep three signals separate

C2PA · EXIF · XMP · CONTAINER
C2PA

Signed OpenAI claim

A readable manifest can identify the claim generator and declared provenance associated with the asset.

TEXT

Prompt-bearing fields

EXIF, XMP, PNG text and comments are inspected separately because a full prompt is not guaranteed by C2PA.

PIXELS

Non-metadata signals

Metadata cleanup does not remove a signal embedded in image content itself, including an invisible watermark.

Create a metadata-clean derivative

WORKFLOW / LOCAL COPY
  1. 01

    Keep the downloaded original

    Preserve the source image if provenance or generation history may matter later.

  2. 02

    Inspect the exact export

    Review C2PA, EXIF, XMP and text fields in the asset you plan to publish.

  3. 03

    Select embedded sections

    Remove the supported provenance or plain-text metadata you do not intend to distribute.

  4. 04

    Reinspect the new copy

    Confirm the report after cleanup rather than assuming every provenance mechanism was removed.