Google’s July 2026 rename of NotebookLM to Gemini Notebook has made the product look more tightly connected to the Gemini app, but it has not removed the constraints that matter most to people using it for real research: each notebook remains an isolated knowledge base, original uploads are hard to retrieve from the service, and its source model is still built around relatively static documents. Android Authority’s five-item Gemini Notebook wish list identifies those gaps well, but Google’s own documentation shows that one supposed upcoming capability — adding website links as sources — already exists in Gemini Notebook today.

The distinction is more than pedantic. Google is merging the branding and navigation of Gemini and NotebookLM while preserving different answer models behind the two interfaces. Gemini Notebook answers are grounded exclusively in the sources selected for a notebook; Gemini can use the notebook and web search and other tools. For an IT department, that means a user can move from a tightly bounded policy or incident corpus to a broader, less-controlled answer path without changing the underlying notebook.

Google announced on July 16 that NotebookLM would become Gemini Notebook, with existing links and shared notebooks continuing to work through redirects. On August 4, Google separately began rolling out synced notebooks in the Gemini app for Google AI Ultra, Pro, and Plus subscribers on the web, with broader mobile and free-tier availability promised later. Android Authority is right to read that integration as a signal that Google wants Gemini Notebook to become a larger part of its AI product, but the five requested features are not a disclosed roadmap.

AI-powered document dashboard links files and analytics while securing data with vaults, locks, and access controls.Notebook merging is the missing organizational primitive​

Android Authority’s top request is a native way to merge related notebooks. Google’s help documentation confirms the present limitation plainly: notebooks are independent, and Gemini Notebook cannot access information across multiple notebooks at the same time. That makes a chapter-by-chapter thesis, a multi-team migration program, or a long-running incident archive harder to consolidate once the initial research phase is over.

Google has built a partial workaround, not a replacement. A user can place a notebook in Gemini, where synced sources and chat context are available, but Gemini’s answers may also pull in web search and other tools. The result is useful for brainstorming across an assortment of material, yet it is not equivalent to combining two curated source sets into one auditable, source-grounded notebook.

A genuine merge tool would need choices Google has not exposed: whether to retain the original notebooks, how to handle duplicate sources, whether to carry chat histories and generated artifacts, and how to reconcile custom instructions. It would also need to preserve permissions. Google says notebooks containing Gemini chats are private and cannot be shared, while shared Gemini Notebook notebooks do not appear in Gemini’s navigation; those two rules would make “merge everything” especially difficult in collaborative work.

There is a narrower feature Google could ship sooner: a read-only multi-notebook query mode that returns citations separated by notebook. That would solve the research problem without pretending that a cross-project synthesis is one clean corpus. Until then, teams should create notebooks around a durable boundary — a product release, customer, case, or project — rather than treat them as folders intended to be recombined later.


Exporting sources is a data-retention problem, not a convenience request​

The request to download original uploaded sources is the most practical item on Android Authority’s list. Gemini Notebook can export notes to Google Docs or Google Sheets, and Google Takeout can produce an archive of Gemini data, but Google does not document a one-click per-source download function inside a notebook. A generated briefing can leave the service; the PDF or document that made it possible may not be readily recoverable from the notebook interface.

That creates an avoidable preservation risk. An employee who uploads a locally stored PDF, then deletes the local copy after extracting answers and artifacts, should not treat Gemini Notebook as the document system of record. Google’s source documentation describes imported content as a copy or auto-synced version used to answer questions, not as a user-facing archive with lifecycle controls.

Google Drive sources are better suited to long-term work because they automatically sync when the original file changes. But that introduces a separate failure mode: if the user loses Drive access or the file is deleted, the notebook can no longer access or display the source, and the source still counts against the notebook’s limits while it is inactive. In other words, Drive linking reduces duplication but makes Gemini Notebook dependent on the original file’s permissions and retention policy.

For sysadmins, the operational rule is straightforward: keep source files in a governed repository — SharePoint, OneDrive, Google Drive, a document-management system, or a version-controlled repository — and use Gemini Notebook as an analysis layer. Do not let it become the only known location of a compliance record, vendor contract, postmortem, or architecture document. A source-export button would improve recovery, but it would not replace a retention policy.

The product already has more study tools than the wish list suggests​

Android Authority wants more interactive ways to recap and learn material, including competitive quizzes, simple educational games, dashboards, and generated mini-apps. Gemini Notebook already has a larger studio than the article’s framing implies: its documented outputs include flashcards, quizzes, mind maps, infographics, slide decks, audio overviews, video overviews, reports, data tables, and notes. The mobile app also supports quiz and flashcard review, and Google’s audio feature has an Interactive Mode beta in English.

The gap is not an absence of formats. It is the difference between an AI-generated artifact and a persistent application with rules, scoring, multiplayer access, data storage, and administrative controls. A “fun game” generated from a notebook may be useful for a classroom or onboarding exercise, but the moment it tracks employee progress or uses production data, it becomes a different category of software with privacy, access, and support requirements.

The reported “App within the Studio” language that TestingCatalog spotted would be worth watching if it becomes public, but it remains an unreleased indicator rather than a product commitment. No other outlet in the material reviewed has independently reported a launch date, supported platforms, or an exact feature set. Google’s published help pages currently list the existing Studio artifacts rather than a general-purpose app generator.

There is also a quality issue that matters more than novelty. Google explicitly warns that Gemini Notebook’s chats and generated artifacts can contain inaccuracies. Turning an imperfect summary into an engaging game can reinforce an error more effectively than a dry answer ever could. For training and study, generated quizzes should expose the source passages behind each answer and be reviewed before they are assigned to staff or students.


Live database connectors would change the security model​

The most consequential request is direct, live connectors for platforms such as Obsidian, Slack, GitHub, inventories, and customer systems. Android Authority correctly identifies the appeal: a notebook that reflects an operational knowledge base automatically would eliminate repeated uploads and make current information searchable alongside documents.

But this is not simply another input type. Gemini Notebook’s current source architecture is primarily based on uploaded copies, web-page text extracts, or supported Drive sources that sync periodically. Google says that a web URL import captures only the HTML page’s text; it does not import embedded media, nested pages, or paywalled content. That is a deliberately limited ingestion model, not a live crawler or a connector framework.

A Slack connector would have to honor channel-level permissions, thread visibility, retention holds, legal discovery rules, deleted messages, and possibly external shared channels. A GitHub connector would need to distinguish public repositories, private repositories, issues, pull requests, commit history, secrets accidentally committed to code, and permission changes that happen after an answer has been generated. A database connector adds row-level access control, query restrictions, audit logs, freshness guarantees, and protection against an AI-generated query becoming an expensive or destructive operational event.

Google could address portions of this with read-only, administrator-approved connectors that index carefully scoped content and honor the source platform’s identities. Yet that would move Gemini Notebook closer to an enterprise search and retrieval product, where the difficult work is authorization and auditability rather than summarization. For now, organizations should assume the product is best used with intentionally selected, minimally necessary exports rather than privileged live business systems.

The PDF limit is not really a page-limit issue​

Android Authority cites Gemini Notebook’s 500,000-word-per-source and 200 MB upload limits as a reason to seek higher PDF capacity. Google confirms both limits, but it does not impose a page limit. That matters because “about 1,000 pages” is only a rough conversion; a 1,000-page document with sparse text, dense tables, scanned images, poor OCR, or a large embedded-image payload can behave very differently from a clean text-heavy PDF.

The harder limitation is source usability. Large PDFs are not guaranteed to produce a full-fidelity representation of complex layouts, image-only pages, footnotes, comments, tables, or appendices. Google’s documentation separately notes that Gemini Notebook does not import footnotes or comments from Google files, an important reminder that a source accepted by the product is not necessarily a complete reproduction of the original record.

Paid Workspace tiers can raise notebook and source-count quotas significantly, but Google’s published limits still describe a per-source ceiling rather than a higher document-size tier. That undercuts the assumption that a premium plan will solve giant-PDF intake. Breaking long reports into coherent sections, applying reliable OCR, retaining meaningful headings, and keeping appendices as separately named sources remains the safer workflow.

The immediate lesson from Android Authority’s list is that Gemini Notebook’s next useful improvements are less likely to be another flashy output format than the unglamorous controls around organization, export, permissioning, and source fidelity. Google has made the tool easier to reach from Gemini; it has not yet made it a replacement for document management, enterprise search, or a governed data platform.


References​

  1. Primary source: androidauthority.com
    Published: August 9, 2026 at 11:00 AM UTC
  2. Related coverage: support.google.com
  3. Related coverage: workspaceupdates.googleblog.com
  4. Related coverage: blog.google
  5. Related coverage: blog.google
  6. Related coverage: techcrunch.com
  7. Related coverage: androidauthority.com
  8. Related coverage: 3t-t.com
  9. Related coverage: tomsguide.com
  10. Related coverage: techradar.com
  11. Related coverage: tomsguide.com
  12. Related coverage: androidcentral.com
  13. Related coverage: support.google.com