Google Gemini shifts to compute-based usage limits: what AI builders need to know
wired.com

Google Gemini shifts to compute-based usage limits: what AI builders need to know

Tech News
4 min read

Published by AINave Editorial • Reviewed by Ramit

TL;DRGoogle Gemini now measures usage by compute power, not request count. Credits vary by prompt complexity, model choice, and plan tier. Track usage in the app with five-hour and weekly resets.

Google has overhauled how Gemini AI usage is measured, moving from request-count metering to compute-based quotas. This change affects Free, Plus, Pro, and Ultra tiers and means that prompt complexity, model selection, and plan tier now directly determine how much you can use the service. For AI builders and developers relying on Gemini, understanding these new Google Gemini usage limits is essential for planning workflows and managing costs.

What happened

Google now measures Gemini AI usage by the computing power requirements of each request, not by the number of requests made. This means a simple weather query consumes fewer credits than generating a complex video or coding a mini-app. The two main factors that determine consumption are the plan you are on and the complexity and length of your prompts. The Gemini model you select (for example, Gemini 3.5 Flash) also affects credit consumption, with more capable models costing more.

Context window sizes scale with plan: Free users get 32K tokens (roughly 24,000 words), AI Plus users get 128K tokens (about 96,000 words), and AI Pro and Ultra users get up to 1,000,000 tokens (about 750,000 words). Video generation and longer, more complex prompts consume more credits. Higher-tier plans grant access to more capable models and longer context windows.

Why AI builders should care

For developers building products or workflows on top of Gemini, the shift to compute-based quotas changes the economics of each API call. You can no longer rely on a simple rule like "5 image generations a day." Instead, you must consider model selection and prompt optimization as primary levers for staying within limits. This introduces pricing uncertainty that may affect product pricing, experimentation cycles, and feature deployment.

Plan differences translate into practical constraints. Free users get "standard" limits that Google does not specify numerically. AI Plus users get 2x those limits, AI Pro users get 4x, and AI Ultra users get either 5x or 20x the AI Pro limits depending on the payment level. All users have access to all Gemini models (Flash-Lite, Flash, and Pro), but smarter models count more toward usage. Each model also has different thinking levels (Standard, Extended, and Deep Think) that affect response quality, speed, and usage limits.

Practical implications

You can monitor your usage directly in the Gemini app. On the web, click the cog icon (lower left) then Usage limits. On mobile, tap the menu button (top left), then the cog, then Usage limits. You will see two bars: the top bar shows your current usage, which resets every five hours. The second bar is your weekly limit, which resets every week. If you hit these limits on a paid plan, you will be demoted to the most basic AI model until the next reset.

Google's support documents note that limits may change without notice due to capacity, testing, or availability, and free users are likely affected first. This means your usage cap could vary from day to day, making it harder to predict costs and availability for production systems.

Caveats

Some details about Gemini usage limits are still evolving. Google does not specify exact per-model credit costs or thresholds, and the company acknowledges that access may change based on capacity constraints. Public documentation states that "access is subject to change or may be limited based on testing, experimentation or availability." This variability means that builders should design for flexibility and have fallback plans for when limits are hit.

If you are building on Gemini, consider implementing retry logic, monitoring usage closely, and designing prompts to minimize complexity where possible. The new system rewards efficient, well-structured prompts and penalizes resource-heavy requests.

FAQs

Credits are tied to the compute resources required by each request, not the number of prompts. Different models and prompt complexities consume varying amounts of credits, with higher-tier models like Pro consuming more than Flash-Lite. Video generation and longer prompts also consume more credits. You can see the details in Google's support documentation.

Sources

Latest Tech News