MAJORFailure Reference

Google Veo Camera Jitter — Pre-Generation Risk Reference

Technical Classification

Camera Path Coherence Failure

Veo 3's camera-conditioning signal is more precise than earlier models but still fails on static-camera prompts. The model produces micro-jitter, horizon wobble, or full-frame shake even when the prompt specifies "static camera," "tripod," or "locked off." The failure is most common on product shots, interview-style framing, and commercial work where a tripod look is required. Output is unusable without aggressive post-production stabilization.

How to identify this failure

✕Sub-pixel jitter in a clip prompted for locked-off camera
✕Horizon line wobbling across the clip
✕Persistent handheld shake despite tripod cue
✕Camera lurch at random intervals
✕Subject drifting across frame on static-subject prompts

Real generation examples

Prompt used

"Static camera, locked off, smartphone on a clean white background"

Failure observed @ 0:00

Camera exhibited handheld jitter throughout 5s clip; smartphone oscillated 4px

Prompt used

"Tripod-locked shot of a product on a turntable, smooth rotation"

Failure observed @ 0:02

Camera path lurched at 0:02; horizon wobbled despite tripod cue in prompt

Documentation strength

If you need to escalate

HIGH — Google AI Studio refunds prompt-camera mismatch on documented commercial work. Submit Generation ID with a frame-by-frame screenshot showing the unintended motion.

AVA is a pre-purchase prevention tool, not a post-purchase recovery tool. Platforms generally do not guarantee credit refunds for output-quality failures; goodwill credits are at each platform's discretion. The strength rating reflects how well-formed your support ticket can be, not a promised outcome.

Prevention + documentation steps

01
Score your prompt before you generate
Run your prompt through AVA's pre-flight scoring against the Camera Path Coherence Failure pattern. Green light = generate. Yellow/red = rewrite using the suggested fix before you commit credits.
02
Capture Generation ID + timestamp if it failed anyway
Find the Generation ID in the URL or share link. Note the exact time when the Camera Path Coherence Failure first appears (e.g. "failure first visible at 1.2s"). Timestamped evidence is significantly stronger than a general complaint.
03
Use the correct technical term in your support ticket
Describe this failure as "Camera Path Coherence Failure". This term maps to a recognised internal workflow in the support system and routes the ticket to the right team.
04
Submit via the correct support channel
Runway has no direct email intake. Pro+ plan: open the in-app AI Assistant (help widget bottom-right of app.runwayml.com), describe the failure with the technical term, attach evidence. Free/Standard plan: human support isn't available — your channel is Discord #community-help with @On Call - Moderators.

Frequently asked questions

Does Veo refund credits for unwanted camera jitter?

Yes. Submit the prompt, Generation ID, and a screen recording showing the unintended motion. The failure is well-documented in Google AI Studio billing — the model violated its own camera-conditioning input.

Why does Veo add jitter when not requested?

Veo's camera path is conditioned on a learned distribution rather than an explicit constraint. Handheld is over-represented in training data, so the model defaults to micro-motion unless multiple static cues override the prior.

How do I get a clean static shot on Veo?

Stack static cues: "static camera, locked off, tripod, no camera movement, fixed frame, zero shake." Avoid scene descriptions implying documentary or street-photography style. AVA flags camera-jitter risk before submission.

Score your prompt

Score your prompt against this failure mode in 30 seconds

Paste your prompt and the platform you intend to use. AVA returns a red/yellow/green score against this specific failure mode plus a concrete rewrite if the risk is high.

Install free All 105 failure modes

AVA Pro · founders' round

$50 for 6 months of unlimited scoring across all failure modes + personal failure-history dashboard. Locks in $13/mo grandfathered after.

Claim $50 founders