Google Veo Problems & Issues

Real user-reported problems, complaints, and limitations for Google Veo. Based on analysis of 13 signals.

Overall score: 55/100

Issues by Category

pricing4 issues

Failed Veo generations still use up my credits

Users on Google's developer forum and Adobe's Firefly forum (which also hosts Veo) report 'Something went wrong' or 'Failed' runs that consumed credits with no video. Google says credits for failed runs are not affected but can take time to reappear; some users say they never came back.

Frequency: 9%Sentiment: -0.80/1004 sources
Impact
8

Why is Veo so expensive? One 8-second clip can cost 20-100 credits

In Flow, Veo 3.1 Fast reportedly costs 20 credits and Quality 100 per generation on non-Ultra plans, so a 1,000-credit Pro month yields only 10-50 clips before retries. One forum user reported 48-60 credits for one 8-second clip.

Frequency: 9%Sentiment: -0.70/1004 sources
Impact
8

Google AI Ultra costs $100-$200 a month and Veo is rate-limited anyway

Ultra subscribers on the Google forum report batches failing for days and credits deducted with zero output. A large balance does not guarantee throughput because generations can be rate limited.

Frequency: 7%Sentiment: -0.70/1003 sources
Impact
8

Older Veo 3.1 models are being retired in favor of Lite and Omni

Third-party trackers say Veo 3.1 Fast and Quality retire in December 2026 and that Google now pushes Omni Flash, so workflows and credit costs change under you. Check Flow for current dates.

Frequency: 5%Sentiment: -0.40/1002 sources
Impact
5
usability3 issues

Veo blocks harmless prompts as policy violations

Users report simple scenes (walking, sitting, a museum, a rooftop) refused, or refused again after rewording. The video and reference images are also filtered, so a clean prompt can still be blocked.

Frequency: 9%Sentiment: -0.70/1004 sources
Impact
7

Veo video has no sound or 'Audio generation failed'

Audio on Veo 3.1 is described as experimental. Low-quality audio can stop the video from being generated; the credits are returned in that case. Some users report silent clips and dialogue turned into on-screen subtitles.

Frequency: 8%Sentiment: -0.60/1004 sources
Impact
7

Veo characters change between clips (outfit, face, hair)

Users say characters drift even with reference images, and scene continuity breaks when clips are extended. Uploaded characters reportedly vanished from inventories after an update.

Frequency: 8%Sentiment: -0.60/1003 sources
Impact
7
reliability2 issues

Veo says 'Something went wrong' or 'Failed' on every generation

Repeated generic errors in Flow, the Gemini app and partner apps, sometimes for days. Causes range from capacity and quota to a stuck backend; the error text rarely says which.

Frequency: 9%Sentiment: -0.80/1005 sources
Impact
8

Veo 'We noticed some unusual activity' error blocks Flow

Paying Ultra users report every generation failing with an 'unusual activity' message even after the documented troubleshooting, with slow support replies.

Frequency: 6%Sentiment: -0.80/1002 sources
Impact
8
performance2 issues

Veo ignores part of the prompt or moves stiffly

Forum users say requested actions don't always happen, motion is slow or stiff, and small wording changes give unpredictable results.

Frequency: 7%Sentiment: -0.50/1003 sources
Impact
6

Veo is slow or queued at busy hours

Guides report demand exceeding capacity in US daytime hours and jobs stuck in the queue; free video generation may be unavailable at some hours. Not all of this is confirmed by Google.

Frequency: 6%Sentiment: -0.50/1003 sources
Impact
6
integrations1 issue

Veo API returns 429, 500, 503 or 504 errors

Vertex AI and the Gemini API return RESOURCE_EXHAUSTED when quota is exceeded, plus 500/503/504 during overload. Developers also report audio-safety false positives burning a Tier 1 daily quota.

Frequency: 7%Sentiment: -0.60/1003 sources
Impact
7
support1 issue

Google gives no refund for wasted Veo credits and support is slow

Users describe slow support tickets, a moderator redirecting Flow issues to the app's feedback button, and refund offers that did not cover credits. Google's help page says credits count as spent once used.

Frequency: 8%Sentiment: -0.70/1004 sources
Impact
7

Regret Patterns

Common reasons users regret choosing Google Veo.

Burning a month of credits on retries

Failed, blocked or off-prompt clips use credits, so the allowance is gone before a finished video exists.

Frequency: 8%In the first week

Upgrading to Ultra for throughput

Higher plans add credits but not guaranteed speed; generations still fail or queue.

Frequency: 6%After hitting Pro limits

Expecting a consistent character

Identity drifts between clips, forcing regenerations.

Frequency: 7%On the second or third clip

Buying for audio that fails

Audio is experimental and can fail or come out silent.

Frequency: 6%First dialogue scene

Building on the API then hitting quota

429 errors and audio-safety false positives drain daily quota.

Frequency: 5%After moving to production

Forgetting to cancel

Annual or Play/Apple-billed plans renew and refunds are limited.

Frequency: 5%After the first month

When Google Veo Breaks Down

Specific scenarios where Google Veo fails or underperforms.

Dialogue-heavy scenes

Audio generation can fail or stay silent.

Long continuous shots

Clips are short; Extend and stitching break continuity.

Prompts with real people or brands

Policy filters block them.

Busy daytime hours

Capacity limits cause queues and failures.

Production API traffic

Quota and 429 errors under bursts.

Reference-image heavy workflows

Reference images can trigger blocks and not every model supports Ingredients.