Skip to content
GenVidKit

ComfyUI Missing Nodes: How to Install Them and Why They Stay Red

Updated 2026-10-10

What the ComfyUI missing nodes warning means, how to install packs with Manager or by hand, and why nodes stay red: import errors, Python, settings.

Quick answer

ComfyUI missing nodes are node types a workflow uses that your ComfyUI does not have. ComfyUI draws each one in red and will not run the graph until every red node is installed or replaced. A missing model file is a different problem: it shows as an empty loader dropdown, not a red node.

Fix it in this order:

  1. Update ComfyUI if the workflow is newer than your install. Recent frontends say so directly: Some nodes require a newer version of ComfyUI. Those are built-in nodes, and no node pack provides them.
  2. Install the named pack through ComfyUI-Manager. Current ComfyUI lists it under Missing Node Packs with an Install All button. The legacy Manager menu calls it Install Missing Custom Nodes. Then restart.
  3. If there is no Manager, turn it on. It is built into ComfyUI but off by default in the Windows portable build and in manual installs. Install manager_requirements.txt with the Python that runs ComfyUI, then start with --enable-manager.
  4. If a node is still red after a restart, read the startup log. (IMPORT FAILED) next to a pack means its files are on disk but its Python code did not load, almost always because of a missing or conflicting dependency.

We read ComfyUI 0.39.0 (released 2026-10-05), the frontend 1.55.14 it pins, ComfyUI-Manager's READMEs and source, and docs.comfy.org on 2026-10-10. The interface text below is copied from the frontend's English locale file for that version.

What the warning says

Missing-node text depends on your frontend version. In 1.55.14, which ComfyUI 0.39.0 ships:

WhereText
WhereNotice when the workflow opensTextSome nodes are missing and need to be installed, with View details
WhereToastTextMissing node: followed by the node type, or Missing nodes for several
WhereBreadcrumb warningTextWorkflow contains unsupported nodes (highlighted red).
WhereRight-side Issues tabTextA Missing Node Packs card with Install All, then Apply Changes once a pack is on disk
WherePack not in the registryTextUnresolved Missing Nodes, which says the nodes could not be found in the registry
WhereBuilt-in node from a newer ComfyUITextSome nodes require a newer version of ComfyUI (current: …), with a list headed Core nodes from version …

Older frontends, 1.30.0 for example, opened a dialog titled Some Nodes Are Missing that began When loading the graph, the following node types were not found. It also warned that a lower installed version could cause the same message. If that is the dialog you see, your frontend is old; see the last row of the table further down.

Fix 1: install from the panel or from Manager

With Manager enabled, the current route is:

  1. Open the workflow and choose View details on the notice, or open the Issues tab.
  2. Under Missing Node Packs, choose Install All, or install the packs one at a time.
  3. Choose Apply Changes. The frontend shows it when a pack is installed on disk but ComfyUI has not restarted yet.
  4. Reload the workflow and check that the red nodes are gone.

In the Manager window itself, the Missing Nodes filter shows the same list. The legacy Manager interface, which you get with --enable-manager-legacy-ui, has an Install Missing Custom Nodes button in its menu.

The new Manager installs only from the Comfy Registry. ComfyUI's documentation says the new interface has no install-from-git option, for security and stability. A pack that is not in the registry lands under Unresolved Missing Nodes, and you install it by hand, as in Fix 3.

Install one pack at a time when you can, and restart between them. Our ComfyUI download page gives the same advice: when a node turns red after an install, the pack you added last is the first suspect.

Fix 2: turn Manager on

ComfyUI-Manager is now a Python package that ComfyUI core enables with a flag. ComfyUI 0.39.0's manager_requirements.txt pins comfyui_manager==4.2.2.

InstallIs Manager on?What to do
InstallComfy DesktopIs Manager on?Yes. Desktop installs it and starts ComfyUI with --enable-managerWhat to doNothing. Its security level is set per install, in the Manage panel's Startup Args tab
InstallWindows portableIs Manager on?No. run_nvidia_gpu.bat does not pass the flagWhat to doInstall the requirements with python_embeded, then add --enable-manager to the launch line
InstallManual install (venv)Is Manager on?NoWhat to doActivate the venv, install the requirements, start with --enable-manager
InstallManager cloned into custom_nodesIs Manager on?Yes, as the older custom-node versionWhat to doWorks, but ComfyUI's docs say this version cannot switch to the new interface

From ComfyUI's Manager installation page, for the portable build, run from the ComfyUI_windows_portable folder:

.\python_embeded\python.exe -m pip install -r ComfyUI\manager_requirements.txt
.\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build --enable-manager

For a manual install, with its virtual environment active, from the ComfyUI folder:

pip install -r manager_requirements.txt
python main.py --enable-manager

If you add the flag before the package is installed, ComfyUI prints the pip command it needs and starts without Manager. Updating ComfyUI may leave the Manager package at its old version, so ComfyUI's docs say to run the requirements install again after an update.

Fix 3: install a pack by hand

For a pack the registry does not have, or a specific revision, ComfyUI's documentation gives this route:

cd ComfyUI/custom_nodes
git clone <repository URL>

Then install the pack's dependencies into the Python that runs ComfyUI. On the Windows portable build, from ComfyUI_windows_portable:

python_embeded\python.exe -m pip install -r ComfyUI\custom_nodes\<pack folder>\requirements.txt

On a manual install, with its venv active, run pip install -r requirements.txt inside the pack's folder. Then restart ComfyUI, refresh the browser, and check the startup log.

Two things go wrong here more than anywhere else:

  • The wrong Python. A bare pip on a portable install usually installs into a system Python that ComfyUI never uses. The pack then fails to import, and the node stays red.
  • A requirements file that replaces PyTorch. A pack that lists torch can pull a CPU-only build from PyPI over your CUDA build. ComfyUI then fails with Torch not compiled with CUDA enabled; our page on that error covers the fix and how to stop it happening again. The new Manager shows a Node Pack Issues Detected! warning for packs whose required package versions differ from your setup.

ComfyUI's README says Python 3.13 is very well supported and suggests trying 3.12 if a custom node's dependencies fail on 3.13. The current portable build ships Python 3.13.

Why nodes stay red after you install them

What you seeCauseFix
What you see(IMPORT FAILED) next to the pack under Import times for custom nodes: in the startup logCauseThe pack's code raised an error on import, usually a missing packageFixScroll up to the line starting Cannot import; its last part names the error. Install that package with ComfyUI's Python
What you seeNothing in the log about the packCauseComfyUI was not restarted. It only loads custom nodes at startupFixRestart, or use Apply Changes, then reload the browser tab
What you seeThe pack installed, still red, pip reported successCauseDependencies went into a different PythonFixReinstall them with python_embeded\python.exe -m pip or inside the venv
What you seeSkipping … due to disable_all_custom_nodes and whitelist_custom_nodesCauseComfyUI was started with --disable-all-custom-nodesFixRemove the flag, or name the pack with --whitelist-custom-nodes
What you seeThe pack folder name ends in .disabledCauseComfyUI skips any entry in custom_nodes whose name ends that wayFixEnable the pack in Manager
What you seeSwap Nodes or Replaceable in the Issues panelCauseThe node was renamed or merged into anotherFixUse Replace Selected. Save a copy first: the frontend warns that it changes the workflow permanently
What you seeSome nodes require a newer version of ComfyUICauseThe workflow uses built-in nodes your version does not haveFixUpdate ComfyUI. Do not install a third-party pack to stand in for a built-in node
What you seeIMPORT FAILED: followed by a node file name, under a warning about comfy_extras/ nodesCauseComfyUI's own nodes lost a dependency after an updateFixOn portable, run update\update_comfyui.bat; otherwise pip install -r requirements.txt in the ComfyUI folder
What you seeInstalled comfyui-frontend-package version … is lower than the recommended version …CauseThe code was updated but the pinned frontend package was notFixSame as above: reinstall ComfyUI's requirements.txt
What you seePlease upgrade ComfyUI-Manager to version 4.2.1 or higher.CauseThe frontend is newer than the installed Manager packageFixReinstall manager_requirements.txt, or update the Desktop app

Renames are not rare in core either. ComfyUI 0.39.0 registers replacements for eight old built-in names, among them SDV_img2vid_Conditioning, a typo now replaced by SVD_img2vid_Conditioning, and Load3DAnimation, merged into Load3D. Custom node authors can register the same kind of replacement for their own packs.

ComfyUI's README also documents --front-end-version Comfy-Org/ComfyUI_frontend@latest, which downloads the newest daily frontend from GitHub at startup. It needs internet access and is meant for testing. For a missing-node problem, reinstalling the pinned frontend from requirements.txt is the safer fix.

When Manager refuses to install

Manager has its own security settings. They live in config.ini, and the startup log prints that file's path. From Manager 4.0.3b4 on, the default location is ComfyUI/user/__manager/config.ini; older versions used ComfyUI/user/default/ComfyUI-Manager/config.ini.

  • security_level takes strong, normal, normal- or weak. Manager's source falls back to normal when it is not set. At normal, on a ComfyUI that listens only on your own machine, installing registry packs is allowed.
  • strong blocks node pack installs, even from the registry.
  • --listen on a network address changes the rules. Manager treats the server as non-local and refuses more, including Git and nightly versions of registry packs at normal.
  • Installing from a Git URL is no longer controlled by security_level. Manager's README says it needs allow_git_url_install = true in the [default] section. The setting defaults to off, and Manager still refuses Git installs when ComfyUI listens on a network address. Restart after changing it.

In Comfy Desktop the same choice appears as Manager Security Level, with four options: Strict, Standard (recommended), Relaxed and Permissive. ComfyUI's docs do not say which config.ini value each one sets.

If you never opened ComfyUI to your network, leave these alone. A refusal on a local install usually means security_level was set to strong, or you tried a Git URL.

Where the official sources disagree

  1. How to allow Git installs. ComfyUI's Manager troubleshooting page still says to set security_level = weak. Manager's own README says that no longer has any effect on Git URL installs and that you must set allow_git_url_install = true. Follow the README.
  2. Which Manager to install. The hint in the frontend's Issues panel suggests pip install -U --pre comfyui-manager, which takes the newest release, pre-releases included; PyPI listed 4.3 on 2026-10-10. ComfyUI's docs and README install manager_requirements.txt, which pins the version ComfyUI was tested with, 4.2.2 for 0.39.0. We would use the pinned file.
  3. Which branch is Manager. The Comfy-Org/ComfyUI-Manager repository's default branch is the older custom-node version, 3.42, and its README still says to clone it into custom_nodes. The manager-v4 branch is the pip package, version 4.3, and its README says not to clone into custom_nodes. ComfyUI's README links the manager-v4 branch.

What nobody has published

  • Which node packs work with which ComfyUI version. There is no compatibility list. ComfyUI's troubleshooting guide names updates without matching custom-node updates as a common cause of breakage.
  • What to do with an unknown pack. When the registry cannot match a node to a pack, the panel says Unknown pack and you are left to search for the node's name yourself.
  • The Desktop security labels. As above, their mapping to config.ini values is not documented.

Where this fits on this site

  • Our ComfyUI troubleshooting page matches an error to its first check, for MiniMax H3. Missing custom nodes are one entry there; this page goes further.
  • Our workflows page explains that its official MiniMax H3 templates use only built-in nodes, and what to do when they show red nodes anyway.
  • Pages for workflows that do need packs: Wan 2.2 Animate names three, and Wan 2.2 GGUF needs ComfyUI-GGUF.
  • To rule custom nodes out of any other fault, start once with --disable-all-custom-nodes, as on our black video output page.

GenVidKit is an independent guide. It is not affiliated with Comfy Org, ltdrdata (ComfyUI-Manager's author) or the authors of any node pack named here.

Sources

All read on 2026-10-10.