Export your life: why Markdown beats lock-in

Markdown beats lock-in because it's plain text with a few readable symbols for structure, which means any computer, in any decade, can open it without needing the app that created it. A proprietary export format needs that app, or a specific importer built by someone else, to mean anything at all. Twenty years from now, a Markdown file opens in Notepad. A proprietary database export might not open anywhere.

What actually happens to your journal when the app disappears?

Apps disappear more often than people expect — not always through drama, usually just quietly: a company gets acquired, a product gets sunset, a founder moves on, and the software stops being maintained. If your journal only exists inside that app's own format, "the app is gone" and "your journal is gone" become the same event. That's true even if you never touched the delete button, and even if you were a paying customer in good standing right up to the end.

This isn't a hypothetical about journaling specifically — it's the general lifecycle of software, and journaling apps aren't exempt from it. A journal is unusually vulnerable to this pattern precisely because it's meant to accumulate for years, sometimes decades, which is a much longer horizon than most software companies plan around. The format your entries are locked in on day one is a bet on that company's survival for as long as you want your own memory to last, whether or not either of you intended to be making that bet.

Why does the export format matter more than having an export button at all?

Because "you can export" and "you can actually use what you exported" are two different promises, and only the second one matters when the moment actually comes. A lot of apps technically let you export your data — into a format only their own importer understands, or a raw database dump that means nothing to a person without a developer's help, or a PDF that captures how it looked but not the underlying structure you might want to search or reuse later. Technically having an export button, while making the export itself close to useless outside the original app, satisfies the letter of "you can leave" while missing the entire point of leaving.

Markdown avoids this because it isn't really a proprietary format at all — it's plain text with a handful of readable conventions (a hash mark for a heading, an asterisk for emphasis) layered on top. Strip away every one of those conventions and what's left is still just words on a page, legible to a human being with nothing more than a basic text editor, exactly the way a typed letter is legible whether or not the typewriter that made it still exists.

What should "own your export" actually mean?

Three things, in plain terms. First, it should be a real file you can open without needing the exporting app ever again — not a format only that app understands. Second, it should hold the actual content and structure of what you wrote, not just a visual snapshot of how it looked on screen. Third, it should be something you can get any time, without a support ticket, a waiting period, or a fee gating what is, after all, your own writing.

Markdown, PDF, and CSV each serve a slightly different version of that promise. Markdown is the one built for reading and rewriting years later — plain, structured, human-legible text that any editor on any platform can open. PDF preserves layout for printing or archiving a fixed copy, exactly as it looked. CSV preserves the underlying data in rows and columns a spreadsheet, or a future replacement app's importer, can actually parse. MetaLife exports to all three, on demand, from settings, precisely because "own your data" should mean the format matches what you're actually trying to do with it, not a single format standing in for every use.

Does this mean you should switch to a plain-text app instead?

Not necessarily, and it's worth separating "the app you use day to day" from "the format your data is trapped in." Plenty of people are well served by an app that classifies, organizes, and reflects their entries back to them — that's real, useful work a plain text file can't do on its own. The point isn't that structure and organization are bad. It's that the underlying record shouldn't be hostage to the tool doing that organizing. A good app can do sophisticated things with your entries during the years you use it, and still hand you something genuinely plain and portable the day you decide to leave, take a backup, or move somewhere else.

This is where naming actual destinations is useful, purely as an interop point rather than a comparison: a Markdown export opens cleanly as a vault of plain files in something like Obsidian, imports readably as pages in something like Notion, or sits as plain text you can paste straight into Apple Notes. None of that requires those tools to know or care what app produced the file. The specific destination matters less than the fact that a real Markdown file has somewhere obvious to go, unlike a format only one app on earth can read.

Is a Markdown export actually a substitute for a backup?

Not fully, and it's worth being precise about that distinction. An export is a snapshot of your data in a portable format — genuinely useful for moving between tools, for keeping an offline copy, for peace of mind. A proper backup is about redundancy: more than one copy, ideally in more than one place, so a single failure doesn't cost you everything. Exporting regularly is a good habit either way, but it's worth treating "I can export" and "I have a backup" as related, not identical, especially for something as irreplaceable as years of your own writing. See who owns your journal for the fuller set of questions worth asking any journal app before trusting it with years of entries, export included, and how it works for what actually happens to an entry between the moment you capture it and where it ends up stored. The glossary has a plain definition of "export" and "structured data" as used across this site.

Frequently asked questions

Q: Does exporting change or remove anything from my account?
No. A proper export is a copy. Your entries stay exactly where they are inside the app, and you can export as many times as you like without affecting the original record at all.

Q: Isn't Markdown too plain for something as personal as a journal?
Plain is the feature, not a compromise. The formatting Markdown skips — custom fonts, embedded widgets, app-specific styling — is exactly the layer that breaks when you move a file between tools or open it in twenty years. What survives is the words, which is the part that was always the actual point of a journal entry in the first place.

Q: What's the difference between exporting to Markdown versus CSV for a personal journal?
Markdown is built to be read by a person — open the file, and it looks like a document, close to how it read in the app. CSV is built to be read by other software — a spreadsheet, or a future app's own importer — with each entry's structured pieces (date, category, text) kept in separate columns rather than folded into prose. Most people want Markdown for reading back their own writing, and CSV for moving the data into something else that processes it in bulk.

The test for any export button, on any app, including this one, is simple: open the file a year from now, on a computer that's never seen the original software, and see if it still means something. A Markdown file passes that test by default. A format built only for one app's own importer usually doesn't, and you don't find out which one you were given until the day you actually need it.