How many references should I start with?

Begin with a small, curated set: 3–6 strong images for identity/style, 1–2 motion clips, and a single clean audio track. Add more only if you need additional cues. Too many overlapping references can cause conflicts and visual jitter.

How do I keep the character consistent throughout the clip?

Use clear, front-facing images with consistent lighting and aspect ratio, place your best identity shots early in the list, and increase the image-reference influence in ByteDance2ReferenceNode. Avoid mixing drastically different hairstyles, angles, or outfits unless you intend to change appearance.

My audio drifts or lip-sync looks off. What can I do?

Use a single, clean vocal track without heavy reverb or background music for best lip-sync. Ensure your target duration and FPS match your audio plan; if the audio is longer than the selected duration, trim it to fit. Re-queue with a fixed seed after adjustments for consistent comparisons.

What affects performance and render time?

Resolution, frame rate, duration, and the number of references all increase compute and memory use. For faster previews, lower resolution and FPS, shorten duration, and limit references. When satisfied with motion and sync, scale up quality for the final render.

Seedance 2.5: Reference to Video

Seedance 2.5: Reference to Video is a multimodal ComfyUI workflow that turns your curated references into a single, coherent video clip with synchronized sound. You can feed up to 20 still images for character identity and visual style, plus up to 6 video clips to guide motion, and up to 6 audio clips to drive rhythm and lip-sync. The core of the pipeline is the ByteDance2ReferenceNode, which fuses these inputs to generate a 4–30 second sequence of frames and an aligned audio track. LoadImage nodes bring your still references into the graph, and SaveVideo encodes the generated frames (and accompanying audio from the generator) into a final video file.

API

Use this workflow from code

Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.

cd0c4f9f61a4.json

Fetching workflow JSON…

Run it from TypeScript or Python with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

// Install (beta)
npm i @comfyorg/sdk

// Run this workflow (TypeScript)
import { Comfy } from "@comfyorg/sdk";

const client = new Comfy({ apiKey: "comfyui-..." });
const wf = await client.workflows.fromFile("workflow_api.json");
const job = await client.run(wf);
await job.getOutputs("<output-node-id>")[0].toFile("output.png");

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API).

Comfy Cloud API access requires a plan with an API key.

SDK docs Get an API key

FAQ

Frequently Asked Questions