How to create NotebookLM slide decks from your sources

To create a NotebookLM slide deck, open a notebook with your sources, choose Studio > Slide Deck, set the format, language, length, and sources, then describe the presentation and select Generate now or Generate later. Google’s slide-deck guide↗ (opens in a new tab) calls the product Gemini Notebook. Review the generated claims before presenting. fenbs can keep the checked evidence, instructions, and remaining work available after the slide-making session ends.

What are the steps from sources to a first deck?

1. Open a notebook containing the documents needed for the presentation. Decide who will watch it and what they should understand afterward.
2. Select Studio > Slide Deck. Choose format, output language, length, and the sources for this deck.
3. Describe the audience, purpose, intended sequence, and important qualifications. Give the presentation one clear outcome.
4. Select Generate now or Generate later. Once the draft is ready, review its claims and order before making visual refinements.
5. Recover the instructions with View custom prompt in the generated deck’s three-dot menu. Keep the prompt and your review notes beside the accepted version.

The feature guide requires users to be over 18 and have edit access to generate or delete decks. Mobile is supported with possible differences. The separate outline co-creation flow is restricted to Google AI Ultra; that restriction should not be applied to every deck-generation workflow.

Start with an audience and a question, rather than a slide count. A short briefing for a teammate who knows the background needs a different structure from an introduction for a new client. Write the distinction down before asking for the first draft.

How should you choose the source collection?

Include the evidence for the main argument and the material that could change it. A recommendation deck might need requirements, findings, and an unresolved-risk list. Leaving out the risks can make a tentative conclusion look final even if the included evidence is summarized correctly.

Check versions and dates before generation. Put a human-readable source title in your own evidence notes so a reviewer can distinguish the accepted report from an earlier draft. If a figure depends on a particular page or appendix, record that location too.

Google’s source guide↗ (opens in a new tab) documents automatic syncing for imported Drive files and a manual Click to sync with Google Drive control. Do not assume every source type updates that way, or that a changed source also updates a deck you already generated.

Make the presentation from a collection you have reviewed, rather than relying on the presentation to reveal everything important in the collection. The wider routine in study with NotebookLM can help when you are still learning the material yourself.

What instructions make the draft easier to review?

Ask for a specific sequence that follows the reader’s needs. State the question first, show the evidence next, then explain the implication and what remains undecided. A source collection has its own order; your audience should not have to reconstruct that order to understand your conclusion.

Audience: a design team reviewing a proposed process change.
Outcome: understand the evidence and the decision still needed.
Sequence: current problem, checked findings, proposed change, risks, next decision.
Use the selected sources and keep uncertainties visible.
Distinguish observed results from recommendations.
Do not turn a proposed action into an approved commitment.

This is a request to evaluate after generation. A sentence in the prompt does not establish that the resulting slides followed it. Compare the deck’s conclusion with the requested outcome, then inspect whether the evidence really supports that conclusion.

Keep the instructions that worked and explain why. “Put the decision needed on the final slide” is useful when it helps your audience act. A record in fenbs lets another assistant retain that reason when helping you write a follow-up presentation.

How do you verify the presentation before presenting it?

Google warns that generated decks can contain factual and visual errors. Review the story as well as individual statements. Ten accurate facts can still produce a misleading recommendation if they omit a relevant exception or appear in a sequence that suggests a stronger conclusion.

• Match important claims to source passages. Confirm figures, time periods, named groups, and units.
• Read slide titles as one continuous argument. Check whether they make a claim the body text does not support.
• Inspect charts and diagrams for implied scale, causation, and sequence. Verify the meaning, rather than only the labels.
• Look for missing qualifications. Preserve the difference between early evidence, an estimate, and an established result.
• Read the final recommendation separately. Name the person who must decide and anything still waiting for verification.

Then rehearse aloud. Notice where you need to add a caveat that the audience cannot see. Either make it visible in the presentation or narrow the slide’s claim. A confident delivery should not have to repair an inaccurate visual summary.

What changes when you revise a generated deck?

In Revise, per-slide instructions collect under Pending Changes; Generate revised deck makes a new deck and uses revision allowance. Crucially, Google says revisions do not take sources into account. Treat every changed factual claim as needing another comparison with the original evidence, rather than assuming revision rechecked it.

Separate a visual request from an evidence request in your review notes. “Increase the heading size” and “replace this estimate with the accepted figure” need different checks. For the second, open the source yourself and record exactly what should change before evaluating the revised result.

If access or generation allowance interrupts the work, consult NotebookLM daily limits and the notice in your account. Google’s general availability guide↗ (opens in a new tab) establishes US and eligible managed-account access, while the deck guide does not provide a complete quota table.

For output, the guide lists Download PDF Document (.pdf), Download PowerPoint (.pptx), and Start slideshow. Its earlier summary mentions PDF alone, so verify your actual download menu before promising a recipient a format. Exporting NotebookLM work covers the broader preservation task.

How to keep the evidence behind your slides with fenbs

Keep the work so you can continue from exactly where you stopped, on any device and in another AI. Save the source locations, accepted argument, working prompt, and slides still awaiting review. A list of what is unfinished is often more useful than another full copy of the conversation.

1. Create a free account.
2. Add a task for the presentation. Write its audience, purpose, source locations, and the decision the audience will need to make.
3. Save the checked findings and useful prompt. List corrections by slide and clearly mark anything not yet verified.
4. Connect a supported AI through Integrations. Ask it to read the saved work before helping with the next version.
5. Save where you stopped before ending the session. Link the current deck and name the next person or check needed.

fenbs does not create the slides, verify the source documents for you, or automatically import the notebook. If you need a one-time presentation with no ongoing review, a deck and a short evidence checklist may be sufficient. It helps when the work must continue across sessions.

What should be ready for the next presentation?

Retain the accepted deck location, source versions, tested instructions, important corrections, and final approval status. Keep unresolved questions visible. The next person should be able to tell what can be reused and what needs a new evidence check.

If the message fits in one visual, creating a NotebookLM infographic is a separate option. For broader research workflows, browse AI at work. NotebookLM command-line tools covers a different route for technical users; it does not replace reviewing the evidence in your presentation.