Gemini Notebook, formerly known as NotebookLM, helps you ask questions about your own sources and create study material, notes and audio overviews from them.
Gemini Notebook (NotebookLM)
Explore features, practical uses and pricing below.
Gemini Notebook, familiar to many people as NotebookLM, is an AI research and study tool built around sources you choose. A notebook can hold material about a particular course, project or question, and you can use that material for explanations, summaries and other learning formats. The starting point is the collection of sources, rather than a blank conversation about any possible topic.
This makes it useful when understanding a set of documents is the main job. A student can work through course readings, a researcher can compare papers, and a team member can make sense of an unfamiliar project. The notebook helps organize the questions you ask of that material. Your reading and judgment still determine whether a passage supports a conclusion and whether the collected sources are sufficient for the question.
For example, imagine joining a product team with a discovery report, interview notes and a launch brief to read. A notebook gives you a place to ask how the launch brief relates to the earlier research. You can look for supporting passages and gaps before writing your own explanation. A useful result identifies the evidence behind a decision, rather than simply producing a smooth account of the project.
Google's source documentation lists documents, PDFs, supported audio and image files, Google files, web pages and public YouTube videos among the available inputs. Source behavior differs by type: imported copies and supported synced material should not be treated as interchangeable. You can select individual sources for a question instead of always using the entire notebook.
Choose a clear purpose before uploading a large collection. A notebook about an upcoming product release might need the approved brief, the latest research summary and the final requirements. Early ideas can be valuable background, but give them names that reveal their status. A document called “Final requirements — September review” is easier to distinguish from “Initial workshop ideas” than two files named “notes.”
Keep a small source register in your own working notes. Record the author, date and reason each document belongs in the notebook. If you later receive a revised brief, check the relevant source's update behavior and make sure the notebook is working from the intended version. Do not assume that a file containing yesterday's information has become current merely because you opened the notebook today.
A focused collection also helps you notice missing evidence. If all your sources are internal proposals, they cannot establish what customers actually experienced. Add appropriate first-hand material before asking customer research questions. The notebook can help analyze what you supply, but a source list with a narrow perspective will remain narrow.
Gemini Notebook is designed for source-grounded work. Google's getting started guide explains how uploaded material supports responses and research tasks. Citations help you move from an answer to the underlying source. The interface can also produce summaries and learning artifacts from the notebook, depending on the features available to the account.
Begin with a question whose answer should exist in your material. For the product team example, ask which customer problems the launch brief intends to address and which interview passages support each problem. That is more useful than asking whether the product will succeed. One question asks for a connection between sources; the other asks for an outcome that those documents cannot establish.
Open a cited passage and read beyond the highlighted sentence. Check who said it, what question they were answering and whether the surrounding text changes its meaning. A short quotation from an interview can look definitive while describing only one customer's unusual situation. Use the citation as a reading aid, then decide how much weight that evidence deserves.
When an answer seems incomplete, narrow the question or select a smaller group of sources. Ask for the passages discussing one requirement before requesting a whole project narrative. A useful follow-up is to ask what the sources do not resolve. This can reveal the next document you need to find or the question that belongs in a team discussion.
A notebook can be particularly helpful when several documents cover the same subject differently. In a project review, one document may describe the original intention, another the implementation and a third the results. Keep those roles separate in the question. Ask for an account of how the plan changed, including dates and supporting passages, instead of a single summary that treats every document as equally current.
For a reading project, try a comparison with named dimensions. Ask how two authors define the main concept, what evidence each uses and where their conclusions differ. Then read the relevant sections yourself. The comparison becomes a map for deeper reading. It should not turn a disagreement between the authors into an apparently settled conclusion.
Use a simple claim-and-evidence format in your own notes. For each claim, record the supporting source, the relevant context and any competing passage. If the notebook supplies a plausible inference, label it as an inference until you have checked it. This keeps your later report from presenting interpretation as a direct statement from the original author.
The current notes documentation places notes in the Sources panel, where selected notes can contribute to answers and generated artifacts. Notes can include your own text or a saved response. Exporting notes to Google Docs creates a separate copy; later changes do not automatically synchronize between the exported document and the original note. Note editing also differs between web and mobile.
This is useful for keeping a running interpretation alongside the original reading. Give personal notes a title that identifies them as your commentary. For example, “My questions after reading the interview report” clearly describes the note's role. A title such as “Customer findings” could make an unreviewed personal summary look like an original research source.
Choose whether those notes should be included when asking a new question. If you are checking what the original sources say, leave your provisional interpretation out of that pass. Otherwise an earlier summary may influence the next answer and make your own assumption appear repeatedly supported. Include the note when you deliberately want to develop or challenge that interpretation.
Before exporting a note for other people, add enough context to make it readable outside the notebook. Explain the question, identify the sources and separate your observations from unresolved issues. Someone reading the exported document may not have the notebook open, so references such as “this passage” need a meaningful source name.
Audio Overviews turn source material into generated spoken explanations. Google's documentation describes formats including Deep Dive, Brief, Critique and Debate, with controls for focus and other options. These are synthesized presentations of the material, not recordings of the original authors. Language and interactive features have their own availability limits.
Choose the format for a specific listening task. A brief overview can help you revisit a topic before reading its details. A discussion format may make relationships between ideas easier to follow. For difficult or contested material, listen with your source notes available and mark any statement you want to investigate. The audio is another way to approach the documents, not a substitute for checking a key quotation or number.
Give the generation a narrow focus when the notebook has several themes. In the product example, you might request an overview of the evidence behind the onboarding changes, rather than the entire release history. After listening, return to the source passages that matter for your work. If the narration overstates an uncertain finding, record the correction in your own reviewed notes.
Gemini Notebook's flashcard and quiz tools generate interactive study aids from notebook sources. The Studio panel provides controls for difficulty and focus. You can request explanations and review missed material. The documented flashcard controls also support downloading a deck as CSV, subject to source-related restrictions in applicable cases.
Use these tools after deciding what you need to learn. A course reading may include background stories, terminology and arguments. If the assessment is about comparing arguments, a deck consisting only of definitions will not prepare you for that task. Ask for study aids focused on the relevant concepts, then compare a sample with the course objectives.
When an answer feels ambiguous, return to the original material. A generated question might simplify a distinction that the reading treats carefully. Write your own explanation of the distinction before practicing again. The goal is to understand why an answer is right in context, rather than memorize the exact wording of an automatically produced card.
Suppose you have a discovery report, a set of interview notes and a final launch brief. Create a notebook specifically for the relationship between customer needs and release decisions. Name each source clearly and record its date. Keep unrelated marketing drafts out of the first pass so they do not distract from the evidence you are examining.
First, ask for the main customer problems in the interview material. Request supporting passages and note whether the same problem appears across different interviews. Read the cited context. A strongly worded comment from one participant should remain distinguishable from a recurring theme. Add your checked observations to a personal research note.
Second, compare those problems with the approved launch brief. Ask which planned changes correspond to which problems and which problems appear unaddressed. Check the matches manually. Similar words do not always indicate the same requirement; a request for easier setup could concern account creation, initial configuration or staff training.
Third, identify decisions that lack enough explanation. Draft a short list of questions for the project owner: why a requirement moved to a later release, whether a missing feature was deliberately excluded, and where success measures were agreed. Keep these as questions instead of asking the assistant to supply a rationale the documents do not contain.
Finally, write a reviewed project brief. Explain the evidence, the approved decisions and the remaining questions in separate sections. Include source names where a colleague needs to investigate further. An Audio Overview can help you revisit the material before a meeting, but the final brief should contain the checked detail needed for the actual discussion.
Google's usage guide describes compute-based allowances that depend on the work performed and the account's plan. Generation, model choice and longer interactions can affect usage. Paid Google AI plans provide different allowances. Use the account's usage view and current plan information rather than relying on old fixed daily chat or audio limits quoted elsewhere.
For a class or work account, confirm that the service and needed capabilities are enabled by the organization. For mobile work, check the controls for the specific task: viewing a note, editing it and generating a particular artifact may not have identical support across devices. Plan a substantial document review around the interface that gives you the source inspection and editing tools you need.
A small trial can help determine whether the notebook fits your workload. Use a real set of material, ask several meaningful questions and inspect the citations. Check whether you can produce an accurate brief with less effort spent locating relevant passages. Include the time spent preparing sources and correcting the result when judging its usefulness.
It suits people whose work begins with a defined body of information: students reviewing readings, researchers comparing publications, analysts examining reports and colleagues learning a documented project. It is less straightforward when the main need is unrestricted conversation, an operational workflow across business apps or a finished visual presentation. Those tasks may need a different tool alongside the notebook.
The strongest reason to use it is the connection between a question and the supplied evidence. Keep that connection visible as you move from reading to notes, audio and a final document. A well organized notebook can make a complicated topic easier to approach without pretending that every generated explanation is the last word on it.
The official notebook website and current help center use Gemini Notebook. This listing retains NotebookLM in its name so people familiar with the earlier name can recognize the tool. Use the official help pages for current features and account limits.
Yes. Select the relevant source or sources in the notebook and make the scope clear in the question. This is useful when checking a single author's position before comparing it with the rest of the collection.
No. They are generated spoken treatments of the notebook's material. Check important statements against the underlying source, particularly when the material contains conflicting views or precise details.
Include them when you want the notebook to work with your interpretation. Leave them out when you are checking the original evidence independently. Label personal notes clearly so your provisional conclusions remain distinguishable from the documents you collected.