How to extend an 8s Veo clip

Veo 3.1 tops out at 8 seconds. The published extend row, VEO 3.1 Extend Video, adds 7 seconds at 720p with native audio, at 40 credits. That is not Gemini Omni 1.1’s 10-second increments to a 40-second cumulative chain. Decide extend versus a new generate versus a storyboard before you spend a second 40-credit pass on a clip that should have been a different row.

This page is the decision and the steps. It is not Omni’s draft loop, and it is not Seedance’s 30-second single pass.

What the extend row actually is

Read the card, not a Google blog post about a different model.

Row	Job	Duration	Resolution	Audio	Credits
Veo 3.1	T2V	4 / 6 / 8s	4K listed	Native audio	40
VEO 3.1 Extend Video	extend-video	7s	720p	Native audio	40

The generate can be 4K. The extend is 720p. If you needed 4K for the whole piece, extending is a resolution drop on the tail, not a longer 4K shot. Plan for that, or do not extend.

Google’s Omni 1.1 Flash (Keyword post, 27 August 2026) extends in 10-second increments with up to 10 seconds of prior context, to a 40-second cumulative cap. That is a Google surface: AI Studio, Gemini Enterprise Agent Platform, Flow, Gemini app. Versely does not publish a gemini-omni-1-1-flash slug. Do not expect the Veo extend row to behave like Omni. Seven seconds, 720p, one increment you can actually buy here.

Extend video length is the editing-job door. The model under it, when you pick Veo extend, is still that 7s / 720p / 40-credit card.

What extend is for:

The 8-second take is the keeper. The action is unfinished: a pour that needs the glass to fill, a walk that needs the doorway, a line that needs the last clause.
The last frame still has motion. Extend conditions on the end of the source. A dead hold gives the model nothing to continue.
You will accept 720p on the added seconds, or you will upscale later as a separate job.

What extend is not for:

Turning 8 seconds into a 40-second ad. Two Veo extends is 8 + 7 + 7 if you chain, and drift compounds. The catalog still is not Omni’s 40s cap.
Changing the shot. New blocking, new SKU, new speaker: that is a new generate.
Fixing a bad 8 seconds. Extend copies the identity of the tail. A wrong face extended is a longer wrong face.

When to extend the keeper

Run this list. If you fail a line, stop and pick another door.

The 8-second file is approved. Face, product, lighting, line. You would ship it if the brief were 8 seconds.
The missing time is the same shot. Same camera, same subject, same beat continuing. Not a cutaway. Not a second location.
The last second is in motion. A hand still moving, a head still turning, a liquid still pouring. Pause on the last frame. If it is a still, trim back to motion or do not extend.
Seven more seconds is enough. If you need twenty, you are in the wrong family. Seedance 2.5 lists 4–30 seconds at 720p with native audio, 47 credits. That is a different generate, not a Veo tail.
720p on the tail is acceptable, or you have an upscale pass in the plan. Do not discover the resolution drop at upload.

Then:

Export or keep the Veo 3.1 take as the source. Do not caption it yet. Burned type on the source will be in the conditioning frames.
Open the extend row. Attach the clip. Do not paste a new screenplay into the box and expect a cut. The job is continuation.
If the row takes a prompt, describe only what continues: the pour finishes, the walk reaches the door, the last clause is spoken. Do not introduce a second character.
Generate the 7-second tail (40 credits).
Watch the join at full speed, then scrub. Colour, face, and label should survive. A teleport at the seam is a failed extend, not a “jump-cut style.”
If the join holds, concatenate. If it does not, do not extend again from the bad tail. Go back to the approved 8-second file or generate new.

Audio is native on this extend card. The tail will make sound. If the source line was exact and the tail invents a second sentence, you now have a dialogue problem. Listen before you caption. Caption after the concat is locked.

One extend is the honest use. A second extend is already a drift bet. A third is how people spend 120 credits to avoid storyboarding.

When to generate new instead

Generate new when the 8-second clip is not a keeper, or when the next seconds are a different shot.

New generate, same row (Veo 3.1, 40 credits, 4/6/8s, 4K, native audio) when:

The take is almost right but the face, the label, or the line is wrong. Extend will not correct those. It will continue them.
You want 4K on the whole piece. The extend is 720p.
You want a different 8-second composition, not more of this one.

New generate, different row when:

You need 15–30 seconds in one pass. Seedance 2.5 is the 30-second 720p native-audio door at 47 credits. Seedance 2.0 is 4–15 seconds at 1080p, 69 credits.
You need a product still to hold. That is I2V or R2V, not a Veo T2V extend.
You need silent cheap drafts. Kling 3 Turbo is 12 credits and silent. Do not extend Veo to “try a longer version” of a prompt you have not locked.

Do not extend a miss hoping the seventh extra second will invent the product you forgot to show. The missing SKU is a still and an I2V job, or a new 8-second prompt that actually names it.

A new 8-second Veo at 4K is often cheaper in attention than an 8+7 concat you will fight in the grade because the tail is 720p and the head is 4K. Match resolution on purpose. Either upscale the tail, downscale the head for a 720p master, or do not join them.

Storyboard when one clip is the wrong object

If the brief is a 20–30 second ad with three beats — hook, proof, CTA — you do not have an extend problem. You have a storyboard problem.

Write the beats as shots:

Hook (2–3s): the claim or the pattern interrupt.
Proof (4–8s): the product doing the thing, or the face saying the specific.
Hold / CTA (2–4s): the pack, the URL, the next step.

Generate each shot on the row that fits it. Concatenate in an editor. Caption once on the combined file.

Veo extend is for this shot, unfinished. Storyboard is for these shots, in order. Omni 1.1’s 40-second cumulative extend (Google, 27 August 2026) is still not a storyboard. It is a longer continuation on Google’s surface, with drift across increments. A 30-second Seedance 2.5 pass is a single generate with a beat list in the prompt. Pick the object:

Same camera, 8s keeper, need ~7s more → Veo extend.
Same idea, 8s is a miss → new Veo generate.
Three beats, one ad → storyboard, or one Seedance 2.5 pass if 720p and 30s is the spec.

Do not chain Veo extends until the file is “long enough for Creativity Program.” Length from drift is not a program strategy. Write the piece, then pick the row that can hold it.

When the concat is the piece, caption after the join. If you need the studio to run the extend row and finish the file, sign up. Bring the approved 8-second take. Do not bring a prompt and expect 40 seconds of Veo.

FAQ

Does Veo extend go to 40 seconds like Omni 1.1?

No. The published Versely row is 7 seconds, 720p, 40 credits. Omni 1.1 Flash’s 10-second increments to 40 seconds cumulative is Google’s 27 August 2026 claim on Google’s surfaces. There is no Omni 1.1 catalog slug here.

Will the extended tail stay 4K?

No. Veo 3.1 lists 4K on the generate. The extend card lists 720p. Plan an upscale, a 720p master, or skip extend if 4K on the whole piece is required.

Should I caption before I extend?

No. Burned captions become pixels in the source. The extend will try to continue them as texture. Extend, concat, then transcribe and burn.