Comparisons

    Veo 3.1 extend is 7s at 720p

    Veo 3.1 extend is 7s at 720p for 40 credits with native audio. Not Omni 1.1 Flash 40s, not Flux 3 extend.

    Versely Team••8 min read

    VEO 3.1 Extend Video is 40 credits, 7 seconds, 720p, native audio. That is the whole row. It is not Google’s Gemini Omni 1.1 Flash 40-second cumulative extend (Google, 27 August 2026; no Versely slug). It is not Flux 3 Extend Video at 21 credits, 5–20 seconds, native audio. You are buying one seven-second hop at 720p.

    Veo 3.1 generate is 40 credits, 4 / 6 / 8 seconds, 4K, native audio. Same sticker, different object. Generate makes a new 4K plate. Extend continues a clip you already have, for seven seconds, at 720p. Teams that treat “Veo” as one slider between eight seconds and a minute are reading a Google blog post onto the wrong card.

    Seven seconds at 720p, 40 credits

    Catalog: slug veo3-1-extend-video, category extend-video, audio true, duration list is the literal 7s, resolution 720p, 40 credits. Description: extend video duration with VEO 3.1. Input is a clip, not a still. You are not buying a duration menu. You are buying seven seconds.

    Write the next beat that can play from the last frame you kept. A three-act story does not compress into a hop. Belt travel continues, a speaker finishes a sentence, the camera holds. New blocking is a generate. New identity is a generate.

    Native audio is on. Picture and soundtrack continue together. If the source already has a voiceover you did not want, the hop is seven more seconds of that voiceover. Fix the source first. A silent brief still returns audio you did not choose. Say the room, or say no speech, in the instruction you actually send.

    Aspects on the family include 16:9 and 9:16. Match the source. Extending a 9:16 take into a 16:9 hop is a crop, not a feature.

    Forty credits is the same number as a Veo 3.1 generate. Do not pick extend because generate “felt expensive.” Generate’s 40 credits buy 4 / 6 / 8s at 4K. Extend’s 40 credits buy 7s at 720p of a file that already exists. If the take is wrong, 40 credits of hop will be seven seconds of wrong. Re-generate. If the take is right and short, hop.

    The AI video generator is the run door for the generate. Extend is the continue door on a keeper. Caption after the file exists. Native audio does not typeset a muted feed. Add captions to video.

    Do not stack hops as a substitute for a 30-second model. Two hops are 80 credits and a seam. Three hops are 120 credits and two seams. Seedance 2.5 is 47 credits, 4–30 seconds, 720p, native audio, one pass. Grok Imagine Video is 7 credits, 6 / 10 / 15 / 20 / 30 seconds, 720p, native audio, one pass. If the brief was always thirty seconds, those rows are the brief. Veo extend is a hop on a Veo keeper.

    Not Omni 1.1 Flash's 40-second cumulative

    Google’s developer post on Gemini Omni 1.1 Flash (27 August 2026) describes model id gemini-omni-1.1-flash. Scene extend: up to 10 seconds of prior context (was the last second only); extend in 10-second increments to a cumulative 40 seconds. Output video 3–10 seconds per increment, 360p / 720p / 1080p / 4K, 24 fps. Access: AI Studio, Gemini Enterprise Agent Platform, Flow Plus/Pro/Ultra, Gemini app for extend.

    That is Google’s surface. Versely does not publish /models/gemini-omni-1-1-flash. Do not write that slug in a brief. It will not resolve.

    Versely’s published Omni rows are generate and edit, not this hop:

    • Gemini Omni Video — 9 credits, T2V / I2V / R2V, 4K, 4 / 6 / 8 / 10 seconds. Audio null. A generate, ceiling 10s.
    • Gemini Omni Flash Edit — 13 credits, edit-video, audio false. A delta on a keeper, not an extend-video slug.

    Do not import Google’s 40-second cumulative as something Veo extend will do in one 40-credit click. Veo extend is 7s. Do not import it as something Omni Video will do at 9 credits. Omni Video lists 4 / 6 / 8 / 10s.

    Flow will show you Veo and Omni. The catalog shows you which job. Google Flow is a Veo surface, not a studio. Keep Veo. Do not live in Flow. Do not live in a 40-second sentence Google wrote for a model id we did not publish.

    If you need Google’s 10-second increments to 40 seconds, that work happens on Google’s doors. On Versely, a long native-audio pass is Seedance 2.5, Grok Imagine Video, or Flux 3 Text to Video (9 credits, 5–20s, native audio). A Veo-shaped continue is this 7s hop.

    Not Flux 3 extend

    Flux 3 Extend Video is 21 credits, 5–20 seconds, native audio, category extend-video. Black Forest Labs called FLUX.3 Video generally available on 4 August 2026. The catalog description: FLUX.3 continues an existing clip beyond its final frame; source clip must be MP4, under 50 MB and under 15 seconds.

    That is a different continue. Different family, different sticker, different duration menu, different source constraint.

    Veo extend versus Flux 3 extend:

    • Credits. 40 versus 21.
    • Duration. 7s locked versus 5–20s.
    • Resolution. Veo extend lists 720p. Flux 3 extend has resolution unset on the card. Do not invent 4K for either hop.
    • Audio. Both true. Both continue sound with picture.
    • Source family. Stay in the family of the keeper. A Veo take continued on Flux will often show the seam as a look change. A Flux take continued on Veo will often show the same. The hop is not a translator.

    Pick Flux 3 extend when the keeper is a Flux 3 file and you want 5–20s more with native audio, inside the MP4 / 50 MB / under-15s source rule. Pick Veo extend when the keeper is a Veo file and seven seconds at 720p is the next beat. Do not pick Veo extend because you heard “Google extend” and meant Omni 1.1 Flash. Do not pick Veo extend because it is 40 credits and Veo generate is 40 credits so they must be interchangeable.

    Grok Imagine Extend is a third continue: 8 credits, 2–10 seconds, audio false. Silent cheap hop on an Imagine keeper. Not this page. If the Veo take has a voice you need to keep, Grok’s silent extend is the wrong family and the wrong audio flag.

    A hop, not a longer Veo generate

    Veo 3.1’s generate ceiling is 8 seconds at 4K. That is the model’s published T2V menu: 4 / 6 / 8s. Extend does not raise that ceiling to a 4K minute. It adds 7s at 720p onto a clip.

    Practical order:

    1. Generate the Veo plate at 4 / 6 / 8s, 4K, 40 credits, until the last frame would ship as a still.
    2. Inspect audio. If the line is wrong, re-generate. Do not hop a bad line.
    3. If the next beat is seven seconds of the same identity, run extend, 40 credits, 720p.
    4. Caption the finished file. Burn the line. Caption styles after the hop, not inside the prompt.

    Do not hop because you wanted 4K longer. The hop is 720p. A 4K eight-second generate plus a 720p seven-second hop is a resolution seam as well as a time seam. If the master must stay 4K, you need a different plan: recut, a different 4K model with a longer menu (LTX 2.3 Fast is 4 credits, 6–20s, 4K, native audio), or accept 8s.

    Do not hop because the first take was 4s and you wished it were 30s. The brief was 30s. Change the row.

    One 7s hop on a locked Veo keeper is the job this slug sells. A 40-second Omni story is Google’s job on Google’s id. A 5–20s Flux continue is Flux’s job. Keep the names on the right cards.

    Run the 7s 720p Veo hop from Versely.

    FAQ

    Can Veo 3.1 extend run past seven seconds in one click?

    No. The duration list is 7s. Another click is another 40 credits and another hop. If you need 20–30 seconds in one pass, use a generate row that lists that ceiling.

    Is this the same as Gemini Omni 1.1 Flash scene extend?

    No. Omni 1.1 Flash’s 10-second increments to 40 seconds cumulative are Google’s 27 August 2026 surface. Versely does not publish that slug. veo3-1-extend-video is 7s, 720p, 40 credits, native audio.

    Why is extend 40 credits when generate is also 40 credits?

    Same sticker, different object. Generate is 4 / 6 / 8s at 4K. Extend is 7s at 720p of an existing clip. The number does not make them substitutes.