seedanceapi
Q3 · Image to Video Pro render example

Vidu · Q3 · image to video

Q3 · Image to Video Pro

Render Q3 through the same job workflow as Seedance — from $0.608 per render.

Model idvidu/q3/image-to-video-proShot spec720p · 1080p · 2k · 4k · 1–16sRatefrom $0.608

What it renders

Vidu Q3 Image-to-Video Pro generates high-resolution videos (720p/1080p/2K/4K) from images with exceptional visual fidelity and diverse motion. Hand over the model id and your shot settings, keep the job id, and collect the finished clip once the job lands. Pricing is per completed render from $0.608 and is locked in before the first frame is queued.

  1. Motion-first defaults

    Q3 · Image to Video Pro opens on workable shot framing before you tune anything.

  2. Async by design

    Renders run as background jobs; poll at your own pace instead of holding a connection open.

  3. Clip-ready output

    Results arrive as a downloadable asset from private storage with a short-lived link.

  4. Image to Video shots

    Image to Video stays available for Q3 · Image to Video Pro without leaving the video workspace.

  5. Q3 shots

    Q3 stays available for Q3 · Image to Video Pro without leaving the video workspace.

  6. Video shots

    Video stays available for Q3 · Image to Video Pro without leaving the video workspace.

From the shot board

Q3 · Image to Video Pro example output.
Q3 · Image to Video Pro output
Q3 · Image to Video Pro example reference.
Q3 · Image to Video Pro reference

Wire the render pipeline

  1. Grab a key

    Sign in, create a server-side key and add a little balance.

  2. Confirm the endpoint

    GET /v1/models lists vidu/q3/image-to-video-pro with its shot limits and current rate.

  3. Queue the render

    POST /v1/jobs with the model id, your shot settings and a unique Idempotency-Key.

  4. Collect the clip

    Poll GET /v1/jobs/{id} until it lands, then fetch GET /v1/jobs/{id}/content.

Queue the render

# Seedance API — queue one render
curl https://seedanceapi.pro/v1/jobs \
  -H "Authorization: Bearer $SEEDANCE_API_KEY" \
  -H "Idempotency-Key: $REQUEST_ID" \
  -H "Content-Type: application/json" \
  -d '{"model":"vidu/q3/image-to-video-pro","bgm":true,"duration":5,"generate_audio":true,"movement_amplitude":"auto","prompt":"A slow dolly across a rain-lit neon street, shallow depth of field.","resolution":"720p","seed":1}'

Shot settings

bgmoptional
boolean · default true
durationoptional
integer · default 5
generate_audiooptional
boolean · default true
imageneeded
string
movement_amplitudeoptional
string · auto / small / medium / large
promptoptional
string
resolutionoptional
string · 720p / 1080p / 2k / 4k
seedoptional
integer

Try a render from here

This queues a real job on this site's /v1/jobs using your signed-in balance, or an API key if you are not signed in. A pasted key lives only in this tab; the render is billed at the quoted USD rate.

Or sign in to use your account balance.

Before you wire it in

How do I start a Q3 · Image to Video Pro render?

Authenticate, check the live model list for vidu/q3/image-to-video-pro, then POST the model id and shot settings to /v1/jobs with an Idempotency-Key. Poll the job id until it settles, then download the clip.

What can I control on Q3 · Image to Video Pro?

Q3 · Image to Video Pro accepts bgm, duration, generate_audio, image, movement_amplitude, prompt, resolution, seed. Unknown keys are rejected before the render is queued, so a typo never burns a job.

What does a Q3 · Image to Video Pro render cost?

Pricing is per render and starts at $0.608. The exact figure for your settings is returned by the model list and reserved before the job is accepted.

Is the same Seedance key valid for Q3 · Image to Video Pro?

Yes — Q3 · Image to Video Pro runs on the same account, key and wallet as Seedance. Each endpoint is enabled individually, so verify the route before you depend on it.

Why does my Q3 · Image to Video Pro job show as queued?

Video rendering is asynchronous: queued and running are normal. Keep polling until the job succeeds, fails or asks for review, and never resubmit the same Idempotency-Key expecting a second render.

More endpoints like this