Install ComfyUI Custom Nodes Without Breaking ComfyUI
Install ComfyUI custom nodes with Manager or manual Git clone, avoid dependency drift, and fix red nodes, import failures, or Manager node-list errors safely.
Tested Environment
- OS: Windows 10 / 11
- Launcher: Wonderful Launcher v1.x
- ComfyUI: Portable / Managed install
- Python: 3.11+
- CUDA / Torch: CUDA 12.x / Torch 2.x
- Last tested: 2026-05-19
Use this page as the install hub for normal custom-node installs. Custom nodes are community plugins that add functionality — and one of the fastest ways to break a working environment, because each node may bring new Python packages, binary dependencies, version conflicts, or imports that only fail after restart.
If your environment already broke
If you already installed custom nodes and ComfyUI stopped working, go to Installed Custom Nodes and Broke ComfyUI? Recover Without Reinstalling.
Which custom node problem do you have?
| Goal or symptom | Stay here? | Where to go |
|---|---|---|
| Install a common custom node | Yes | Use ComfyUI Manager below |
| Install a node from GitHub manually | Yes | Manual Git clone below |
| Fix red nodes in an imported workflow | Usually no | Workflow missing nodes |
Plugin folder exists but startup says IMPORT FAILED | No | Plugin import failed |
| Startup says a custom node is missing a Python package | No | Custom node requirements missing |
Manager says failed to get custom node list | No | Failed custom node list guide |
| Installing one node broke the whole environment | No | Broken custom node recovery |
| Git clone fails or Git is not found | Yes | See "If Git clone fails" below |
Installing custom nodes
Method 1: ComfyUI Manager (recommended)
ComfyUI Manager is the official package-management layer. On current Desktop builds it is included. On recent portable/manual installs it is built into core but may need its dependencies installed and the manager flag enabled.
Desktop users: Manager ships enabled by default. Restart and look for the Manager button in the toolbar.
Recent portable users — from the portable package root:
.\python_embeded\python.exe -m pip install -r .\ComfyUI\manager_requirements.txt
.\python_embeded\python.exe -s .\ComfyUI\main.py --windows-standalone-build --enable-managerRecent manual-install users — activate the launch venv:
python -m pip install -r manager_requirements.txt
python main.py --enable-managerLegacy fallback — if your build still expects the older plugin-style install, use the legacy clone method documented by the ComfyUI Manager team:
cd ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Manager.git comfyui-managerOnce available, use the Manager button to browse, install, and update nodes, and to install missing nodes from imported workflows.
Method 2: Manual Git clone
- Open a terminal in
ComfyUI/custom_nodes/. - Clone the node repository:
cd ComfyUI/custom_nodes
git clone https://github.com/[author]/[node-name].git- Install dependencies only if the node has a
requirements.txt, using the same Python that starts ComfyUI:
| Install type | Safer dependency command |
|---|---|
| Official GitHub Windows portable package | From the portable package root: .\python_embeded\python.exe -s -m pip install -r .\ComfyUI\custom_nodes\[node-name]\requirements.txt |
| Manual Git + venv install | Activate the venv, then run python -m pip install -r custom_nodes/[node-name]/requirements.txt |
| ComfyUI Desktop or managed launcher | Use the app's environment/terminal tools. Do not assume python_embeded exists. |
- Restart ComfyUI.
Do not blindly run requirements on every node
The highest-risk step is pip install -r requirements.txt. Before running it, check whether the plugin is about to change Torch, numpy, opencv-python, pillow, or other core packages.
If Git clone fails
A clone failure means the plugin files were not downloaded — installing Python packages will not fix that.
| Clone symptom | Likely blocker | What to do first |
|---|---|---|
git is not recognized | Git is missing or this terminal cannot see it | Install Git, reopen the terminal/launcher, retry |
| Git is installed but the app still cannot clone | Stale PATH in the app process | Fully restart the app after installing Git |
| SSL, timeout, reset, proxy, or GitHub errors | Network, DNS, proxy, antivirus, or GitHub access | Test the repo URL in a browser and retry on a known-good network |
| Repository URL is malformed or wrong project | Node name mistaken for a repo URL | Find the plugin's official repository first |
| Folder exists but is empty or corrupt | A previous clone stopped halfway | Back up or remove the broken folder, then clone again |
After a successful clone, restart ComfyUI before judging the workflow. If the folder exists but startup shows IMPORT FAILED, switch to plugin import repair.
Method 3: Copy files
Some simple nodes are a single .py file — copy it into custom_nodes/ and restart:
ComfyUI/
+-- custom_nodes/
+-- my_node.pyFixing red nodes
A red node means ComfyUI cannot find a backend node class the workflow needs. That can mean "plugin not installed" or "plugin folder exists but failed to import." The chain: the workflow asks for a node class → a plugin must register it at startup → the plugin registers only if its Python imports succeed → those imports may depend on packages, native wheels, CUDA, or PyTorch.
With Manager: click Manager → Install Missing Custom Nodes, then restart.
Without Manager: read the red node name, search GitHub, install via git clone, restart, and check the startup log for IMPORT FAILED.
Updating custom nodes
With Manager: Manager → Update All.
Manually:
cd ComfyUI/custom_nodes/[node-name]
git pull
python -m pip install -r requirements.txt # only if this is the Python that starts ComfyUIFor the official Windows portable package, run dependency installs from the portable package root with .\python_embeded\python.exe -s -m pip ..., then restart.
Install with less risk
- Install one node or node family at a time.
- Restart ComfyUI after each change.
- Check the startup log for
IMPORT FAILED. - Avoid stacking multiple
requirements.txtinstalls without testing. - Stop as soon as you see dependency drift.
Troubleshooting
| Problem | Solution |
|---|---|
| Red nodes after importing a workflow | Install missing nodes via Manager or manually |
| Node installed but not showing up | Restart ComfyUI; check the console for import errors |
ModuleNotFoundError on startup | The plugin imported a package not in ComfyUI's Python. Install it in the exact environment that starts ComfyUI, or use the plugin's documented wheel. |
| Node conflicts / crashes | Some nodes are incompatible. Disable by renaming the folder (add .disabled). See Dependency Conflicts |
| Manager cannot load the custom node list | Check GitHub/raw GitHub access, Manager cache, and proxy rules. See Failed to Get Custom Node List |
| Missing nodes fixed but model files still missing | Move to model placement or missing-model repair — separate steps |
FAQ
What is the safest way to install ComfyUI custom nodes?
Use ComfyUI Manager when available. For manual installs, clone into ComfyUI/custom_nodes/, install only that node's requirements in the same Python that starts ComfyUI, and restart before testing.
Why did installing a custom node break ComfyUI?
The node may have changed shared packages such as Torch, NumPy, OpenCV, Pillow, Transformers, or Diffusers. Read the first IMPORT FAILED or traceback before running more package commands.
What should I do if Manager cannot get the custom node list?
That is usually a Manager registry, network, cache, or GitHub access problem. Use Failed to Get Custom Node List.
Related Guides
- ComfyUI Failed to Get Custom Node List
- Installed Custom Nodes and Broke ComfyUI
- How to Fix ComfyUI Plugin Import Failed Errors
- ComfyUI Dependency Conflicts
- Plugin Management
- Troubleshooting Decision Tree
Source References
Start free with Wonderful Launcher if this affects your real ComfyUI environment. It keeps launcher-native repair, task logs, and runtime checks in one place; credits are only for image generation and metered tools.
Download Wonderful LauncherSee credit packagesDid this fix your issue?
Your answer helps prioritize verified ComfyUI repairs.