Verified against Veo 3.1 · 2026-08-06
Generate a macro slow-motion liquid splash clip with named fluid physics
A Veo 3.1 prompt for a macro slow-motion splash or pour, built around explicitly named viscosity and droplet behavior, since fluid dynamics is one of the hardest physical behaviors to infer without being told exactly how the specific liquid should move.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Write a Veo 3.1 prompt for an 8-second macro slow-motion clip of a single liquid splash, pour, or impact, structured around explicitly named fluid physics rather than a generic "splash in slow motion" instruction, since the specific behavior of a liquid — how viscous it is, how large its droplets are, how it separates on impact — has to be stated for the model to render it correctly rather than defaulting to a generic water-like behavior regardless of what liquid was actually named. LIQUID AND ACTION thick raw honey, being poured from a height onto a stack of pancakes. Name the liquid specifically — water, honey, cream, wine — not just "liquid," since viscosity is the single largest driver of how a fluid should move and a generic instruction defaults to a thin, water-like behavior even when a thick liquid like honey was actually described elsewhere in the prompt. FLUID PHYSICS DETAIL a thick, unbroken ribbon that folds and pools rather than scattering, with slow, heavy drips trailing behind the pour. Describe the specific droplet size and separation behavior for this liquid — thin water breaks into fine, fast-scattering droplets; a thick syrup separates into slower, larger ropes and blobs that hang and stretch rather than scatter — since this physical detail is what actually distinguishes one liquid from another on screen far more than color does. CAMERA A locked-off extreme macro shot, framed tightly on the point where the honey first contacts the top pancake, capturing the moment of impact and its immediate aftermath — no camera movement, since a moving camera this close to a fast, chaotic fluid event compounds the amount of motion the model has to resolve correctly at once. SLOW MOTION DETAIL The moment should read as significantly slowed — describe the specific detail that sells the slow motion, a single trailing drip stretching and elongating before finally breaking free and falling, such as individual droplets visibly suspended mid-air or a surface tension bubble taking a full second to collapse. LIGHTING a warm backlight positioned to make the honey glow amber as it catches the light, angled specifically to catch the liquid's surface — backlight to make droplets read as individually lit spheres, a raking side light to show a viscous liquid's sheen — matched to the fluid physics named above. STYLE AND MOOD warm, appetizing, high-detail food commercial look. AUDIO a low, slow, thick pouring sound, deeper in pitch than a normal-speed pour — if genuinely slow motion, describe the impact sound as time-stretched and lower in pitch, matching the same audio-speed discipline any slow-motion clip needs, rather than a normal-speed splash sound under visibly slowed footage. WHAT TO AVOID Do not name a viscous liquid and then also describe its behavior using thin-liquid language like "splashing" or "spraying" — those verbs carry an implicit low-viscosity assumption that will fight the named liquid's actual physical properties, producing a result that looks like water dyed the wrong color rather than the actual liquid described. OUTPUT The finished prompt, followed by one line confirming the named liquid's viscosity matches every verb used to describe its motion.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Fluid dynamics is one of the harder physical behaviors for a generative video model to infer correctly, because a liquid's movement is determined almost entirely by a property — viscosity — that is invisible in a single still frame and only becomes apparent through how the fluid behaves over time, which means naming the liquid alone ("honey") is necessary but not sufficient; the model also needs the specific behavioral consequence of that viscosity spelled out, since a generic splash instruction defaults to the thin, fast, fine-droplet behavior of water regardless of what liquid was named, unless the droplet size and separation pattern for this specific liquid is described directly. This is exactly why naming the verb matters as much as naming the liquid: describing a thick liquid's motion with thin-liquid verbs like "splashing" or "spraying" smuggles in a low-viscosity assumption that directly contradicts the named liquid, and the model resolves that contradiction by producing something that looks like water dyed the intended color rather than a liquid with the intended physical weight and behavior — the verb choice is doing real physical work, not just stylistic flavor. Anchoring the slow motion to one specific, concrete detail — a trailing drip stretching before it breaks free, a droplet suspended mid-air — rather than leaving "slow motion" unanchored gives the model something to actually demonstrate as evidence of the slowed timescale; without that anchor, the difference between "slow motion" and "filmed at a slightly reduced real-time speed" can be difficult for the model to commit to distinctly, since both would technically satisfy an unspecified instruction to "slow it down." Locking the camera off entirely rather than adding any movement addresses a compounding-complexity problem specific to fast, chaotic fluid events at macro scale: a splash or pour already asks the model to resolve a large amount of fine, fast-changing detail within a tight frame, and adding camera movement on top forces it to simultaneously track that motion relative to a moving reference point, which is where macro fluid shots most often lose coherence at the fluid's edges — exactly the detail the shot exists to showcase.
Verified against
Veo 3.1 3.1 · 2026-08-06
Changelog
- 2026-08-06 — Initial publish, verified against Veo 3.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
