Video Models

Google

VEO 2

High-quality image-to-video and text-to-video generation.

Image-to-videoText-to-video

At a glance

Plan the shot before you generate.

App mapping & provider reference
Workflow / inputs
App: text route; Google reference also supports image-to-video
Resolution reference
Google reference: 720p at 24 fps; current host unverified
Duration reference
Google reference: 5–8 seconds; app card: up to 8
Audio reference
No verified audio control for this app route
Serving host
WaveSpeed (audit mapping; current endpoint page unverified)
Catalog status
App-listed in owner audit; not live-tested

API model or route: google/veo2

App catalog ID: veo-2

Capabilities & boundaries

What it supports. What the app exposes.

Provider features and app integration are different layers. A feature in the upstream documentation is not automatically enabled in your workspace.

Model and hosting capabilities

  • Google's Veo 2 model reference documents 720p video at 24 fps, using English prompts.
  • Google lists 16:9 and 9:16 aspect ratios, text-to-video and image-to-video; the app's WaveSpeed mapping does not establish direct Vertex AI access.
  • The owner audit includes VEO 2 as a selectable choice, but current host acceptance still needs confirmation.

Before you choose

  • The shared app wrapper and the host's accepted durations can differ. A value inside the app's clamp is not necessarily valid for this specific endpoint.
  • The supplied WaveSpeed route's public model page returned 404 during review. This does not establish model retirement, successful routing or a replacement endpoint.
  • Do not carry newer Veo audio, resolution or reference-image capabilities over to this older route.
  • Review motion, anatomy, continuity and any generated sound before publishing. Prompt instructions are creative targets, not guarantees of an exact result.
  • Only upload media you have permission to use, including consent for identifiable performers. Provider safety rules and usage terms still apply.

Controls in the audited app integration

  • The audited WaveSpeed wrapper forwards prompt, duration and aspect_ratio. It clamps duration to 3–10 seconds (default 5); this is a wrapper range, not the endpoint's supported set of durations.
  • Resolution and audio settings are not forwarded by this wrapper. Neither are reference images, seed or advanced camera controls. Provider support for them does not establish app support.

Put it to work

Start with a more useful visual brief.

Original examples from EZ Ai Assist. Choose supported controls separately. Some workflows require source media; a text brief does not supply those inputs.

Workflow 01

Continuity baseline

Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.

A red wooden ball rolls slowly along a shallow groove on a pale oak table and stops at a small block. Keep the camera stationary and close enough to see contact with the surface. Preserve object sizes and lighting, with no extra movement or cuts.

Workflow 02

Lighting baseline

Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.

One white ceramic vase stands beside a softly lit window while a sheer curtain moves gently behind it. Use a fixed eye-level composition and natural shadows. Keep the vase perfectly still and avoid changing its silhouette, color or position.

Workflow 03

Landscape baseline

Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.

A low stone wall borders a field of tall grass under a cloudy sky. Slowly move the camera sideways as the grass bends in a light breeze. Keep the wall's stones consistent, the horizon steady and the scene free of people, signs or transitions.

Developer reference

Provider & hosting API pricing

Public provider or hosting API reference prices in USD, not EZ Ai Assist subscription prices or app charges. Check the app for your current plan, allowance and charge before generating.

View EZ Ai Assist plans

A current price for the audited google/veo2 hosting route was not verified. Newer Veo rates and the app card's estimate are not substitutes.

  • Provider prices can change. Verify the exact hosting route and request settings before relying on a published rate.
  • The owner audit found differences between some app-card estimates and backend calculations. This website update does not change or certify app billing.

Common questions

VEO 2 FAQs

What is VEO 2 useful for?

VEO 2 reference guide with its audited app route, shot-planning examples and a warning that current hosting specifications and pricing need confirmation.

Which inputs does this workflow need?

App: text route; Google reference also supports image-to-video. Confirm that the app accepts any required media before using a provider-only workflow.

What duration and resolution can I use?

Google reference: 5–8 seconds; app card: up to 8. Google reference: 720p at 24 fps; current host unverified. Provider values, app labels and successful runtime behavior are different layers; the audit is not a generation test.

Are these prices what EZ Ai Assist charges?

Public provider or hosting API reference prices in USD, not EZ Ai Assist subscription prices or app charges. Check the app for your current plan, allowance and charge before generating. A current price for the audited google/veo2 hosting route was not verified. Newer Veo rates and the app card's estimate are not substitutes.

Is this model available or retired?

The app audit lists google/veo2, but its public WaveSpeed page could not be verified. Keep this as an app-mapping reference until a live route check confirms service; no provider retirement date is asserted.

Sources & freshness

Check the original references.

Reviewed . Public provider or hosting documentation supports the reference specifications and prices. App behavior is based on the owner-supplied code-audit reports labeled October 9, 2026, not live generation tests. No retirement date is inferred from a missing listing, a legacy name or an unresolved route.

Same provider