comfyui_vidu_api/图生视频

Image-to-video is the community's favorite way into video generation for a reason: anchoring the first frame to a real image solves most of the consistency problems that plague pure text-to-video. ViduImage2Video is exactly that - one IMAGE in, one clip out, with a prompt describing what should happen. If the first frame already shows your astronaut, Vidu doesn't have to invent her, just move her.

You'd reach for this node in two situations. First, the obvious one: you made a still you love locally - with SDXL, Flux, whatever - and you want it to move, but you don't want to rebuild it as video locally or retrain it for Wan. The image is your anchor; the node uploads it as PNG and Vidu animates forward from it. Second, and just as common: you want Vidu's quality specifically. Like every node in this pack, this one calls the closed Vidu API - there's no local model and no open weights, so this is the "model you can't run" case, not a shortcut around a GPU you already own.

How it works. The shared base class does all the heavy lifting: read the key from api.json, upload your image through Vidu's presigned upload flow (/tools/v2/files/uploads, a PUT, then a finish call that returns the image URI), submit a job to /ent/v2/img2video, poll every 5 seconds, download the resulting mp4, and hand it to ComfyUI as a VIDEO. The node blocks while the cloud renders - the queue sitting on this node for a minute or five is normal. Everything is logged with a [Vidu::ViduImage2Video] prefix in your console, which is where you go when something's wrong.

The inputs that matter. The profile dropdown (运行配置) is where this node is richest - five options: viduq1 - 5秒, vidu2.0 - 4秒, vidu2.0 - 8秒, vidu1.5 - 4秒, vidu1.5 - 8秒. That's model plus duration. There's no aspect-ratio dropdown here - the frame shape comes straight from your image, which is the whole point of I2V. Set 图像 (any IMAGE - a Load Image node, or a VAE-decoded latent), type a short motion description in 提示词, and leave 动态幅度 on 自动 if you can't be bothered - it maps to auto/small/medium/large on Vidu's side.

One thing the node enforces for you: each profile only accepts certain resolutions, and it validates this before calling the API. viduq1 - 5秒 demands 1080p; vidu2.0 - 8秒 and vidu1.5 - 8秒 demand 720p. Pick a mismatch and you'll get a refusal message instead of a wasted API call - annoying until you realize it's saving you money.

Outputs: video (VIDEO), 封面链接 (cover image URL string), and 任务ID (the API task id). When a run fails, the node doesn't raise - it returns the error text on 封面链接 and "error" as the task id, so an error string landing on an output socket is how this pack tells you it broke. Check the console logs for the details.

Install. Identical for all six nodes in this pack, and it's tiny:

cd ComfyUI/custom_nodes
git clone https://github.com/josephxie1/comfyui_vidu_api_node
# restart, then create api.json beside the nodes:
#   { "api_key": "vda_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }

Key from platform.vidu.cn; ComfyUI Manager search comfyui_vidu_api_node also works. No models to download - the only dependency is requests.

Where people get burned. Beyond the pack-wide gotchas (missing api.json kills every node, and you need a ComfyUI build new enough to have comfy_api), the cost is the thing to watch here. This is the node the billing complaints orbit: one r/comfyui user traced a Vidu i2v template that advertised $0.40 per 5-second 1080p clip but found their credits draining far faster than that, and ended up publicly warning people off the Vidu i2v API path until the accounting is transparent. Your mileage may vary - but if you're doing a batch, check platform.vidu.cn's balance after the first clip before you queue twenty more. And remember the image and prompt both leave your machine to a server with its own content moderation, so don't send Vidu anything you wouldn't send a cloud API.