GALAXY OF TOOLS

AI SECTOR

AI Video Prompt Generator

Plan shots — camera, action, dialogue and sound — and get prompts for Veo 3.1, Runway, Kling and Luma.

Write the prompt for

This model makes one clip per prompt — the storyboard is written as one prompt per shot to generate and edit together.

Scene
Describe the character or product once, the same way every time.
Three to five colours keep shots consistent.
Aspect ratio
Shot 1
One clear action and one camera move per shot work best.
Shot 2
Shot 3
Shot 4
Shot 5
Shot 6
Sound and exclusions
Used for Veo 3.1 and Kling 3.0 (native audio) and the generic prompt.
Veo and Kling get a separate negative prompt; Runway and Luma get positive wording.

The storyboard and prompts are built in your browser and never sent to a video service. Share links keep them after the #, which is never sent to a server; favourites stay in this browser. “Improve with AI” runs on your device and asks before any download.

An AI video prompt generator built around shots

A video prompt is really a shot list. This AI video prompt generator lets you describe a scene once — subject, place, style, light, colour and mood — then plan up to six shots, each with a shot size, angle, camera move and speed, lens, action, dialogue, sound effects and a length in seconds. A timeline shows how the shots add up.

The same storyboard is then written the way each vendor documents: one prompt per clip for Veo 3.1 with quoted dialogue, SFX and a separate negative prompt; [Shot 1: …] blocks for Kling 3.0 multi-shot with native audio; natural-language camera sentences and positive phrasing for Runway; camera “concepts” for the Luma API; and a clear generic layout for any other model.

The checklist catches what usually goes wrong: a Veo clip that is not 4, 6 or 8 seconds, a ratio Veo doesn’t make, dialogue too long for its shot, sound sent to a model that ignores it and “no …” wording that can backfire. For stills, use the AI image prompt generator.

How to write a video prompt shot by shot

  1. Choose the model under Write the prompt for, or load an example.
  2. Describe the Main subject once, then the location, visual style, pacing, light, palette and aspect ratio.
  3. For each shot pick a shot size, angle and Camera movement, write what happens and add dialogue as Name: line.
  4. Set the seconds per shot and use Add shot for more; watch the timeline.
  5. Add ambient sound and anything to leave out, fix the checklist, then copy the prompt or the JSON.

AI Video Prompt Generator features

Up to six shots

Shot size, angle, 20 camera moves with speed, lens and focus, action, dialogue, SFX and duration per shot.

Five targets

Veo 3.1, Runway, Kling 3.0, Luma Ray 2 and a generic layout — each following its own guide.

Live timeline

Start and end of every shot and the total length.

Audio where it exists

Quoted dialogue, SFX and ambience for Veo and Kling; left out, with a note, for Runway and Luma.

Negative prompts per model

A separate field for Veo and Kling, positive rewrites such as “a locked camera that remains still” for Runway and Luma.

Timing checks

Veo’s 4/6/8-second clips and 16:9 or 9:16 frames, Runway’s 5/10-second clips, dialogue pace.

What each video model documents

ModelPrompt shapeLength and frameSoundLeave out
Veo 3.1Subject, action, style, camera, composition, lens, ambiance4, 6 or 8 s; 16:9 or 9:16Dialogue in quotes, SFX, ambient noiseSeparate negative prompt, no “no”
Runway (Gen-4.5)[Camera] shot of [subject] [action] in [environment]Gen-4: 5 or 10 sNot documentedPositive phrasing only
Kling 3.0Subject, action, scene, camera, lighting, mood; [Shot n] blocksFlexible; multi-shotNative audio, speaker labelsAPI negative_prompt
Luma Ray 2 (API)Natural language + camera conceptsaspect_ratio, loopSeparate “add audio” requestNo field

Sources read on 14 October 2026: Google’s Veo 3.1 page in the Gemini API docs (updated 8 October 2026) and Google Cloud’s video prompt guide (updated 13 October 2026); Runway’s Text to Video and Gen-4 prompting guides; Kling’s prompt guide (7 August 2026); Luma’s Dream Machine API docs. Sora: OpenAI’s guide says the Sora 2 models and Videos API were shut down on 24 September 2026, so the generic layout is the closest replacement here.

Worked example: a two-shot storm scene

The start example plans an 8-second crane shot and a 6-second close-up with one line of dialogue. For Veo 3.1 it becomes two clip prompts and one negative prompt:

Shot 1 — 8 s, 16:9
Low-angle wide shot of a lighthouse keeper in a yellow raincoat on a rocky island during a night storm. The keeper climbs the iron stairs outside the tower as waves explode against the rocks. The camera cranes up slowly. Cinematic 35mm film look. The sweeping beam of the lamp and flashes of lightning, deep blue, slate grey and warm amber, tense mood. SFX: waves crashing, wind howling. Ambient noise: rain hammering on metal, a distant foghorn.

Shot 2 — 6 s, 16:9
Eye-level close-up of a lighthouse keeper in a yellow raincoat on a rocky island during a night storm. The keeper wipes rain from the lamp glass and stares out to sea. The camera stays locked off and still. Cinematic 35mm film look. The sweeping beam of the lamp and flashes of lightning, deep blue, slate grey and warm amber, tense mood. Keeper: "Hold on, whoever you are." Ambient noise: rain hammering on metal, a distant foghorn.

Negative prompt (all shots): text, watermark

Switch to Kling 3.0 and the same plan becomes one multi-shot prompt — the scene first, then [Shot 1: Low-angle wide shot, slow crane up] and [Shot 2: Eye-level close-up, static camera] blocks with the quoted line and an ambience line.

Directing tips that work across models

  • One move, one action per shot — “takes four steps to the window and pulls the curtain” beats “walks around”.
  • Use film words: dolly in, truck left, crane up, orbit, rack focus, shallow depth of field.
  • Keep the subject’s description identical in every shot so the character stays recognisable.
  • Short dialogue — about 2.5 spoken words a second, so an 8-second clip holds roughly 20 words.
  • Say what you want to see — “a locked camera that remains still” rather than “no camera movement”.

AI Video Prompt Generator FAQ

How do I write a good AI video prompt?

Name the shot size, angle and one camera move, then the subject and one visible action, the setting, style, light and mood. This AI video prompt generator lays those out per shot and checks timing and wording.

Can I still write Sora prompts?

OpenAI shut down the Sora 2 models and Videos API on 24 September 2026. The generic layout keeps the same idea — scene, camera, actions, dialogue — for whichever model you use now.

How long can a Veo 3.1 clip be?

Google documents 4, 6 or 8 seconds, with 8 seconds required for 1080p, 4K and reference images, in 16:9 or 9:16. Longer stories are separate clips edited together.

Which models generate dialogue and sound?

Veo 3.1 and Kling VIDEO 3.0 generate native audio from the prompt. Runway’s guides don’t document audio, and Luma adds audio with a separate API request.

Why does Runway get “a locked camera that remains still” instead of “no camera shake”?

Runway’s Gen-4 guide says negative phrasing is not supported and may produce the opposite, so exclusions are rewritten as what should happen.

Is my storyboard uploaded?

No. It is built in your browser; share links keep it after the # sign.

You might also need