EvoLink Seedance 2.5 Video Edit (Official)

Here's the node the whole EvoLink pack is designed around. The README's pitch is a pipeline: generate → edit → upscale, chained node to node, and EvoLink Seedance 2.5 Video Edit (Official) is the middle of that chain. It takes an existing video and a text instruction - "remove the background music, swap the subject for a shiba" - and returns an edited clip whose length follows the source. Closed ByteDance model, API-only, so this node is the entire access path.

What it is

• prompt (required) - the edit instruction, in plain language. The tooltip's example format: "Edit the video: 去掉背景音乐，主体换成柴犬." Chinese or English, both work.
• video_urls - the video(s) to edit, one URL per line, up to 10 (each 4–30 seconds). Marked required. This is where the chaining happens: paste an upstream node's result_urls straight in and the output of one render becomes the input of the next.
• quality - 480p / 720p / 1080p.
• generate_audio - on by default, free.
• audio_urls - optional reference audio, up to 10 entries, if you want to steer the new sound.
• image1–image2 - optional image references (up to 30 with the URL box) for subject or style anchors.

Outputs: video, task_id, status_info, result_urls (24-hour expiry), response_json. Connect the video output to a Save Video node - an edit that renders but never gets saved is just a bill.

Install and key

Shared EvoLink install. ComfyUI Manager → search EvoLink → install → full restart (close the console, not just the browser). Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/deeplearning-goethe/comfyui-evolink

Dependency is just requests; no models, no GPU. Key from evolink.ai/dashboard/keys (sk-), pasted once into api_key - saved locally, blank after, never in a shared workflow JSON.

How to actually chain it

The pattern that makes this pack sing: Seedance T2V → this node → an upscaler node, wiring result_urls between them. You generate a clip, edit it into what you actually wanted, and hand it on - no manual downloads, no file juggling, no imgbb. The result_urls are plain text with a 24-hour expiry, so chain within the session and the links stay alive.

Honest limits: the edit quality tracks the source clip, so editing a 720p draft gives you a 720p edit; edit the good render, not the test render. The 4–30 second per-clip window means long projects need to be chopped first. And it's metered like everything here - per-render cost, your clips and prompt leave the machine, failed and moderation-blocked tasks don't charge. This is the node that justifies the pack's existence; just don't feed it a draft you're going to re-generate anyway.