NS WaveSpeed Wan 2.5 Image to Video

Image-to-video is the community's favorite way to use Wan - anchoring the first frame to a real image solves the consistency problems that text-to-video keeps stumbling on. NSWaveSpeedWan25ImageToVideo from symbiotica-ai/comfyui-nodes is that workflow pointed at Wan 2.5, the hosted-only model: your still goes in as a URL, and you get a video_url back, with the two extras that make this node more than a one-trick wrapper - a real 1080p resolution menu and audio-conditioned generation.

How it works

image (a URL string from ComfyUI's Upload Image node) plus a motion prompt goes to WaveSpeed's Wan 2.5 i2v endpoint. resolution offers 480p, 720p, and 1080p - the 1080p rung is exactly what separates 2.5 from the pack's 2.2 i2v node, which stops at 720p. duration is 5 or 10 seconds, and there's a negative_prompt worth filling ("no flicker, no morphing"). enable_prompt_expansion (off by default) enriches your prompt before rendering.

The audio input is the sleeper: give it a URL to a wav/mp3 (3–30 seconds, ≤15MB) and the video is conditioned on the audio - the motion follows the sound. That's a real capability, not a novelty. enable_sync_mode defaults off - submit, poll every second, block until done, Cancel honored.

The inputs that matter

• image - the still to animate, as a URL.
• prompt - the motion and characteristics.
• resolution - 480p, 720p, or 1080p.
• audio (optional) - a URL that conditions the video on sound.
• duration - 5 or 10 seconds.
• client - the WAVESPEED_AI_API_CLIENT socket from the NS WaveSpeed Client node.

Output: video_url (STRING) - preview in a browser or feed a download-from-URL node.

Install and keys

# ComfyUI Manager: search "Symbiotica", or:
cd ComfyUI/custom_nodes
git clone https://github.com/symbiotica-ai/comfyui-nodes.git symbiotica
pip install -r symbiotica/requirements.txt

Restart, add the NS WaveSpeed Client node with your wavespeed.ai key (widget, Settings → Symbiotica, or WAVESPEED_API_KEY), wire client in. No model files.

Common issues

The audio URL has to be fetchable and in spec. 3–30 seconds, ≤15MB, wav/mp3. If a render fails and you've wired audio, suspect the URL first - an unreachable or oversized file is the classic culprit.

1080p i2v is a hosted-only privilege. Wan 2.5 has no weights, so this node isn't competing with a local option - it's the only option at this resolution. If that stings, local Wan 2.2 i2v remains free after your GPU, just capped at 720p in practice (wan-video.md).

Billing and moderation are the standing deal. Per-call pricing, minutes per render, your still leaving the machine (external-api-nodes.md). And "API_KEY is empty" still means the NS WaveSpeed Client node isn't wired in.