Local file tool
ComfyUI workflow validator
Run bounded static shape and reference checks against a stated format version.
18 October 2026 · Check AI Free
Local ComfyUI static checks
Check saved graph structure
Check workflow 0.4 or 1.0 JSON, or an API prompt with its own reference rules. Errors, warnings and unsupported checks are listed separately. The JSON stays in this browser; nodes, scripts, URLs and extensions never run.
Project-authored fixtures; no model is loaded. Limits: 1000 nodes, 10000 connections, depth 64, 150000 JSON values and 5000 diagnostics. Exact number tokens are retained. Integer IDs use integer JSON tokens; alternate number encodings are outside this subset.
What these checks cover
Implemented structural subset of the fixed official 0.4/1.0 workflow schemas. API checks the prompt envelope, node class_type/inputs and conventional [string node ID, integer output slot] references separately; the official envelope schema leaves prompt internals open. No full JSON Schema conformance, custom-node definitions, model availability, socket data types, execution, subgraphs or installation checks.
Workflow checks cover required root/node fields, position/size pairs, port lists, duplicate typed IDs, stored endpoints, port ranges when available, and port/link agreement. Named slots are reported as unchecked. API arrays are checked against the conventional two-item reference form; other list semantics are unsupported.
Fixed official docs revision 7ca6a40804ef: workflow 0.4, workflow 1.0, API envelope. Passing these checks does not establish full schema compliance, installed models/plugins or successful execution.
Supported files and output
Bounded static checks against pinned official workflow 0.4/1.0 format references, with API prompt checked separately. Reports implemented shape, ID, port and reference checks as error/warning/unsupported with source offsets. This is a stated subset, not full schema certification or proof that a workflow can run. Nodes, models, extensions and URLs are never executed, installed or fetched.
Read the result with its coverage
Stored fields can be edited, copied or removed. A successful read describes the selected file’s supported containers; missing fields cannot be recovered from its pixels. A damaged or unsupported container has its own result. Review private values before copying or sharing a report.
These file operations run locally. The separate image checker can send file-header data and a reduced image copy for a model reading. Read the method and limitations when that is the task you need.
Continue the task
- ComfyUI workflow inspection: get the JSON, read nodes and list references — Choose a local path from a PNG or JSON file to stored nodes, connections, literal model references and scoped compatibility questions. Follow UI, API and unrelated-JSON scenes.
- Find and correct a known ComfyUI saved-structure error — Locate duplicate IDs and a dangling connection in a defined workflow, edit the local text, recheck it, and distinguish errors, warnings, unsupported checks and runtime questions.
- Build a concrete ComfyUI pre-import checklist from a saved file — Record source and format, static diagnostic scope, model literals, node-version questions and report privacy before deciding what to import elsewhere.
- EXIF viewer and exports — Inspect the stored camera, location and caption fields.
- Remove selected metadata — Create a verified static-image copy with supported categories removed.
- Choose another file operation — Browse available tools by task.