PromptFork

All-purpose AI video prompt with motion design principles

One reusable shot template for Sora, Veo, Runway, and Seedance — with the key insight most people miss: video prompts need to describe CHANGE, not a still frame.

Open in Studio
Prompt
The #1 mistake in video prompting: describing a photograph instead of a MOTION SEQUENCE. Video generators need to know what CHANGES — in subject, camera, and light — across the duration.

'[CAMERA MOVE + SPEED] of [SUBJECT] [ONE CONTINUOUS ACTION WITH START AND END STATE], [SETTING], [TIME OF DAY], [LIGHTING + HOW IT CHANGES], [MOOD], [FILM LOOK], [DURATION]s'

Example: 'Slow dolly-in of a lone astronaut walking toward a habitat dome across red dunes, footprints forming behind them, a distant dust storm building on the horizon, golden hour transitioning to blue twilight, warm light cooling as shadows lengthen, solitary and awe-struck, anamorphic 35mm with subtle lens flare, 5s'

Notice the difference from a photo prompt: the dust storm is BUILDING, the light is TRANSITIONING, the astronaut is walking TOWARD something. Every element implies motion through time.

How different generators handle motion:
• Sora — handles complex multi-element motion well; you can be more ambitious with camera + subject + environment all moving
• Runway Gen-3 — best with a single clear camera move; lead with the camera direction
• Veo — strong with natural/physical motion and audio; describe sounds for richer output
• Seedance — rewards explicit 'smooth motion, consistent lighting' stability tags; keep physics grounded

Describing lighting for video (not photo):
Static: 'golden hour light' ← this is a photo prompt
Dynamic: 'golden hour light with long shadows sweeping left as the sun drops' ← this is a video prompt
Always ask: what is the light DOING during these 5 seconds? Flickering? Shifting color temperature? Clouds passing over?

Duration strategy:
• 3-4s — one clean action, one camera move. Highest quality.
• 5-6s — room for a slow build or reveal. Sweet spot for most generators.
• 8-10s — only if the action is simple and continuous. More time = more chance of artifacts.

Rule: ONE continuous action + ONE camera move per clip. If you need a cut, generate two clips. Describe every motion explicitly — 'the camera slowly rises' not 'aerial view.' Vague prompts get vague motion.
Source
promptfork seed
License
CC-BY-4.0
Published
6/22/2026

More prompts you might like

Sora cinematic drone / aerial establishing shot

A Sora prompt for a smooth cinematic aerial shot with camera move, lighting, and mood.

New

Runway Gen-2 VFX element for compositing

Prompt an isolated VFX element (smoke, sparks, energy) on black for easy compositing.

New

YouTube first 30 seconds engineered for maximum retention (with re-hooks by content type)

Script the first 30 seconds using curiosity gap theory and pattern interrupts — with the critical first-3-second visual hook, B-roll direction, and re-hook lines tailored to tutorials vs commentary vs storytelling.

New
Editor’s pickVideo & MotionSeed

Cinematic book trailer concept + shot list

Turn a book's premise into a 30-second trailer concept with a shot list ready for Sora/Runway.

New

Sora cinematic shot prompt

Write Sora prompts like a director's shot list — shot size, camera move, action, lighting, lens — for film-quality clips.

New

Veo prompt with audio + camera direction

A structured Veo template that uses its strengths — camera moves and synced audio — laid out field by field.

New