I had a whole scene in my head. A woman walks into a rain-soaked alley, neon signs buzzing, she looks up, and the camera pulls back to reveal the city. Maybe forty seconds. Cinematic. I'd read that Veo 3.1 could do "up to a minute," so I figured one good prompt would get me most of the way there.
The clip it gave me back was breathtaking. The rain looked real. The neon reflected in the puddles. There was even ambient sound, the hiss of wet tires, a distant car horn, generated automatically.
It was also exactly eight seconds long. And that turned out to be the whole story.
What Veo 3.1 actually is
Let me back up for anyone who hasn't tried it yet.
Veo 3.1 is Google DeepMind's video generation model. You give it a text prompt or a starting image, and it generates a short, cinematic clip, in 1080p, with synchronized audio it creates itself, including dialogue, sound effects, and ambient noise. It does both text-to-video and image-to-video, and the motion and lip-sync are noticeably better than the version before it. Here's the number that matters most, and the one the marketing pages bury: a single generation is about eight seconds long. On the tool I used it costs 35 credits per clip, and new accounts get some free credits to start.
Eight seconds of genuinely film-grade footage from one sentence is, objectively, remarkable. A shot like that used to mean a camera, a location, and an afternoon. I got it in a couple of minutes for free.
The trouble started when I wanted the ninth second.
The "up to a minute" fine print
Here's what I learned, and what I wish the landing page had said plainly.
Veo 3.1 does not generate a one-minute video in a single shot. What it offers instead is scene extension: it takes the last moment of your clip and generates the next eight seconds from there, and you can repeat that, stitching extensions together, up to around twenty times. That is how you get to "a minute."
Google's own page is honest about this, it describes extending clips "into longer, more dynamic videos" by continuing from the last second of the previous shot. The tool I tried it on, imagvio.ai/veo3-1, which runs Google's model and is upfront that it isn't Google itself, actually contradicts itself on this point: one table implies you can get roughly a minute, and then the FAQ admits clips are capped at eight seconds and length comes from extension. Both things are true at once, which is exactly why people get confused.
So the mental model isn't "write a prompt, get a minute." It's "generate eight seconds, then extend, then extend again, guiding it each time." That's a different craft. Closer to editing than to wishing.
Why the wall actually matters
It changes what you should try to make.
When I stopped fighting the eight-second limit and started designing for it, the tool got dramatically more useful. A single dramatic beat. A product turning in the light. A logo animation. A establishing shot to drop into a longer edit. Those are eight-second jobs, and Veo 3.1 nails them.
My forty-second continuous alley scene, with a consistent character and a moving camera the whole way, is where the seams show. Each extension drifts a little. The neon shifts. The rain changes character. It's the same reason a relay race isn't the same as one runner going the whole distance.
When Veo 3.1 (free) is enough
From my week with it, here's the honest line.
It's plenty when you want:
- A single cinematic clip, a b-roll shot, or a social video under ten seconds
- Native audio without a separate step
- To test whether an idea looks good on screen before committing real budget
Don't expect it to:
- Produce a finished one-shot film longer than eight seconds
- Hold perfect consistency across many stitched extensions
- Give you 4K here, the model can do 4K, but the tool I used caps at 1080p, so check what your app actually offers
And the usual note on "free": it means free credits, not unlimited. At 35 credits a clip you'll test a handful of ideas, which is the point. Production volume is a paid plan, and that's fair.
What I'd tell myself before starting
If you're about to try it:
- Plan in eight-second beats, not minutes. Design the shot, not the movie.
- Use a start or end frame when you can, it gives the model something concrete to hold onto.
- Extend deliberately, not hopefully. Each extension is a new prompt, guide it.
- Keep the clips you love. The best eight seconds is often better than a shaky stitched minute.
- Decide up front: one strong shot, or a stitched sequence? That choice changes everything downstream.
The clip I kept
I never made my forty-second alley scene. What I kept instead was that first eight-second clip, the woman, the rain, the neon, the sound of the city, and it's genuinely beautiful. I just had to let go of the minute I'd imagined to see it.
That's the quiet lesson of Veo 3.1 right now. It's not a movie machine. It's the most astonishing eight-second camera ever built, and if you make peace with eight seconds, it will hand you things that used to cost a crew.
So before you start: what's the one shot, not the whole film, the one shot you'd want to see come alive?
If you liked this, I write up the AI tools I actually test, the honest version, not the landing-page version. Follow along and I'll send the next one.
Top comments (0)