Veröffentlicht
Exporting Highlights to Obsidian and Other Note Apps
A highlight nobody exports disappears the moment you close the file. Here's what a Markdown export actually contains, and how to get it into Obsidian, Bear, or anywhere else you keep notes.
Quick answer
A highlight nobody exports disappears the moment you close the file. The fix is one step: export it to Markdown, then drop that file into your Obsidian vault — or Bear, or Apple Notes, or anything else that reads plain text. The file itself doesn't change depending on where it's headed. Only how you get it there does.
This is for anyone already keeping notes in Obsidian or Bear who doesn't want two separate systems: one for things you've read, another for things you've written. If that's you, the highlights you make while reading should land in the same place as everything else.
Why the export step matters
A highlight trapped inside a PDF or EPUB reader can't be searched alongside your other notes. It can't be linked to anything else you've written either — it just sits there, tied to a file you may not open again for months. Personal knowledge management is the practice of gathering and connecting your own notes over time, rather than letting an app impose a filing system on you. Export is the step that actually feeds it. Exporting your highlights out of a reading app is what closes the gap between reading and writing.
That's also why Markdown became the default hand-off format. It was designed to be as readable as possible — plain text that reads like normal writing even before any app touches it, independent of whatever produced it or whatever opens it next.
What a Markdown export actually contains
A well-formed highlight export isn't just a wall of quoted text. It's a short block of metadata — the source title, sometimes an author, sometimes a date — followed by the highlights themselves, usually one per line or blockquote. That metadata lives in YAML, fenced by a pair of --- lines at the very top of the file:
---
source: "The Book You Were Reading"
exported: 2026-09-09
---
> A line you highlighted while reading.
> Another one, further into the chapter.
That block matters more than it looks like it should. Obsidian reads it as structured Properties — searchable, filterable fields, not just inert text sitting above your highlights. Get the frontmatter right and you can query it later ("show me every highlight from this author"). Skip it, and you're stuck with a page you'll have to read again just to remember what's in it. It's part of why plain text is sometimes the better format for something you actually intend to keep — nothing about it is locked to a specific app.
Getting the file into Obsidian
Obsidian's vault is just a folder of .md files sitting on your device — nothing proprietary, no conversion step. Drag the exported file into your vault folder, or into the File explorer pane inside the app, and it shows up as a normal note: searchable, linkable, readable by any other Markdown tool you pick up later.
Bringing in more than one file at a time — a backlog of highlights from several books, say — is where the official Importer plugin earns its keep. It standardizes formatting, turns inline tags into Properties, and applies a template so every incoming note comes out the same shape. For a single file, you don't need it. Drag, drop, done.
Getting the file into other note apps
The same export works almost anywhere that reads Markdown, because the file itself doesn't change:
- Bear — drop the
.mdfile straight into a notebook, or paste its contents into a new note. The frontmatter and highlight blockquotes carry over as plain text. - Apple Notes — imports Markdown files directly. No reformatting needed first.
- A plain text editor — already readable exactly as it is. That's the whole point of exporting to Markdown in the first place.
Doing this in Margina
Margina exports your highlights the same way — one Markdown file per document, frontmatter at the top, highlights as blockquotes underneath. The idea behind it is simple: a highlight should stay attached to the book it came from, even after you've exported it somewhere else. No account, no server round-trip. The file is generated on your device, and it's yours from the moment it exists.
Frequently Asked Questions
Do I need a plugin to get my highlights into Obsidian?
No. Obsidian reads plain .md files directly, so dragging an exported highlights file into your vault folder is enough. A plugin like the official Importer only helps if you're bringing in a whole folder at once, or want to standardize formatting and map fields into Properties as you go.
Will my highlights still be linked to the book they came from?
Only if the exported file's frontmatter says so. A well-formed export carries the source title, and often the author and a page reference, as YAML metadata at the top of the file — which is what lets Obsidian treat it as a linkable, searchable note instead of a loose block of text.
What if my note app isn't Obsidian?
The same file works almost anywhere that reads Markdown — Bear, Apple Notes, or a plain text editor. The export format doesn't change; only how you get the file into the app does.
Why not just keep highlights inside the reading app?
Because a highlight that only exists inside a PDF or EPUB reader can't be searched alongside your other notes and can't be linked to anything else you've written. Exporting it once to Markdown is what turns it into something you can actually find again months later.
Conclusion
Exporting is a five-second habit that turns a highlight into something permanent. Once it's a Markdown file sitting in your vault, it belongs to whatever system you build next — not to the app that happened to open the book in the first place.