NotebookLM Audio Overview Stuck or Not Generating? Here's the Fix (2026 Guide)

I fed a stack of PDFs into NotebookLM to turn them into a podcast-style Audio Overview I could listen to on a walk, and the progress indicator just... sat there. Ten minutes. Twenty minutes. I closed the tab, reopened it, tried again — same thing. If you searched for this, there's a good chance you're dealing with the exact same spinning "Generating" state, and to make it more confusing, Google renamed NotebookLM to Gemini Notebook on July 16, 2026, so a lot of the advice floating around right now is either outdated or talking about a slightly different product than the one you're actually using.

I dug into what's actually causing this, sorted it from what's a genuine bug versus a limit you're quietly hitting, and worked through every fix in order of how likely it is to actually solve it.

Quick Note: Which Product Are You Actually Using?

This matters more than it sounds like. There are now two separate places you can generate an Audio Overview:

1. Gemini Notebook (the standalone research tool, formerly NotebookLM) — you upload sources into a notebook and generate the overview from the Studio panel.
2. Audio Overview inside the main Gemini app — a newer, separate feature where you attach a file directly in a Gemini chat and ask it to generate an audio overview.

They use the same underlying feature but different limits and different failure points. Everything below is written for Gemini Notebook (the old NotebookLM), since that's where "stuck on generating" is reported most.

Why It Gets Stuck

Audio Overview generation is a multi-step pipeline — Gemini has to read every source, build a script, then synthesize two AI voices having a conversation about it. If any one step chokes (a source that's too dense, a scanned file with no readable text, or the backend simply being under load), the progress bar doesn't show an error. It just stays on "Generating" indefinitely instead of failing loudly. That silent failure is the whole problem.

Step 1: Actually Wait It Out, Then Regenerate — Don't Assume It's Broken

Generation for a single document is usually done in a few minutes, but a notebook packed with several long sources can genuinely take 15–20 minutes. Before troubleshooting anything else, give it that long.

If it's still stuck after that:

1. Navigate away to another notebook or page, then come back
2. In the Studio panel, click the three-dot menu next to the Audio Overview card
3. Select Regenerate

This alone clears the stuck state more often than any other fix, simply because it forces the pipeline to restart from a clean job instead of whatever silently failed.

Step 2: Check Whether You've Hit a Source Limit

Gemini Notebook has hard limits that don't always show a clear warning before you hit them:

• PDFs: capped around 500 pages / 200MB each
• Sources per notebook: 50 on the free tier (300 if you're on the Plus/Pro tier)

If your notebook is close to either ceiling, remove a source or split your material across two notebooks, then try generating again. This is one of the most common causes I found once I actually counted my sources — I had quietly gone past 50 without noticing.

Step 3: OCR Any Scanned PDFs Before Uploading

If one of your sources is a scanned document (a photo-based PDF with no selectable text), Gemini Notebook can't extract meaningful content from it, and this is one of the quieter causes of a stuck generation — it doesn't reject the file, it just struggles silently downstream.

Fix it before uploading:

1. Upload the scanned PDF to Google Drive
2. Right-click it → Open with Google Docs (this automatically OCRs it into selectable text)
3. Download the result as a new PDF
4. Upload that OCR'd version to your notebook instead of the original scan

Step 4: Rule Out a Wider Outage

Since Audio Overview depends on Gemini's backend, a broader Gemini slowdown will take Audio Overview down with it even though the rest of Gemini Notebook looks fine. Check the Google Workspace Status Dashboard before assuming the problem is on your end — if there's an active incident listed for Gemini, regenerating won't help until Google resolves it on their side.

Step 5: If You're on a Work or School Account, Try a Personal Gmail

If your notebook belongs to a Google Workspace account (a work or school email), an admin may have restricted AI features org-wide — sometimes this shows up as a generic stuck state rather than a clear "blocked" message. Try creating a test notebook on a personal Gmail account with the same sources. If it generates fine there, the restriction is coming from your organization's admin settings, not a bug.

A New Wrinkle: The NotebookLM → Gemini Notebook Rename

Because the rename rolled out gradually starting July 16, 2026, some users are seeing a mix of old and new branding depending on their browser cache or a bookmarked link. If your notebook looks like it's loading an inconsistent or half-updated interface, do a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) or open the notebook in a fresh incognito window. Your existing notebooks and links still work either way — Google confirmed the rename doesn't require migrating anything — but a stale cached version of the old interface can absolutely cause the Studio panel to misbehave.

What Didn't Work (So You Can Skip It)

• Switching browsers alone — didn't make a difference for me when the actual cause was the source count.
• Deleting and re-adding the same oversized source repeatedly — if a file is over the limit, re-uploading the identical file just fails the same way again.
• Uninstalling and reinstalling the mobile app — Audio Overview generation on mobile has other limitations regardless, and reinstalling didn't fix a stuck job that was already queued from the web version.

How to Tell If the Fix Actually Worked

After regenerating, the progress indicator should move past the initial "Generating" state within a few minutes for a small notebook. For a large one, give it the full 15–20 minutes again before checking. If it completes and you can press play in the Studio panel, you're done. If it's still stuck after trying Steps 2–5, it's worth checking back in a few hours — this is genuinely more likely to be a temporary backend issue than something wrong with your setup.

My Honest Take

None of this is a scandal — Audio Overview is doing a lot of AI work behind a single progress bar, and silent failures are always going to be more confusing than a clear error message would be. The timing of the rename didn't help either; landing in the middle of a name change while also hitting a generation bug is exactly the kind of thing that makes a normal hiccup feel like something's seriously broken. If you've tried everything above and it's still stuck, drop your notebook size and source types in the comments — I'm keeping track of which cases are actually rename-related cache issues versus genuine backend problems.

Frequently Asked Questions

Is NotebookLM the same thing as Gemini Notebook?

Yes. Google renamed NotebookLM to Gemini Notebook on July 16, 2026. It's the same product, the same notebooks, and the same Audio Overview feature — just a new name and logo. Nothing needs to be migrated.

How long should Audio Overview generation normally take?

A few minutes for a single, short source. Larger notebooks with multiple long documents can take 15–20 minutes. Anything beyond that without progress is worth regenerating rather than continuing to wait.

Why does my Audio Overview fail without any error message?

Generation is a multi-step process, and a failure partway through (an oversized source, a scanned PDF with no readable text, or a backend slowdown) doesn't always surface as a visible error — it just leaves the job stuck on "Generating" instead of failing outright.