Skip to content
Delete Image Metadata

Remove ComfyUI Workflow Metadata

ComfyUI writes your whole node graph into the file — not just the prompt. That is the most detailed record any generator embeds.

  • .png
  • .jpg
  • .jpeg
  • .webp
Free
No account, no limit on files
0
Files uploaded — processing is local
4 formats
Lossless — pixels never re-encoded
Processed in your browser
Ready

How it works

  1. 1

    Load the PNG

    The workflow chunk is listed with its keyword and size.

  2. 2

    See how large it is

    Often tens of kilobytes — the whole graph, serialised.

  3. 3

    Remove and verify

    Chunks are dropped, pixel data is untouched, and the output is re-read.

The workflow chunk is your entire pipeline

Where Automatic1111 writes a single line of settings, ComfyUI serialises the complete node graph as JSON into the PNG's text chunks — usually under the keywords `workflow` and `prompt`. That JSON is not a summary. It is the graph: every node, every link between them, every widget value, and the names of every custom node and model you loaded.

On a complex pipeline that block runs to tens of kilobytes, and it is frequently the largest single piece of data in the file after the image itself. Drag such a PNG back into ComfyUI and the whole workflow reconstructs — which is the feature, and also precisely the exposure.

What that reveals in practice

The prompt is the least of it. A workflow graph typically also gives away:

  • Every checkpoint, LoRA, embedding and upscaler by filename — including private or unreleased models
  • The custom nodes you have installed, which fingerprints your setup fairly precisely
  • Sampler, scheduler, CFG, seed and step counts for each pass in a multi-stage graph
  • Local file paths in some node configurations, which can contain your username
  • The structure of a pipeline you may have spent a long time developing

Why saving as JPEG is the wrong fix

Exporting to JPEG does remove the chunks, because JPEG has no equivalent to PNG text. It also re-compresses every pixel, and generated images — with their smooth gradients and fine synthetic detail — show JPEG artefacts more readily than photographs do.

Removing the chunks directly avoids that entirely. PNG keeps its pixel data in separate IDAT chunks with their own checksums, so the text chunks can be dropped while the image data is copied through without being decompressed. The cleaned PNG decodes to bit-identical pixels.

Keep a copy before you clean

The workflow chunk is genuinely useful — it is how you reproduce or resume your own work. Clean the copy you publish, not the copy you keep. The tool never modifies your original file, so downloading the cleaned version leaves the original workflow intact on disk.

What this tool does

  • Removes workflow and prompt chunks along with EXIF and XMP in a single pass
  • Pixel data is bit-identical — IDAT chunks are never decompressed
  • Handles very large graphs without truncating the file

What it does not do

  • Removal is per file: individual nodes cannot be redacted from the graph
  • Does not affect any copy you have already shared
  • Does not change how a visual classifier reads the picture

Remove ComfyUI Workflow Metadata

ComfyUI writes your whole node graph into the file — not just the prompt. That is the most detailed record any generator embeds.

Open the tool

Reviewed and updated . Behaviour described on this page is covered by the project’s automated tests.

Frequently asked questions

What does ComfyUI store in a PNG?

The full node graph as JSON, usually under the keywords 'workflow' and 'prompt'. It includes every node, link, widget value, model filename and custom node in the pipeline — enough to reconstruct the workflow exactly.

How is this different from Automatic1111 metadata?

Automatic1111 writes one settings line: prompt, steps, sampler, seed, model. ComfyUI writes the entire graph, which is far larger and describes your whole setup rather than the final parameters.

Can someone rebuild my workflow from a published image?

Yes, if the chunks are intact — dragging the PNG into ComfyUI restores the graph. That is the intended feature and the reason to clean images before publishing them.

Does the workflow contain my file paths?

Some node configurations do store paths, which can include your username or directory structure. Load a file into the tool above to see what yours holds.

Will removing the chunks change the image?

No. PNG pixel data lives in separate chunks that are copied through without being decompressed, so the cleaned file decodes to exactly the same pixels.

Should I save as JPEG instead?

It removes the chunks but re-compresses the image, which is visible on generated art. Removing the chunks from the PNG keeps the file lossless.

Can I keep the workflow but remove everything else?

Not in this version — removal is per file. Keep your original as the working copy and publish the cleaned one.

Does this work on images from Forge or InvokeAI?

Yes. They use the same PNG text chunk mechanism, so their generation data is detected and removed the same way.