Veo 3.1 Prompts: How to Get a Film, Not a Slideshow

Veo 3.1 prompts explained: how to build a request, direct camera movement, set lighting and sound, and why skimping on detail kills the shot.
Veo is less forgiving than most other models. Feed it a short, lazy prompt and you get a pretty but empty shot with no movement and no point. Feed it a detailed one and it works like a cinematographer with a budget. Veo 3.1 prompts live or die on detail, so let's break down what building blocks go into one. I covered the general prompt structure in my AI video prompting guide; this piece is about what's specific to this model.
What a Veo 3.1 Prompt Is Made Of
A working prompt for Veo 3.1 rests on five layers. Scene and subject: what's in frame, what product, what setting. Action: what's happening, where the object or person is moving. Camera: static, slow push-in, orbit, lateral tracking shot. Light and mood: soft morning light, backlit, studio lighting, warm evening glow. And sound, because Veo handles native audio: street noise, footsteps, the click of a lid closing.
The more specific each layer, the less room the model has to guess on its own. "Nice video of a sneaker" gets you nothing. "A sneaker on a concrete slab, slow orbit left to right, backlit, a little dust in the air, muffled city noise in the background" gets you a shot.
Where Veo Beats Everyone Else
Premium visuals and lighting are its strong suit, so it's worth packing cinematic details into the prompt: depth of field, rim light, reflections. Native audio is a separate strength: describe the sound environment, not just the visuals, or you'll end up with silence or some random background noise. For more on what it can do, see our Veo 3.1 review.
What Not to Ask For
Veo renders text in frame badly, same as most video models, so I never put packaging labels or on-screen text in the prompt. I add that in post instead. Fine hand movements with small objects are also rough. And don't cram too many events into ten seconds: one scene, one action, or the clip falls apart.
In my experience, the most common failure is under-describing the shot. The creator pictures the whole frame in their head but writes down maybe a third of it. The model fills in the rest its own way, and the result misses the mark. So I write longer than feels necessary and adjust one parameter at a time. You can run several prompt variations on Veo in Flami and compare which layer actually changed the shot.
FAQ
What makes a good Veo 3.1 prompt?
Five layers: scene and subject, action, camera movement, light and mood, sound. Veo handles native audio, so describe the sound environment too, or the clip comes out silent or with a random background track.
Why does Veo produce a pretty but empty shot?
Usually it's a short prompt: you picture the frame in your head but only write down a third of it, and the model guesses the rest on its own. A detailed prompt describing action, camera, and light instead of vague phrases fixes this.
Can I ask Veo for text in the frame?
Better not to. Video models render text badly, and the letters come out warped. It's more reliable to generate the shot clean and add any text you need in post over the finished clip.
How many actions should go into one clip?
One. Ten seconds isn't enough room for several events, and the clip falls apart into fragments. One scene, one clear action; build a longer story out of several separate generations instead.
Sources
- Flami: How to Write an AI Video Prompt
- Flami: Veo 3.1 Review
About the author
Ryan Mitchell
Reviewer at Flami