Remove FLUX Image Metadata

Three ways to run FLUX, three different files

FLUX is a family of models, and the same prompt produces very different files depending on how it was run.

• Black Forest Labs' API — output carries cryptographically signed C2PA metadata declaring that FLUX produced it.
• Open weights run locally — no C2PA from Black Forest Labs. The reference code for FLUX.2's open models includes an example pixel-layer watermark, and ComfyUI saves your prompt and the full workflow into the PNG.
• Apps and hosts built on FLUX — each one decides what to keep or add, so the file is the only reliable answer.

Black Forest Labs' terms on API output

Black Forest Labs' developer terms (August 2026) prohibit removing, disabling, altering or obscuring Content Credentials on output, and representing output as free of provenance metadata or as human-generated.

If your file carries a credential signed by Black Forest Labs, it came through the API and those terms apply, so leave it in place. The checker shows the signer before you remove anything.

Local runs: your prompt is in the file

A PNG saved by ComfyUI contains two text chunks: the prompt as executed and the full node graph — prompts, seeds, model and LoRA file names and every setting. Sharing the PNG shares the recipe, and often details of your machine's folder structure.

That is your own file from your own setup, and removing it is ordinary privacy work. The chunks are deleted and the image data is copied across byte for byte, so the picture is identical.

What removal does not touch

A pixel-layer watermark, like the one in FLUX.2's reference code, is part of the image and survives metadata removal. Classifiers that judge the picture are unaffected too.