Two node paths, one model
Choose the right SeedVR2 ComfyUI node
There are two SeedVR2 ComfyUI node paths and mixing them up is the most common install error. ComfyUI 0.28.0 ships native SeedVR2 support through core template nodes. A separate NumZ community custom node adds a v2.5 layout with GGUF, BlockSwap, and batch controls. Use the native path unless your workflow names a feature only the community node provides.
This is a SeedVR2.net node explainer based on the public ComfyUI SeedVR2 template and the NumZ community repository. Neither path is an official ByteDance product for local installs; the hosted tool is a separate SeedVR2.net service.
The hosted path needs no nodes
If node installation is the obstacle, upload a short lawful source and read the credit preflight. You can still install the local node later once a finished file is no longer blocked.
First eligible 5-second 720p Standard run: free
Verify your email to use your first video run without credits or a card. A failed run does not use the trial; longer clips and other settings show their exact credit cost before submission.
Browser upload limit: 500 MB. For larger files, paste a publicly accessible HTTPS URL. Each job supports videos up to 10 minutes.
Quick scene presets
Presets pick a model for a common scenario. You can still switch models manually below.
Upscaled preview
Compare the enhanced output before exporting the final file.
Upload a clip, paste a direct video URL, or load the sample. No example video is downloaded until you ask for it.
Tip: keep your original FPS and avoid pre-scaling. The upscaler handles cadence better than most NLE plugins.
Test before processing the full video
Upscaling cannot recreate detail removed by heavy messaging compression. Test the hardest 5–10-second segment first; a higher-priced model is not automatically a better fit.
Two node paths compared
The native path is maintained inside ComfyUI core. The community path is a separate package. Knowing which one your workflow actually references saves most install pain.
- Native core
- ComfyUI 0.28.0+
- Community node
- NumZ v2.5
- Install route
- ComfyUI Manager
- After install
- Restart + read log
SeedVR2 template nodes shipped with core; no extra package.
ComfyUI-SeedVR2_VideoUpscaler custom node with GGUF, BlockSwap, batch.
Install custom nodes through Manager or clone into custom_nodes, then restart.
Resolve the first terminal error before importing a workflow.
The native template is the shortest path
ComfyUI 0.28.0 or newer includes a SeedVR2 template in its Template Library. It uses core nodes, points to the Comfy-Org 3B INT8 diffusion model and shared VAE, and is the shortest current install path. An old v2.5 custom-node graph should not be your first test.
If a search result tells you to install a custom node before you have even opened the template, it is probably outdated. Open the Template Library first and confirm the native workflow does not already cover your use case.
When the community node earns its place
The NumZ ComfyUI-SeedVR2_VideoUpscaler node exists for workflows that name specific controls: GGUF quantized models, BlockSwap, attention backend, or batch settings beyond the core template. It is useful and it is also extra software with its own version and dependency risk.
Install it only when a known workflow explicitly depends on it. Label it clearly as community software in your notes, because it is not an official ByteDance release and its behavior can change between versions.
Install a custom node without breaking ComfyUI
Confirm a clean base ComfyUI can queue and save before adding anything. Install through ComfyUI Manager or clone the repository into the custom_nodes directory, then restart and read the terminal. Missing-node errors after this usually mean the workflow references a different package or an older version.
Install one package group at a time and restart after each change. Installing several nodes at once turns a one-line dependency error into a mystery.
- Verify base ComfyUI queues and saves first.
- Install one node package, restart, read the log.
- Use the hosted tool when dependency repair blocks delivery.
Read missing-node errors literally
A missing node means the workflow references a node type this ComfyUI build cannot load. That is either an outdated ComfyUI or a missing community package. A model-not-found error is different: the node loaded, but the model filename or directory is wrong.
These are setup errors, not proof the source cannot be upscaled. Solve the first real error in the terminal before you change memory settings or blame the model.
Node control versus a finished file
Choose the local node when you need graph control, private media, or a repeatable offline pipeline. Choose the browser when you need one deliverable and node installation is the obstacle.
The two paths answer different questions. A hosted test proves whether SeedVR2 helps your file; the local node lets you own the graph after that proof. Do not install a node just because a search result said SeedVR2 lives there.
Node guidance limits
Node names, versions, and install routes change frequently. This page reflects public documentation at review time; always confirm against current ComfyUI and the community repository before installing on a production machine.
- ComfyUI and community node versions move independently and can break workflows.
- Neither path is an official ByteDance local installer.
- No node makes an 8GB card officially supported; hardware limits remain.
SeedVR2 ComfyUI node questions
Do I need a custom node to run SeedVR2 in ComfyUI?
Not on a current install. ComfyUI 0.28.0 or newer ships a native SeedVR2 template using core nodes. Install the NumZ community node only when a workflow explicitly needs GGUF, BlockSwap, attention, or batch controls beyond that template.
Why does my workflow say a node is missing?
The workflow references a node type your ComfyUI build cannot load. Update ComfyUI and reopen the native template first; if the workflow names a community feature, install the matching custom node, restart, and read the terminal.
Should I install through ComfyUI Manager?
ComfyUI Manager is the usual route for custom nodes, but confirm a clean base install works first. Install one package at a time, restart after each, and resolve the first terminal error before importing a workflow.
My tutorial shows an old v2.5 node layout. Is it still right?
Old tutorials can still be useful for concepts, but the current native template uses core nodes. Treat the v2.5 community node as a separate path and verify any screenshot against current documentation.