ComfyUI Metadata Viewer
Use ComfyUI Metadata Viewer to read PNG prompts, seeds and sampler settings locally. Inspect saved nodes and download workflow JSON without uploading files.
One PNG up to 50 MB · JSON / decoded metadata up to 8 MB
PNG and JSON only. Summaries cover standard nodes; raw graphs remain available. Files are not executed.
Recover the saved recipe from a ComfyUI PNG
Inspect what the file actually contains. Missing fields are not reconstructed from image pixels.
Sampler-specific settings
Read seed, steps, CFG, sampler, scheduler and denoise from supported KSampler nodes. Each sampler keeps its node ID, so a refinement pass is not confused with the initial generation.
Prompts with a traceable source
Resolve positive and negative inputs that directly reference standard CLIPTextEncode nodes. Custom encoders, combined conditioning and runtime-generated text remain unresolved references; the original API nodes stay available for inspection.
Two distinct JSON exports
Download workflow.json for the saved editor graph and prompt-api.json for the execution graph when present. Listed checkpoint, LoRA and other loader inputs remain associated with their own nodes, not presented as a verified final model.
Start with the original output file
A screenshot or re-encoded copy may look identical while carrying different metadata.
Choose PNG or JSON
Drop one PNG, editor workflow JSON or API prompt JSON. PNG files may be up to 50 MB; JSON and the combined decoded prompt/workflow text are limited to 8 MB. Click Analyze metadata to begin.
Review every relevant branch
Check the sampler IDs, linked prompt text and loader nodes. A graph can contain unused loaders or several output branches. The summary does not certify which branch produced the visible image.
Export the graph you need
Save workflow.json to reopen the stored editor graph in ComfyUI. Keep prompt-api.json separately for API-oriented inspection. Before running either elsewhere, check required models, custom nodes and input assets.
Your prompts stay on your device
This viewer reads PNG text chunks and JSON locally. It does not run ComfyUI, execute nodes or send your images and prompts to an AI service.
- PNG tEXt, zTXt and iTXt entries named prompt or workflow are decoded, including supported compressed text. Size limits bound decoded metadata as well as the input file.
- The first version accepts PNG and JSON only. WebP, video, model files and a visual node canvas are not supported here. Use the general PNG viewer for unrelated image metadata.
- Exported JSON can reveal private prompts, model names and embedded paths. Review it before sharing. This page does not remove metadata or verify authorship.
Method and primary references
The summary intentionally covers standard sampler and loader nodes. Unrecognized structures remain visible in the raw graph. Compare the saved fields with these official format references:
Understand what can be recovered
Keep execution data, editor layout and missing information separate.
The prompt field describes executable API nodes and their inputs. The workflow field describes the editor graph, including layout information. A file can contain either or both. This tool keeps them separate and only offers a download for a recognized graph that is present.
Saving metadata may have been disabled, the save node may not have received it, or an editing service may have stripped it. Try the original PNG in your ComfyUI output folder. A screenshot cannot restore a missing graph, and this tool does not infer one from pixels.
The quick summary follows direct KSampler links to standard CLIPTextEncode text. If conditioning passes through custom nodes, multiple encoders or runtime logic, assigning one string could be misleading. Inspect the preserved prompt JSON for those connections instead.
Not by itself. The graph does not bundle model weights, custom node packages or input assets. Versions, runtime behavior and the available environment also matter. The export preserves the stored graph; it is not a promise of identical output.
Yes. The viewer recognizes editor JSON with a nodes array, API JSON with class_type and inputs for each node, and an object containing prompt or workflow. Editor-only JSON is preserved without guessing the meaning of positional widget values.
No. Metadata is editable and can be copied between files. A successful read only establishes that recognized data was present in the selected file. Conversely, missing ComfyUI fields do not establish that an image was made without AI.