Lesson 5 of 9 · about 18 minutes
AI Video Generation: Tools, Costs and Limits
You'll be able to
- Tell text-to-video from image-to-video and know why one gives more control
- Estimate the cost of a short AI video from per-second prices
- Recognize the typical failures: hands, physics, text, drifting faces
- Understand why AI video pieces are built from 4 to 8 second clips joined on a timeline
AI video in 2026 makes gorgeous eight-second clips and terrible thirty-second films. Anything longer that looks good was planned by a person and assembled from shots. The model supplied pieces.
Two ways in
Text-to-video takes a prompt and returns a clip. Fast to try, hard to control. Every run gives a different-looking person, room and color grade.
Image-to-video takes a still image (often one made and approved in a tool like ImageStudio) plus a prompt about motion: "slow push in, steam rising from the mug, she looks up." The look is locked by the still. The model only has to invent movement. For anything in a series, this is the usual choice.
Serious tools add more controls:
- First and last frame. The user supplies the opening and closing images and the model fills in the motion. Google's Veo 3.1 supports this.
- Extension. More seconds generated to continue an existing clip. Veo 3.1 can extend a Veo clip by 7 seconds at a time, up to 20 times, to a combined maximum of 148 seconds, at 720p only. Quality and consistency tend to sag with each extension.
The tools as of October 2026
This field moved fast enough this year that one of the best-known products, OpenAI's Sora, closed. The Sora app closed on April 26, 2026, according to a trade report (The Decoder), and OpenAI's developer docs say the Sora 2 models and Videos API were shut down September 24, 2026, with no direct replacement. Any older tutorial built around Sora is out of date.
| Tool | Clip length per generation | Resolution | Audio | Price signal (as of October 2026) |
|---|---|---|---|---|
| Google Veo 3.1 (Standard, Fast, Lite) | 4, 6 or 8 seconds; 1080p, 4K, references and extension need 8 | 720p default, 1080p, 4K (not Lite) | Native audio always on | Per second: Standard $0.40 (720p or 1080p), Fast $0.10 to $0.12, Lite $0.05 to $0.08; 4K costs $0.60 (Standard) or $0.30 (Fast) |
| Runway Gen-4.5 | 2 to 10 seconds | 720p | Not mentioned in Runway's help page | 12 credits per second; Runway's API lists $0.01 per credit, so $0.12 per second |
| Kling (Kuaishou) | 5 or 10 seconds per generation; extensions to 3 minutes total, per a third-party guide | Not confirmed; Kling's home page lists native 4K only for its Image 3.0 model | Kling bills 4.0 as "audio-visual" | Kling announced Kling 4.0 on its home page; check current prices on the site |
| Midjourney video | 5 seconds, extendable by 4 seconds up to 4 times (21 seconds) | 480p default, 720p on some plans | Not mentioned in Midjourney's docs | Uses plan GPU time; a batch of 4 SD clips costs 8 GPU minutes |
| Others on Runway's API menu | Varies | Varies | Varies | Seedance, Wan, Grok Imagine and MiniMax models range from about $0.02 to $1.50 per second depending on model and resolution |
Specs differ between a company's consumer app and its API, and third-party sites list conflicting numbers. Where this lesson leans on a third party (Kling's lengths, the Sora app date), treat it as approximate; the tool's own page has the current figure.
Worked example: budgeting a 30-second piece
Plan: nine shots, most 4 seconds, two at 3 seconds trimmed from longer clips. Each shot takes about three tries to get one keeper.
With Veo 3.1 Fast at 1080p ($0.12 per second), clips must be 8 seconds at 1080p. So: 9 shots x 3 tries x 8 seconds = 216 generated seconds. 216 x $0.12 = $25.92.
At 720p, 4-second clips are allowed at $0.10 per second: 9 x 3 x 4 = 108 seconds x $0.10 = $10.80. Upscaling 720p to 1080p in the editor is fine for social video.
With Runway Gen-4.5 at $0.12 per second and 5-second clips: 9 x 3 x 5 = 135 x $0.12 = $16.20.
Notice what dominates: the number of tries. Better stills and tighter prompts cut the bill more than any model choice.
Where AI video breaks
| Failure | What you see | What works better |
|---|---|---|
| Hands | Fingers merge, multiply or melt when hands move | Hands still, out of frame, or in pockets. "Counting on fingers," "typing" and "shuffling cards" fail most. |
| Physics | Water flows uphill, a cup passes through a table, a door opens both ways | Simple motion: slow pans, push-ins, steam, wind in grass. Pouring, catching and collisions fail most. |
| Text | Signs that re-spell themselves every frame | No text in the prompt; titles added in the editor |
| Identity drift | The face changes between the start and end of a clip, or between clips | Image-to-video from the same approved still; reference images; shorter clips |
| Crowds and backgrounds | Background people walk into each other or vanish | Empty or blurred backgrounds, few figures |
| Speech | Lips do not match words, voice sounds generic | Narration recorded or generated separately; no on-camera talking unless lip sync is the point |
How shots get planned
Producers who get usable results write a shot list before generating anything. Every shot gets a number, a length, framing, action and source.
Example: shot list for a 30-second explainer (opening)
| # | Length | Framing | Action | Source |
|---|---|---|---|---|
| 1 | 3 s | Wide, 9:16 | Slow push in on a small-town water tower at dawn | Image-to-video from ImageStudio still |
| 2 | 4 s | Medium | Rosa opens an envelope at a kitchen table, hands still after | Image-to-video |
| 3 | 4 s | Close | A water bill on the table; number added as a title in the editor | Still image held on screen, no AI motion needed |
| 4 | 3 s | Wide | Pipes in a trench, light rain | Text-to-video |
Shot 3 uses no video model at all. A still costs nothing and never melts.
Other habits explain why some AI video looks cleaner than the rest:
- Clips are generated a little long, 6 or 8 seconds for a 4-second shot, and trimmed. The first and last half-second are often the weakest.
- Aspect ratio matches delivery. Veo 3.1 offers 16:9 and 9:16, and a clip made in the wrong shape loses its subject when cropped.
- Frame rates match. Veo outputs 24 fps; Runway Gen-4.5 offers 24 or 25. Mixed rates on one timeline can stutter.
- A log records prompt, model, seed if any, date and which take was used. Honest disclosure depends on it.
Stitching it together
The generator is not an editor. The keepers get assembled on a timeline.
VideoStudio runs in the browser and does not upload files. It trims a clip with in and out handles, splits at the playhead, mixes or replaces audio tracks, adjusts color, and can build a slideshow video from 1 to 10 images with "Create Video." It exports MP4 and other formats at presets from 360p up to 4K. It opens one video at a time, so a multi-clip piece means trimming each clip there and joining them elsewhere, or using the slideshow builder for a still-based piece.
AVPrep3, the desktop timeline editor, is the better fit for a multi-clip piece. It has multiple lanes, crossfades and fades from black, "Add Title" with text presets, captions that can be transcribed, edited and burned in, volume and ducking of music under speech, platform export presets and a target file size option. Its "Images to Video" tool turns stills into clips.
A few editing facts matter for AI clips in particular. A cut during a camera move hides seams between shots. Crossfades between AI clips often show two different worlds melting together, which is why straight cuts are the norm (the AV chapter what a transition says explains the grammar). Narration and music sit on their own lanes (lesson 6), numbers and names arrive as titles rather than generated text, and the AI disclosure appears as an on-screen title (lessons 4 and 7).
Reporting angle
When a campaign or agency releases an AI video, ask for the project log, the tool and model, the prompts and the source files. Check whether it carries the platform disclosure label. Per-second prices are public, so a contract that pays far above list price is worth a question. Providers also retire products: ask what happens to a department's video work when a service shuts down, as OpenAI's Sora did.
Research angle
- Google Gemini API docs: Veo: durations, resolutions, reference images and SynthID.
- OpenAI API docs: Video generation: the Sora 2 shutdown notice and usage restrictions.
- The Decoder: Sora shutdown: the report on the two-stage Sora shutdown dates.
- Runway API pricing: credits per second by model.
- Google Gemini API pricing: list prices per image and per second of video.
- YouTube Help: Disclosing altered or synthetic content: when a creator must label synthetic media.
Common mix-ups
- Claim: Typing a script gets a finished ad. What the evidence shows: Some apps chain shots automatically, but control over each shot is poor. Professionals still plan shots and edit.
- Claim: Higher price means fewer failures. What the evidence shows: Better models fail less, but every model fails on hands and physics. Simple motion helps more than spending.
- Claim: Native audio means no voice work is needed. What the evidence shows: Generated audio is good for ambience. Narration with exact wording is generated or recorded separately.
Check yourself
1. Why does image-to-video usually give more control than text-to-video?
Starting from an approved still locks the look. The model only has to invent motion.
2. As of October 2026, Google lists Veo 3.1 Fast at $0.12 per second for 1080p with audio. What do six 8-second clips cost?
6 clips x 8 seconds = 48 seconds. 48 x $0.12 = $5.76.
3. What happened to OpenAI's Sora 2 API in 2026, according to OpenAI's developer docs?
OpenAI's docs say the Sora 2 models and Videos API were shut down September 24, 2026; the Sora app closed in April.
4. Which method produces readable on-screen text in an AI video most reliably?
Text in generated video often warps from frame to frame. Titles added in VideoStudio or AVPrep3 stay sharp and spelled right.
5. Why is a 30-second AI piece usually built from eight or nine short clips instead of one long generation?
Clip limits, drift and cost all point the same way: short, planned shots joined on a timeline.
6. Google's Veo docs say generated videos carry what?
Google states Veo videos are watermarked with SynthID.
Terms in this lesson
- Text-to-video
- Generating a video clip from a written prompt alone.
- Image-to-video
- Generating motion from a starting still image, usually with a prompt describing the movement.
- First and last frame
- A control where the user supplies the opening and closing images and the model invents the motion between them.
- Extension
- Generating more seconds that continue an existing clip.
- Shot list
- A numbered plan of every shot: length, framing, action and source, written before generating.
Sources
- Google Gemini API docs: Veo (durations, resolutions, reference images, extension, SynthID) checked 2026-10
- Google Gemini API pricing (Veo 3.1, Fast, Lite per-second prices) checked 2026-10
- OpenAI API docs: Video generation (Sora 2 shutdown notice, restrictions) checked 2026-10
- The Decoder: OpenAI sets two-stage Sora shutdown checked 2026-10
- Runway Help: Creating with Gen-4.5 checked 2026-10
- Runway API pricing (credits per second by model) checked 2026-10
- Midjourney docs: Video checked 2026-10
- Atlas Cloud: Kling AI video length limit by version (August 2026) checked 2026-10
- Kling AI home page (Kling 4.0 announcement) checked 2026-10
- VideoStudio (Journal Tools) checked 2026-10
- AVPrep3 help checked 2026-10