How to Make Gemini Omni Flash Videos Longer Than 10 Seconds
Need longer than Omni 1.1's 40-second scene extension? Storyboard stitching and last-frame chaining for 60s+ videos, with real API cost math.
Quick Answer
Gemini Omni Flash still generates 3–10 seconds per request. Gemini Omni 1.1 Flash added native scene extension to 40 seconds — continue a clip in 10-second steps, with 10 seconds of prior context. This page is the 40-second-and-up playbook. Once extension tops out — a 60-second ad, a Short with real cuts, a scene the model won't hold — you chain shots yourself: plan a sequence of ≤10-second clips, keep continuity with a last-frame chain (the final frame of clip N becomes the image input for clip N+1), and assemble in an editor. Two of the three methods need no code. A 60-second video costs about $6 raw at $0.10/second, more with retakes.
If you only need 10–40 seconds of one continuous take, stop here and use scene extension instead.
Key Takeaways
- The 10-second cap is per generation, not per video. Native scene extension stretches one take to 40 seconds; everything longer is still a chain.
- Use native extension for 10–40 seconds. This guide starts where that wall is.
- Last-frame chaining is the continuity workhorse past 40s: export the final frame of one clip, use it as the starting image of the next. It works in a browser studio and in the API, and it's the only method with no length ceiling.
- Refine vs continue.
"Make the jacket red"re-edits the same clip."Continue the scene"on 1.1 appends, up to 40 seconds. Neither replaces chaining past that. - Don't waste money prompting a fresh take for "60 seconds." A new request still returns ≤10 seconds. Extend, then chain.
- Budget ~$6 per raw minute via the API (6 × 10s at $0.10/second) — realistically $10–15 with retakes, before editing time.
- No code required: methods 1 and 2 work entirely in a browser workflow — plan shots, generate, chain frames, stitch.
Why every clip stops at 10 seconds
The Gemini Omni Flash API (now GA as gemini-omni-1.1-flash; legacy preview string gemini-omni-flash-preview) generates 3–10-second base clips at 720p, billed at ~$0.10 per second of output. The same per-generation cap applies in the Gemini app, Google Flow, and YouTube Shorts.
1.1 added native scene extension to 40 seconds — 10 seconds of context per step, uploaded sources still ≤10 seconds, video references still capped at 3 seconds (style and motion, not extra length). Past 40 seconds — a YouTube Short, an ad, a scene with real cuts — length is a workflow problem, and the workflow is well understood.
Method 1: Storyboard and stitch (no code)
The professional default. Instead of fighting for one long take, write your video as a shot list where every shot fits inside 10 seconds:
- Script the beats first. A 45-second product video is typically 5–6 shots: hook, problem, product reveal, feature close-up, social proof, call to action.
- Write one prompt per shot, keeping the style block identical across all of them — same lighting description, same camera vocabulary, same color grade. Our prompt templates are structured exactly for this.
- Generate each shot separately, retaking only the shots that miss.
- Assemble in any editor — CapCut, Premiere, DaVinci Resolve, or YouTube Create. Hard cuts between shots read as intentional filmmaking; nobody watching a cut expects one continuous take.
This is also how you sidestep the cap's real cost: when shot 4 of 6 fails, you re-roll one $1.00 clip, not a whole minute. The full planning workflow — hooks, pacing, stitching for 9:16 — is in our YouTube Shorts playbook.
Where it breaks: across hard cuts, the model has no memory. If the same character or product must appear in every shot, you need reference discipline — which is Method 2's job.
Method 2: Last-frame chaining (no code)
When you need continuity — the same subject, the same scene, motion that flows across the 10-second boundary — chain the clips:
- Generate clip 1 (up to 10 seconds).
- Export its final frame as an image (any video player or editor can do this; in a browser studio it's a right-click).
- Start clip 2 as image-to-video with that frame as the starting image, plus a prompt describing what happens next: "continuing the same shot, she turns from the window and walks toward the door, same lighting, same color grade."
- Repeat. Stitch the clips end-to-end — the seams land on identical frames, so the joins are nearly invisible.
Because each link starts from your exact previous frame, the subject, composition, and grade are locked by the image rather than re-invented from text. That's the same property that makes image-to-video the most reliable path to on-brand video — chaining just applies it repeatedly.
Three craft rules that decide whether the seam shows:
- Cut on stillness, not motion. End each clip on a natural pause (a look, a landing, a held pose). A frame grabbed mid-motion-blur makes a mushy start for the next clip.
- Restate the style block every link. The image carries composition; the prompt still controls motion and mood. Drop the style text and the grade drifts by clip 3.
- Carry a character reference alongside the frame if a face must survive many links — technique in the consistent characters guide.
Where it breaks: audio. Each clip generates its own synchronized audio, so a chained sequence has audio seams even when the picture flows. For anything dialogue- or music-led, mute the generated audio and lay a continuous voiceover or music bed over the stitched cut — standard practice for Shorts anyway.
Method 3: Chaining via the API (code)
The programmatic version of Method 2, for anyone building length into a product. Each link is an image-to-video call whose input image is the last frame of the previous output — extract it with ffmpeg -sseof -0.05 -i clip1.mp4 -frames:v 1 last.jpg, then pass it as the image part of the next request. Setup, parameters, and working Python/JavaScript/curl for image-to-video calls are in the API tutorial.
Don't confuse this with 1.1 scene extension. On gemini-omni-1.1-flash, previous_interaction_id plus "Continue the scene" does append, up to 40 seconds — that's the scene-extension path. The same ID plus "make the jacket red" still refines the current clip. Use interactions to perfect each link and to native-extend while you're under 40 seconds; use last-frame chaining to add the 41st.
What a 60-second video actually costs
At $0.10 per second of output, length is a budget line, not just a technical limit:
| Final length | Clips (10s) | Raw API cost | Realistic (≈2× with retakes) |
|---|---|---|---|
| 20 seconds | 2 | $2.00 | ~$4 |
| 30 seconds | 3 | $3.00 | ~$6 |
| 60 seconds | 6 | $6.00 | ~$12 |
Two ways to keep the multiplier near 1×: lock look-and-feel on cheap stills before rendering motion (the Nano Banana 2 Lite → Omni Flash pipeline exists for exactly this), and remember that conversational-edit turns bill like generations — three edits on a 10-second clip is $4.00 total, not $1.00.
If you'd rather not manage API keys, quota panels, and ffmpeg: Omni Flash runs this whole loop — prompt templates, image-to-video for frame chaining, per-clip credits — in the browser. It's an independent platform (not affiliated with Google) that generates on available advanced models such as Veo 3.1 with the same shot-based workflow, so your storyboards and chains port straight across model generations. Credit packs map one-to-one onto the clips-per-video math above.
FAQ
Can Gemini Omni Flash generate videos longer than 10 seconds?
Not in a single generation — 3–10 seconds per request remains the base cap. Scene extension continues a clip up to 40 seconds. Beyond that, longer videos are made by generating multiple clips and joining them — that's this page: storyboard stitching or last-frame chaining.
Does conversational editing make a video longer?
Depends on the prompt. "Make the jacket red" on previous_interaction_id re-edits the current clip at the same length. "Continue the scene" on 1.1 is native extension — it appends, up to 40 seconds. Past that, chaining is still the only path.
Can I feed a finished clip back in and ask it to continue?
Up to 40 seconds, yes — that's native scene extension (upload ≤10s, or continue a clip you just generated). Past 40 seconds, fall back to the still-image path: the last frame of your previous clip as the image input for the next one.
How much does a 1-minute Omni Flash video cost via the API?
About $6.00 in raw output (6 × 10-second clips at $0.10/second); plan $10–15 once retakes are included. Each conversational-edit turn bills at the same per-second rate.
Do I need to write code to make longer videos?
No. Storyboard stitching and last-frame chaining both work in a browser: generate clips, export final frames, re-upload them as image-to-video starts, and assemble in any editor — or run the whole loop in the Omni Flash studio.
Is Omni Flash affiliated with Google?
No. Omni Flash is an independent platform built for the Gemini Omni era and is not affiliated with Google. Gemini, Gemini Omni, Omni Flash, Veo, and related names are trademarks of their respective owners.
Next steps
- Try the Omni Flash studio → — shot-based generation and image-to-video chaining in the browser, no API key required.
- Read: How to extend Gemini Omni 1.1 Flash to 40 seconds → — native scene extension: prompts, API, cost. Use that first if you don't need past 40s.
- Read: Image to video with Gemini Omni Flash → — the technique last-frame chaining is built on.
- Read: Gemini Omni Flash API tutorial → — model ID, pricing, and working code for programmatic chaining.
- Read: The YouTube Shorts playbook → — planning, stitching, and audio for short-form.
- Read: Consistent characters guide → — keeping a face stable across a long chain.
- Compare credit packs → — budget clips-per-video without managing preview quotas.