Guide
Adobe Firefly Content Credentials
Adobe attaches Content Credentials to many images made or edited with its tools, including Firefly and Photoshop. They are C2PA-based provenance data embedded in the file, and they can trigger AI labels when you publish the image elsewhere.
How to use it
- 1Scan the exported image for a C2PA or Content Credentials indicator.
- 2Decide whether you need the record; checking is read-only.
- 3If you want a clean file, rebuild the image.
- 4Verify the after-scan shows no credential container.
- 5Keep the original if you need its provenance.
What Content Credentials record
A credential container is a structured record, not a simple tag. It travels with the image and stays readable by platforms and viewers that understand the format.
- The application used to create or edit the image.
- A history of the edits or actions applied.
- A statement about whether generative AI was involved.
- A claim signer, so a platform can show it as verified.
Why platforms show a label
Social platforms that take part in provenance standards read the credential from the uploaded file and can display a label such as an AI info note. The label is a signal about the file, and it appears regardless of how the picture looks.
Firefly's visible and invisible marks
Some Firefly plans add a visible watermark to generated output. A visible mark drawn into the picture is content and cannot be removed by metadata cleaning. The invisible Content Credentials are file metadata, and those are what a tool can remove.
Where credentials live by format
The container is stored in a format-specific place.
| Format | Credential location | Notes |
|---|---|---|
| JPEG | APP11 (C2PA/JUMBF) | Typical of Photoshop exports. |
| PNG | caBX chunk | Used by many Adobe exports. |
| WebP | C2PA chunk | Compact and widely supported. |
| AVIF / HEIC | ISO-BMFF C2PA box | Newer formats and phone captures. |
Inspect before you decide
Checking is read-only. You can confirm that a credential exists without changing the file, then choose whether to publish the signed original or a cleaned copy. MetaRase reports that a supported container is present; it does not perform a full cryptographic validation of every manifest.
Removal is not editing
Rebuilding the image from its pixels leaves the picture intact while dropping the embedded container, along with other supported metadata. It does not alter the content, and it does not pretend the image was never edited.
Keep the proof if you need it
Removing the container also removes the embedded proof, and it cannot be rebuilt from the cleaned file. If provenance matters, for clients, archives, or compliance, keep the original signed file before you clean a copy for publishing.
Frequently asked questions
Are Content Credentials mandatory?
Adobe adds them to exports from many of its tools. Whether they are required depends on your workflow and platform policies.
Does Firefly add a visible watermark too?
Some plans produce files with a visible mark. A mark drawn into the picture cannot be removed by metadata cleaning.
Can I verify an image later if I remove credentials?
No. Removing the container removes the embedded proof, so keep the original if you need it.
Is this the same as C2PA?
Yes. Content Credentials are Adobe's name for a C2PA-based provenance record.
Does removing credentials change image quality?
Only through the ordinary re-encoding. The scene is untouched.
Will Photoshop re-add credentials on export?
Many Adobe tools attach them again on export, so clean the final file you intend to publish.
Is it legal to remove them?
For your own images it is generally allowed. Do not remove ownership or copyright information that belongs to someone else.
Sources
Inspect, clean, and verify in your browser
Your image bytes never leave your device. MetaRase rebuilds the image locally, then scans the output again before you download it.
Open the cleanerRelated pages
Results describe supported embedded indicators only and cannot guarantee how a platform will classify an image.