Google Tests Weekly Gemini Usage Limits for Free Users

Android Authority reports that leaked screenshots posted by AshutoshShrivastava on X show Google testing weekly usage caps for some free Gemini users, replacing the shorter rolling cooldowns some users previously saw. Android Authority also notes the Gemini app now displays a warning that limits "may change frequently" and that throttling can be adjusted during testing or periods of high demand.

9to5Google's APK Insight analysis found references to an intermediate subscription tier codenamed "Neon," labelled in the app as "Google AI Ultra Lite," which would sit between the Google AI Pro and AI Ultra plans according to the report.

Mashable reports that paying subscribers have received higher daily prompt allocations, citing examples such as 300 prompts per day for the Google AI Pro Gemini Thinking model and larger daily caps for AI Ultra subscribers; Mashable adds that free-tier prompt limits are not publicly disclosed and can change.

Companies running large multimodal and reasoning models face sharply rising inference costs and concurrent-load pressure. Industry reporting frames the move toward weekly or variable throttles and an intermediate paid tier as tools to smooth peak demand and monetise heavy users, similar to recent rate-limit changes seen at other providers.

Observed patterns in similar transitions: providers commonly introduce mid-tier plans and stricter free-tier quotas when compute costs and latency at scale become operational constraints. For engineering teams, these shifts frequently change capacity planning for public-facing AI features and increase the importance of cost-aware token budgeting in production workloads.

Watch three indicators: adoption of an explicit token-budget dashboard (9to5Google reports a subscriber dashboard is planned in some code artefacts), whether weekly limits are rolled out broadly beyond test cohorts (Android Authority documents an ongoing test), and how API pricing or Gemini API quotas evolve if desktop/mobile throttles push power users toward paid or API usage.

Reporting does not include an official statement from Google on the rationale; if Google issues a public clarification, that would be the clearest source on intended scope, enforcement mechanics, and subscriber migration paths.

The sourced reporting describes active tests and client-side discoveries rather than announced company policy. Practitioners should treat the current details as provisional until Google publishes official limits or subscription structures.