Gemini Notebook and Obsidian: Moving Notes and Sources Between Them

Gemini Notebook (the service previously known as NotebookLM, renamed by Google in July 2026) and Obsidian take different approaches to notes and sources. Gemini Notebook is a source-grounded Q&A tool that lives in the cloud; Obsidian is a local Markdown vault you control. There is no direct official integration between them. Tools like fenbs help by keeping linked conclusions and project context outside both apps, so that work is accessible whichever assistant or tool you use next.

This guide covers the supported paths for moving notes and sources between the two, where manual steps are unavoidable, and how to keep the useful output from both tools in a durable record.

What each tool is for

Gemini Notebook is built around sources. You upload documents, paste in links, or add files, and it generates a notebook grounded in those materials. You can ask questions, get summaries, and create study guides, all tied to the sources you provided. Check Google's Gemini Notebook page↗ (opens in a new tab) for current capabilities.

Obsidian is a local Markdown editor with a plugin ecosystem. Your notes are plain text files you own. It does not require a cloud account and does not process your files on an external server by default. The two tools have different trust models, different data locations, and different use cases.

For a comparison of the two across more dimensions, see NotebookLM vs Obsidian.

Importing Obsidian notes into Gemini Notebook

Gemini Notebook accepts uploaded files and pasted text as sources. Obsidian notes are plain Markdown files stored in a folder on your computer. You can upload them to Gemini Notebook as text files.

1. Find the Obsidian note you want to use as a source. It is a .md file in your vault folder.
2. In Gemini Notebook, open or create a notebook and use the option to add a source from a file upload.
3. Upload the .md file. Gemini Notebook will process it as a source and make it available for Q&A.
4. If you want to combine several Obsidian notes, either upload them as separate files or copy the relevant sections into one text file before uploading.
5. Check that Gemini Notebook's responses are citing the content you expect. Ask a question you know the answer to from the note and verify the response.

Be aware that uploading a note to a cloud service means the content leaves your local machine. Review Gemini Notebook's data policies for what applies to uploaded source content if that matters for your work. If your vault includes personal data, confidential client information, or anything sensitive, check those policies before uploading.

Exporting Gemini Notebook output back to Obsidian

Gemini Notebook does not export notes directly to Obsidian. The path is manual: copy the output you want to keep, create a new note in Obsidian, and paste it in. Add the source file name and the date so the note has provenance.

If you generated a study guide, summary, or Q&A from a Gemini Notebook session, copy the parts you want to keep into a new Obsidian note. Save the source list alongside the output, so a future reader knows which documents the summary came from.

Community tools and automation options

Community-built Obsidian plugins and automation tools can reduce the manual steps. Because these change frequently and are not maintained by either Google or Obsidian directly, check current availability in the Obsidian community plugin browser and in automation tool directories before designing a workflow around one.

For connections between Notion and Obsidian that some teams use alongside AI tools, see Notion MCP vs Obsidian. For alternatives to Gemini Notebook for source-grounded Q&A, see NotebookLM alternatives.

The limitation worth planning around

The most common frustration is that verified conclusions end up locked in one tool. A Gemini Notebook session produces useful output; you want to use that output in an Obsidian-based workflow, or vice versa. Manual copying works but breaks the link between the conclusion and the source. Over time, you end up with a collection of notes that summarize things you once knew, without any way to trace which source supported each point.

The practical answer is to keep the verified conclusions and their source references in a location that is independent of both tools. That way the work is accessible regardless of which tool generated it. When you start a new Obsidian session or a new Gemini Notebook, the project context travels with you rather than staying behind in the other tool.

How to do this with fenbs

1. Create a free account and open a project for the research or work the notes support.
2. After a Gemini Notebook session, copy the key conclusions into fenbs as context notes. Include the source document title and the date.
3. After an Obsidian AI session, do the same: record verified findings in fenbs with source note titles linked.
4. Add unresolved questions as open tasks so the next session knows what still needs to be checked.
5. Connect an AI assistant from Integrations so future sessions start from the shared project record, regardless of which tool the previous session used.