INITIALISATION DU SYSTÈME...
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.
Node pipelines readily store the whole graph in the PNG: every node, every parameter, and the local file paths touched — sometimes a username or a client name. GhostMeta removes those chunks with a pixel-lossless re-encode, in your browser, and the file usually comes out lighter.
Flux is heavily used inside node-based pipelines. Those interfaces readily store the entire graph in the PNG metadata: every node, every parameter, every local file path the generation touched.
A file path is more revealing than a prompt. It often contains a system username, a project tree, sometimes a client name. That information leaves with the image without anyone thinking about it, because it shows up in no preview interface.
A PNG is re-encoded pixel-lossless: the resulting image is identical to the eye and to a comparator, only the metadata is gone. It is the format to prefer when fidelity matters.
The file usually comes out lighter, because a serialised workflow graph can weigh tens of kilobytes. Drop the PNG, read what it carries, download the clean copy.
Team workflows deserve particular care. A shared node graph often references paths from the machine that built it, so an image rendered by one person can expose another person's directory structure. Cleaning before the file leaves the team removes that, and it costs nothing once it becomes a habit.
On a commission, a file path written into the PNG can reveal another client's name, an internal directory tree or a confidential project title. That is the kind of leak nobody notices until the image has shipped.
So check before delivery rather than after. A read takes seconds and spares you having to explain why a name appears in a file that should never have carried it.
| Data | Risk | Removed |
|---|---|---|
| Local file paths | Username, directory tree, client name | Yes |
| Full node graph | Reproduction of the whole chain | Yes |
| Prompt and seed | Reproduction of the render | Yes |
| Model and LoRA names | What the setup contains | Yes |
| Image pixels | Unchanged | Not applicable |
Both ship the C2PA manifest when run through BFL infrastructure. Local Flux Dev runs do not unless your wrapper explicitly attaches one.
Replicate adds its own metadata layer on top of the BFL manifest. GhostMeta strips both as a single canvas re-encode.
If the wrapper writes the LoRA filename into the parameters tEXt chunk, yes. After GhostMeta the chunk is gone.
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.
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.
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.
Partner : M.E Expert Serrurier