You have ComfyUI installed, you want to run Seedance 2.5 inside it, and every tutorial you open is a minefield. One video tells you to install a node that no longer exists. Another asks you to paste an API key into a random Discord bot. A third is actually a tutorial for Seedance 2.0 with the version number swapped in the thumbnail. After the third dead end you start wondering whether "Seedance 2.5 in ComfyUI" is even real.
It is real — but the confusion is also real, and it has a cause worth understanding: ByteDance does not ship an official ComfyUI integration. Seedance 2.5 is offered by ByteDance through CapCut, Dreamina, and the Volcano Engine/BytePlus platform and API, while everything that plugs Seedance into ComfyUI is a community or third-party custom node. That single fact explains every broken tutorial you have seen. This guide is built from the primary sources that do exist — the ComfyUI repository itself, the actual custom-node repos, and ByteDance's announcement — and it tells you exactly how to tell a real node from a trap.
Quick honesty note, standard for this model generation: Seedance 2.5 was previewed by ByteDance on June 23, 2026, with 30-second native generation, up to 50 multimodal references, and native 4K as announced specs. Community nodes are third-party software, not ByteDance products, and their names, versions, and API requirements change frequently — treat the GitHub README of whichever node you choose as the source of truth, and check it before you run anything.
How Seedance 2.5 Actually Gets Into ComfyUI
ComfyUI is an open-source, node-based interface where you build generation pipelines by connecting blocks. It is developed in the open, and adding a model to it means installing a custom node that wraps that model's API. For Seedance 2.5 there are currently three realistic routes, and picking the right one is the entire game:
| Route | What it is | Who maintains it | Best for |
|---|---|---|---|
| Volcano Ark API node | Custom node that calls ByteDance's own Volcano Ark (火山方舟) API — the same backend as Seedance's official release | Community repo, e.g. ComfyUI-Jimeng-API | You already have a Volcano Ark account and key |
| Third-party API node | Node that routes Seedance 2.5 through a hosted API provider (e.g. MuAPI) | Third-party provider repos | No ByteDance account yet, want one key for several models |
| Official surfaces, no ComfyUI | CapCut, Dreamina, or the Volcano Engine console directly | ByteDance | You wanted ComfyUI for the interface, not the pipeline |
The version check matters more than the route. Seedance 2.0 nodes have been around longer and are well documented; Seedance 2.5 support is newer and sits in a smaller set of repos. Before installing anything, open the node's GitHub page and look for "2.5" in the README or release notes. If a repo says Seedance but never mentions 2.5, it is a 2.0 node, and half of what it claims may not apply.
Step 1: Make Sure ComfyUI Is Installed and Updated
You cannot skip this step, and most tutorials assume you already did it. ComfyUI is installed from its official GitHub repository, and it matters that your install is current: newer custom nodes are written against newer ComfyUI versions, and an old install produces errors that look like node bugs but are actually version mismatches.
How to update depends on how you installed it — the portable build, pip install, or package manager each have their own update command, all documented in the official repo. If your ComfyUI can open at all and you have not updated it in months, update first. Then restart the server, and only then move to nodes.
Step 2: Install the Seedance Node via ComfyUI Manager or Git
There are two standard ways to install a custom node, and the first one is safer for beginners.
ComfyUI Manager (itself a custom node, installable from its own repository) lets you search and install other nodes from inside the UI. Search for the node name from the repo you chose, click install, and restart. The catch: Manager shows what the registry knows about — if the repo you picked is not in the registry, you need the manual route.
Manual git install is the fallback and works for every repo. In a terminal:
cd <your-comfyui-directory>/custom_nodes
git clone https://github.com/<owner>/<seedance-node-repo>.git
cd <seedance-node-repo>
pip install -r requirements.txtThen restart ComfyUI. After restart, the new node blocks should appear in the node list — usually under a folder named after the repo. If they do not appear, check the terminal output for an import error; it almost always means a missing Python dependency or a ComfyUI version mismatch, not a broken repo.
Step 3: Get the API Key the Node Expects
This is where people get burned, so read this carefully. The node is a wrapper; the actual video generation happens on the provider's servers, and the node needs an API key to authorize calls.
- For a Volcano Ark node: create the key in the Volcano Ark console. The key stays in the node's configuration (or its env file) on your machine.
- For a third-party API node: create the key on that provider's site, then follow the repo README for where it goes — some nodes read an env variable, some have a key field in the node UI.
Three rules that apply to both: never paste the key into a prompt or share it in a chat; never commit it to git (add the env file to .gitignore); and if a node asks you to put your key in a shared or hosted queue, stop — that is not how any legitimate node works. Your key is only ever read by your local ComfyUI instance and sent to the API provider it belongs to.
Step 4: Run Your First Text-to-Video Workflow
Once the node is installed and the key is configured, the fastest first test is a minimal text-to-video graph. The exact node names differ by repo, but the graph shape is the same everywhere:
- Text input node — your prompt, kept short: a subject, one action, a camera move, a tone.
- The Seedance node — prompt input wired in, model set to the 2.5 variant if the repo exposes one, plus duration/resolution options where available.
- Output node — usually a Save Video or preview node that writes the clip to
output/.
If the repo ships a ready-made workflow JSON (most do), download it and drag it onto the ComfyUI canvas — that auto-builds the whole graph, and you only need to fill the prompt and check the key config. Then generate.
Two settings worth knowing before your first run: keep resolution modest for tests (a short 720p clip generates far faster than 4K, and you are testing the pipeline, not the grade), and keep the prompt to one action — the same discipline that applies everywhere else in Seedance prompting, covered in detail in our prompt guide.
Step 5: Diagnose Failures Like a Node User
| Error you see | Most likely cause | Fix |
|---|---|---|
| 401 / authentication failed | Wrong or expired API key | Re-create the key in the provider console, re-enter it in the node config |
| Model not found / unknown model | The node is a 2.0-era build without 2.5 variants | Update the node repo (git pull), or check the README for the exact model id |
| Import error on restart | Missing Python dependency | Run pip install -r requirements.txt for that repo and restart |
| Node missing from the list | Install did not land or version mismatch | Re-check the path in custom_nodes/, update ComfyUI itself |
| Generation hangs forever | Key is fine but the provider queue is long | Check the provider's status page; retry at off-peak hours |
The pattern: most failures are configuration problems — key, model id, or version — not model problems. Fix those three before you suspect the node itself.
What Most ComfyUI Tutorials Don't Tell You
Three things this guide adds that the typical tutorial leaves out.
First, the official-versus-community boundary. ByteDance's own announcement covers CapCut, Dreamina, and the enterprise platform — there is no official ComfyUI integration, and no official ComfyUI documentation page exists. Any tutorial implying otherwise is selling you something. Second, key hygiene is a feature, not paranoia — the moment a node asks for your key in a hosted service, you are leaking it. Third, the 2.5 version check — the fastest way to filter the tutorial graveyard is to search the node repo for "2.5" before you install. That one habit would have saved you the three dead ends you hit before reading this.
And one honest alternative: if your goal was never the pipeline itself but just the ability to generate Seedance 2.5 video with control over prompts and references, the browser route skips all of the above. You can run text-to-video, image-to-video, and reference-to-video directly in Seedance 2.5 AI with no node install, no local setup, and no API key — the same model, with the workflow kept as a web form instead of a node graph. If you are here for the interface, that is a feature; if you are here for the model, it is the fastest path to first clip.
Frequently Asked Questions
Is there an official Seedance 2.5 ComfyUI node from ByteDance? No. ByteDance offers Seedance 2.5 through CapCut, Dreamina, and the Volcano Engine/BytePlus platform and API. All ComfyUI integration is community or third-party custom nodes, maintained in their own repositories.
Which ComfyUI node supports Seedance 2.5? Several community repos add Seedance 2.5 support, generally by wrapping the Volcano Ark API or a third-party hosted API. Check the repo's README for explicit "2.5" support before installing; a node that only mentions Seedance 2.0 will not handle 2.5 correctly.
Do I need a ByteDance account for a Seedance 2.5 ComfyUI node? For Volcano Ark-based nodes, yes — you need a Volcano Ark account and API key. For third-party API nodes, the key comes from that provider instead. Both are required for generation; neither is a ByteDance consumer account.
Is running Seedance 2.5 in ComfyUI free? Generation is billed by the API provider the node uses, with rates set by that provider. ComfyUI itself is open source and free. Check the provider's pricing page for current rates.
I installed the node and it is not in the list. What now?
Check the terminal for an import error, confirm the repo is in custom_nodes/, and make sure ComfyUI is recent. Most "node not found" cases are a missing dependency or an outdated ComfyUI install.
The Bottom Line
Seedance 2.5 in ComfyUI is real, but it is a community-built path with no official map. The way to walk it safely is to remember three checkpoints: pick a node repo that explicitly says 2.5, install it through Manager or a clean git clone into custom_nodes/, and treat the API key as the one thing that never leaves your machine. After that, a minimal text-to-video graph is the same three-node shape you already know.
And if the node graph was never the point — if you just want the model in your workflow — you can skip the whole setup and generate directly in Seedance 2.5 AI. Start with one short clip, check the output, and decide later whether the node route earns its setup time.
Sources
Seedance 2.5 specifications are preview claims from ByteDance's June 23, 2026 announcement. Community custom-node repos are third-party software maintained independently of ByteDance; their features, names, and requirements can change at any time — always verify against each repo's README before installing.
- ComfyUI official repository — the open-source node-based UI: install, update, and custom-node documentation.
- ComfyUI-Jimeng-API — community custom node calling the Volcano Ark API for ByteDance Seedream and Seedance models, including how the API key is configured.
- seedance2-comfyui — community custom nodes and workflows covering Seedance 2.0 and 2.5 via a third-party hosted API, with 2.5 support explicitly listed.
- TechTimes — ByteDance's Seedance 2.5 preview: 30-second native generation and the official rollout surfaces (CapCut, Dreamina, enterprise platform).
- GIGAZINE — June 23, 2026 announcement details: 50 multimodal references, native 4K, and availability timeline.
