How do I ensure the output is truly 4K and 10-bit?

In ByteDance2ReferenceNode, set resolution to 3840x2160. In SaveVideo, select a 10‑bit-capable encoder and pixel format (e.g., HEVC Main10 with yuv420p10le or ProRes via prores_ks) and verify your FFmpeg build supports them. If 10‑bit isn’t available, the node will export 8‑bit.

How can I preserve more fine detail from the reference image?

Use a sharp, high-resolution source image, keep motion/strength settings moderate, and reduce any aggressive denoising if exposed. Lock a seed for consistency and try a few nearby seeds to find a motion field that keeps textures stable.

How do I change the video duration and frame rate?

Duration is frame_count ÷ FPS. Increase frame_count for longer clips, adjust FPS for smoother or more cinematic motion (e.g., 24 or 30). Make sure SaveVideo matches your intended FPS.

What if I run out of GPU memory at 4K?

Try lowering the frame batch size (if exposed by your build), reducing motion complexity, or temporarily testing at a lower resolution. Once settings are dialed in, switch back to 3840x2160 for the final pass.

Seedance2.0 4K: Reference to Video

This ComfyUI tutorial shows how to turn a single still image into a native 4K video using Seedance 2.0’s reference-to-video method. The workflow is intentionally minimal: LoadImage brings in your reference frame, ByteDance2ReferenceNode (the Seedance 2.0 reference model) synthesizes temporally consistent motion while preserving the look of the source, and SaveVideo encodes the generated frames into a 4K file. The result is a reference-faithful clip with clean, fine detail that’s suitable for editorial finishing and downstream color work.

Technically, the ByteDance2ReferenceNode conditions its generative video on the appearance of the input image and drives motion from learned priors, with user-adjustable parameters like output resolution, frame count, frame rate, seed, and motion/strength controls (names may vary by build). Set the node to 3840x2160 to produce true UHD frames, choose a frame count and FPS for duration, and keep a fixed seed for repeatability. SaveVideo then assembles the frames; when configured with a 10‑bit-capable encoder and pixel format, it exports in 10‑bit color, which helps maintain subtle gradients and grading latitude. If a 10‑bit encoder or pixel format isn’t available, the node will export in standard 8‑bit.

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.

6645006a0cb7.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