LogoWonderful Launcher
  • Product
  • Pricing
  • Solutions
  • Docs
  • Blog
  • Get Help
  • Download

Nodes Show Red After Importing a ComfyUI Workflow

Needs verification

Fix ComfyUI nodes that turn red after importing or loading a workflow — caused by missing custom nodes, version differences, or import failures.

Community Knowledge

This page is based on common ComfyUI troubleshooting patterns and has not been fully tested across all environments. Back up your environment before changing packages.

If you import a ComfyUI workflow from a file, image metadata, or a shared link and some nodes appear red, those node types are not available in your current ComfyUI session.

This is different from nodes that were working and suddenly turned red. This guide covers the specific case where nodes are red immediately after importing a workflow that was created elsewhere.

Fast answer

  1. Note the names of all red nodes
  2. Use ComfyUI Manager > Install Missing Custom Nodes
  3. Install all suggested node packs
  4. Restart ComfyUI and reload the workflow

What you see

After loading a workflow (from a .json file, from an image's embedded workflow, or from a shared URL):

  • Some nodes appear as red rectangles
  • A popup lists "node types not found"
  • The workflow cannot be queued — ComfyUI shows an error
  • Other nodes in the workflow appear normal

Why it happens specifically after import

When you import a workflow from another user or another machine, the workflow file contains references to node types by name. If your ComfyUI does not have those node types registered, they show as red.

Common scenarios:

  • The workflow author used custom nodes you do not have: This is the most common case. Their ComfyUI had custom node packs installed that yours does not
  • The workflow was made with a newer ComfyUI version: Some built-in nodes were added in recent versions
  • Custom nodes are installed but failed to load: The node pack exists in your custom_nodes/ folder but has an import error
  • The node pack was renamed: The author's node pack registers different class names than what the workflow expects (due to version differences)

Step-by-step fix

Step 1: List all red node types

Click each red node to see its type name, or check the popup that appeared when loading the workflow. Common examples:

IPAdapterApply
ControlNetApplyAdvanced
LoadFluxControlNet
KSamplerSelect

Step 2: Check if the nodes are built-in or custom

Some nodes that look custom are actually built-in to ComfyUI. If a red node has a simple, generic name (like KSampler or CLIPTextEncode), try updating ComfyUI first:

cd ComfyUI
git pull

Do not run pip install -r requirements.txt blindly.

  1. Confirm which Python environment is active (where python or which python)
  2. Inspect requirements.txt — check if it pins torch, numpy, or opencv versions
  3. Install only the missing package when possible: pip install <package-name>
  4. Run pip check after installation to verify no conflicts were introduced

Step 3: Use ComfyUI Manager to install missing nodes

If you have ComfyUI Manager:

  1. Click Manager in the ComfyUI menu bar
  2. Click Install Missing Custom Nodes
  3. Manager will attempt to match red node names to known custom node packs
  4. Install all suggested packs
  5. Restart ComfyUI

Step 4: If Manager cannot find a match

Some custom nodes are not in Manager's registry. Try:

  1. Search GitHub for "NodeTypeName" comfyui (use the exact node type name from the red node)
  2. Ask the workflow author which custom nodes they used
  3. Check if the workflow page or post mentions required node packs

Step 5: If nodes are installed but still red

Check the startup log for IMPORT FAILED messages:

.\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build

If you see import failures, fix the dependency errors. Common fixes:

.\python_embeded\python.exe -s -m pip install -r ComfyUI\custom_nodes\<node-name>\requirements.txt

Step 6: Reload the workflow

After installing all missing nodes and restarting ComfyUI:

  1. Open the workflow file again
  2. All previously red nodes should now show with their normal appearance
  3. Test the workflow by queuing a prompt

What if only some nodes are fixable

If you cannot find one or two node types but the rest of the workflow works:

  • Check if the red node can be replaced with a built-in alternative
  • Check if another custom node pack provides equivalent functionality
  • The workflow may still partially work — you can disconnect the red nodes and use the remaining parts

When not to run pip install blindly

  • Do not install every custom node pack suggested online without checking if it is the right one
  • Each custom node pack adds dependencies that may conflict with others
  • If Manager suggests multiple options for the same node type, check which one the workflow author actually used
  • Installing too many node packs increases startup time and conflict risk

How Wonderful Launcher can help

Wonderful Launcher helps analyze imported workflows and identify which custom nodes are needed. It assists with installation and dependency management, helping reduce the conflicts that often arise from installing multiple node packs at once.

Download Wonderful Launcher — it's free and makes workflow sharing painless.

Related errors

  • Workflow Missing Nodes
  • Red Nodes in ComfyUI Workflow
  • ComfyUI Plugin Import Failed
  • Custom Node Requirements Not Installed
  • Install Custom Nodes

Source References

  • ComfyUI GitHub
  • ComfyUI Documentation
  • ComfyUI Manager GitHub

You can fix it manually, or download Wonderful Launcher for Windows to diagnose plugin errors, missing dependencies, and broken ComfyUI environments without reinstalling.

Download free for Windows

Did this fix your issue?

Your answer helps prioritize verified ComfyUI repairs.

Table of Contents

What you see
Why it happens specifically after import
Step-by-step fix
Step 1: List all red node types
Step 2: Check if the nodes are built-in or custom
Step 3: Use ComfyUI Manager to install missing nodes
Step 4: If Manager cannot find a match
Step 5: If nodes are installed but still red
Step 6: Reload the workflow
What if only some nodes are fixable
When not to run pip install blindly
How Wonderful Launcher can help
Related errors
Source References