veo31 is the quality-first video model in the Google Veo 3.1 series, suitable for turning text concepts, product stills, and storyboards into dynamic shots. It supports text-to-video, image-to-video with a first frame or start-and-end frames, and can further extend generated clips. Compared with Fast models designed primarily for rapid drafting, veo31 is better suited for asset production and shot review where image quality takes priority.
Submit requests to the public API at api.acedata.cloud using the documented parameters, then use the results in your application.
api.acedata.cloudveo31Input parameters and result formats vary by service. Use the public API for this model and follow its guide for generation, task retrieval and editing operations.
The above are this platform's veo31 invocation specifications; generation and extension each use their own resolution options, and series capabilities should not be regarded as jointly supported across all operations.
Image-to-video can begin with one first-frame image, or use two images to specify the start and end points. Compared with text alone, this approach establishes the composition at both ends of the shot first, then uses prompts to describe the action in between, camera movement, and the transition process. It is suitable for product reveals, scene transitions, and storyboard previsualization.
veo31 belongs to Quality mode and is suitable for tasks where review focuses on visual presentation rather than rapid drafting. During generation, you can select landscape or portrait aspect ratios and resolution options such as 1080p and 4k, allowing the same concept to serve both landscape displays and portrait content; compositions should be redesigned for the target aspect ratio.
Generated clips can be further developed through extension, with new prompts guiding subsequent visuals—for example, having the camera pull back or the subject continue moving. Asynchronous tasks and callbacks make it easy to connect generation, review, extension, and asset archiving into a workflow, without requiring the application to wait continuously for video generation requests to finish.
Use a product still as the first frame, describe subject movement, camera angles, and lighting changes, and create dynamic assets for advertising edits. If you already have a clear ending composition, add last-frame constraints to define the shot endpoint. After delivery, focus on checking the product shape, branding, and details, then combine it with subtitles and music.
Submit the opening and ending images from a storyboard as the first and last frames, along with descriptions of character actions, spatial changes, and camera direction, to generate transition shots for discussion. It is suitable for verifying whether visual continuity works, helping directors and design teams evaluate shot options before formal production, rather than directly replacing production of an entire film.
Select generated clips that have passed review, use their video IDs to initiate extensions, and describe the actions or shot scale desired in the next segment. The returned video links can enter the editing asset library; extension results can also be extended further. Keep the original clips during production to facilitate continuity comparison and fallback options.
When a task already has a clear composition and you want to conduct quality review around a small number of options, prioritize veo31. If you need to first explore a large number of prompts and camera directions, consider veo31-fast, then select options for quality-first production. The two are independent models; when comparing them, keep the image, aspect ratio, and prompt consistent, and do not assume a fixed speed difference.
If the task is to animate an existing image or create a transition between specified starting and ending images, veo31's first-frame and first/last-frame modes are more direct. If you want to blend elements from multiple assets into a single creation, consider veo31-fast-ingredients. The latter uses multi-image fusion and requires image uploads; it is not equivalent to veo31's first/last-frame control.
Use text2video for text only; use image2video for image-driven generation. One image in image_urls is the first frame, and two images are the first and last frames; describe the action that occurs in between.
Specify model=veo31 for /veo/videos, choose the action based on text or images, and fill in prompt. Start with aspect_ratio=16:9 and resolution=720p, then increase the output tier within this model's supported range.
After setting async=true, save the task_id and obtain the finished video through /veo/tasks or a callback; also save data[].id. Veo 3.1 extensions use video IDs and cannot use task IDs as a substitute.
The first frame is a closed wooden door, and the last frame is an open wooden door with a warm interior. The shot slowly moves in from outside the door, keeping the doorframe and environment consistent.
First verify the perspective and composition of the two images, then check the motion in between; for subsequent extension, save data[].id. Generating in 4k does not mean extension also supports 4k.
Yes. Use /veo/videos, set model to veo31, action to text2video, and provide a scene prompt. It is recommended to clearly specify the subject, action, environment, and camera direction; if the composition is already determined, you can instead use image2video, using an image as the starting point of the shot.
One image is used as the first frame, so the video starts from the specified image; two images are used as the first and last frames, guiding the shot to connect the start and end points. Submit image links through image_urls, then use prompt to describe the transition. veo31 should not be used as a three-image blending method.
When generating a video, you can set resolution to 4k, but the resolution options for /veo/extend are 720p or 1080p; the two operations cannot share the same set of settings. If the project requires a consistent delivery resolution, determine the extension requirements first, then arrange asset generation and final output.
Submit model=veo31 and data[].id from the generation result to /veo/extend, and you can add a prompt to guide the subsequent footage. This uses the video ID, not the asynchronous task's task_id. The new video ID obtained after the extension is complete can also be used for the next extension.
You can describe scenes in Chinese and enable automatic translation through translation. After setting async=true, first obtain the task_id, then query the task result; you can also set callback_url to receive completion notifications. The video_url in the completed result is used to retrieve the video, and data[].id is used for subsequent video operations.
Choose a development approach or application suited to this model and follow its setup guide.
↗Python SDK Integration Guide
SDK installation, authentication and examples↗TypeScript SDK Integration Guide
SDK installation, authentication and examples
↗
↗
↗Pricing
$0.48–$0.73· per generation
You pay$13,584for 142,800 credits · $0.0951 / credits46% OFF
You're billed in credits. Pick a top-up tier to see its per-credit rate — the larger the top-up, the cheaper each credit.
This is only a basic call example. See the full docs for more parameters and advanced usage.
View Docs