NotebookLM Audio Overview not generating can mean the source never imported, the notebook does not allow editing, a usage allowance is exhausted, or a generation job is still running. An audio file that exists but will not play is a different problem.
I would establish which stage failed before deleting a notebook or repeatedly pressing Generate. The best comparison is a new notebook with one short, nonconfidential text source. If that works, the service can generate audio for your account and the original notebook deserves closer inspection.
Google’s current help pages use the name Gemini Notebook for this product. This guide retains NotebookLM in the title because readers still use that name, but the controls and limit guidance below follow the current documentation checked on October 13, 2026. Audio Overviews created directly in Gemini Apps are a separate interface and may have different controls.
Check what happens before trying another generation
Open the notebook and look at the source list and Studio panel. Note the exact message, not just the fact that no sound plays.
The source still shows an import error: resolve the source first. There is no useful audio-generation test until the notebook has readable material.
The Audio Overview control is missing or unavailable: check edit access, the active account, and the product interface you are using.
A usage-limit notice appears: inspect the allowance and reset information. Browser cleanup does not increase an account quota.
Generation is in progress: avoid starting several replacement attempts. Return to Studio and check whether the audio becomes available.
An audio player appears but is silent: investigate playback, volume, and output devices rather than generating another copy.
Google’s official Audio Overview instructions say generation requires edit access and runs in the background. You can navigate away while it completes. That makes reopening Studio a better check than assuming that leaving the page canceled the job.
Use one short text source to isolate the failure
Create a fresh notebook in the same account. Add a small source that you wrote and are comfortable uploading. Keep the first test simple enough that you can immediately recognize whether the source was imported correctly.
Here is an original example you can use:
A community library is testing three changes: extending Thursday opening hours, adding a quiet study room, and offering a monthly computer-help session. The trial lasts six weeks. Staff will compare attendance and reader feedback before deciding which changes to keep.
Open the source after importing it and confirm the text is present. Ask a simple source question, such as which day has extended opening hours. A correct answer is useful evidence of source access, though it is not proof that every later output will be accurate.
Then generate one Audio Overview with minimal customization. Choose a shorter option if your account offers it. Do not add several sources or an elaborate instruction while you are trying to isolate a basic failure.
The new notebook generates audio
Return to the original notebook. Investigate unavailable sources, import errors, access permissions, and unnecessary complexity. The result makes an account-wide inability to generate audio less likely.
If you have several original sources, test a smaller permitted subset in a separate notebook. Add material gradually and note when the failure returns. Do not delete the only copy of your research to perform this comparison.
The new notebook also fails
Now compare the same account in a current browser or another supported client. If a private window is available, it can help separate the normal browser profile from the account itself. Sign in with the same account and confirm the notebook is the one you intended to open.
If the same small source fails across clients, collect the error and usage information. The investigation has moved beyond one malformed document; service availability, account access, or quota is more relevant.
A source appearing in the list does not prove it is usable
Open the source and check the content the notebook can actually use. A title in the sidebar is not sufficient evidence that the entire document was imported or remains accessible.
Google’s source guidance distinguishes imported text from the original material. For example, webpage imports do not include every embedded element, and YouTube sources rely on supported captions. A video that plays normally in a browser can still be unsuitable as a source.
For a difficult PDF, check whether the relevant text is selectable and readable in the original document. A scan may need OCR; avoid assuming that splitting or renaming it will repair poor extraction. Export a clean supported copy when appropriate and when you have permission to use the material.
If a Drive source becomes inaccessible after permission changes, resolve the access problem rather than asking the generator to summarize a document it cannot reference.
For alternatives focused on readable document summaries, Free AI PDF Summarizers compares that narrower task. Changing tools is not a substitute for checking what the source contains.
A usage-limit message needs an account check
Older tutorials often describe a fixed number of Audio Overviews per day. Google’s current usage-limit documentation describes compute-based allowances influenced by the task and features used, with refresh behavior and a weekly limit.
Open Settings > Usage where available. Read the reset information displayed for your account. A limit reached after other work is not necessarily evidence that the Audio Overview button is broken.
If Generate later is offered, check its terms and timing before choosing it. Google’s documentation describes this as a web option when immediate usage is unavailable. A queued generation is not the same as an instant retry.
I would not buy a subscription solely because one attempt failed. First confirm that the message identifies a limit and that a higher allowance would address your actual workload. Paying more does not repair an unreadable source, wrong account, or notebook without edit access.
The button is missing in a shared notebook or mobile app
Check whether you are an editor or a viewer. Being able to read a shared notebook is different from being able to generate new artifacts in it. Ask the owner for the appropriate access when generation is part of the collaboration.
Also compare the full web interface with the mobile app. Google notes that the mobile app can have feature limitations. Update the app, confirm the account, and use the web interface for the comparison before reinstalling.
For a work or school account, check with the administrator when the product or feature is unavailable. Do not transfer restricted organizational documents to a personal account merely to make the control appear.
If you only need a study summary, AI Study Tools offers other approaches. An audio overview is one way to review material, not a requirement for effective study.
Generation appears stuck, but there is no error
Note when you started the job and whether Studio still reports it as in progress. Google describes generation as taking a couple of minutes, but that is not a guaranteed completion deadline.
Reopen the notebook and inspect the existing artifact before retrying. A page that has stopped updating may be different from a job that failed on the service.
Compare one small-source test only when your allowance permits it. If that completes while the original job remains unresolved, report the notebook-specific failure with its source types and approximate size. If both fail, record the account-wide pattern.
Avoid repeatedly clearing all browser data. A targeted private-window comparison is more informative and leaves your normal sign-ins and preferences intact. On a managed connection, ask the administrator about access rather than bypassing controls.
Audio exists, but playback or download fails
If Studio shows a completed Audio Overview, generation has succeeded. Start with playback: check media volume, a muted browser tab, Bluetooth headphones, and the selected speaker.
Play another audio clip on the same device. Then test the generated overview on another supported client. This separates a local output problem from an artifact that cannot load anywhere.
If playback works but downloading is unavailable, do not immediately delete and regenerate the overview. Google notes that some source content restrictions can affect downloads, including eligible Play Books material. Review the restriction and the notebook’s access settings.
A failed shared link also needs a sharing check. Confirm that the recipient has the required access. Making private research public just to test a link is unnecessary.
A completed overview can still need editorial review
An Audio Overview is a generated summary, not a guaranteed verbatim reading. Missing a paragraph or emphasizing a different topic is an output-quality issue, not proof that generation failed.
I would listen for names, numbers, qualifications, and any claims the source does not support. Ask focused questions in notebook chat and check the cited passages against the original material. Can AI Be Trusted? explains why source-grounded tools still require verification.
If your purpose is a multilingual presenter video rather than a study conversation, AI Avatar Tools for Multilingual Voiceovers covers that different production workflow. Do not assume a generated discussion is a finished script or public podcast.
For an unresolved failure, send feedback with the exact message, timestamp, account type, client, source types, and the result of the short-source test. Use nonconfidential examples. A reproducible failure in a small notebook gives support more useful evidence than repeatedly deleting and rebuilding a large one.
