Answers
Why must an edited AI video keep the exact length of the source?
Short answer
Because the length is validated after the clip is generated, not before. If the result does not match the requested duration to within a tenth of a second, the whole job is failed upstream — minutes of compute wasted. So an edit inherits the source's length instead of taking it from the form, and sources are trimmed to whole seconds before they are sent.
- Rule
- An edited clip comes out the same length as its source
- Validation tolerance
- 0.1 seconds, checked after generation
- Source handling
- Trimmed to whole seconds before upload
- Minimum source length
- About 3 seconds
- Model input limit
- 10 seconds for an edit (a scene extension reads the whole clip, up to 37 s), 720p
- If it fails anyway
- Full automatic refund
Facts on this page were checked against the live platform on .
What the error actually says
The upstream message is explicit: *Edited video duration (9.958s, rounded to 1st decimal: 10s) does not match config duration (7s)*. The validator compares the produced file against the duration in the request and rejects a mismatch — after the model has already done the work. Two to five minutes gone, and the only thing that changed was a number in the request.
The tolerance is a tenth of a second, and the comparison rounds. That is why a 3.167-second source declared as 3 seconds fails — 3.125 rounds to 3.1, not 3.0 — while 9.958 declared as 10 passes.
How the platform avoids it
Two rules, applied everywhere a video can enter an edit. First, duration is never taken from the form when editing: a conversational edit inherits the parent generation's actual length, and a video-to-video edit is measured from the file itself.
Second, every source is trimmed to a whole number of seconds before it is sent — a hard cut at N seconds produces exactly N.000, which removes the rounding ambiguity entirely. That applies to uploads, to clips picked from your history, and to sources fetched by URL through the MCP tool alike. Sources shorter than about three seconds are rejected rather than padded, because below that the length no longer rounds to a legal value.
The price follows the same logic: you are billed for the effective duration of the result, not for whatever the form last showed. The final charge is always the amount recorded on the finished generation.
What if I need the clip to be longer?
Editing is not the tool — extension is. Since September 2026 Omni Flash runs on the 1.1 generation, which has a separate *extend* task: pick a finished clip, choose Extend, and the model appends 3–10 seconds to its end, reading the whole source first. Chain it and the clip grows to 40 seconds. It is a different job from an edit, and it is the only way an Omni clip gets longer; the original 1.0 generation refuses the task outright with *This model does not support video extension*.
For a longer continuous take than that, use Veo 3.1 extensions: each adds 7 seconds to an existing clip and they can be chained up to 148 seconds. Or cut several clips together; conversational editing keeps the character and lighting stable enough across shots that the cuts hold up.
Where this is documented
Longer reads on the same thing
More on this question
Can I trim the source myself first?
You can, and a source that is already a whole number of seconds passes straight through. The trim happens server-side regardless, so it is not required.
What is the longest clip I can edit?
Ten seconds. Longer sources are cut down to the model's input limit before the request is sent.
Does editing cost less than generating?
No — it is priced per second like any other generation, from the effective duration of the result.
Can I edit a Veo clip on Omni Flash?
Yes. Any finished video you own can be sent as a video-to-video source, regardless of which model made it.
Questions next door
How long can a Gemini Omni Flash video be?
Three to ten seconds per clip, set to the exact second, with a synchronised audio track that cannot be turned off. Asking for 3 seconds really does produce a 3.0-second file and bills a third of a 10-second one. Since the 1.1 generation (September 2026) a finished clip can be extended: each pass appends 3–10 seconds to the end, and the chain stops at 40 seconds. Edits still keep the source length.
Read the answerDo I get my money back when an AI generation fails?
Yes, automatically and in full. The charge happens when a generation starts and is reversed the moment it is marked failed — upstream errors, capacity errors and content-filter rejections all refund without a support ticket. A batch that is only partly rejected is refunded proportionally. There is nothing to claim and no waiting period.
Read the answerCan I cancel an AI video generation that is already running?
No, and not because of a missing button. Google's video APIs expose no working cancel operation — the request answers 501 Unimplemented, and delete is rejected outright. Once a generation starts it runs to completion or fails. A failure is refunded in full, so a mistake costs you the wait rather than the money.
Read the answerTry it on your own prompt
New accounts start with $0.20 of balance — no card, nothing expires.