Google switches Gemini Notebook to compute-based usage limits that refresh every 5 hours

Google is replacing Gemini Notebook's simple daily usage caps with flexible, compute-based limits that take prompt complexity into account and refresh every five hours instead of once a day.

What's new

In a post from product manager Yesul Shin, Google says: "We're introducing new flexible, compute-specific usage limits to Gemini Notebook — giving you more control over your workflow." Instead of a flat daily cap, the overall usage limit will now factor in prompt complexity, chat length, number of sources, and which features are used in a session. Because limits refresh every five hours rather than daily, users can keep working throughout the day rather than losing access after hitting a single daily ceiling.

Google is also adding tools to help users manage the new system: Gemini Notebook will track usage and suggest alternative, less compute-intensive outputs if a user's first choice would exceed their remaining limit. If a user does hit their limit, outputs like Video Overviews or Slide Decks can be deferred — they'll generate automatically later, with an optional notification when they're ready, rather than being blocked outright.

The change rolls out to consumer accounts on web and mobile starting September 2, 2026.

Context

Gemini Notebook is the product formerly known as NotebookLM, Google's AI-powered research and notes tool that lets users query and generate content (summaries, video overviews, slide decks) from their own uploaded sources. Google has been steadily building out the product with features like Expert Intelligence for engaging trusted external content. Moving from flat daily quotas to compute-metered, faster-refreshing limits mirrors the usage-limit model Google already uses in the main Gemini app.

Why it matters

Daily usage caps are a common friction point for AI products that combine free access with expensive backend compute, and a flat daily limit penalizes users unevenly — someone who runs a few large, source-heavy notebooks hits the same wall as someone who runs many small, cheap queries. By pricing usage against actual compute cost and refreshing every five hours instead of once every 24, Google is making the limit feel less like a hard daily cutoff and more like a rolling budget, which should reduce the number of users locked out mid-task. It's also a signal of how Google is managing the real infrastructure cost of increasingly agentic notebook features like autogenerated video overviews and slide decks, which consume far more compute than a simple text query.