Workflow Doc turns a ComfyUI workflow into a private, readable structural report. Drop in a workflow JSON file or Sweet Tea .tea package to see what the file appears to do, which components it contains, and which models or node packs Sweet Tea can identify without executing the workflow.
Workflow Doc is descriptive. It preserves unknowns and labels ambiguity instead of claiming that a static file is safe, correct, or ready to run.
Supported Files and Limits
Workflow Doc accepts:
- ComfyUI API-format workflow JSON;
- ComfyUI editor-format workflow JSON; and
- Sweet Tea
.teapackages containing a supported workflow.
JSON files can be up to 2 MB. .tea packages can be up to 25 MB. The page rejects an oversized file, malformed JSON, an invalid package, or a structure it cannot interpret instead of trying to repair or execute it.
Inspect a Workflow
- Open /workflow-doc.
- Drag a file onto the upload area or choose Choose workflow file.
- Wait for the browser-local parse and structural classification.
- Review the report's warnings, resource matches, inputs and outputs, and component groups.
- Copy or download the report before leaving if you need to keep it.
You can drop another file to replace the current report. The current MVP does not provide saved report history or a public report URL.
What the Report Shows
The exact sections depend on what the file contains. A report can include:
- an overall descriptive classification of the workflow;
- detected input and output modalities;
- static structural observations and parser warnings;
- a functional component breakdown;
- model references grouped by model role;
- ComfyUI core and custom node-class usage;
- identified or possible node-pack resources;
- canonical model information when an evidence-backed match exists; and
- a separate Ambiguous or unknown section for components Sweet Tea cannot identify defensibly.
Match labels describe identity evidence, not runtime readiness:
| State | Meaning |
|---|---|
| Identified | The available evidence supports one canonical resource match |
| Possible | One or more candidates exist, but the evidence does not support a single definitive match |
| Unknown | No defensible canonical match was found |
| Not checked / unavailable | Canonical matching did not complete; the browser-local structural report remains usable |
A matched model or node pack can still be the wrong version for your runtime, require files the report did not observe, or fail when executed. Validate the actual imported Pipe against the intended ComfyUI runtime in Studio.
Browser-Local Privacy Boundary
The raw workflow is parsed in your browser. Workflow Doc does not upload the raw JSON or .tea package. Prompt text, arbitrary literal values, absolute paths, local media filenames, credentials, and embedded metadata stay in the browser.
After local parsing, Workflow Doc automatically sends a bounded, sanitized inventory to Sweet Tea Resources for canonical matching. That inventory can include node-type signatures and path-free model references. It does not include the raw workflow or the local path and prompt data listed above.
If Resources matching is unavailable, the local report is not discarded. Workflow Doc marks enrichment as unavailable and leaves the structural findings visible.
Resources Identification
When canonical matching succeeds, identified and possible components can link to their Resources entries. Use those pages to inspect available source, version, provenance, artifact, requirement, guide, and related-workflow information.
Do not convert a possible match into a dependency decision by guesswork. Compare the workflow's exact identifier, source package, version, and any hash or manifest evidence. Leave an unresolved component unresolved until the file or upstream source provides stronger evidence.
Copying and Downloading the Report
Use Copy report to place the generated report on the clipboard. Use Download report to save it as workflow-doc-report.md.
The exported Markdown is a snapshot of the current interpretation. It is useful for review, support, or dependency research, but it is not a modified workflow package and cannot be imported as a Pipe.
What Workflow Doc Does Not Do
The current Workflow Doc does not:
- execute the workflow or contact your ComfyUI runtime;
- claim that the workflow is runnable, safe, or high quality;
- install or download models and custom nodes;
- prescribe fixes, repair the graph, or rewrite the uploaded file;
- save the raw workflow to your account;
- publish a public Workflow Doc or shareable analysis page;
- open or import the workflow directly in Studio; or
- replace Studio's Pipe import, dependency review, and runtime validation.
To continue with the workflow, import the original JSON or .tea package through Studio's supported path, review its generated interface and dependencies, and run a low-cost validation before relying on it. See Pipes & Workflows, Models, and Nodes.