Skip to content
SynthIDX

Share a Firefly Image Without the Content Credentials

Adobe Firefly Metadata Remover

Strips the C2PA Content Credentials Firefly attaches to fully generated assets. Firefly adds no visible watermark; Adobe may keep a cloud copy of the credentials.

Sign in to run. Free credits included.

Removes the C2PA record Firefly writes into the file · Metadata-only strip at the original resolution · 5 credits per image strip

What are Content Credentials in Adobe Firefly?

Content Credentials are the user-facing layer of the C2PA standard, an open technical project from the Coalition for Content Provenance and Authenticity. The coalition counts Adobe among its founders, and its specification defines a cryptographically signed record that travels inside a media file. The record answers a narrow question: how was this asset made, and what happened to it afterward? Adobe picks that mechanism as the disclosure channel for its generative AI features. The Firefly documentation states that Adobe applies Content Credentials automatically whenever an asset is generated entirely inside Firefly, such as an image produced by Text to Image.

The record is structured rather than free text. Per the same Firefly overview, a credential attached to a Firefly generation always lists a fixed set of non-personal fields. It names Adobe Inc. as the issuer, the date the credential was issued, the Adobe app or device used, the generative AI tool used, and the actions taken to produce the asset. For Firefly output those actions are limited to Created and Other edits. A Text to Image generation made on the Firefly website can also carry a no-frills thumbnail of the output. If you never opted into the optional Content Credentials fields in Photoshop, Lightroom or Content Authenticity, the record holds nothing beyond that list. The official description lives at https://helpx.adobe.com/firefly/web/get-started/learn-the-basics/content-credentials-overview.html.

That signature is the point. C2PA binds the credential to the exact pixels it describes, so any later change to the image shows up as a broken chain. A viewer with an inspection tool can then see that the file was generated by Adobe Firefly and that nothing has altered it since. Platforms are starting to read the same record on upload and display it beside the image. For a Firefly asset the credential may be the only machine-readable marker inside the file, because Firefly adds no visible watermark of its own. That is also why some creators want it gone before they share the file.

What Firefly writes into the file

Under the hood the credential is a C2PA Manifest. The specification packs a set of assertions about the asset into a claim, signs that claim with the issuer’s signing certificate, and wraps the result with the signature into a verifiable unit. The manifest is then embedded beside the pixels, in JUMBF boxes inside a JPEG, in dedicated chunks inside a PNG or WebP file, or in the equivalent container for other formats. Nothing is burned into the image itself. The C2PA technical overview at https://spec.c2pa.org/specifications/specifications/2.5/index.html describes the same structure for any compliant producer, and Adobe’s Firefly credentials follow it.

For a typical Firefly generation the embedded record is concise. It carries the Adobe Inc. issuer identity, the issue date, the app or device, the Firefly tool name and the creation action. When the output came from Text to Image on the Firefly website, it can also include the thumbnail preview mentioned in the overview. Optional fields such as a verified creator name or generative AI training preferences only appear if you added them deliberately through another Adobe app. The credential is therefore a compact statement of machine origin rather than a biography of the work.

Reading the record and deleting it are different jobs, and this page does the second. The strip targets the manifest store and its wrapper, the XMP fields that point at the manifest, and the AI-bearing EXIF tags and text chunks that generators write. Standard metadata stays where it is: genuine camera EXIF, timestamps, GPS coordinates and the embedded color profile are preserved by default. The pixels are copied through without re-encoding. What leaves the tool is the same picture with the signed provenance removed. Many files arrive with nothing left to remove because a screenshot or a re-export already dropped the metadata. The job reports what it finds either way.

The credentials may also live in Adobe’s cloud

A Firefly credential is not only a passenger inside your file. Adobe’s overview says Content Credentials for Firefly-generated assets are attached to their files and may also be stored in Adobe’s public Content Credentials cloud. A cloud copy makes the credential durable and recoverable through the Inspect tool in Adobe Content Authenticity, even after the metadata leaves the file. Adobe describes Inspect as a recovery tool, not a gallery or a search service. The cloud stores the credential and a thumbnail preview of the work, not a copy of the actual asset file.

The Manage screen in Adobe Content Authenticity lets you find, view and delete credentials you stored in that cloud. There is one important exception. Adobe’s documentation for Manage states that Content Credentials applied to disclose the use of generative AI cannot be deleted. Firefly’s automatic attribution belongs to that category. In practice, stripping your downloaded file removes the local record; the credential Adobe holds for the generation can remain available to its own inspection tools. The Manage documentation is at https://helpx.adobe.com/creative-cloud/apps/adobe-content-authenticity/content-credentials/manage-content-credentials.html.

That split is the honest shape of this tool. It removes the credential from the file you own and upload, which is the copy a recipient, a platform or a client will inspect. It cannot reach Adobe’s servers, and it does not claim to. If a verifier already has the asset tied to a Firefly generation, the cloud copy may still let them confirm that origin. The tool changes what travels with your file, not what Adobe retains about it.

How it works

How to remove Content Credentials from a Firefly image

  1. Step 1: Upload your Firefly image

    Load the image Firefly exported into the panel. The file travels directly to processing storage and is never published or shared. The fullest record comes from the original export; a screenshot or a chat-app copy usually carries little or none.

    Tip

    Keep an untouched copy of the original before you run the strip.

  2. Step 2: Strip the Content Credentials

    The metadata pass reads the file and clears the C2PA manifest store and its JUMBF wrapper. The XMP fields that reference the manifest go too, along with the AI-provenance EXIF tags generators write. Standard metadata such as genuine camera settings, timestamps, GPS coordinates and the color profile is preserved. The image keeps its dimensions and framing, and a JPEG is copied without re-encoding its scan.

    Tip

    There is no visible Firefly watermark to remove, so the strip works entirely at the metadata layer.

  3. Step 3: Download the cleaned file

    Preview the result and download it. The output keeps your image’s dimensions, with no signed provenance record left inside. Inspect the file once more if you want to confirm the credential is gone before you publish it.

    Tip

    If the image came from a partner model inside Firefly, check for a pixel watermark too; this pass does not touch the pixels.

What the strip clears

  • C2PA manifest store

    The signed provenance record and its JUMBF wrapper are removed from the file, so a validator no longer finds a Firefly credential to read.

  • XMP provenance references

    XMP fields that point at the manifest go with it, closing the side channel that some tools use to locate the credential.

  • AI EXIF tags and generator fields

    The EXIF tags and text chunks that name a generator go in the same pass. Genuine camera EXIF and GPS stay put; clear those with the Remove Metadata page.

  • Credential preview thumbnail

    The small output preview embedded with the record is removed along with the rest of the credential payload.

Firefly output vs partner-model output

Firefly is not a single image model. The web app can route a prompt to partner models such as FLUX, Gemini, GPT Image, Imagen or Ideogram, and those routes carry their own disclosure conventions. A Gemini or Imagen image may have a SynthID signal woven into its pixels, which a metadata pass cannot reach. A partner model may also place a visible mark near a corner. Firefly’s own generations do not add a visible watermark, but a file made through a partner route is a different case.

The practical test is simple. If the image was generated by Firefly itself, this page removes the C2PA credential and there is no visible mark to worry about. If the image came from a partner model, the metadata pass removes whatever C2PA and XMP records the pipeline wrote, while any pixel-level watermark stays in place. For Google-routed images, pair this page with a pixel-level pass and verify the result separately. The origin of the pixels decides which layer matters.

Limitations and honest expectations

The cloud copy may keep the record verifiable

Stripping the file removes the credential inside it. Adobe states that Firefly credentials may be stored in its public Content Credentials cloud, and that credentials used to disclose generative AI cannot be deleted there. A verifier who already has the asset tied to the generation may still be able to confirm it through Adobe’s inspection tools. This tool cannot reach that server-side record.

There is no visible Firefly watermark to remove

Firefly adds no visible watermark of its own, so this tool has no mark to erase. If a visible label appears on an image, it came from a partner model, a platform or an editor, and it lives in the pixels rather than the metadata. A metadata strip will not remove it.

Partner-model pixels may carry their own signals

Firefly can route prompts to partner models whose outputs include pixel-level watermarks, such as a SynthID signal from Google models. A metadata strip leaves those signals untouched. Check the source model before assuming a clean metadata pass means a clean file.

Signed history, once gone, stays gone

Removal is one-way. Keep an untouched copy of the original if you may ever need the provenance chain for licensing, archiving or platform verification. The credential cannot be rebuilt from the stripped file.

Absence of credentials proves nothing

A Firefly image without Content Credentials may have been stripped, screenshotted, re-encoded or simply exported without the record. A validator cannot tell a deliberately stripped file from an innocent re-export. Removing the credential also erases the evidence that removal happened.

Personal EXIF and GPS stay in the file

This page removes the AI provenance record, not the privacy layer. Genuine camera EXIF, timestamps and GPS coordinates are preserved by default. To clear those fields, use the Remove Metadata page, which runs a separate personal-metadata pass.

Still-image formats only

The strip covers JPG, PNG, WebP, BMP, HEIC and AVIF still images. TIFF and raw camera formats are not supported. This page does not process Firefly video or audio output.

A clean file is not a clean conscience

Stripping provenance from work you own is generally legitimate. Presenting stripped files as unedited originals, yours or anyone else’s, can breach platform policies or the law. This tool edits metadata; it does not settle the legal questions around how you use the result.

Identity and official documents are not supported

This tool is not for passports, identity cards, driver licenses, visas, certificates, statements, or other official documents, whether the document is real, generated by AI, or put together from a template. Editing one of these can be document fraud, and we close accounts that try. Use the tool on other images you generated or have the right to edit.

FAQ

Frequently asked questions

Common questions about removing Content Credentials from Firefly images, from what the record holds to what a strip cannot reach.

Explore more tools

C2PA Remover

Inspect the Content Credentials inside any image, then strip the signed record in the same run.

Open tool

AI Metadata Remover

Clear C2PA, IPTC, XMP and generator fields from images that did not come from Firefly.

Open tool

Remove Metadata

Strip EXIF, GPS, device details and editing history when privacy is the reason for cleaning a photo.

Open tool

Bing Image Creator Metadata Remover

The Microsoft side of the same job: C2PA and IPTC records in Bing Image Creator, Designer and Copilot images.

Open tool

Image Metadata Viewer

Inspect the credential and field list inside a Firefly export before you strip anything.

Open tool

All tools

Every remover and detector on one page, grouped by what each one cleans or checks.

Open tool

Strip the Firefly credential, keep the pixels

The strip removes the signed C2PA record from your file and leaves the image at its original dimensions. Adobe’s cloud copy stays where it is, and the page says so plainly.