ComfyUI Workflow Library
3 structure-checked ComfyUI core-node workflows: UI graphs vs API prompts kept distinct, with real SHA-256, model revisions and import troubleshooting. No GPU this round; all entries remain drafts.Local static catalog · no workflow execution
Operations
Workflow library search
Filter the 3 bilingual entries by keyword, format and status; show id, UI/API format label, status, testedAt and model revision. Drafts are inspectable but excluded from the public catalog.
Workflow detail / verify / import steps
Inspect model source URLs + revisions, core nodes, real SHA-256, byte size, media type, dependencies and troubleshooting by id; verify mode checks pasted JSON text; import mode gives format-correct steps; preset mode checks the P16 allowlist.
Real examples and limits
This site is a static catalog and inspector only: it never runs ComfyUI, never executes library JSON, never accepts user-uploaded workflows and never allows public arbitrary-node execution. All 3 entries are draft (testedAt:null, empty testEvidence); no download button and no public index entry is rendered. A published entry requires a real verification record; a missing testedAt/testEvidence/model revision or a missing download file fails the build. P16 accepts only reviewed, registered presetIds.
FAQ
Can I generate images on this page?
No. There is no GPU, no ComfyUI service and no JSON execution. You get verifiable catalog metadata, import steps and checksums.
What is the difference between UI workflow JSON and API prompt JSON?
A UI JSON is a canvas graph with nodes[], links[], last_node_id and version 0.4 (Workflow -> Open). An API JSON is a map of numeric node ids to {class_type, inputs} with ["node-id", slot] links (POST /prompt). They are not interchangeable; each file is classified and validated separately.
Why is every entry a draft?
No GPU was available this round, so there is no real import/run record. A published workflow requires a non-null testedAt, non-empty testEvidence, at least one model with a revision and at least one example asset; the validator rejects any published entry that lacks them.
Where are the model weights?
Weights are not copied here. Each entry lists the source URL, revision and target directory; weight licences stay with their sources.
Can P16 point a presetId at arbitrary library JSON?
No. Only the 3 reviewed, registered presetIds are accepted. Cross-site flow is download -> navigate -> import; no file body, no private token and no uploaded workflow execution.