Gemini Notebook

A general chatbot given a document will answer from the document and from everything else it knows, and it will not tell you which is which.

For casual questions that is fine. For research it is disqualifying, because the whole point of asking about a source is finding out what the source says — and an answer blending your document with the model's prior training is worse than useless, since it is confidently unattributable.

Gemini Notebook is built around refusing to do that. It answers from what you gave it, with citations back into your own material, and that constraint is the entire product.

Gemini Notebook: The Rename And The Rest

• NotebookLM is now Gemini Notebook, renamed by Google on 16 July 2026. Same team, same notebooks, same product focus.
• Answers are grounded in your sources, not the open web — the design decision that makes it different from a chatbot.
• New: code execution in a secure cloud environment, so a notebook can run data analysis on your uploaded material rather than only summarising it.
• Notebooks now sync with the Gemini app, so the same notebook is available in both places.
• Scale behind it: Google states over 30 million users and 600,000 organisations since the 2023 debut.

Gemini Notebook: Naming And Capabilities

What Changed When NotebookLM Was Renamed?

On 16 July 2026 Google renamed NotebookLM to Gemini Notebook. The product remains a standalone research tool run by the same team, with existing notebooks and sources untouched and links redirecting.

The name matters mostly for finding it. Anyone searching for NotebookLM will land on the same product under a different label, and documentation, tutorials and internal references written before that date now use a name that no longer appears in the interface.

The strategic read is that Google is consolidating its AI products under the Gemini brand, and the announcement frames the change as reflecting how the product will evolve across the Google ecosystem rather than as a change of direction.

Two substantive changes shipped alongside it. Notebooks can now run code in a secure cloud environment, doing data analysis grounded in your uploaded sources rather than only summarising them — rolling out first to AI Ultra and Workspace customers, then to Pro users.

And notebooks created in the Gemini app now sync with the standalone site, so the same notebook is available in both. Google has also said integration with Search's AI Mode is planned, which suggests the standalone product is becoming a component as much as a destination.

Naming churn is not unique to Google. It is worth keeping a note of what a tool was called when you wrote about it — the same problem arises with any product that rebrands, and it quietly breaks internal documentation.

The rename changed the label, not the tool. Same team, same notebooks — but anything you wrote about NotebookLM before July now names something that no longer appears on screen.

Code Execution Is The Real New Capability

Running code in a secure cloud environment against your own sources is a larger change than the rename, and it is worth understanding why.

Language models are famously unreliable at arithmetic. Ask one to compute a total across forty rows and it will produce a plausible number, sometimes correct, with no way to tell which. That has been the hard ceiling on using them with quantitative material.

Executing code removes the guessing. The model writes the calculation, the calculation runs, and the result is the actual result — arithmetic done by a computer rather than predicted by a language model.

For a research notebook holding spreadsheets, reports and datasets, that turns summarisation into analysis. You can ask what the trend is across the quarters in an uploaded file and get a computed answer rather than an impression.

The caution is unchanged from any analysis: the code is only as right as its assumptions about your data. A calculation over a column the model misidentified is precisely wrong rather than vaguely wrong, and precisely wrong is harder to spot.

Source Grounding Is Why People Trust It

The defining constraint is that answers come from the sources you upload, with citations back to them. Everything else the product does follows from that.

The immediate benefit is verifiability. A claim in an answer points at the passage it came from, so checking it takes seconds rather than requiring you to re-read the document you were trying to avoid re-reading.

The deeper benefit is a category of error that simply cannot occur. A grounded notebook cannot tell you something plausible that appears nowhere in your material, which is the failure mode that makes general chatbots unsafe for anything you will be held to.

It also changes what a wrong answer means. If a grounded tool says something incorrect, either the source is wrong or the retrieval missed — and both are diagnosable. When a general chatbot is wrong, you frequently cannot tell why.

The corresponding limit is that grounding is not verification. A notebook built on a poor source will faithfully report poor information with full citations, and the confidence of the presentation makes that more dangerous rather than less. What goes in decides what comes out.

Compare that with a web answer engine. Perplexity cites pages it found rather than pages you chose, which is the right behaviour for a different question entirely.

• Curate sources deliberately — grounding reports what you gave it, wrong or right.
• Check citations on anything you will repeat, since the passage is one click away.
• Use code execution for numbers rather than trusting a model's arithmetic.
• Keep separate notebooks per topic, since a mixed corpus dilutes retrieval.
• Update anything you wrote referring to NotebookLM, which is no longer the product's name.

Where A Notebook Beats A Chatbot

The distinction is about what you are asking for, and getting it right saves a great deal of frustration.

A chatbot is the right tool when you want knowledge you do not have — explain this concept, draft this email, what are the common approaches to this problem. Its training is the asset.

A notebook is the right tool when the answer must come from specific material — what does this contract say about termination, what did these twelve papers conclude, what is in this 200-page report I have not read. Here the training is a liability, because you want the source rather than the average.

The confusion arises because both accept documents. A chatbot with an attachment feels like a notebook and behaves quite differently, blending the attachment with everything else it knows, invisibly.

The practical test is what you would do with a wrong answer. If you would need to know where it came from, use a notebook. If you would simply try again, a chatbot is fine and usually faster.

For academic work specifically, Elicit retrieves from an indexed literature corpus, and a workspace like Cleve answers from everything you have written rather than from one session's uploads.

Setting Up A Notebook That Answers Well

Retrieval quality is decided by what you upload and how you organise it, far more than by how you phrase questions.

The most common failure is one enormous notebook containing everything, which dilutes every query.

1. Create one notebook per question or project, not one per person, since mixed corpora blur retrieval.
2. Upload the primary sources rather than summaries of them, because the notebook can only cite what it holds.
3. Remove sources you know to be outdated, since grounding will faithfully report them alongside current ones.
4. Ask a question you already know the answer to first, and check that the citation points at the right passage.
5. Use code execution for anything numerical rather than accepting a stated total.
6. Re-check citations before repeating anything externally, since a grounded answer is only as good as its source.

Is Gemini Notebook Your Research Tool?

Ideal when

• Your question is about specific documents rather than general knowledge.
• You need to be able to show where an answer came from.
• You have more source material than you have time to read.
• Your notebook contains numbers and you want them computed, not estimated.
• You already work in the Google ecosystem and want the Gemini app sync.

Reach for a chatbot when

• You want knowledge you do not have, where a model's training is the asset.
• You are drafting or brainstorming rather than interrogating sources.
• You have no curated sources, since grounding has nothing to ground in.
• Your sources are of unknown quality, which grounding will faithfully report.
• You need an answer from the live web rather than from what you uploaded.