Install a custom node in three stages: code, dependencies and registration

Downloading a repository is only one step. Identify the owning package, satisfy its dependencies and confirm that the running backend actually registers the required class.

Updated 2026-09-24Published revision: 4Source baseline: not recorded

Purpose and scope

Downloading a repository is only one step. Identify the owning package, satisfy its dependencies and confirm that the running backend actually registers the required class.

Source-supported context

Official guidance distinguishes Manager/manual installation and failed imports. Display title, technical class, Registry identifier and repository name may all differ. Source 1 Source 2

Before you start

1. Record the missing technical class and workflow source rather than relying on color or an edited title.

2. Verify the original repository, maintenance status and instructions before executing installer commands.

3. Check core, Python, Torch, model and external-tool requirements for that node.

Steps and checks

The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.

Step 1. Use the workflow author or a trusted Registry mapping to identify the package, retaining uncertainty when several candidates exist.

Step 2. Back up and install code into the correct instance. Choose Manager or a manual method without creating duplicate nested copies.

Step 3. Use the correct interpreter for declared requirements and inspect whether pip proposes replacing core dependencies such as Torch.

Step 4. Restart, inspect registration and /object_info, then test a minimal example and complete its model dependencies.

Completion check

The backend exposes the technical class and a minimal input executes. Manager's installed label alone is not enough.

Limitations and cautions

Custom nodes execute local code and may access files/network. Disabling one does not undo changes to shared Python packages.

Original sources

Install custom nodes — original record checked 2026-09-21.
ComfyUI custom node troubleshooting — original record checked 2026-09-21.

Localization prepared: 2026-09-22. The source-check dates above were inherited from the existing article; this translation does not claim they were all rechecked today. No GPU run, minimum-memory measurement or runtime guarantee is supplied.

Was this page helpful?

Anonymous. Only a yes/no counter is stored; no account, IP address or device details.

Sources & references

Localized from the existing Chinese research draft. Original source-check dates are retained; this translation is not new technical verification or a runtime test.

01Install custom nodesSource checked: 2026-09-21 02ComfyUI custom node troubleshootingSource checked: 2026-09-21