Veo 3.1 Text to Video

Name: Veo 3.1 Text to Video
Author: Google

google/veo3.1/text-to-video

Veo3.1 by Google - generate cinematic videos from text descriptions with AI. Create high-quality video content with natural motion, camera control, and optional audio generation.

Use in agent Get API key

Base price: $3.20USD / run
Execution: async
Model type: video
Input fields: 7

Production route

Try the model

Playground

Open playground

Input

Prompt(string)

The text prompt describing the video you want to generate

Duration(integer)

Duration of the generated video in seconds. Allowed values: 4, 6, 8.

Resolution(string)

Output resolution. Allowed values: 720p, 1080p, 4k.

Aspect Ratio(string)

Output aspect ratio. Allowed values: 16:9, 9:16.

Generate Audio(boolean)

Generate synchronized audio. Videos without audio are cheaper.

Negative Prompt(string)

What to avoid in the video.

Seed(integer)

Random seed for more reproducible results. Range: 0 to 4294967295.

OutputReady

Your output will appear here

Complete the inputs, then click Run.

Specifications

Pricing

Base price: $3.20 / run
Billing formula: (params.duration ?? 8) * ((params.resolution ?? "720p") == "720p" ? ((params.generate_audio ?? true) ? 0.40 : 0.20) : (params.resolution ?? "720p") == "1080p" ? ((params.generate_audio ?? true) ? 0.40 : 0.20) : (params.resolution ?? "720p") == "4k" ? ((params.generate_audio ?? true) ? 0.60 : 0.40) : (0 / 0))

Context & modalities

Input: Schema-defined
Output: video

Capabilities

Chat: Not supported
Vision: Not supported
Reasoning: Not supported
Structured output: Not supported
Function calling: Not supported
Audio input: Not supported

Access

Provider: Google
Model ID: google/veo3.1/text-to-video
Execution: async
API: Unified Run API
Endpoint: /v1/run

API README

Veo 3.1 Text to Video

google/veo3.1/text-to-video creates a cinematic video from written scene direction, interpreting subject action, environment, camera language, lighting, and pacing. Veo 3.1 improves instruction following, physical consistency, character continuity, and audiovisual quality while supporting more ways to anchor or continue a shot. This combination makes the model a practical choice when the creative outcome depends on those qualities rather than on a generic media conversion.

For production work with google/veo3.1/text-to-video, the text-guided video generation workflow suits storyboards, campaign films, product moments, narrative shots, and visual concepts that need coherent motion rather than isolated animated frames. The result is most reliable when the source material and creative brief clearly describe the intended subject, progression, visual or sonic character, and the qualities that must remain unchanged.

Highlights

Cinematic prompt interpretation turns scene, action, lens, lighting, and camera language into moving imagery.

Improved physical coherence strengthens object interactions, character movement, and cause-and-effect across shots.

Visual continuity maintains subjects and scene logic across the generated sequence.

Native audio generation coordinates dialogue, ambience, and sound effects with the visual action.

Pricing

Official Google list price per generated second.

Resolution	Audio off	Audio on
720p	$0.20/s	$0.40/s
1080p	$0.20/s	$0.40/s
4k	$0.40/s	$0.60/s

Default: 8 seconds at 720p with audio = $3.20.

When to Use

✅ Good fit	❌ Consider alternatives
The model's named workflow matches the source material and intended output	A different input modality or model route is required
A managed asynchronous result is suitable for the production pipeline	A synchronous, interactive editor is essential
The documented controls cover the required duration, framing, or format	The project needs controls outside this endpoint's schema
Creative iteration benefits from a repeatable request structure	Exact deterministic pixels, frames, geometry, or samples are mandatory
A finished downloadable media asset is the desired deliverable	Editable source layers or a native project file are required

Prompt Guide

For generation, state the intended result first, then add the subject or source treatment, progression, style, and delivery constraints. Keep one creative variable per phrase, use the documented field names for controls, and change one setting at a time when comparing results.

{
  "prompt": "A paper boat drifting down a rain-soaked street at dusk, cinematic close-up, soft reflections",
  "duration": 8,
  "resolution": "720p",
  "aspect_ratio": "16:9",
  "generate_audio": true
}

Technical Specs

Spec	Value
Model ID	`google/veo3.1/text-to-video`
Inputs	aspect_ratio, duration, generate_audio, negative_prompt, prompt, resolution, seed
Required inputs	prompt
Output fields	content_type, url
Execution	Async (submit, then poll for result)
Duration	4 / 6 / 8 seconds
Resolution	720p / 1080p / 4k
Aspect Ratio	16:9 / 9:16

Related Models

Start building

Send your first request

OpenAI-compatible endpoint with unified authentication and usage tracking.

Production API

Unified Run API endpoint

https://api.sandbase.ai/v1/run

Model ID

google/veo3.1/text-to-video

# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
  -X POST "https://api.sandbase.ai/v1/run" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'SANDBASE_JSON'
{
  "model": "google/veo3.1/text-to-video",
  "prompt": "Two person street interview in New York City.\nSample Dialogue:\nHost: \"Did you hear the news?\"\nPerson: \"Yes! Veo 3.1 is now available on fal. If you want to see it, go check their website.\"",
  "duration": 8,
  "resolution": "720p",
  "aspect_ratio": "16:9",
  "generate_audio": true
}
SANDBASE_JSON
)
run_id=$(printf '%s' "$result" | jq -r .id)
for attempt in $(seq 1 120); do
  status=$(printf '%s' "$result" | jq -r .status)
  case "$status" in completed|failed|timeout) break ;; esac
  sleep 2
  result=$(curl --fail-with-body --silent \
    -H "Authorization: Bearer $SANDBASE_API_KEY" \
    "https://api.sandbase.ai/v1/run/$run_id")
done
status=$(printf '%s' "$result" | jq -r .status)
[ "$status" = completed ] || { echo "Generation ended: $status" >&2; exit 1; }
printf '%s\n' "$result"

Choose your model

Compare models

All image & video models

Model	Type	Default price	Released
Veo 3.1 Text to VideoThis model `Google`	Video	$3.20 / run	Oct 8, 2025
Gemini Omni Flash 1.1 Edit `Google`	Video	$1.12 / run	Aug 27, 2026
Gemini Omni Flash 1.1 Text to Video `Google`	Video	$0.80 / run	Aug 27, 2026
Gemini Omni Flash 1.1 Image to Video `Google`	Video	$0.80 / run	Aug 27, 2026
Gemini Omni Flash 1.1 Reference to Video `Google`	Video	$0.80 / run	Aug 27, 2026
Gemini Omni Flash Reference to Video `Google`	Video	$1.04 / run	Jun 30, 2026

Questions

FAQ

How do I call Veo 3.1 Text to Video through SandBase?

Create a SandBase API key, then send requests with the model ID "google/veo3.1/text-to-video" to Unified Run API (/v1/run) at https://api.sandbase.ai. The request examples on this page show the exact payload.

Do I need a separate Google account?

No. One SandBase API key and balance gives you access to Veo 3.1 Text to Video and the other models in the catalog; you do not need to sign up with Google separately.