Skip to content
checkaifree

Local image workflow

ComfyUI workflow inspection: get the JSON, read nodes and list references

Start with what you actually received: an original PNG, a UI workflow JSON, an API prompt or a document whose shape is unknown. Extract and inspect the saved data, preserve the original, and keep resource and compatibility questions explicit before deciding what to do elsewhere.

18 October 2026 · Check AI Free

Choose the first tool from the input's role

Choose the first tool from the input's role
What you haveFirst actionKeep or check
An original PNG that may contain a graphRead its text in ComfyUI workflow from imageSeparate workflow and prompt occurrences; exact downloaded JSON and read status
A saved UI workflow JSONOpen it in the direct JSON viewerRecognized version, nodes, widgets, links and original numeric tokens
An API prompt JSONOpen the named node/input representation directlyclass_type, named inputs and stored reference arrays; no fabricated UI layout
Unrelated or malformed JSONKeep unknown shape or syntax failure visibleObtain an intact supported export; no workflow success is inferred
A model/dependency questionReview known literal references and unresolved entriesNode/field/source, fixed adapter/catalog scope and provider questions

Three reproducible representation scenes

These are source-defined, project-authored JSON fixtures with fictional prompts, model strings and custom-node names. They are not three independent generated images or an accuracy benchmark. The UI and API samples serve separate shape exercises; their similar node labels do not certify a conversion or runtime equivalence.

Three reproducible representation scenes
SceneObserved/expected resultDecision
S-H04-UI · workflow.jsonworkflow-0.4; 4 nodes, 2 links; exact large seed; one literal checkpoint and one unknown-node entryRead UI widgets/links, keep the unresolved type and original JSON.
S-H04-API · api-prompt.jsonapi-prompt; 4 nodes, 3 links; named inputs; exact large seedRetain the API role; resource literals do not establish installed files.
S-H04-UNRELATED · unknown.jsonValid JSON with unrecognized shape; no workflow successAsk for a supported export rather than inventing a graph or treating parseability as safety.

Carry one actual document through an inspection

  1. Step 1

    Preserve the original and record its role

    If you start with a PNG, extract each stored JSON field separately. If you start with JSON, keep whether it was exported as UI or API when that is known. A filename or .json extension alone does not establish format or provenance.

  2. Step 2

    Read nodes and locate a connection

    Use the recognized shape, search/filter the node list, inspect stored inputs/widgets and choose a connection endpoint to locate a node. Exact source text and number tokens remain available. A static browse does not execute nodes or establish that every runtime type matches.

  3. Step 3

    Review literal references and unknown scope

    List known loader strings with node IDs and fields. Retain connected values and unsupported custom nodes as unresolved. The fixed catalog contains 65 base types from one official nodes.py revision; frontend-only nodes, extras and later/custom implementations are outside it.

  4. Step 4

    Download only the material you intend to share

    Download original JSON for private preservation or the reference list for a scoped resource/type handoff. Review prompts, paths, notes and literal filenames before posting. The reference list is not a redaction operation, an installed-model inventory or a runnable package.

Use absent and damaged controls without inventing a recipe

empty.json is a supported UI workflow with zero nodes, distinct from unknown.json's unrelated shape. Try malformed JSON fails at incomplete syntax. A PNG without text provides no workflow; prompt-only.png has a small API prompt but no UI workflow field. These controls describe the available stored data, not a recovered generation history.

Direct JSON input is bounded to 5 MiB and 1000 nodes, with connection, depth and value limits. PNG fields have tighter text/decompression limits. A readable document, matching node catalog name or known model string does not establish authenticity, safe execution or installed compatibility. The site does not fetch stored URLs, scan your folders, install extensions or run a graph.

For an official interoperability example, extract the SDXL PNG's 24-node UI graph and 11-node API prompt. Their raw strings match independent Pillow extraction, while Note and PrimitiveNode in the UI graph remain outside the limited base catalog. That known example demonstrates why catalog scope must accompany an unknown label.

Continue from reading to a specific saved-data result

Continue from reading to a specific saved-data result
What you need nextUseKeep the boundary
Which types and versions should I ask about?Viewer node-type inventory and reference-list exportA fixed base catalog is not a scan of installed plugins.
What changed between two revisions?Compare two saved graphsSame-format typed IDs align entries; renumbered nodes stay unmatched.
Where is a known structural problem?Static checker and Select source locationErrors, warnings and unsupported checks differ; checked does not mean runnable.
What can I send with a support question?Previewed support reportAliases and documented omissions produce a separate diagnostic document.
What remains in the PNG I will share?Selected PNG text deletion and re-readingReport omissions never delete the source fields; retained Author/Software remain visible.

Use the same three representation scenes with the new checks

The original UI/API/unrelated scenes still answer which representation was received. They are reading fixtures, not full runnable graphs: a viewer recognizing their shape does not imply the static checker will accept every required saved-node field. Use saved-valid.json for the complete one-node saved-structure control, and saved-broken.json to reproduce and repair two explicit errors.

For private-fields.json, keep one unknown-type warning and one unresolved custom implementation in the handoff. Compare diff-before.json and diff-after.json for exact stored-value changes, then use the key-reordered and renumbered controls to test what the comparer does and does not align. Preserve input roles rather than counting these related fixtures as independent generated pictures.

Keep shared reports separate from source files

The default support report replaces IDs and unknown type names with aliases and omits prompt/path/note values. Its preview and JSON/Markdown downloads contain the same reviewed report. Changing optional content requires regenerating the preview; the original JSON remains unchanged.

If the shared artifact is a PNG, selected-field deletion is a separate operation. The private-workflow.png exercise removes parameters, workflow and prompt from a new copy while retaining Author, Software and original IDAT bytes. Neither that partial edit nor a default diagnostic report establishes anonymity or certifies imported code.

Sources and reproducible inputs

Continue with your file