Veo 3.1 dialogue prompts: examples and fixes

Quick answer

For reliable dialogue in Veo 3.1, identify one visible speaker, put the exact line in quotation marks, describe delivery separately, and keep the action simple enough for the clip. Example: “Medium close-up of one baker facing the camera. She says, ‘The bread is ready,’ in a calm, warm voice. Quiet kitchen ambience; no music.” Generate with audio enabled, then inspect the actual words and lip movement before publishing.

Veo can generate native audio, dialogue, sound effects, and ambience, but a prompt is direction rather than a guarantee. Shorter lines, clear speaker attribution, and one controlled shot make failures easier to diagnose.

A reusable Veo dialogue prompt formula

[Shot and camera] + [speaker] + [action] + [exact dialogue] + [delivery] + [ambience and sound] + [visual style].

Google's general Veo framework is cinematography, subject, action, context, style, and ambience. For speaking scenes, add explicit speaker attribution and the exact quoted line. Do not bury the dialogue inside several unrelated actions.

Three prompt structures that work for different jobs

1. One speaker to camera

Locked medium close-up of a woman in a quiet pottery studio, looking into the camera. She says, ‘Every piece starts with a patient hand,’ in a natural, thoughtful voice. Soft room tone and a faint pottery wheel; no music. Warm documentary lighting.

Try in Text-to-Video

Use this for a product line, testimonial-style scene, presenter moment, or social hook. State whether the person addresses the camera or another character.

2. Two-person exchange

Static two-shot in a small train compartment at night. The conductor looks at the traveler and quietly asks, ‘Are you sure this is your stop?’ The traveler glances toward the dark window and replies, ‘It has to be.’ Low train rumble, no music, restrained suspense.

Try in Text-to-Video

Give each person one short line and an observable action. If speaker attribution, timing, or lip sync fails, generate each line as a separate shot and assemble the exchange in an editor.

3. Voice plus environmental sound

Wide shot of a mechanic closing the hood of a vintage car in an open garage. He says, ‘Now listen to that engine,’ with quiet pride. The engine starts and settles into a smooth idle; distant birds and light workshop ambience; no background music.

Try in Text-to-Video

Separate dialogue, sound effects, and ambience so each has a clear role. Avoid asking for several loud effects under a quiet line.

Test a Veo 3.1 dialogue prompt

Generate a short Veo 3.1 dialogue shot, then review the spoken words, speaker attribution, lip movement, ambience and disclosure before using it.

Create with Veo 3.1

How to make the speech easier to generate

Use one primary speaker per shot. Multi-person speech increases attribution and timing complexity.
Keep the line short. A line that does not fit naturally in the chosen duration is likely to rush, truncate, or drift.
Put exact speech in quotation marks. Google explicitly recommends quotation marks for specific dialogue.
Name the delivery. Describe tone, pace, volume, accent only when necessary, and emotional state in plain language.
Describe visible mouth orientation. A speaker facing away, covered, tiny in frame, or moving rapidly gives the model less visual information for lip movement.
Control the soundstage. State the important ambience and effects; say “no music” only when silence behind speech matters.
Limit simultaneous action. One camera move and one character action are easier to evaluate than a crowded mini-film.

Structured, narrative, or reference-led prompting?

Structured prompt: best when exact speech, staging, and sound cues matter. Label the shot, speaker, dialogue, delivery, SFX, and ambience.
Narrative prompt: useful for a fast first exploration, but harder to debug when the spoken result is wrong.
Image-to-video: useful when the first frame should establish the speaker, wardrobe, product, or composition. The image guides the visual start; it does not guarantee identity or speech accuracy.
Reference images: Veo 3.1's Gemini API supports up to three references for a person, character, or product. Use only images you have permission to process.
Separate shots: usually safer for an exchange or longer script. Generate one short line per shot, then edit the scene and sound continuity.

Common dialogue failures and what to change

Wrong words or extra speech: shorten the line, remove competing narration, and keep one quoted utterance.
The wrong person speaks: use one speaker, a closer shot, explicit names or descriptions, and separate the exchange into shots.
Weak lip sync: face the speaker toward camera, reduce motion, shorten speech, and inspect at normal speed and frame by frame.
Rushed delivery: reduce word count or use a longer supported duration in the provider you are using.
Speech masked by audio: simplify effects, lower the described ambience, and remove music from the generation or mix it later.
Character drift: use a permitted reference or first frame, hold the description stable, and generate separate shots. Repetition can help direction but cannot ensure identity.
Blocked generation: review the prompt and reference media against the provider's safety rules. Google notes that audio processing can also cause a Veo generation to be blocked.

A controlled way to improve a prompt

Start with one speaker, one short line, a locked or simple shot, and quiet ambience.
Generate several candidates and save the prompt, model, provider settings, duration, aspect ratio, resolution, audio setting, and output.
Score the exact words, speaker attribution, lip movement, vocal delivery, visual continuity, and sound balance.
Change one variable at a time: line length, framing, delivery, motion, or ambience.
Once speech works, add one visual or sound detail at a time.
Choose the lowest-cost candidate that clears the intended quality bar, then finish captions and audio in an editor when needed.

Current Veo 3.1 limits depend on where you use it

In the Gemini API, Google documents Veo 3.1 clips of 4, 6, or 8 seconds, with 8 seconds required for some higher-resolution or reference-image modes. It supports native audio and 16:9 or 9:16 output. Vertex AI and consumer Gemini access, quotas, prices, and controls are separate surfaces and can change.

Check the language as well as the accent. Google’s Gemini API guide lists English as fully supported and says other languages have not been evaluated, although they may work. For a non-English deliverable, have a fluent reviewer check the actual wording and pronunciation; an English-language prompt example is not evidence of equal dialogue quality in every language.

Extending dialogue needs speech near the cut

In Google’s documented Veo 3.1 extension workflow, the continuation is based on the final second of the input. Google says voice cannot be effectively extended if none is present in that last second. A silent ending after the line can therefore break the voice handoff. Keep a speaking tail where appropriate, or make a separate dialogue shot. Gemini API extension is 720p, uses the eight-second setting, and is not supported by Veo 3.1 Lite; other hosts must be checked separately.

Inside Magic Hour's Veo 3.1 workflow, current platform settings can differ from Google's direct Gemini API. Check the selected interface for duration, resolution, aspect ratio, audio, price, plan, and commercial-use terms instead of carrying over an old Gemini Ultra price or temporary free-access promotion.

Direct Gemini API integration note, checked October 10, 2026: Google’s model lifecycle schedule lists October 22, 2026 as the earliest possible shutdown date for veo-3.1-generate-preview, veo-3.1-fast-generate-preview and veo-3.1-lite-generate-preview, with gemini-omni-1.1-flash as the recommended replacement. Verify the actual model ID and migration instructions before automating a new workflow. This is a future Gemini API preview schedule, not evidence that Magic Hour or Google’s separately listed GA Cloud models have stopped working.

Dialogue QA before publishing

Transcribe the generated speech and compare it word for word with the intended line.
Confirm the intended person speaks each line and no extra voice appears.
Watch lip movement, teeth, tongue, jaw, eyes, hands, and identity at full size.
Listen on headphones and a phone speaker for clipping, noise, phase issues, abrupt ambience, or masked speech.
Add accurate captions and identify synthetic media when context could mislead viewers.
Confirm consent for any recognizable person or voice and rights for references, brands, music, and other assets.
Reject a plausible-looking result when the words, identity, safety, or disclosure are wrong.

Frequently asked questions

Yes. Google's Veo guidance explicitly recommends quotation marks for specific speech. Also identify who says the line and how they deliver it.

Yes, Google's examples include multi-person dialogue. For production reliability, keep turns short and attribution explicit; generate separate shots if the speakers or timing drift.

No. Stable descriptions and reference inputs can guide continuity, but they do not guarantee identity. Review every shot and use permitted references where the chosen Veo surface supports them.

No. Google's current Gemini API documentation lists 4-, 6-, and 8-second choices, with mode-specific restrictions. Other providers can expose different controls, so verify the selected interface.

It should not be treated as an exact recording system. Verify the words, speaker, voice, lip movement, rights, and disclosure before publishing or using it in customer-facing work.

Official sources checked

Current Gemini API capabilities, durations, audio cues, safety notes, and reference behavior come from Google's Veo 3.1 developer guide. Prompt structure and soundstage guidance come from the Google Cloud Veo 3.1 prompting guide. Current Magic Hour access comes from the Magic Hour Veo 3.1 model page. Sources were checked September 13, 2026.