Popular ComfyUI Custom Node Packs: Easy Use, Layer Style, rgthree, and VideoHelperSuite
Install and troubleshoot popular ComfyUI custom node packs safely: Easy Use, Layer Style, rgthree, VideoHelperSuite, and missing-node import failures.
If you searched for comfyui-easy-use, ComfyUI Layer Style, rgthree comfyui, or ComfyUI-VideoHelperSuite, you are probably trying to install a workflow's missing node pack or fix a custom node that no longer imports.
These are community custom node packs, not core ComfyUI features. Install them through ComfyUI Manager when possible, restart ComfyUI, and then check the startup log before installing more packages.
Why this page exists
Full Wonderful Launcher telemetry through June 29, 2026 shows repeated install and dependency repair attempts for Easy Use, Layer Style, rgthree, and VideoHelperSuite. Third-party keyword research also shows search demand for the same names. This page uses those signals for prioritization, not as an official popularity ranking.
Fast routing
| What you searched or saw | Best next step |
|---|---|
| You just want to install one of these packs | Start with Install ComfyUI Custom Nodes |
| A workflow opens with red nodes | Use ComfyUI Workflow Missing Nodes |
The folder exists but startup says IMPORT FAILED | Use ComfyUI Plugin Import Failed |
| Startup names a missing Python package | Use Custom Node Requirements Missing |
| The node loads but model files are missing | Use Where to Put Safetensors in ComfyUI |
Packs users keep running into
| Custom node pack | Common reason users need it | Safer install note |
|---|---|---|
| ComfyUI-Easy-Use | Efficiency nodes, workflow shortcuts, loaders, and integrations used by shared workflows | Use the official Easy Use repository or Manager entry. Do not install random packages just because an easy node is red. |
| ComfyUI Layer Style | Layer, mask, image compositing, and Photoshop-like workflow nodes | Treat missing Layer Style nodes as a custom-node pack issue first; model or mask errors can appear later. |
| rgthree-comfy | Workflow organization and quality-of-life nodes used in many shared graphs | If rgthree nodes stay red after install, check whether the pack imported during startup. |
| ComfyUI-VideoHelperSuite | Video loading, image sequence, preview, and save helpers | Video workflows often reveal a second layer of missing models, codecs, or package requirements after the node pack loads. |
What the telemetry says
The June 29, 2026 full-history export covered 175,136 launcher telemetry events from 699 installs. The custom-node package pivots showed these repeated install or dependency repair signals:
| Pack | Full-history affected installs | Last 30 days affected installs | Keyword signal |
|---|---|---|---|
| ComfyUI Layer Style | 15 dependency repair installs, 12 clone result installs | 4 dependency, 3 clone | comfyui layer style |
| ComfyUI-Easy-Use | 10 dependency repair installs, 8 clone result installs | 4 dependency, 3 clone | comfyui-easy-use |
| rgthree-comfy | 11 dependency repair installs, 10 clone result installs | 3 dependency, 3 clone | rgthree comfyui |
| ComfyUI-VideoHelperSuite | 8 dependency repair installs, 8 clone result installs | 3 dependency, 3 clone | comfyui-videohelpersuite |
This does not mean these packs are broken by default. It means real users repeatedly reach the point where missing nodes, dependency repair, or clone results need clearer routing.
Install from Manager first
For most users, the safest path is:
- Open ComfyUI.
- Open Manager.
- Search the pack name.
- Install one pack.
- Restart ComfyUI.
- Check the startup log for
IMPORT FAILED.
If the workflow still has red nodes after restart, do not install every dependency you can find. Use the workflow's missing-node popup and the startup log to identify the next layer.
Manual clone only from the official repo
Manual clone is valid when Manager cannot fetch the list, the pack is not mapped, or you are repairing a specific repository. Clone into ComfyUI/custom_nodes/, then install only that pack's documented requirements in the same Python that starts ComfyUI.
For the official Windows portable package, the dependency command usually needs the embedded Python from the portable root:
.\python_embeded\python.exe -s -m pip install -r .\ComfyUI\custom_nodes\<pack-folder>\requirements.txtFor a manual venv install, activate the venv first and use:
python -m pip install -r custom_nodes/<pack-folder>/requirements.txtIf it still fails after install
Use the first failing layer, not the visible symptom, to decide the next page.
| After install you see | What it means | Next guide |
|---|---|---|
| Red nodes are still visible | The backend node class did not register | Workflow Missing Nodes |
Startup log says IMPORT FAILED | The folder exists, but Python could not import it | Plugin Import Failed |
ModuleNotFoundError: No module named ... | A package is missing in ComfyUI's Python | No Module Named in ComfyUI |
pip check reports conflicts | A package install changed shared dependencies | ComfyUI Dependency Conflicts |
| The node is loaded but a model dropdown is empty | Node repair is done; model placement is next | Where to Put Safetensors |
What not to do
- Do not run
pip install -r requirements.txtfor several custom node packs at once. - Do not treat a failed Git clone as a Python package problem.
- Do not assume a folder under
custom_nodes/means the pack loaded. - Do not reinstall ComfyUI before checking the first
IMPORT FAILEDtraceback. - Do not download unofficial mirrors when the official repository is reachable.
When Wonderful Launcher helps
Wonderful Launcher is useful when the repair is no longer a single install:
- several packs are missing in one workflow
- Manager cannot map the node pack
- the pack installed but did not import
- dependency repair reveals another missing module
- the node pack loads, but model assets are still missing
The launcher helps keep those stages separate so you do not mistake a partial repair for a working workflow.
Related guides
- Install ComfyUI Custom Nodes
- ComfyUI Workflow Missing Nodes
- ComfyUI Plugin Import Failed
- Custom Node Requirements Missing
- Where to Put Safetensors in ComfyUI
Source References
Start free with Wonderful Launcher if this affects your real ComfyUI environment. If the repair is blocking work, Agent Access is the paid guided path; credits are for image generation and metered tools.
Download Wonderful LauncherSee Agent AccessDid this fix your issue?
Your answer helps prioritize verified ComfyUI repairs.
Model Path Not Detected
Fix ComfyUI model path not detected, extra_model_paths.yaml not loading models, path format errors, and missing model dropdowns step by step.
ComfyUI "clean library entry point is missing" Fix
Fix the ComfyUI clean library entry point is missing error by checking workflow compatibility, frontend package drift, corrupted workflow JSON, and missing custom nodes.