Google is renaming NotebookLM to Gemini Notebook. The company says it remains a standalone product focused on research and learning, rather than becoming merely a tab inside the Gemini app. The new name signals closer integration with Google’s wider AI ecosystem, while a cloud-computing feature changes what notebooks can do.

Google says more than 30 million people and 600,000 organizations use the product. Those are company-reported adoption figures, not independently audited usage data, but they explain why a rename carries more weight than ordinary product housekeeping. Existing users are being told that the core source-grounded notebook concept continues.

Code execution is the substantive update

Each supported notebook can receive a secure cloud computer that lets the system write and execute code for analysis grounded in the user’s sources. At announcement, Google said the capability was available to Google AI Ultra users and certain Workspace business customers with qualifying access. A web rollout to Pro users was planned over the following weeks.

  • Code execution can turn uploaded tables and documents into calculations, visualizations, and new structured outputs.
  • Access varies by subscription, so users should not assume the feature is present merely because the product name changed.
  • Notebooks can already be created or accessed in the Gemini app with cross-app syncing.
  • Google says notebook access in AI Mode in Search is coming later; that is a plan, not a currently universal feature.

A larger trust boundary

Source grounding has been NotebookLM’s central appeal: the system answers from a bounded collection rather than the open web alone. Giving that environment a computer can make it far more useful, but it also introduces execution risk. Teams should understand what files are mounted, whether network access is available, how generated code is isolated, what logs are retained, and which administrators can control the feature.

The rename also reduces the conceptual distance between a private research workspace and Google’s general assistant and search products. Cross-product access can remove friction, but organizations will need clear rules for sensitive notebooks, syncing, account separation, and data retention. Product convenience should not quietly become broader data exposure.

For users, there is no need to treat the change as a forced migration to a different product. The accurate near-term reading is narrower: the standalone notebook survives, gains staged code execution, and is becoming easier to reach from other Google surfaces.