NotebookLM moved to notebook.google.com

NotebookLM was renamed Gemini Notebook in July 2026. The address change below is a separate event that followed the rename, and it affects the app under either name.

What changed, and when

Google renamed NotebookLM to Gemini Notebook on 16 July 2026, folding it into the Gemini brand. The rename was announced properly — a blog post, a Workspace Updates entry, press coverage. The app kept its old address that day.

The address moved afterwards, and much more quietly. Through late July, notebook.google.com began serving the app alongside the original. By the first days of August the changeover was total: every request to the old host now gets forwarded.

Checked today, that's exactly what the old address returns:

$ curl -sI https://notebooklm.google.com/

HTTP/2 302
location: https://notebook.google.com/
cache-control: no-cache, no-store, max-age=0, must-revalidate

Two details in there are worth reading properly. It's a 302, not a 301 — in HTTP terms, "found elsewhere for now" rather than "moved permanently." And the no-store cache headers tell your browser not to remember the redirect. Together those are the settings you choose when you want to keep your options open, not the ones you choose when you're retiring a domain for good. Google has not committed publicly to switching off the old address, and until it does, the sensible reading is that notebooklm.google.com keeps working for a while yet.

No, you haven't been phished

This is the actual reason people are searching for the new address, so let's deal with it directly. An unannounced redirect to a domain you don't recognise is exactly what a credential-stealing page looks like, and being suspicious was the correct instinct. In this case the destination checks out.

notebook.google.com ends in .google.com. That's the part that matters. Only Google can create a subdomain of google.com, which puts it in the same category as mail.google.com or drive.google.com. The lookalike domains used in real phishing have to live somewhere else — notebook-google.com, notebooklm.google.security-check.net, google.notebook.co. Read a URL from the right: the last two labels before the first slash are the real owner. Here they are google.com, and the padlock in the address bar will show you a certificate issued to Google.

The thing that made this feel wrong was Google's own silence. There is no entry for the address change in the Gemini release notes, no Workspace Updates post, no help-centre note — even though the rename three weeks earlier got all three. A rebrand gets a blog post; the URL move got nothing. If you want the general picture on what Gemini Notebook does with your uploads, that's a separate question covered in is NotebookLM safe.

What still works

More than you'd expect, because the redirect preserves the path rather than dumping everyone on the homepage. A request for /notebook/<id> on the old host comes back pointing at /notebook/<id> on the new one. The practical consequences:

• Old bookmarks — including bookmarks to individual notebooks, not just the app root — still land in the right place.
• Links you've already shared with collaborators still resolve. You don't need to re-send anything.
• Password manager entries saved against the old host still autofill, because the redirect happens before the login form.
• Your notebooks, sources and Studio outputs are untouched. This was an address change, not a migration — there is nothing to export, re-import or recover.

What breaks: browser extensions

Extensions are the real casualty, and the reason is structural rather than anyone's mistake. A Chrome extension declares up front which sites it may run on, and it does that by naming the host in its manifest. An extension built against notebooklm.google.com has no permission to touch notebook.google.com — so on the new address it doesn't misbehave, it simply never wakes up. That failure is silent: no error, no warning, just a button that used to be there and now isn't.

Several NotebookLM add-ons went dark this way in late July. Most maintainers shipped updates within days, declaring both hosts so the extension works either side of the redirect. So the fix is almost always the boring one:

1. Open chrome://extensions and switch on Developer mode.
2. Click Update to force a check — Chrome's automatic updates can lag by hours or days.
3. Reload the Gemini Notebook tab. Extensions only inject on page load, so a tab you left open since last week won't pick up the new version.
4. Still nothing? Check the extension's store listing for a recent update. One that hasn't been touched since July may simply be abandoned.

Our own NotebookLM to PDF exporter is kept current with the app; if it ever goes quiet after a Google-side change, forcing the update above is the first thing to try. For failures that turn out not to be the address at all, NotebookLM not working covers the other usual causes.

What to update

Nothing here is urgent — the redirect is doing the work. But while the old address still resolves is the cheap time to fix references, rather than after it stops:

• Documentation, onboarding docs and internal wikis that tell people to "go to notebooklm.google.com".
• Browser shortcuts and pinned tabs, so you stop bouncing through a redirect on every launch.
• Allowlists, SSO configuration and firewall rules that name the old host — these are the ones that fail hard rather than gracefully, and they're worth auditing before a 302 becomes a 404.

People also ask

Is notebook.google.com legit?

Yes. It is the current official address of Gemini Notebook, the app formerly called NotebookLM, and it is a genuine subdomain of google.com — a namespace only Google can create. The old notebooklm.google.com redirects to it. Google never announced the change, which is why it looks suspicious, but the destination is authentic.

Does notebooklm.google.com still work?

Yes, as a redirect. Every request is forwarded to notebook.google.com, and the path is preserved, so links to specific notebooks still open the right notebook. Google is using a temporary 302 redirect rather than a permanent one, so there is no published date for the old address being switched off.

Why did my NotebookLM extension stop working?

Almost certainly the address change. Extensions declare which hosts they can run on, and one built for notebooklm.google.com has no permission to run on notebook.google.com, so it silently does nothing. Force an update from chrome://extensions with Developer mode on, then reload the tab.

Did I lose any notebooks in the move?

No. Only the address changed — your notebooks, sources, notes and Studio outputs stayed where they were and are reachable at the new URL with the same account. There is nothing to restore.

Is this the same thing as the Gemini Notebook rename?

No, they are two separate events. The rename from NotebookLM to Gemini Notebook happened on 16 July 2026 and was announced. The URL move to notebook.google.com followed in late July and completed in early August, with no announcement at all.