Skip to main content

Vidu Q3 Turbo is the fast tier of Vidu's Q3 line, turning an opening frame and a required prompt into 1 to 16 seconds of video. It outputs 540p or 720p with audio generated in the same pass, in the frame's shape.

From $0.042/s

Workbench

Input

Image to video
Required. Describe the movement, camera and sound only; do not re-describe the frame. at least 1 characters
1/1

Drop files or media links, paste, or browse · 1 file · Max 10 MB · JPG · PNG · WEBP · GIF

  • 1
1 / 1 files
Required. It fixes subject, look and output shape - export the still at the shape you want back. Keep its aspect ratio within 1:4 to 4:1.
Movement amplitude
AutoSmallMediumLarge
How much things in the frame move: `auto` (default) lets the model judge from the prompt; `small` keeps motion restrained, `medium` and `large` push it further. Pair `small` with portraits and products, `large` with action; the prompt still decides what moves and how. No effect on price.
Durationaffects price
Whole seconds, 1 to 16. One to four is the practical range for variant passes. no lower than 1 · no higher than 16
affects price
540p or 720p. Draft at 540p while the motion is still moving, then raise it once for the take you intend to deliver.
Generate audio
On by default. Set it false when the cut goes under an existing mix.
Background music
Adds a background music bed that fits the scene’s mood. On by default; switch it off when the clip goes under your own music or should carry only the scene’s own sound. It is separate from `generate_audio`, which renders the sound of the scene itself (steps, room tone, voices). No effect on price.
Seed
Makes two runs comparable when you change one variable. Not a frame-identical guarantee. no lower than 0 · no higher than 2147483647
Safety checkerOff

SpicyAPI does not run a safety checker on this model. Your prompt and media go to the model as written, and the model itself decides what comes back.

Checking your account before enabling submission and pricing.

Output

Ready for a new run
Example result

Related models and next tasks

Missing the model you need?

Tell us what to add and where you would use it. Requests go to the people who decide what gets onboarded next.

The speed tier of Q3, with a 540p draft step built in

Vidu Q3 Turbo image-to-video API animates one opening frame into a clip of 1 to 16 whole seconds at 540p or 720p, with sound produced in the same pass. Both prompt and image_url are required, and the still also fixes the shape of the output, because this endpoint publishes no aspect_ratio field. The published resolution list stops at 720p.

Open the playground
The speed tier of Q3, with a 540p draft step built in
Required fields
prompt and image_url; the other four are optional
Duration
1 to 16 whole seconds, default 5
Resolution
540p or 720p, default 720p
Audio
generate_audio, default true, and no music-bed field
Output shape
Comes from the still you send; no aspect_ratio field
Source image
One frame, aspect ratio inside 1:4 to 4:1
Vidu's own comparison puts Turbo ahead of Q3 Pro on speed

Speed

Vidu's own comparison puts Turbo ahead of Q3 Pro on speed

Vidu's documentation describes Q3 Turbo as generating faster than Q3 Pro, and publishes no figure for the gap, so read it as a direction and not as a number. What it changes in practice is how many versions of a movement you can try from one still before choosing the one to deliver.

Two steps sit on one field

Resolution

Two steps sit on one field

resolution takes 540p or 720p and defaults to 720p, so the exploratory pass and the delivery pass are the same request with one value changed. The frame, the prompt, the duration and the seed all stay where they are, which is what makes a cheap first pass worth running.

Audio
One switch decides whether the clip has soundgenerate_audio defaults to true, so a clip arrives with a synchronised track unless the request sets the field to false. Q3 models publish no music-bed field, so the prompt is where the sound of the scene gets named, and a music track goes under the clip in the edit.

How to call the Vidu Q3 Turbo API

  1. Settle the still before you build the request

    image_url decides the subject, the styling and the shape that comes back, and nothing later in the request overrides it. Keep the frame's aspect ratio inside 1:4 to 4:1, and adjust anything narrower or wider in the image before you upload it.

  2. Write the prompt for what happens after the frame

    prompt is required even when the still already shows the scene. Name the action, the camera behaviour and the sound, and leave out what the image has already settled, because this text is the only direction the model gets.

  3. Choose duration_seconds to fit the action

    The field takes whole numbers from 1 to 16 and falls back to 5 when a request omits it. Two or three seconds holds a single gesture or one camera move; an action that changes direction partway needs the upper half of the range.

  4. Run the variants at 540p

    Hold image_url and prompt fixed, change seed between calls, and read several takes at the cheaper step before any of them goes out at the higher one. This is the pass the tier is built around.

  5. Re-run the chosen take at 720p

    Set resolution to 720p and leave every other value alone, including the seed that produced the take you picked. Nothing in the frame or the prompt has to be rewritten between the two passes.

Vidu Q3 Turbo worked examples

  • A dance move drafted before the final render

    A few 540p passes settle the timing and the sway, and the request that wins goes out again at 720p with only the resolution changed.

    The dancer turns once toward the lens and settles into a slow sway, warm stage light from the left, handheld framing
  • A kitchen beat timed against the clip length

    The pan slide has to finish inside the clip, so duration_seconds is tried at a few values on the cheap step before the delivery pass.

    The chef slides the pan forward and steam rises across the frame, the camera drifts right without cutting, evening kitchen light
  • A cut that has to arrive silent

    The clip is going under a mix that already exists, so generate_audio is set to false and nothing else about the request changes.

    A cyclist rolls past the shopfront, the awning lifts in the draught behind them, the camera pans a few degrees to follow

Vidu Q3 Turbo API questions

Write the prompt as a short sequence of physical events and let the frame carry the rest. A take that comes back too static is usually a text problem: this endpoint has no strength or amplitude field, so more movement means naming a second beat, and a longer beat means raising duration_seconds. If two takes from the same still read differently and you cannot tell why, fix seed and change one field per call until you can.