Wiki with Markdown export: which ones are actually clean

TL;DR. A wiki with Markdown export is your insurance against ever being stuck. The catch is that “exports Markdown” hides a lot of shapes — per-page only, whole-space zip, API-only, or the dreaded PDF-only that isn’t really export at all. Clean means readable plain text, structure preserved, images bundled, no paywall. Obsidian is Markdown already. Notion exports Markdown with quirks. Confluence exports HTML you convert. Raccoon Page exports per-page Markdown and a per-space zip on every plan. Judge the shape, not the checkbox.

Every wiki claims it lets you take your content with you, right up until you ask it to. A wiki with Markdown export is the one you can actually leave — your pages come out as plain text that opens anywhere, imports into nearly anything, and doesn’t need the vendor’s blessing to read. That is the short answer to why this criterion is worth shopping on. The long answer is that “exports Markdown” is a checkbox hiding at least four different realities, and one of them is a trap.

This post is the product-finder version of the question: not what is Markdown (our Markdown documentation post covers the format-as-portability-layer thesis), but which wikis actually export clean Markdown, and what do they lose on the way out. If you are choosing a wiki on the export criterion specifically, this is the page for you.

What “clean Markdown export” actually means

Before the comparison, the spec. A lot of tools tick the “Markdown export” box and still hand you something you wouldn’t wish on a coworker. Clean export means all of the following, not just the first one:

Readable plain text. Headings are #, bullets are -, links are [text](url). Not a .md file that’s secretly 90% HTML blocks because the converter gave up.
Structure preserved. The page tree survives as folders. A nested page stays nested. Export a space and you get a vault shaped like your space, not a flat dump of three hundred files named Untitled (1).md.
Images and attachments bundled. Pictures come out as files with working relative links — not broken links, not base64 blobs wedged inline, not silently dropped.
Frontmatter kept. Title, tags, dates — the metadata lives in YAML frontmatter at the top, the way every Markdown tool expects.
No paywall. An export you have to upgrade to run isn’t an exit. It’s a toll booth with better branding.

Hold any candidate wiki against those five and most of the marketing evaporates. Most editors live up to the second word — export — and quietly skip the first one, clean.

The four shapes of “Markdown export”

When a tool says it exports Markdown, it means one of four things. The shape decides how much of your weekend the migration eats.

Per-page export. You open a page, hit a menu, get one .md file. Fine for one page. Across three hundred pages it’s a repetitive-strain injury with a progress bar.
Whole-space (or whole-wiki) zip. One action, one zip, the entire space as a folder tree of Markdown. This is the shape you want for an actual migration.
API-only export. The export exists, but only through a REST API. Translation: you (or someone you like less by the end) write a script. Powerful, not friendly.
PDF-only “export.” The tool offers PDF and calls it export. It is not export. See the next section, because this one earns its own.

The rule of thumb: a wiki you’d choose on the export criterion should offer at least the whole-space zip. Per-page is table stakes; zip is the real thing.

PDF-only is not export, and the gotchas that hide

This is the trap, and it catches careful people. PDF is a print format, not a data format. You cannot re-import a PDF into another wiki as editable content. You cannot diff it in version control. You cannot reasonably edit it again. A PDF is a photograph of your content wearing a nice suit. If a tool’s “export” is PDF-only, your content is not portable — it’s framed.

The other gotchas, in rough order of how often they ambush a migration:

Proprietary export formats. Some tools export to their own format that only re-imports into themselves. That is a backup, not an exit.
Lossy conversion. Tables flattened into ASCII, callouts dropped, code blocks losing their language hint, toggles silently unwrapped. The text survives; the structure doesn’t.
HTML masquerading as Markdown. A .md file where every non-trivial element is a raw <div>. Technically Markdown allows inline HTML. Practically you’ve exported HTML with a Markdown extension.
Broken image links. Export the text, leave the pictures behind. You find out three weeks later when someone opens an old runbook and every diagram is a sad grey box.

(If you’ve ever watched an exported page open with every image replaced by a broken-link icon, you have suffered enough. We have a canon story about exports turning content into the wrong thing — see the comparison below for the short version.)

Which wikis export clean Markdown — the comparison

Here is the field, factually. Real vendors, real shapes, no disrespect — just what comes out the other end.

Wiki	Export shape	What you get	What it loses
Obsidian	Already Markdown files	Native `.md` vault, your folders, your images	Nothing — it was never not Markdown. The trade-off is upstream: it’s a local notes app, not a team wiki.
Notion	Per-page and per-space Markdown + CSV	Markdown for pages, CSV for databases	Database views flatten to CSV; nested toggles and some embeds convert imperfectly; large exports can be slow
Confluence	Per-space HTML / XML	A structured export of the whole space	Not native Markdown — you convert the HTML/XML yourself or via an importer; macros need best-effort conversion
Raccoon Page	Per-page Markdown + per-space zip	Obsidian-compatible Markdown, frontmatter preserved, attachments included, on every plan	Honest answer below — export isn’t the only criterion

The pattern: Obsidian is Markdown by birth but isn’t a team wiki. Notion exports Markdown with quirks around its database-as-doc model. Confluence doesn’t do native Markdown at all — it does HTML/XML you convert, which is why every modern wiki ships a Confluence importer. And Raccoon Page exports both per-page Markdown and a per-space zip of Obsidian-compatible Markdown — frontmatter preserved, attachments included — on Free, Team, and Business alike.

We learned the “what it loses” column the embarrassing way. During our own first export-format smoke tests, a borrowed third-party helper quietly swapped a rabbit emoji for the raccoon emoji in exported files — a “small mammal normalisation” lookup table inherited from a previous job, written before that team had met a raccoon. The fix was a one-line deletion. The lesson outlived the bug: exporting your wiki and exporting your wiki without secretly turning it into a different animal are two different promises. Clean export is the second one.

You’re never locked in — what that’s worth

Here’s the opinion this post stands behind, and the spine of the whole thing: an export you have to pay for is not an exit — it’s a toll booth. Data portability shouldn’t be the upsell. It should be the floor.

That’s why Raccoon Page ships both per-page Markdown export and the per-space zip on every plan, including the Free tier at $0 — three users, one space, one hundred pages, no card. The export isn’t gated behind Team ($8/user/month) or Business ($15/user/month). The reasoning is plain: a wiki you can leave for free is a wiki you stay in by choice. A wiki whose exit costs money is a wiki betting you won’t pay the tax to leave. Those are very different relationships with a piece of software, and only one of them is healthy.

The mechanism underneath is boring on purpose. Pages are stored as structured documents — real tables, callouts, code blocks, inline comments — and the export converts that structure to clean Markdown on the way out. Sub-second loads. Keyboard-first. The structure is what makes the wiki fast; the Markdown is what makes the exit honest. You don’t have to trade one for the other.

When Markdown export shouldn’t be the deciding factor

Honesty section, because a post that only sold you on one criterion would be exactly the kind of brochure prose this blog refuses to write.

Export is your insurance policy, not your daily experience. You will spend orders of magnitude more time loading pages, searching, and writing than you ever spend exporting. If you pick a wiki purely on the cleanliness of its Markdown export and the thing is slow, the search is bad, or the editor fights you, you’ve optimised the one feature you’ll use twice a year and ignored the ones you’ll use every hour.

So the honest ordering is: pick on speed, search, the editor, permissions, and price first. Then treat clean Markdown export as the non-negotiable safety check that makes that whole decision reversible. Export is the seatbelt, not the engine. A great wiki you can leave beats a mediocre one you happen to be able to export.

And if you’re a solo writer with a folder of notes, you might not need a team wiki at all — Obsidian’s local Markdown vault is already the cleanest export there is, because there’s nothing to export. The Free tier of a real wiki is the right answer when you have a team; a plain folder is the right answer when you don’t.

Things people actually ask

Which wikis can export to Markdown? Obsidian is already Markdown files, so it is the cleanest by default. Notion exports Markdown plus CSV, with some quirks around databases and nested toggles. Confluence does not export native Markdown — it exports HTML or XML, and you convert that yourself or via an importer. Raccoon Page exports per-page Markdown and a per-space zip of Obsidian-compatible Markdown on every plan. The shapes differ; check the shape, not just the checkbox.

What does clean Markdown export actually mean? Clean means the exported file is readable plain Markdown a human and any other tool can use, with structure preserved and minimal junk. Headings, lists, code blocks, tables, and links should survive as Markdown syntax. Images should come as files with working relative links. Frontmatter metadata should be kept. Clean export does not bury content inside HTML blocks, does not lose the page hierarchy, and does not require a paid tier to run.

Can you export a whole wiki at once or just one page at a time? It depends on the tool. Some only export one page at a time through the editor menu, which is painful across hundreds of pages. Better tools offer a bulk or whole-space export as a single zip that keeps the folder hierarchy. A few only expose export through an API, which means writing a script. Raccoon Page does both — one-click per-page Markdown and a per-space zip — so you are not clicking export three hundred times.

Why does Markdown export matter when choosing a wiki? Because it is your exit. A wiki you cannot leave cleanly is a wiki you are stuck in, and stuck is a bad reason to stay. Clean Markdown export means your content is portable plain text that imports into nearly every other tool, so switching later is a mechanical step instead of a rescue mission. It is the difference between choosing to stay and being unable to leave.

Is PDF export the same as Markdown export? No, and treating them as equivalent is the most common mistake. PDF is a print format, not a data format. You cannot re-import a PDF into another wiki as editable content, you cannot diff it in version control, and you cannot meaningfully edit it later. PDF export is for sharing a snapshot. Markdown export is for keeping your content portable. If a tool only offers PDF, it does not really let you take your content with you.

Does exporting from Confluence give you Markdown? Not directly. Confluence exports HTML or XML at the space level, not native Markdown. To get Markdown you either run a conversion tool or use a wiki importer that reads the Confluence export and converts it. Most modern wikis ship a Confluence importer that handles this and preserves the page tree and attachments, which is usually less work than converting the HTML yourself.

Does Markdown export preserve images and attachments? It should, but not every tool does it well. A clean export bundles images as files alongside the Markdown and rewrites the links to point at them with relative paths. A poor export leaves images as broken links, embeds them as base64 blobs inside the text, or drops attachments entirely. Raccoon Page includes attachments in the per-space zip and preserves frontmatter, so the export is a working vault, not a pile of text with missing pictures.

Should Markdown export be the only thing I judge a wiki on? No. Export is your insurance policy, not your daily experience. You will spend far more time loading pages, searching, and writing than exporting. Pick a wiki on speed, search, the editor, permissions, and price first, then treat clean Markdown export as the non-negotiable safety check that makes the rest of the decision reversible. A great wiki you can leave beats a mediocre one you happen to be able to export.

The whole point of shopping for a wiki with Markdown export is to never need it in anger. Pick the one that’s fast, searchable, and pleasant to write in — and make sure the door out is plain text the moment you change your mind. The CommonMark spec defines the syntax; Obsidian defines the vault shape most clean exporters target. Ours hands you that vault on every plan, frontmatter and attachments included. Use the export and we’ll be a little sad. Never use it because you never wanted to leave, and we’ll count that as the win it is.