topaz/colorize/video
Colorize Video by Topaz Labs - AI-powered video editing and transformation. Apply style transfer, motion control, lip-sync, and visual effects to existing videos with natural language instructions.
Example output — click Run to generate your own
Send your first request
OpenAI-compatible endpoint with unified authentication and usage tracking.
https://api.sandbase.ai/v1/runtopaz/colorize/videoInput Schema
2 parameters · 0 required · 2 optional
| Parameter | Type | Required | Description |
|---|---|---|---|
video | string | Optional | URL of the black-and-white video to colorize |
H264_output | boolean | Optional | Whether to use H264 codec for output video. Default is H265. · Default: false |
Output Schema
| Field | Type | Description |
|---|---|---|
id | string | Unique identifier for the generation task |
status | string | Task status: pending, running, completed, failed, timeout |
model | string | Model used for the generation |
outputs | array | Array of output items |
outputs[].url | string | URL of the generated artifact |
outputs[].content_type | string | MIME type (e.g. image/png, video/mp4) |
error | object | null | Error details if failed, null on success |
error.type | string | Machine-readable error type code |
error.message | string | Human-readable error description |
Async Workflow
This model uses asynchronous execution. Submit a request and poll for the result.
- Submit — POST to /v1/run, receive an
id - Poll — GET /v1/run/{id} until status is
completed,failed, ortimeout - Retrieve — Read
outputsfrom the completed response
Code Examples
Ready-to-run snippets
# Step 1: Submit
curl -X POST https://api.sandbase.ai/v1/run \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"model": "topaz/colorize/video",
"video": "https://v3.fal.media/files/kangaroo/y5-1YTGpun17eSeggZMzX_video-1733468228.mp4",
"H264_output": false,
"prompt": "a beautiful sunset over mountains"
}'
# Step 2: Poll result (replace <id>)
curl https://api.sandbase.ai/v1/run/<id> \
-H "Authorization: Bearer YOUR_API_KEY"API README
Video
Video is designed around the topaz/colorize/video workflow for video work in video production. Teams can place this named operation inside review, asset preparation, and publishing pipelines while keeping the original request attached to every result. Colorize Video by Topaz Labs - AI-powered video editing and transformation. Apply style transfer, motion control, lip-sync, and visual effects to existing videos with natural language instructions. Because topaz/colorize/video is a separate catalog entry, evaluations should use this route’s own inputs, output expectations, and billing behavior. The endpoint is especially useful when a project has a defined transformation goal and needs a repeatable request contract instead of an ad-hoc desktop step. This capability boundary is specific to the endpoint named above.
Video exposes video, H264_output as its documented request surface. The mandatory portion is no mandatory fields declared by the schema. video controls uRL of the black-and-white video to colorize; H264 output controls whether to use H264 codec for output video. Default is H265. For example, the route documentation includes “https://v3.fal.media/files/kangaroo/y5-1YTGpun17eSeggZMzX_video-1733468228.mp4”. Applications can submit that exact shape asynchronously, retain the chosen arguments in job metadata, and collect the resulting media URL for review or publishing.
Highlights
- Temporal colorization. Topaz Colorize Video introduces color across a monochrome clip while keeping the treatment coherent from frame to frame.
- Motion-aware consistency. The workflow is designed to avoid the distracting color flicker that independent frame coloring can create around moving subjects.
- Archive-to-modern conversion. It is suited to historical, documentary, and restored footage whose luminance detail should remain recognizable after color is introduced.
- Video-native finishing. The route accepts a source video and returns a processed clip, so colorization stays inside a repeatable media pipeline.
Pricing
| Billing option | Price |
|---|---|
| Billing formula | (usage.duration ?? 10) * ((((usage.width ?? 1920) * (usage.height ?? 1080)) > 2073600) ? 0.0345 : 0.0115) * ((usage.fps ?? 30) / 30) |
| Catalog base price | $0.115000 |
When to Use
| Scenario | Why it fits |
|---|---|
| Choose Video | Use it when the job specifically calls for video and the route’s documented input contract matches assets already available in your workflow. |
| Keep the request reproducible | Use the required inputs explicitly, then record optional choices alongside the prompt for repeatable reruns. |
| Build controlled creative variations | Change one declared control at a time when comparing framing, format, duration, resolution, style, or other route-supported output decisions. |
| Integrate asynchronous delivery | Use this endpoint when an application can submit work, track completion, and collect the returned media URL instead of requiring an immediate inline artifact. |
| Validate before a large batch | Run representative prompts and source assets first, confirm the visual or audio behavior, then lock the successful request shape for scaled production. |
Prompt Guide
Lead with the subject or transformation, then add the composition, environment, style, lighting, motion, voice, or fidelity details relevant to this route. Keep every parameter inside the documented schema; the example below uses only fields declared for topaz/colorize/video.
{}
Technical Specs
| Specification | Details |
|---|---|
| Model ID | topaz/colorize/video |
| Execution mode | async |
| Task type | video |
video | string · optional |
H264_output | boolean · optional |