You prompted a glass of water on a wooden table and got back a clip where the camera gently drifts and wobbles like a handheld phone shot. You wanted a locked-off product shot. The subject is right, but the motion ruins it.
Fastest fix: put a static-camera clause in the prompt, set the camera control to Static, and drag the motion slider to its minimum. In Runway (Gen-4/4.5) write a positive clause like The camera holds completely static, with movement only from the subject (Runway does NOT support negative prompts). In Kling/Hailuo also fill the separate Negative Prompt field with motion terms. Do this and the drift is gone on the next generation.
This is one of the most common AI video frustrations. As of June 2026, every major model (Runway Gen-4/4.5, Kling 2.5/2.6/3.0, Pika 2.5, Luma Ray3, Hailuo/MiniMax) defaults to subtle “cinematic handheld” motion because it scores higher in user testing than a perfectly static frame. To get truly locked footage you have to override that default in two or three places at once: the prompt, the motion controls, and (on tools that support it) the negative prompt.
One thing that changed recently and trips people up: Runway’s Gen-4 family dropped negative-prompt support. Per Runway’s own prompting guide, Gen-4/4.5 interprets what should happen, not what to avoid, so an old “no shake, no pan” negative prompt can backfire there. Use a positive static clause instead. Kling and Hailuo still have working negative-prompt fields.
Which bucket are you in?
| Symptom | Most likely cause | Jump to |
|---|---|---|
| Whole frame slowly drifts/floats | Prompt has no camera instruction | Step 1 |
| Jitter even with a static prompt | Motion slider above minimum | Step 3 |
| Camera swoops or pans on its own | A handheld word in the prompt | Step 2 |
| Subject is still but background pushes in | Separate camera-motion control not zeroed (or paint the background with Kling’s Static Brush) | Step 4 |
| Image-to-video adds motion you never asked for | Start frame implies movement, or Enhance Prompt is on | Step 5 |
| Drift persists with everything at zero | Old model version | ”Still drifting?” |
Common causes
Ordered by hit rate, highest first.
1. Prompt has no camera instruction
The prompt describes the subject but says nothing about the camera. Default = handheld with subtle motion. The model fills the gap with “cinematic feel” and adds drift.
How to spot it: read the prompt. If it contains none of static, locked, tripod, fixed, no motion, the default behavior kicks in.
2. Wording implies handheld
Words like cinematic, documentary feel, cinéma vérité, dynamic, energetic, vlog, gopro, action cam, dynamic camera all tell the model to make the shot feel hand-held.
How to spot it: the prompt contains any of those words. Strip them.
3. Motion slider / preset above minimum
Runway’s motion intensity, Pika’s Motion Intensity slider (0-10 scale as of Pika 2.5), Kling’s motion preset, Luma’s motion strength all default to mid-range. Any non-zero motion can produce shake.
How to spot it: check the tool UI. The motion control sits at the default rather than its floor.
4. Camera motion is a separate control from subject motion
Kling and Hailuo separate “camera motion” from “subject motion.” You can set subject motion to its minimum and still leave the camera-motion control at default.
How to spot it: the tool has a distinct camera-motion control (a slider or a Static toggle). Check it independently of subject motion.
5. Start frame implies movement (image-to-video)
Image-to-video tools infer motion from the start frame. A blurry or dynamic-looking start frame makes the model add motion to “explain” the implied blur. A prompt-enhancement feature (Luma’s Enhance Prompt, Runway’s auto-rewrite) can also re-inject camera words you deleted.
How to spot it: your start frame has motion blur, a dutch angle, or implied movement; or the tool rewrote your prompt before generating.
6. Tool version with persistent baked-in drift
Some early model versions (Runway Gen-2, early Pika) had drift that could not be eliminated. The current models follow static instructions far more reliably.
How to spot it: even with all motion at zero and a static clause in the prompt, drift persists. Check the model version in the generation settings.
Shortest path to fix
Step 1: Add an explicit static-camera clause at the START of the prompt
The earlier in the prompt this sits, the more weight it carries. Use one of these verbatim:
locked tripod shot, completely static camera, no pan, no tilt,
no zoom, no shake, fixed frame, no camera movement
static product shot, locked camera on tripod, no camera motion,
absolutely still frame, subject is the only thing moving
fixed wide-angle locked-off shot, no camera drift, no motion,
tripod-mounted, stationary camera throughoutLuma’s own help docs recommend starting the prompt with still camera shot of..., locked viewpoint of..., or fixed viewpoint of... (all three work on Ray2 and Ray3; Ray3 follows them more reliably).
Runway Gen-4/4.5 is the exception: it does not take negative prompts, so the positive clause is your main lever. Runway’s docs suggest phrasing like The camera holds completely static for the duration of the scene, with movement only occurring from the subject. Put that in the body of the prompt rather than as a “no movement” instruction.
For Kling, the most reliable phrase as of June 2026 is static camera, tripod shot, no movement appended at the END of the prompt (Kling weights the tail differently from Runway). Use static camera alone if you want the subject to move but the frame to stay locked.
Step 2: Add an anti-motion NEGATIVE prompt (Kling, Hailuo, Pika — NOT Runway)
This is the single most-skipped fix on the tools that support it. Kling, Hailuo (MiniMax), and Pika have a separate negative-prompt field; filling it with motion terms gives the model an explicit boundary that works better than relying on the positive prompt alone. Paste this into the negative-prompt box:
camera shake, camera drift, handheld movement, panning, zooming,
tilting, shaky cam, motion blur, wobble, floating camera, sudden zoomIn Kling the field is labeled Negative Prompt under the main prompt box. In Hailuo it is in the advanced/generation settings. Do NOT do this in Runway Gen-4/4.5 — negative prompts are unsupported there and can produce the opposite of what you want; lean on the positive static clause (Step 1) and the camera control (Step 3) instead.
Step 3: Drop motion strength to its minimum (and use the Static mode if there is one)
# Runway Gen-4 / Gen-4.5
- Camera Control panel -> pick a preset and set its
speed/intensity to 0, OR leave camera presets off entirely
- Reinforce with the positive static clause from Step 1
(Runway has no "Static" toggle; the prompt does the work)
# Pika 2.5
- Camera control -> Static (locks the camera in place)
- Motion Intensity slider -> lowest value (scale is 0-10)
# Kling 2.5 / 2.6 / 3.0
- Camera Movement -> None / Static
- Motion preset -> the lowest available
# Hailuo (MiniMax)
- Camera motion -> 0 / off
- Subject motion -> low
# Luma Dream Machine (Ray3)
- Motion strength -> low or off
- Turn OFF Enhance Prompt so it can't re-add camera wordsStep 4: For Kling / Hailuo, zero BOTH motion controls separately
# Kling
- Subject / motion strength: lowest (allow slight subject motion if you want it)
- Camera Movement: None / Static (this is the control most people miss)
# Hailuo (MiniMax)
- Subject motion: low
- Camera motion: 0 / offSetting subject motion to zero does nothing for a drifting camera if the camera-motion control is still at default. Check both.
Kling power move — the Static Brush: Kling’s Motion Brush has a Static Brush mode. Paint the background, the floor/ground plane, and anything that should stay fixed; Kling then holds those regions locked and only animates what you painted with the regular motion brush. This is the most reliable way to kill background “push-in” drift while still letting the subject move. It is image-to-video only.
Step 5: Use a tripod-style start frame (image-to-video) and strip handheld words
For image-to-video:
- Pick a start frame that LOOKS static: no motion blur, level horizon,
no dutch angle
- Avoid start frames where the subject is mid-action
- Subject should be at rest or in a stable poseThen remove these handheld-implying words from the prompt entirely (don’t replace them with static/locked, which conflicts; just delete them):
cinematic, dynamic, energetic, documentary, cinéma vérité,
vlog, gopro, action cam, handheld, dynamic camera,
dramatic angles, found footage, real-life feelStep 6: Stabilize in post if the tool still drifts
If a stray clip still wobbles, fix it after the fact:
# Premiere Pro
- Effects -> Warp Stabilizer
- Result: "No Motion", Smoothness: ~50% (use "No Motion" only for
shots that should read as a true tripod shot)
# DaVinci Resolve (free version works too)
- Color page -> Tracker palette -> Stabilizer mode
- Mode: Similarity, Cropping Ratio lower = stronger lock
- Or right-click the clip in Edit/Cut -> Stabilization
# Final Cut Pro
- Inspector -> Stabilization -> Method: "SmoothCam" or "Tripod Mode"No Motion / Tripod Mode crops in slightly but usually turns a drifty source into a perfectly locked result.
How to confirm it’s fixed
- Generate one short test clip (3-5 seconds) with the static clause, negative prompt, and Static camera mode all set.
- Scrub it frame by frame, or freeze the first and last frame and compare: a locked shot has the frame edges in exactly the same position throughout. Any subject motion is fine; the frame boundary must not move.
- If you still see drift, you almost certainly missed the separate camera-motion control (Step 4) or left Enhance Prompt on (Step 5). Fix that one thing and regenerate.
Still drifting?
If everything above is set and the camera still moves, it is the model version. Confirm you are on the current generation (Runway Gen-4/4.5, Kling 2.5+, Pika 2.5, Luma Ray3) rather than a legacy model; older versions baked drift in and cannot fully lock. Re-run the same prompt on the newer model.
Prevention
- Default to a
locked tripodclause in every prompt unless you specifically want motion. - Keep a saved negative prompt with the motion terms and reuse it on every static shot in Kling/Hailuo/Pika (not Runway).
- Set motion strength to its minimum as your default; raise it only when needed.
- Pick image-to-video start frames that are themselves static-looking, and keep Enhance Prompt off for locked shots.
- For tools with a separate camera-motion control, always set it to Static / 0 explicitly.
FAQ
Why does my AI video drift even when I wrote “static camera”? Two usual reasons. Either the motion slider is still above its floor (Step 3), or you have a separate camera-motion control that is still at default while you only zeroed subject motion (Step 4). On Kling/Hailuo, also fill the negative-prompt field. On image-to-video, turn off Enhance Prompt so it doesn’t re-add camera words.
Do negative prompts stop camera shake in Runway?
No. As of June 2026, Runway Gen-4/4.5 does not support negative prompts; its docs say to describe what should happen, not what to avoid. A “no shake, no pan” negative prompt can backfire. Use a positive clause like The camera holds completely static, with movement only from the subject and set the camera-control intensity to 0. Negative prompts still work in Kling and Hailuo.
Where do I put the static-camera phrase — start or end of the prompt?
Runway weights the start more, so put it early. Kling weights the tail, so append static camera, tripod shot, no movement at the end. When in doubt, include it in both places.
Can I lock just the camera but still let the subject move?
Yes. Use static camera (Kling) or The camera holds completely static, with movement only from the subject (Runway) and keep subject motion non-zero. On Kling, the Static Brush is the cleanest way: paint the background static and the subject region with the regular motion brush.
Everything is at zero and it still drifts — now what? You are probably on a legacy model. Confirm you are on Runway Gen-4/4.5, Kling 2.5+, Pika 2.5, or Luma Ray3, not Gen-2 or early Pika, which baked drift in. Re-run on the current model, then stabilize in post (Warp Stabilizer “No Motion” or DaVinci’s Tripod-style lock) if a stray clip still wobbles.
For Runway’s exact guidance on static shots and why negative prompts don’t apply, see Runway’s Gen-4 Video Prompting Guide.