Pixazo APIVideo Tools APIImage to MP4
Pixazo APIVideo Tools APIImage to MP4

Image to Video 1 API: Pricing, Documentation

by Pixazo

Turn a still image into a video file of a chosen length. This is a deterministic hold, not generation — there is no prompt, no motion and no model inventing frames: the picture is held for duration_seconds and encoded as a silent H.264 MP4 at the source’s own dimensions. Use it to give a still a slot on a timeline, pad a sequence, or feed a photograph into a tool that only accepts video. duration_seconds runs from 1 to 60 and defaults to 5.

Get API Key
Image to Video API

Models Version

WELCOME BONUS

Get $5 Free Credit on First Payment

No strings attached — add funds and get $5 bonus instantly

Claim Your $5 →

Image to Video 1.0 API Documentation

https://gateway.pixazo.ai/media-tools/v1/image-to-video

Authentication

All requests require an API key passed via header.

Pricing: Billed at $0.002 per clip — a flat rate per call. Duration does not change the price: a 1-second clip and a 60-second clip both cost $0.002.

Retries: this is an asynchronous job on shared encoding capacity, so a request can occasionally come back processing_failed or take much longer than usual. These are transient and succeed on a retry, and a failed job is never charged — the wallet hold is released. If you chain these tools, retry a failed step rather than failing the whole pipeline.

HeaderTypeRequiredDescription
Ocp-Apim-Subscription-KeystringYesYour API subscription key

Image to Video generate request

Request Code

POST https://gateway.pixazo.ai/media-tools/v1/image-to-video
Content-Type: application/json
Cache-Control: no-cache
Ocp-Apim-Subscription-Key: YOUR_API_KEY

{
  "image_url": "https://api-assets.pixazo.ai/media-api-test/sample.png",
  "duration_seconds": 5
}
import requests

url = "https://gateway.pixazo.ai/media-tools/v1/image-to-video"
headers = {
    "Content-Type": "application/json",
    "Cache-Control": "no-cache",
    "Ocp-Apim-Subscription-Key": "YOUR_API_KEY"
}
data = {
  "image_url": "https://api-assets.pixazo.ai/media-api-test/sample.png",
  "duration_seconds": 5
}

response = requests.post(url, json=data, headers=headers)
print(response.json())
const url = "https://gateway.pixazo.ai/media-tools/v1/image-to-video";
const headers = {
  "Content-Type": "application/json",
  "Cache-Control": "no-cache",
  "Ocp-Apim-Subscription-Key": "YOUR_API_KEY"
};
const data = {
  "image_url": "https://api-assets.pixazo.ai/media-api-test/sample.png",
  "duration_seconds": 5
};

fetch(url, {
  method: "POST",
  headers: headers,
  body: JSON.stringify(data)
})
.then(response => response.json())
.then(data => console.log(data));
curl -X POST "https://gateway.pixazo.ai/media-tools/v1/image-to-video" \
  -H "Content-Type: application/json" \
  -H "Cache-Control: no-cache" \
  -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  --data-raw '{
    "image_url": "https://api-assets.pixazo.ai/media-api-test/sample.png",
    "duration_seconds": 5
  }'

Output

{
  "request_id": "media-image-to-video_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "QUEUED",
  "polling_url": "https://gateway.pixazo.ai/v2/requests/status/media-image-to-video_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

Webhook (Optional)

Add the X-Webhook-URL header to your generate request to receive a POST callback instead of polling.

X-Webhook-URL: https://your-server.com/webhook/callback

Request Parameters - Image to Video generate request

Parameter Required Type Default Allowed values / range Description
image_urlYesstringHTTP(S) URL to an image; JPG, PNG, WebP, AVIF, HEIC, TIFF, BMP, GIF or SVG; under 50 megapixelsPublicly reachable HTTP(S) URL of the still to hold on screen. A source over 50 MP is rejected before you are charged.
duration_secondsNonumber51 – 60How long the still is held, in seconds. Outside that range the request is rejected rather than clamped.

What this endpoint actually does: it holds your image on screen, unchanged, for duration_seconds and encodes that as a silent H.264 MP4. It is a deterministic re-wrap, not a generative model — nothing moves, nothing is invented, there is no pan, zoom, parallax or AI-generated motion of any kind. The same input always produces the same output. If you want real motion, use one of the image-to-video generation models in the catalog instead; they are priced per second and cost far more than this.

Those two parameters are the whole API. There is no prompt, no fps, no width/height, and no motion, zoom or effect setting. Anything else you send is not honoured.

Output: H.264 video in yuv420p, no audio track, running exactly duration_seconds long. The frame is downscaled to fit inside a 1920×1920 box, preserving aspect ratio, and is never upscaled — a 400×300 raster source gives you a 400×300 video. Dimensions are nudged to even numbers, which yuv420p requires. Transparency (PNG, WebP, SVG) is flattened, because MP4 has no alpha channel.

SVG is the exception to “never upscaled”. A vector file has no native pixel size, so there is nothing to upscale from: an SVG is rasterised by librsvg to the 1920×1920 box, aspect ratio preserved, whatever the width/height or viewBox in the file says. A 400×300 SVG therefore comes back as a 1920×1440 video, not a 400×300 one. The 50 megapixel source limit does not apply to SVG either — there are no source pixels to count.

Example Request

{
  "image_url": "https://api-assets.pixazo.ai/media-api-test/sample.png",
  "duration_seconds": 5
}

Response

{
  "request_id": "media-image-to-video_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "QUEUED",
  "polling_url": "https://gateway.pixazo.ai/v2/requests/status/media-image-to-video_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

Request Headers

Header Value
Content-Typeapplication/json
Cache-Controlno-cache
Ocp-Apim-Subscription-KeyYOUR_API_KEY

Response Handling

Common status codes.

CodeMeaning
202Accepted — Request queued
Bad Request
401Unauthorized
402Insufficient Balance
403Forbidden
Too Many Requests
500Internal Server Error

Error Responses

Queue system errors and model validation errors.

Queue System Errors

// 402 — Insufficient balance
{
  "error": "Insufficient Balance",
  "message": "Your wallet does not have enough balance."
}
// 400 — Model not found
{
  "error": "Model not found",
  "message": "Model 'media-image-to-video' not found or is disabled"
}

Error via Status/Webhook

{
  "request_id": "media-image-to-video_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "media-image-to-video",
  "error": "Description of the error",
  "output": null
}

Retrieving Results

Poll the universal status endpoint to check progress and retrieve results.

Endpoint

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}
Ocp-Apim-Subscription-Key: YOUR_API_KEY

cURL Example

curl -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  "https://gateway.pixazo.ai/v2/requests/status/media-image-to-video_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

Response (Completed)

{
  "request_id": "media-image-to-video_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "media-image-to-video",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/media-image-to-video_019dxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-03-31T10:00:00.000Z",
  "updated_at": "2026-03-31T10:00:15.000Z",
  "completed_at": "2026-03-31T10:00:15.000Z"
}

Response Fields

FieldTypeDescription
request_idstringUnique request identifier
statusstringQUEUED, PROCESSING, COMPLETED, FAILED, or ERROR
model_idstringModel that processed the request
errorstring|nullError message if failed
output.media_urlarrayURLs to generated media (R2 CDN)
output.media_typestringMIME type of the output
created_atstringWhen request was created
completed_atstringWhen request completed
polling_urlstringStatus URL (initial response only)

Status Values

StatusDescription
QUEUEDRequest accepted, waiting to be processed
PROCESSINGBeing processed by the model
COMPLETEDDone — output contains the result
FAILEDFailed — check error field
ERRORSystem error — not charged

Status Flow

QUEUED → PROCESSING → COMPLETED
                    → FAILED
                    → ERROR

Typical Workflow

  1. Send a generate request to the API endpoint
  2. Save the request_id from the response
  3. Poll every 5-10 seconds: GET /v2/requests/status/{request_id}
  4. When status is "COMPLETED", download from output.media_url

Tip: Use X-Webhook-URL header to get a callback instead of polling.

Image to Video 1.0 API Pricing

Your request will cost $0.002 per clip.
every clip costs $0.002, whether it runs 1 second or 60

⚡ Performance

Live usage measured on Pixazo's gateway, split by model version. Generation time is how long a generation takes end-to-end (lower is better). Success rate is the percent of generations that complete (higher is better).

Show data for the last
Generations
300last 30d
~10 per day
Success rate
33.3%
of completed generations
Generation time
22.6savg
p95 22.6s
Requests
Aug 8max 300Sep 6
Image to Video 1.0Avg 10/day
Generation Time
Aug 8max 22.6sSep 6
Image to Video 1.0Avg 22.6s
Error Rate
Aug 8max 66.7%Sep 6
Image to Video 1.0Avg 66.7%

〰 Uptime

Percent of generations that succeeded over the selected period, per model version.

Avg. Success Rate (30d)
33.33%
across all generations of this model family
Uptime
Aug 8max 100%Sep 6
SuccessfulAvg 33.33%