Home / ComfyUI workflow checker

ComfyUI workflow checker

Drop a workflow file or ComfyUI image and see right away which custom nodes and models you need – before ComfyUI shows red boxes.

Drop a workflow (.json) or ComfyUI PNG here

or tap to choose.

Choose file

Step by step

  1. Drop a workflow file (.json) or a PNG straight from ComfyUI. The regular workflow format including subgraphs and the API format are both read.
  2. Read the summary at the top: it gives the number of nodes, how many custom node types come from how many packages, and how many models the workflow uses.
  3. Go through the “Custom nodes” list. Each package is shown with its node types. “open” leads to the registry or the GitHub project, “search on GitHub” runs a search for the node name.
  4. Install the packages, for example in ComfyUI-Manager under “Install Custom Nodes”, where you can find them by name.
  5. Get the files from the “Models” list. If the author stored a download link in the workflow, it is shown; otherwise you get search links to Hugging Face and Civitai. If a folder is listed, that's where the file belongs.
  6. Only then load the workflow in ComfyUI. That way you start with everything it needs.

What you can use it for

  • Check other people's workflows before loading: You got a workflow from a forum or community. Before opening it, you see how many extensions it requires and can decide whether it's worth it for you.
  • Prepare a new installation: Setting up ComfyUI on a new computer or a rented GPU server? The list works as a shopping list: all packages and model files at a glance.
  • Share your own workflows: Before you share a workflow, check which custom nodes and models recipients will need, and hand them the list along with it.
  • Clean up dependencies: Lots of packages installed and no idea which one is needed for what? Run your most important workflows through the tool to see which packages are actually in use.

What the tool shows

  • Custom nodes: all nodes that aren't part of ComfyUI itself, grouped by package. Newer workflows store which package a node comes from – then you get a direct link to the registry or GitHub.
  • Models: all checkpoints, LoRAs, VAEs etc. selected in the workflow, with search links. If the author stored a download link, it is shown.

So you know beforehand what to install instead of hunting for red nodes in ComfyUI. To see an image's prompt and settings, use the “Read prompt and workflow” tool.

Frequently asked questions

Is my workflow uploaded?

No. The file is analyzed in your browser.

Why do some nodes have no direct link?

Older workflows don't store which package a node comes from. Then you get a GitHub search for the node name.

What does “None – the workflow only uses built-in ComfyUI nodes” mean?

All nodes belong to ComfyUI itself. You only need the model files from the second list.

How does the tool know which nodes are built in?

It compares the node types with a list of ComfyUI's node names. Newer workflows also store which package each node comes from, and that is used as well.

Does the tool install the missing parts?

No. It only shows what is missing and gives you links to find it. Installing and downloading is up to you.

Why does the model search find nothing?

The search uses the file name from the workflow. If someone renamed their file, the name often no longer matches the original. Then the workflow's description or a question to its author helps.

My PNG is rejected. Why?

There is no workflow in the image, usually because it was sent via social media or a messenger. Use the original file or ask for the JSON file.

It says “No nodes found”. What now?

Then the file is not a ComfyUI workflow or has a different structure. Check that you really picked the exported workflow file and not, say, a settings file.