How Well Do Note Apps Actually Let You Leave? An Export-Fidelity Roundup

Export fidelity is a spectrum, not a switch. Apps that store your notes as plain Markdown files export losslessly, because the files already are the export. Apps that keep notes in a database must serialize them on the way out, and serialization is where attachments, nesting, links, formatting, and metadata quietly drop.

Most advice about leaving a note app stops at the button. Settings, Export, done. But the question that decides whether a migration is painless or a weekend of manual repair is not how you export — it is how much survives the export.

Amber Williams, who left a commercial app to build her own plain-Markdown system, described the payoff in one line: "All my notes are stored in Markdown so I can export them with two command lines to my terminal." ¹ The 2019 Ink & Switch essay Local-first software named the underlying ideal — "In local-first apps, the ownership of data is vested in the user" ² — but ownership on paper is not the same as fidelity in practice. You can own an export that arrives with its images scattered, its folders flattened, and its callouts rewritten as HTML. This roundup scores six popular note apps, plus MNMNOTE, on the same six axes, so you know what you will have lost before you click the button, not after.

The six axes of export fidelity

Six dimensions decide how much of a note survives leaving an app: attachments, nested structure, internal links, formatting, and metadata — plus the round-trip re-import. The first five are what a note contains. The sixth is a test: export, then re-open the result in a neutral Markdown reader and count what is missing.

Each axis fails in its own way. Attachments can travel as separate files, embed as base64 blobs, or hide inside a container the reader cannot open. Nested structure can flatten from a tree into a heap. Internal links can decay from live references into dead file paths. Formatting can be rewritten into markup no other editor speaks. Metadata — created and updated times, tags, geolocation — is the quietest of the five, because you rarely watch it leave. The rubric is deliberately architectural and vendor-neutral: it names the cost, it does not crown a winner.

Plain-file apps export losslessly by construction

When an app stores your notes as plain Markdown files on disk, there is nothing to serialize. Obsidian keeps notes "locally as plain text Markdown files"; ³ Logseq keeps Markdown or Org-mode files. ⁴ Leaving is a file copy, not a translation, so all six axes survive intact — the export and the original are the same bytes.

This is the structural reason plain-file tools score a clean sweep. Obsidian's own homepage states it stores notes "privately on your device, so you can access them quickly, even offline." ³ Because the vault is a folder of .md files, attachments already sit beside the notes, the folder tree is the structure, wiki-links and relative paths persist as plain text, Markdown formatting is verbatim, and any YAML frontmatter is inside the file.

Williams built her own system for exactly this property: "I wanted to know with certainty that I control my data." ¹ The honest caveat is that "lossless" here means nothing is lost in the transfer — it does not mean the files are backed up. Plain text on one disk is still one accident from gone.

Database apps have to serialize on the way out

A database-backed app cannot simply hand you your folder; it has to reconstruct one. That reconstruction is an export format, and the format decides the loss. Joplin proves the ceiling is high — its JEX export is genuinely lossless. ⁵ The catch is where JEX round-trips to, and what the plainer formats drop.

Joplin's own documentation is explicit: JEX is "a lossless format in that all the notes, but also metadata such as geo-location, updated time, tags, etc. are preserved." ⁵ But JEX round-trips cleanly back into Joplin, not into a neutral Markdown reader — it is Joplin's own container. Joplin also offers a plain-Markdown directory export, and that path is lossier: it drops the app-managed metadata JEX keeps. So even the best-behaved database app carries an asymmetry worth naming — high fidelity into itself, lower fidelity into the open.

Bear is the same shape from a different angle: "On both iOS and macOS, Bear's notes are stored in a SQLite database," ⁶ and it exports clean Markdown, .textbundle, and other formats on its free tier ⁷ — genuinely portable output, produced per note, out of a database rather than copied from a folder. Storing notes in a database is a design choice with real benefits, not a flaw. It simply moves fidelity from a property of the storage to a property of the export format you choose.

Where fidelity leaks: attachments, structure, links, and formatting

Four axes take most of the damage on the way out. Attachments scatter into separate folders, embed as base64, or hide inside a container file. Nested databases flatten to CSV. Internal links decay into relative file paths. And formatting with no Markdown equivalent gets rewritten as HTML you then have to strip out by hand.

Notion is the clearest worked example, because it documents each cost itself. "Any non-database Notion page can be exported as a Markdown file. Full page databases will be exports as a CSV file, with Markdown files for each subpage" ⁸ — so a database of notes leaves as a spreadsheet, not prose. Images survive, but scattered: the export folders "will also contain the images and other assets on your pages saved separately." ⁸

And the sentence that names the formatting axis exactly: "Callout blocks will be exported as HTML, as there is no Markdown equivalent." ⁸ Attachments behave differently in every app. Bear can embed photos in an HTML export "by enabling the base64 option." ⁷ Evernote wraps resources inside its export container, where each is referenced by an "MD5 checksum of the Resource body" and marked in place by an en-media tag "used to mark the location where one of a note's resources should be embedded within the document." ⁹ Same job, three incompatible answers.

Metadata is the quietest loss

Metadata is the data about your data: created and updated times, tags, geolocation. It is the easiest thing to lose because you rarely see it leave — the prose looks intact, and the invisible fields are simply gone. Joplin's JEX preserves geo-location, updated time, and tags; ⁵ its plain-Markdown export does not. What survives depends on the format you pick.

The pattern generalizes across the database apps. Evernote's export keeps note metadata, but inside an Evernote XML container: "You can choose to save your notes as an Evernote XML file (.enex) or as HTML files (.html)." ¹⁰ An .enex file is readable, but it is XML you have to convert before another editor treats it as notes.

In plain-file apps the question never arises — frontmatter and inline tags are already in the file, in plain text, so metadata travels because it was never separated from the note in the first place. The rule of thumb: the richer the app-managed metadata, the more you should check the target format before you trust the export.

The round-trip test: re-open the export in a neutral reader

The only honest fidelity check is a round trip. Export your notes, then open the result in a neutral Markdown reader you did not write them in, and count what is missing: broken images, flattened folders, dead links, callouts turned to HTML. This is old, diffuse quality-assurance practice — the one measurement marketing never runs for you.

Run it before you commit, not after you are locked in. The round trip is what separates a format claim ("we export Markdown") from a fidelity claim ("your notes open somewhere else and still look like your notes"). A plain-file app passes the round trip by definition, because the reader opens the same files you already had. A database app passes only to the degree its export format matches a neutral reader's expectations — which is why Joplin's JEX aces a round trip into Joplin and a plain-Markdown export does not.

If you already have a messy export in hand, cleaning a vendor dump back into plain Markdown is the repair job the round trip predicts; and if you have never run the drill, a twenty-minute export rehearsal is how you find the losses while they are still cheap to fix.

The export-fidelity matrix

Here is the whole rubric in one view. Read the columns, not a ranking. Two apps are lossless because their files are already Markdown; one keeps notes locally in your browser on the same side of the line; and four keep notes in a database, each serializing to a different format with a different, nameable cost.

Where MNMNOTE sits on the rubric

MNMNOTE keeps your notes as plain, open Markdown files on your own device, and works offline with no account. On the fidelity axis that places it beside the plain-file column: the files are already the export, so attachments, structure, links, formatting, and metadata travel as written. It is one more entry on the rubric, scored the same way.

The trust-boundary logic is the same one that separates a note you own from a note you rent, and we audited where each app physically keeps your bytes as its own question. MNMNOTE adds opt-in, end-to-end encrypted sharing when you choose to send a note; the notes themselves stay in plain Markdown on your device. That is a capability on the same axis as every other app here — not a verdict on them, and not the answer to the rubric. The rubric is the answer.

Who should worry about export fidelity — and who should not

Export fidelity matters most if you keep notes for years, expect to switch tools, or store attachments and structure you cannot afford to rebuild by hand. It matters least if your notes are short-lived, live happily inside one app, and never need to move. Both are legitimate positions; the rubric only tells you which one you are standing in.

Two caveats keep the scoring fair. First, database apps are not villains: Joplin's JEX is genuinely lossless, ⁵ Notion produces real Markdown and real asset files, ⁸ and Bear exports clean, portable Markdown. ⁷ The cost is a property of the export format, precise and nameable, not a moral failing.

Second, plain-file apps are not magic. Their fidelity is perfect and their durability is only as good as your backups — and the separate question of whether a file will still be readable after the vendor is gone is its own axis we scored elsewhere. Fidelity is what survives the transfer today; survivability is what survives the company. The law, meanwhile, gives you the right to leave at all — this rubric measures the quality of the export that right entitles you to.

Frequently asked questions

These are the questions people actually type when they worry about getting their notes out. Each answer traces to the vendor's own export documentation, because on a fidelity question the authoritative source is the company that wrote the export code — not a review that summarizes it.

Which note app exports cleanly without losing anything? Apps that store notes as plain Markdown files — Obsidian and Logseq among them — export losslessly, because the files already are the export. ^{3 4} Database-backed apps can also export cleanly, but the fidelity depends on the format: Joplin's JEX is lossless into Joplin, ⁵ while a plain-Markdown export from any database app drops app-managed metadata.

How do I export Notion to Markdown, and what do I lose? Notion exports non-database pages as Markdown files, but "full page databases will be exports as a CSV file," and "callout blocks will be exported as HTML, as there is no Markdown equivalent." ⁸ Images are saved as separate files in per-page folders. ⁸ You keep your prose; you lose database structure to CSV and callouts to HTML.

Does Evernote export to Markdown? No. Evernote exports to "an Evernote XML file (.enex) or as HTML files (.html)." ¹⁰ The .enex format is Evernote's own XML container — readable, but not something another editor opens as Markdown natively. Getting to Markdown means a conversion step after the export.

What happens to attachments when I export my notes? It varies by app. Notion saves images as separate files in per-page folders. ⁸ Bear can embed photos in an HTML export "by enabling the base64 option." ⁷ Evernote references each resource by an "MD5 checksum" and embeds it inside the .enex container via an en-media tag. ⁹ Plain-file apps keep attachments as separate files beside the notes.

Does Obsidian lock you in? No. Obsidian stores notes "locally as plain text Markdown files" in a folder on your device. ³ There is nothing to unlock, because the files are already open Markdown you can copy anywhere. Leaving is a file copy, and every fidelity axis survives it intact.

Will I lose my notes if I switch note apps? It depends entirely on the app's export fidelity. If your notes were plain Markdown files, you keep everything — the files move as written. If they lived in a database, you keep whatever the export format preserves: prose usually survives, while nested structure, internal links, and metadata may not. Run a round-trip test before you commit.

The button is the easy part. The honest question is the one no export dialog answers: when your notes land somewhere else, will they still be your notes — images attached, folders intact, links alive, metadata present — or a lossy sketch of them. Score the export before you trust it, and you will always know which.

If you want notes that stay plain, open Markdown on your own device, mnmnote.com opens in a browser tab and keeps the files yours.