AI Tools
Tutorial8 minNovember 10, 2026By AIGCDev

NotebookLM Source Import Failed or Not Updating? Troubleshooting Steps

When NotebookLM shows outdated information or cannot answer a question, don't reimport everything immediately. The problem may be in the import, the content captured in a source, the source version, or the answer's citations. Open the specific source and compare a distinctive sentence or version marker with the original before deciding whether to restore access, sync, add material again, or regenerate an output.

This guide covers the desktop experience. Google's current help center calls the product Gemini Notebook; we also use the familiar NotebookLM name here. The features and limits below were checked on November 10, 2026. Interface labels may change by language or product update. The steps are based on official documentation; we have not run an end-to-end product test for this guide.

Find the layer with the problem

What you see Check first Next step
A source fails to add File size, format, or link conditions Check the import-failure section and retry after correcting the condition
The source opens but content is missing Whether the target text appears in the source viewer Compare the import scope for that source type; add text you have rights to use if needed
The original Drive file changed but the source looks old Whether the source came from Drive and your account still has viewing access Reopen the notebook, allow time to sync, then manually sync if needed and check
The source has new content but an old report or audio has not changed Whether you are viewing a previously generated Studio output Select the updated source, generate a new output, and inspect it
The source contains the information but the answer is wrong Whether the right source is selected and its citation supports the answer Narrow the selected sources, ask again, and inspect the citation

More than one issue can occur at once. A Drive document can update while an earlier Audio Overview stays unchanged. Google says updating or deleting a source does not change Studio outputs already generated from it. See the official source guide for source selection and this limitation.

1. The source won't import: rule out documented limits

Record the source type, exact error, and time, then retry only the affected source. Check the link or make sure the file opens at its original location. Google's import troubleshooting lists sources exceeding 500,000 words, uploaded files exceeding 200 MB, and copy-protected PDFs as possible causes. The source guide lists supported formats and additional limits for some formats. If splitting a large document, preserve section headings and order, then open each part to confirm the required passages are present.

Also check whether the notebook has reached the source count limit for your plan. The official plan table distinguishes plans and source types, and limits can change. Inaccessible Drive sources still count toward the limit; consider removing one only after confirming you no longer need it.

For a webpage, make sure the URL points to the page you need, rather than an index or content visible only after signing in. Paywalled pages are unsupported, and a page opening in your browser does not prove the service can fetch it. If the link still fails, you can copy the necessary text into a new source if you have the rights to use it; record the original URL and date and check the new source for completeness. This workaround does not establish that the original URL was fixed.

For YouTube, check that the video is public, the link is correct, and captions are available, whether uploaded or automatically generated. Google says videos without speech are unsupported, videos uploaded less than 72 hours ago may not be available yet, and an unsupported language or missing caption file can also cause failure. If it still fails after waiting and you have rights to use a transcript, add the transcript as a separate source and record its origin. That does not prove the video link itself is fixed. See the official YouTube import conditions.

If the conditions appear satisfied but import still fails, retain the error and report it using the in-product feedback option. Repeated retries alone do not establish the cause.

2. The source was added, but content is missing

Open the source from the left panel and look for a distinctive passage that you can identify in the original. First confirm that the original contains it. A single generated answer cannot establish whether the import is complete.

  • Webpages: Google says the import extracts the HTML page's text, not images, embedded videos, or nested pages. Add a relevant subpage separately. If the information exists only in a chart or video, find a text explanation or another supported source you have rights to use, then open it and check the content.
  • YouTube: The imported source is the video transcript, not its visuals. A transcript cannot supply onscreen text, charts, or visual details that captions do not describe. Compare the original captions with the imported source; add a separate text explanation you have rights to use if needed.
  • Google files: Google says footnotes and comments are not imported. If a necessary fact appears only there, put the material you have rights to use into the document body or a separate source, then check the viewer.

These are documented source boundaries, not explanations for every possible omission. If content remains missing after adding it again, retain the difference between the original and the imported source for feedback. Don't assume the model has read text that does not appear in the source.

3. The Drive original changed, but the source looks old

Check how the source was added: a file imported from Google Drive and a locally uploaded file copy do not have the same update path. Google currently says Drive-imported sources update automatically every few minutes, and changes update when you open the notebook. If needed, open the source and select “Click to sync with Google Drive” to update it manually. See the official Drive import instructions.

  1. Confirm the edit was saved in the original Drive file and identify a new sentence or version date. Make sure the current account can still view the correct file. If the file was deleted or access was lost, the source becomes inaccessible; restore access or request it from the owner.
  2. Reopen the notebook, wait a few minutes, and open the source to look for the same marker. This reflects Google's stated sync frequency, not a guarantee that every edit completes within a fixed deadline.
  3. If it is still old, open the source and use the manual sync option when available, then check the marker again. If it remains inaccessible or outdated, retain the file, account, time, and observed error details for the owner or in-product feedback.

For a locally uploaded file, treat the imported material as a copy of that upload; do not assume later local edits enter the notebook automatically. When you need a new version, upload a file you have rights to use again. Open the new source and check its version marker, then select it and deselect the old version when asking questions to avoid mixing them. Decide whether to remove the old source only after confirming you no longer need it; removal will not automatically alter old Studio outputs.

Similarly, a link in an old webpage or video source does not by itself establish that its content is current. When you need the latest content, add it again and check its date and key text in the source viewer. If you keep the old source for comparison, explicitly select the intended version before asking.

4. The source is current, but an answer or output is still wrong

Old Studio output: A report, audio overview, or other output generated before the source update will not change with it. Select the current sources you need and generate a new output, then compare it with the version marker in the source. If the new output still contains old information, inspect the selected sources and the new result; regeneration does not guarantee correctness.

Chat answer: In the source panel, select only the sources you want to check. Ask a specific question about the passage you already inspected, for example:

According to the selected source, what is the project deadline? Cite the text supporting that date; if the source does not say, state that it is not specified.

Open the answer's citation and compare its surrounding context with the original. A citation alone does not prove the interpretation is correct. If the target text is visible in the source but the answer omits or misreads it, try a more specific question or a narrower source selection. Google's FAQ notes that unclear questions, information absent from sources, and safety flags can affect answers; rephrasing will not necessarily resolve every error. Google also notes that a very short source may be cited as a whole rather than by individual passage, so check the original manually.

To build a project knowledge base that stays useful as materials change, see the NotebookLM project brief workflow for source selection, access, and human review responsibilities.

notebooklmgoogle-driveai-research