Black Forest Labs · FLUX.2, FLUX 3

Remove Metadata from FLUX Images

What a FLUX image carries depends on how you ran it. Black Forest Labs' API adds signed C2PA Content Credentials. The FLUX.1 reference code writes your prompt into EXIF and adds an invisible watermark; the FLUX.2 command-line script writes a short EXIF tag; the diffusers pipeline adds nothing; ComfyUI saves its workflow. BlankAI removes every metadata layer. It cannot remove a pixel watermark.

Runs in your browser. Nothing is uploaded. Reviewed September 25, 2026

Check a FLUX image

Drop a FLUX output to see which of these layers your setup added.

Drop images here or click to choose

JPG, PNG, WebP, AVIF, HEIC · Up to 20 images · Nothing is uploaded

EXIFGPSXMPIPTCC2PAPNG text

What FLUX output carries, by setup

Layer	Present	Details	BlankAI
C2PA Content Credentials	Sometimes	Signed C2PA on FLUX.2 Pro, FLUX.2 klein and Kontext Pro API output. Black Forest Labs' terms forbid removing it.	Removed
EXIF / XMP / IPTC label	Sometimes	FLUX.1 reference code: Software “AI generated;txt2img;flux”, Make “Black Forest Labs”, the model name, and your prompt in ImageDescription. FLUX.2 script: Software “AI generated;flux2” and Make.	Removed
PNG workflow data	Sometimes	ComfyUI saves the prompt and full node graph in PNG text chunks.	Removed
Invisible watermark	Sometimes	A DWT-DCT watermark in the FLUX.1 reference code, on by default. Commented out in the FLUX.2 script. None in diffusers.	Not removed
Visible watermark	No	No visible mark.	Nothing to remove

API versus local generation

Through the API, Black Forest Labs signs output with C2PA, as a signatory to the EU Code of Practice would be expected to. Running open weights locally gives you control, but the reference scripts are not neutral: the FLUX.1 code writes your full prompt into the EXIF ImageDescription field by default, which is easy to overlook when you share a JPEG.

FLUX 3, announced on 23 July 2026 as a unified image, video and audio model, did not describe its provenance approach at launch. Check a real file to see what it contains.

About the DWT-DCT watermark

The FLUX.1 reference code and several Stable Diffusion scripts embed a small invisible watermark using the invisible-watermark library. BlankAI does not alter pixels and does not try to remove it.

What BlankAI removes, and what it does not

The same rules apply to every file, whatever made it. BlankAI cleans the metadata that travels with a file. It cannot reach anything that is part of the image itself.

Layer	Where it lives	What it holds	BlankAI
EXIF and GPS	File metadata	Camera or phone model, serial numbers, capture time and location coordinates.	Removed
XMP and IPTC	File metadata	Creator tool, edit history, captions, credits and the IPTC Digital Source Type AI label.	Removed
C2PA Content Credentials	Signed manifest inside the file	Who or what created the file and how it was edited, signed by the issuing app.	Removed
PNG text chunks	File metadata	Stable Diffusion prompts, seeds and model names, ComfyUI workflows.	Removed
Invisible watermarks	The pixels	SynthID (Google and OpenAI images), Meta's Content Seal, TikTok and ByteDance watermarks.	Not removed
Visible watermarks	The pixels	Logos, sparkle icons and corner badges drawn onto the image.	Not removed
AI classifiers	The platform	Models that judge an image by how it looks. File metadata plays no part.	Not affected

Questions

Does FLUX add a watermark?

The FLUX.1 reference code adds an invisible DWT-DCT watermark by default. The FLUX.2 script and the diffusers pipeline do not. API output is signed with C2PA.

Where is my FLUX prompt stored?

With the FLUX.1 reference code, in the EXIF ImageDescription field. With ComfyUI, in the PNG prompt and workflow chunks. BlankAI removes both.

Can I remove C2PA from FLUX API images?

Technically yes, but Black Forest Labs' terms forbid removing it from API output.