NotebookLM Not Working? Fix Source, Upload and Generation Errors

The source is rejected, disappears after upload, or displays “source import failed.” A PDF may fail even while smaller files continue to work.

Official cause The source exceeds the documented word or file-size boundary, or the original PDF is copy-protected. If none applies, the file may be damaged, permission-restricted or unusually complex.

1. Check the source word count and local file size.
2. Open the original file and confirm every page renders normally.
3. Check whether copying text from the PDF is restricted.
4. Upload a small known-good PDF to the same notebook, then test the problem file in a new notebook.

1. Save an unlocked copy you are authorized to use.
2. Re-export the document as a standard PDF rather than printing through a proprietary viewer.
3. Split a very large document into logical chapters.
4. For a Drive source, confirm that the signed-in account can open it directly.

Recommended workaround Convert the essential content to a clean Google Doc, Markdown or text file while preserving the original filename and source record. For image-heavy scans, create a searchable text layer before importing.

Only for a temporary upload incident. Waiting does not fix copy protection, an oversized source or a damaged file.

Usually no. Upgrading does not raise the documented 500,000-word or 200 MB per-source ceiling.

A website, YouTube or other URL is rejected immediately, shows “Invalid URL,” or imports without usable content.

The URL may be malformed, redirected, login-gated, private, unsupported, missing a usable transcript, or blocked from automated access. YouTube imports can also fail when the link or source is not eligible.

1. Open the URL in a private browser window without signing in.
2. Remove everything after tracking parameters such as ?utm_ or session identifiers.
3. Use the final canonical article or watch-page URL rather than a shortened or redirecting link.
4. For YouTube, confirm the video is public and has an available transcript or captions.

1. Paste the clean public URL again.
2. Use the article page instead of a category, search or share-preview URL.
3. For a page you are authorized to use, save the content as PDF or copy the essential text into a clean document.
4. For video, add an authorized transcript as a text source when direct import is not available.

Recommended workaround Create a source note containing the page title, publisher, date, canonical URL and copied text. This preserves provenance even when the live page cannot be imported.

Sometimes. Waiting may help a temporary access or service problem, but not a private, unsupported or malformed URL.

No. A higher plan does not make an inaccessible URL public or supported.

The source never becomes ready, remains unavailable for chat, or appears without usable citations and summaries.

Observed behavior Complex layouts, OCR-heavy scans, embedded media, remote-access changes, browser-session problems and temporary processing delays can all produce the same symptom.

1. Wait long enough to distinguish normal processing from a true stall.
2. Add a small known-good source to the same notebook.
3. Add the problem source to a fresh notebook.
4. Try a private browser window with only the intended Google account signed in.

1. Refresh once without repeatedly deleting and re-adding the source.
2. Re-export the source with a simpler layout.
3. Split image-heavy documents into smaller logical files.
4. Remove and re-add a remote source only after confirming its permissions.

Recommended workaround Continue analysis from a clean text export or chapter-level file. Keep the original source in an external inventory so the temporary workaround does not become the only surviving copy.

Yes, when the cause is a temporary queue or service delay. If the same file repeatedly stalls, waiting alone is unlikely to help.

Usually no. A higher plan does not repair a source that cannot be parsed or accessed.

The Add source action is blocked or the notebook says it cannot accept another source while existing sources still work.

Official limit The notebook has reached the sources-per-notebook capacity for the active account tier. This is different from a single source exceeding its own size boundary.

1. Add the same source to a new notebook.
2. If it works there, the original notebook is full or has a notebook-specific issue.
3. Check the current account badge and the live plan table rather than an old screenshot.

1. Remove duplicates and superseded versions.
2. Move archival sources to a separate notebook.
3. Keep only sources that directly support the notebook’s current question.

Recommended workaround Use a master source inventory, topic notebooks and bridge documents that summarize local findings with source references. Merge only tightly related documents when file-level citation separation is not important.

No. Capacity limits do not reset with time.

Sometimes. Upgrade only when the higher source capacity is enough; otherwise the project still needs a multi-notebook design.

The New notebook action is unavailable, creation fails, or a message says the maximum number of notebooks has been reached.

Official limit Notebook counts are account-level capacity limits. They are separate from sources per notebook and from daily generation quotas.

1. Confirm that existing notebooks still open normally.
2. Check the notebooks-per-user limit for the account’s access level.
3. Verify that the intended Google account—not another profile—is active.

1. Export critical notes and artifacts from obsolete notebooks.
2. Delete only notebooks that are no longer needed and whose contents are backed up.
3. Consolidate abandoned test notebooks into an external project archive.

Recommended workaround Maintain an external notebook register with purpose, owner, status, last review date and archive location. Create new notebooks only for distinct research questions or production stages.

No. Account-level notebook capacity does not reset after 24 hours.

Sometimes. It helps only if the upgraded access level includes more notebooks per user.

New chat questions are blocked, a usage-limit notice appears, or chat works in some contexts but the account refuses additional queries.

Official limit The active access level has reached its daily chat allowance. Google states that daily quotas reset after 24 hours.

1. Record the time of the last successful chat or first limit message.
2. Confirm the signed-in account and its current badge.
3. Test whether the block affects all notebooks under the same account.

1. Stop repeated retries that add no value.
2. Save unanswered questions in one prioritized list.
3. Combine related questions into a structured prompt for use after reset.

Recommended workaround Use notebook notes to organize evidence and draft the next analysis request. For urgent work, export the grounded evidence and continue drafting in another tool while preserving citations and source links.

Yes. Allow the full 24-hour reset window stated by Google rather than assuming midnight local time.

Yes, when a higher plan raises the daily chat allowance enough to match sustained use.

The same limit message remains after waiting, or a feature still appears unavailable the next morning.

The quota may be rolling, monthly rather than daily, attached to another signed-in account, or not the real cause. A notebook or source-capacity limit will not reset at all.

1. Identify whether the message refers to daily use, monthly use or capacity.
2. Use the time of the first block or last successful action as the reference point.
3. Confirm the account badge and whether multiple browser profiles are active.
4. Test a simple action in a fresh notebook after the full window.

1. Wait for the complete documented window.
2. Sign out of extra Google accounts, then sign back into the intended account.
3. Refresh the page and test a new notebook before changing existing work.
4. Capture the exact message and time if the block persists.

Recommended workaround Plan generation-heavy work in batches and keep a lightweight usage log when a deadline depends on reset timing. Avoid repeatedly regenerating near-identical artifacts.

Yes, for daily or monthly quotas after the full window. No for notebook, source or file capacity.

Sometimes. Upgrading helps future allowance but does not repair a misidentified account, stuck source or capacity boundary that the plan does not change.

The product still behaves like the previous tier, premium controls are missing, or the expected account badge does not appear.

The active browser profile may be signed into a different account, the purchase may belong to another Google One profile, or a managed account may need a qualifying Workspace license or administrator action.

1. Check the account email in the profile menu.
2. Look for the distinct Plus, Pro, Expanded or Ultra badge next to the profile image.
3. Open the plan-management page from the same account.
4. For work or school accounts, confirm the assigned license with the administrator.

1. Sign out of extra Google accounts and sign back into the upgraded one.
2. Open a private window and sign into only that account.
3. Create a new test notebook after the badge appears.
4. If the badge remains missing, use official feedback or support rather than repeatedly editing content.

Recommended workaround Keep personal and Workspace research environments clearly separated. Add the account email and plan badge to your project runbook so collaborators do not diagnose an entitlement problem as a file problem.

A short entitlement delay may clear. Waiting is not a substitute for verifying the account and badge.

You already upgraded. The task is to restore the correct entitlement, not buy another plan.

The app is unavailable, a feature is missing only on a managed account, or the work/school account has lower access than expected.

Official access rule Gemini Notebook is a core service for many Workspace and Education editions, but feature access and higher limits vary by edition and add-on.

1. Compare behavior in the managed account and a personal account without moving confidential data.
2. Check the current account email and access badge.
3. Ask the administrator which Workspace edition and Notebook access level are assigned.

1. Ask the administrator to confirm that Gemini Notebook is available for the organizational unit.
2. Request the qualifying license or expanded access when the role requires it.
3. Use only organization-approved accounts for protected work content.

Recommended workaround For deadline work, build a compliant fallback using approved Drive documents and exported notes. Do not move confidential sources into a personal account merely to bypass administrator controls.

Not usually. Administrator and license issues do not resolve simply by waiting.

Yes, through the correct Workspace license or add-on. A personal Google AI purchase may not change the managed account.

The Audio Overview control is missing, generation ends with “failed to generate,” the player says it could not load audio, or the artifact never becomes playable.

Common causes include exhausted usage allowance, viewer-only access, incomplete source processing, mobile feature differences, complex custom instructions or a temporary generation or playback issue.

1. Confirm that you have edit access to the notebook.
2. Verify that the selected sources finished processing.
3. Try a default Audio Overview without a long custom prompt.
4. Check whether an existing audio artifact loads in another browser or device.

1. Generate from a smaller, source-ready notebook.
2. Shorten the custom instructions and remove conflicting requirements.
3. Refresh the notebook before starting one new attempt.
4. If the artifact exists but will not play, download or reopen it from the Studio panel when available.

Recommended workaround Create a briefing document or structured script from the sources, then produce audio in an approved external tool. Keep NotebookLM as the grounded synthesis layer rather than making the entire deliverable depend on one audio render.

Yes. Background generation and temporary incidents can require time; repeated immediate retries may consume allowance without improving the result.

Only for quota or feature-access limits. It does not repair edit permissions or unfinished sources.

The Video Overview control is missing, the job remains in progress, generation fails, or Cinematic or Short format is unavailable.

Possible causes include no edit access, unfinished sources, usage limits, mobile differences, language restrictions for certain formats, or a long-running background generation.

1. Confirm edit access and source readiness.
2. Check whether the requested format supports the selected language.
3. Allow a long-running job to finish rather than starting duplicates.
4. Test the default Explainer format in a smaller notebook.

1. Use default format and language for the diagnostic attempt.
2. Reduce the number of selected sources or simplify custom instructions.
3. Return later to the existing job instead of creating a second identical job.
4. Use a shorter source-grounded script as a fallback.

Recommended workaround Export a storyboard, narration script and visual brief, then render the final video in another production tool. This protects the research work from a single long-running generation dependency.

Often. Google says Video Overview may sometimes take more than 30 minutes.

Only when higher access changes the relevant usage or format availability.

NotebookLM says “Slide deck generation failed. Try a new one,” the deck remains in a failed state, or NotebookLM is not generating a Slide Deck even though other Studio outputs still work.

Likely causes include viewer-only access, unfinished sources, a usage limit, conflicting custom instructions, a temporary service issue, or repeated revisions consuming deck quota.

1. Confirm that you can edit the notebook.
2. Check that all selected sources finished processing.
3. Try a short default deck without a detailed custom prompt.
4. If revising, group all pending slide changes into one generation.

1. Generate a short default deck as the diagnostic baseline.
2. Reduce conflicting audience, style and length instructions.
3. Batch revisions rather than submitting one change at a time.
4. Download a successful deck before attempting major changes.

Recommended workaround Generate a grounded outline and slide-by-slide content brief, then finish design in PowerPoint, Google Slides or another approved tool. Preserve source references in speaker notes or a separate evidence map.

Yes. Generation can take multiple minutes; a quota block requires the reset window.

Only if the account needs higher generation or revision capacity. It does not fix permissions or source readiness.

The Deep Research action is missing, disabled, blocked by a quota message, or fails before returning a report and sources.

Availability and usage limits vary by access level. Managed accounts can also differ by Workspace edition and administrator-assigned license.

1. Confirm the signed-in account and its badge.
2. Check whether the feature is available from the source-discovery or research interface.
3. Test a narrower research request.
4. For managed accounts, verify the assigned access level with the administrator.

1. Reduce the research scope and retry once.
2. Use Fast Research or manually add a curated set of web and Drive sources.
3. Preserve the research question and inclusion criteria before switching tools.

Recommended workaround Run the discovery stage in Gemini, Google Search or another approved research tool, then import the selected evidence and research report into NotebookLM for grounded synthesis.

Yes, if a time-based quota was reached or the service is temporarily unavailable.

Yes, when the needed access is included in a higher Google AI or Workspace level.

Controls disappear, actions silently fail, the page loops, or several features stop without naming a quota or maximum.

The cause may be a browser session, account mismatch, source access change, notebook-specific state, Workspace policy, network restriction or temporary service issue.

1. Try a known-good source in a new notebook.
2. Use a private browser window with only one account signed in.
3. Test the same action on another device or network.
4. For managed accounts, confirm administrator access.

1. Preserve the notebook and source files before making destructive changes.
2. Refresh the session and test one clean action.
3. Remove only the most recently added source if the issue began immediately afterward.
4. Record the exact time, browser, account and action, then report the problem.

Recommended workaround Continue from exported notes, a source inventory and a backup notebook. Avoid repeatedly forcing the same failed action when the underlying research can continue elsewhere.

Maybe. Waiting helps service incidents but not permission, account or source defects.

Not until the cause is identified. A silent failure is not evidence that the plan is too small.

The upload is rejected immediately, an audio or document file is labeled unsupported, or the same content works only after conversion.

Official source rule The extension may be unsupported, the file may be mislabeled or damaged, or the user may be trying an unsupported route such as importing an audio file from Drive.

1. Compare the file extension with Google’s current supported-source list.
2. Open the file locally to confirm it is not damaged.
3. Try a small known-good file with the same extension.
4. For audio, upload the local file instead of importing it from Drive.

1. Rename the file only when the extension accurately matches the format.
2. Export the source to PDF, DOCX, TXT, Markdown, CSV or another supported type.
3. For audio, use a supported local audio format with clear speech.
4. Avoid converting a protected or inaccessible file without permission.

Recommended workaround Preserve the original and create a clean derivative specifically for NotebookLM. Record the original filename and source URL so provenance is not lost.

Only for a temporary upload fault. Waiting does not make an unsupported format supported.

Usually no. Plan upgrades do not change whether the source type or import path is supported.

A Google Doc, Slide or Sheet changed in Drive, but NotebookLM still shows an older copy, the refresh control is missing, or the source becomes inaccessible.

Official sync behavior The account may have lost view access, the original file may have been deleted, sync may be delayed, or the source may need a manual Drive sync.

1. Open the original Drive file with the same signed-in account.
2. Verify that the document still exists and you retain at least view access.
3. Open the source inside NotebookLM and look for the manual Drive-sync control.
4. Check whether the notebook is shared and the active user has different permissions.

1. Select “Click to sync with Google Drive” from the source view.
2. Close and reopen the notebook after the sync attempt.
3. Restore Drive permissions when access was removed.
4. Re-import only when the existing source remains inaccessible after permissions are fixed.

Recommended workaround For high-stakes work, keep a source inventory with the Drive URL, owner, last-edited date and last-synced date. This makes stale-source problems visible before analysis begins.

Yes. Automatic sync may take a few minutes, but waiting will not restore deleted files or lost permissions.

No. A higher plan does not restore Drive access or repair a deleted original.

The Mind Map option is missing, generation appears to finish but no map appears, or the map is available on desktop but not in the mobile app.

Official availability rule Mobile does not currently support Mind Maps; on desktop, usage quotas, unfinished sources or a failed artifact can also block generation.

1. Confirm whether you are using desktop web or the mobile app.
2. Verify that the selected sources are ready and active.
3. Check the Studio panel for an existing generated Mind Map note.
4. Test a small notebook with one clean source.

1. Use Gemini Notebook in a desktop browser.
2. Delete the failed or stale Mind Map note and regenerate once.
3. Reduce the selected source set for a diagnostic attempt.
4. Wait for the applicable creation quota to reset when a limit message appears.

Recommended workaround When the map remains unavailable, ask chat for a hierarchical topic outline and relationship list, then move that structure into a diagram tool.

Yes. Waiting helps only for a temporary generation issue or quota reset.

Sometimes. A higher plan may raise creation quotas, but it does not add mobile support.

Chat says it cannot answer, asks you to rephrase, returns no usable answer, or repeatedly misses information you believe is in the notebook.

Common retrieval pattern The source set may not contain the answer, the wrong sources may be selected, the wording may be ambiguous, or the topic may trigger a safety response.

1. Search the source text directly for the key fact or phrase.
2. Select only the two or three sources most likely to contain the answer.
3. Ask for the location of evidence before asking for interpretation.
4. Rephrase the question with the document name, date, entity and desired output.

1. Use a question such as: “In [source name], what does the section on [topic] state?”
2. Ask NotebookLM to list which selected sources contain relevant evidence.
3. Split a compound question into fact retrieval, comparison and conclusion.
4. Add a missing authoritative source when the evidence is not in the notebook.

Recommended workaround Build a question ladder: locate evidence, extract the passage, compare sources, then synthesize. This reduces failures caused by asking for a conclusion before retrieval succeeds.

Usually no. Waiting does not add missing evidence or clarify an ambiguous question.

Usually no. More quota does not fix a missing-source or question-design problem.