4 reasons Gemini users hit caps so fast
4 reasons Gemini users are hitting usage caps fast, plus what Google says about the new compute-based limit system.

Gemini’s new compute-based limits can burn through a five-hour allowance in minutes.
Google’s Gemini quota system is drawing complaints because one task can now consume a lot more of a plan’s allowance than users expect. In one reported case, a single video-generation prompt used up a five-hour limit after just a few minutes.
1. Compute-based limits replace simple prompt counts
Get the latest AI news in your inbox
Weekly picks of model releases, tools, and deep dives — no spam, unsubscribe anytime.
No spam. Unsubscribe at any time.
Google has moved Gemini from a fixed prompt quota to a credit-style system that tracks how much compute a request uses. That means the same number of prompts can now produce very different results depending on what each prompt asks the model to do.

This is the core reason the new system feels unpredictable to many subscribers. A short text question may cost little, while a generation task with richer output can eat through the allowance much faster.
- Uses complexity, feature type, and conversation length
- Refreshes on a five-hour cycle for Google AI Pro
- Can still count toward a broader weekly quota
2. Video generation can drain the allowance quickly
The clearest complaint came from a Google AI Pro subscriber who said one avatar-based video prompt used the entire five-hour limit. The user reported that the task ran for about three to four minutes before hitting 100% of the rate limit and failing.
That kind of result is especially frustrating because the work did not even finish. When a failed generation still consumes the whole window, users feel they are paying for access that is hard to predict and hard to trust.
Example reported by a user:
- Start: 0% usage
- Task: one avatar video prompt
- Time: about 3–4 minutes
- Result: 100% of five-hour limit used3. The new system is harder for users to predict
Before the change, Gemini usage felt more straightforward to many people. Now, the amount consumed by a single task depends on what the model is doing behind the scenes, so users cannot easily estimate how far their quota will go.

That uncertainty is the main source of anger across social posts and subreddit threads. People do not just want higher limits; they want a clearer sense of what each action costs before they commit time to it.
- Text chats may be cheap
- Image or video tasks may cost far more
- Long conversations may also add to usage
4. Google is responding, but the fix is not clear yet
Google’s Gemini lead, Josh Woodward, replied to the complaint with, “Yikes, let us take a look!” That response shows the company is aware of the issue, but it does not yet answer the bigger question of whether limits will change.
The company has been raising some quotas for Antigravity users, but regular Gemini subscribers have not seen the same relief. For now, the pressure is on Google to make usage clearer, loosen the limits, or both.
- Google acknowledged the complaint
- Antigravity users have seen higher quotas
- Most regular subscribers still report tight caps
How to decide
If you use Gemini mainly for short text tasks, the new limits may be easier to live with, though they are still less predictable than before. If you rely on video generation or other heavy features, expect the allowance to move fast and plan around the five-hour reset.
For readers deciding whether the system is acceptable, the key issue is not just how much Gemini can do, but how clearly it tells you what each task costs. Until that improves, the biggest pain point will remain surprise usage spikes.
// Related Articles
- [IND]
OpenAI’s IPO filing turns hype into scrutiny
- [IND]
Skatteetaten proves public sector AI should be judged by outcomes
- [IND]
OpenAI’s IPO filing puts AI’s biggest test on Wall Street
- [IND]
OpenAI’s latest moves now center on pricing, safety, and scale
- [IND]
RISC-V mini PCs are worth buying now, but only as a bet on the future
- [IND]
Fedora 44 RISC-V widens Linux board support