Remove Flux image metadata

Flux models from Black Forest Labs (Flux Pro, Flux Dev, Flux Schnell) embed a C2PA Content Credentials manifest when generated through the BFL API or via Replicate's official deployment. Outputs from local installs (ComfyUI, Forge) usually carry only the PNG tEXt chunks with prompt and generation params. GhostMeta detects both signals — the JUMBF-encoded manifest and the freeform tEXt blocks — and strips them with one canvas re-encode. When you resell Flux renders on a stock or print-on-demand marketplace, the embedded seed and sampler settings let a competitor reproduce a near-identical image from the same prompt, eroding the exclusivity you are selling. GhostMeta neutralises that by wiping the chunk before the listing goes live, with the visible pixels untouched. Whether your Flux file arrives as a PNG (with a caBX chunk) or as a JPEG export (with the manifest in an APP11 segment), the same single canvas re-encode handles it client-side, with nothing uploaded.

FAQ

Does Flux Pro embed the same data as Flux Dev?

Both ship the C2PA manifest when run through BFL infrastructure. Local Flux Dev runs do not unless your wrapper explicitly attaches one.

What about Replicate-generated Flux images?

Replicate adds its own metadata layer on top of the BFL manifest. GhostMeta strips both as a single canvas re-encode.

Are LoRA names preserved in metadata?

If the wrapper writes the LoRA filename into the parameters tEXt chunk, yes. After GhostMeta the chunk is gone.

Flux files reach me as both PNG and JPEG — does GhostMeta handle the two formats the same way?

Yes. A PNG-exported Flux render stores its C2PA manifest in a caBX chunk and its prompt in tEXt/iTXt chunks; a JPEG export carries the manifest in an APP11 segment instead. GhostMeta decodes either container to canvas and re-encodes locally, so both end up with no metadata layer regardless of the source format.

My host wraps Flux (Fal, Together, a custom API) — will GhostMeta still find the metadata?

GhostMeta does not rely on knowing which host produced the file. It inspects the actual byte structure: it reads the JUMBF box that holds the C2PA manifest and lists every PNG tEXt/iTXt chunk present. Any provenance or parameter block a wrapper attached is surfaced and then dropped on re-encode, even if the host is one we have never seen.

Does the negative prompt get embedded too, not just the positive prompt?

On local Flux runs through ComfyUI or Forge the parameters tEXt chunk typically stores the full generation context, which can include the negative prompt, guidance scale and seed. GhostMeta removes the entire chunk, so the negative prompt leaves with everything else — it is not preserved separately.