How to Export Gmail to Obsidian as Markdown Notes

Export formats

Gmail Exporter Guide

Obsidian appeals to people who want their knowledge in plain files they control, not locked inside someone else's app. Email is a strange gap in that system: some of your most important thinking, decisions and references live in Gmail threads you can search but never truly own as notes. Bringing those emails into your vault as Markdown turns them into first-class citizens of your knowledge base — linkable, taggable, and permanent. This guide shows how to do that cleanly and privately.

Why Markdown is the right target for Obsidian

An Obsidian vault is just a folder of Markdown files on your disk. There is no database and no cloud requirement; the app reads and writes plain .md files. That means importing email is not about a special integration — it is about producing Markdown files that Obsidian can see. Get your Gmail into Markdown and the import is simply moving files into the vault folder.

This also means the whole workflow can be local. You never need to connect Obsidian to Gmail or grant a plugin access to your account. The email leaves Gmail as files on your machine and lands in a folder on the same machine.

Step 1 — Export Gmail to Markdown or JSON

Run a local exporter against the mail you want in your vault. Exporting Gmail to Markdown gets you closest to the target format directly. If you prefer to script the conversion yourself, exporting to JSON gives you structured fields — sender, date, subject, body — that are easy to template into notes. Either way, a tool like Gmail Exporter builds the output in your browser with nothing uploaded.

Narrow the export before you run it. You rarely want your entire inbox in a vault; you want a project's threads, a label of research, or a date range. Filter in Gmail first, then export just those messages using export search results.

Step 2 — Turn each email into a note

If you exported Markdown, you may already have one file per message. If you exported JSON or CSV, a short script or a spreadsheet formula can generate a .md file per row. A clean note has YAML front-matter at the top — fields like from, date, subject, and any tags — followed by the email body as Markdown underneath.

Front-matter is what makes the notes powerful in Obsidian. With a date and from field on every email note, you can query them with Dataview, sort a project's correspondence chronologically, or list every note from a particular sender.

Step 3 — File and link the notes in your vault

Move the generated files into a folder in your vault, such as Inbox/Email or a project folder. Obsidian indexes them instantly. Now the real value appears: you can link an email note into a project page with [[note-name]], tag it, or reference a decision from a meeting note. The thread stops being a thing you re-search in Gmail and becomes a node in your graph.

A useful convention is to name files with the date and subject, like 2026-05-12 Kickoff plan.md, so they sort naturally and are easy to find. Keep the original full inbox backup separately as your archive; the vault holds the curated notes you actually think with.

Working with attachments

Emails often carry attachments you want alongside the note. Export those too and store them in your vault's attachments folder, then embed or link them from the email note. Because Obsidian references files by path, a PDF or image sitting next to the note is available offline, forever, with no external dependency. For pulling files out of mail, see the attachment-focused export guides on the blog.

Keeping attachments local matters for the same reason the notes do: an Obsidian vault is meant to survive any single service disappearing. Files you hold beat links that can rot.

A repeatable capture routine

Rather than a one-time dump, many people set a light routine: whenever a project wraps, export its label to Markdown and file the notes. This keeps the vault current without a live sync and without ever connecting Gmail to Obsidian. Each capture is a small, private, on-device operation.

If you work across tools, the same export can feed other systems too — the Notion guide covers the same idea for a database-style workspace, so you can choose the destination that fits how you think.

Privacy fits Obsidian's philosophy

Obsidian users chose local files for a reason: independence from the cloud. A local Gmail export is the only import method that honors that. The messages move from Gmail to your disk without passing through a third-party server, and no plugin holds standing access to your account. Your vault stays exactly as private as it was before you added email to it. For more on keeping exports private, see exporting without third-party access.

Automating the note templating

If you are importing more than a handful of emails, hand-formatting each note gets old fast. This is where the JSON export earns its place. With structured fields for sender, date, subject and body, a short script can stamp out one Markdown file per message using a consistent template — front-matter at the top, a tidy title, the body below. Run it once and a hundred emails become a hundred well-formed notes, all following the same shape your vault expects.

A good template does small things that pay off later: it slugifies the subject into a clean filename, formats the date so notes sort chronologically, and adds a source tag so you can always tell an email note from a written one. You only have to design the template once; every future capture reuses it, and your email notes stay visually and structurally consistent with the rest of your vault.

Linking email notes into your knowledge graph

The reason to put email in Obsidian rather than leave it in Gmail is connection. An email note that just sits in a folder is only marginally more useful than the original thread. The value appears when you link it: reference the kickoff email from the project's index note, connect a source's message to the topic note it informs, or backlink a decision to the meeting where it was made. Obsidian's graph then shows email as part of the web of your thinking, not a separate silo.

Tags help the same way at scale. A consistent set — the project, the person, the type of correspondence — lets you pull up every relevant email note with one query, and Dataview can assemble living lists such as 'all correspondence for this project, newest first.' At that point the emails have genuinely joined your knowledge base: searchable, linkable, and permanent, living in plain files you will still be able to open in a decade.

The bottom line

To get Gmail into Obsidian, export the relevant mail to Markdown or JSON locally, convert each message into a Markdown note with front-matter, and drop the files into your vault. Link and tag them like any other note, keep attachments alongside, and repeat the capture per project. The result is an email archive that lives inside your knowledge base as plain, permanent, fully local files.