Kling VIDEO 3.0 Turbo

Read the positivePrompt tooltip on this one before you write anything, because it's the best feature in the whole node and it's buried in a tooltip. Kling 3.0 Turbo accepts a multi-shot template - shot <n>, <seconds>, <prompt>; repeated up to six times - where each shot gets its own prompt and duration, and the seconds add up to your total duration. That's a storyboard built into a prompt box. You can sketch a whole six-shot mini-sequence in one generation instead of running six separate queues and cutting them together.

The tradeoff is the name: Turbo is the speed tier, so it's also the one where you iterate fast and accept a little less polish. Same closed-model situation as every Kling node - it renders on Runware's cloud, no local GPU, pay per run - but the multi-shot prompt makes it uniquely useful for planning.

How it works

Node is standard pack fare: widgets become a request (klingai:[email protected], videoInference), the runware-sdk sends it over REST, and the returned MP4 comes back as a native VIDEO output. Where Turbo differs from the other Kling 3.0 nodes, beyond the prompt template:

• size - a dropdown with 720p and 1080p options in 16:9, 1:1, and 9:16, plus 720p (from input) and 1080p (from input). No width/height widgets here.
• duration - 3–15 seconds; your per-shot seconds must sum to it.
• negativePrompt - present, though ignored when guidance is disabled (CFG ≤ 1).
• frameImages - an IMAGE socket for conditioning.
• No advanced_json, no sound toggles. Turbo keeps the control surface deliberately small.

Keep the per-shot prompt under 512 characters and the shot count at six or fewer. The template format matters - shot 1, 2, close-up of a cat stretching; - so if a queue comes back with a validation error, check your punctuation before you blame the model.

The output

One video socket, type VIDEO, into Preview Video or Save Video. On older ComfyUI it degrades to a file path string; upgrading ComfyUI fixes that.

Installing it

Standard pack install, once for all nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/Runware/ComfyUI-Runware
pip install -r ComfyUI-Runware/requirements.txt

Restart, then set your key in ComfyUI Settings → Runware API key, via RUNWARE_API_KEY, or with runware auth login. Only the SDK, pillow, and soundfile install - nothing else to manage.

Where people get burned

The multi-shot template is easy to get subtly wrong - mismatched seconds that don't sum to duration, or a shot prompt running past 512 characters, and the request bounces. And since Turbo is the cheap tier, the temptation is to iterate until the sun comes up; the run info line prints the cost for a reason. If all you need is one clean shot, Pro or Standard might serve you better. If you need to pitch a sequence, Turbo's template is the trick.