Guide

Why plain text outlives every app you'll use

Your notes will probably outlast the software that created them. Whether they survive that transition is decided by a choice you make once, at the beginning, and rarely think about again.

Updated November 2026 · 7 min read

The part you are actually trusting

When you choose a note application, you evaluate the parts you can see: the editor, the search, the mobile app, the way it looks. Those are the parts that persuade you. They are not the parts your notes depend on.

Your notes depend on something you never look at: the format they are stored in. If that format is a database only one program understands, then every note you own is contingent on that program continuing to exist, continuing to care about old data, and continuing to let you take it out.

That is a lot of things to be true for a decade.

Two ways an archive dies

The company goes away

It happens slowly and then suddenly. A product is acquired, the team is reassigned, a new version drops support for the old data model, or a service simply closes. Sometimes you get an export tool and a warning; sometimes you get an announcement and ninety days.

The format goes away

This is quieter and more common. The company is fine — it is the file you can no longer open. The document format needs a licence, or requires a version of the app that no longer runs on current systems, or depends on a server that was retired. The data exists, intact and unreadable.

Both failures look the same from the outside: a folder full of files you cannot open, on a day you did not choose.

What plain text actually buys

A plain text file has no owner. It is not licensed, it does not call home, and it does not need a program to be interpreted. Anything that can open a file can open it — an editor written today, one written twenty years ago, a phone, a terminal, a printer driver.

This sounds like nostalgia. It is closer to a guarantee:

  • Every tool can read it. Search, diff, version control, scripting — the entire machinery of software works on text without being asked.
  • Nothing needs installing to check it. You can open the file, read it, and know it is fine. No renderer required to confirm the content is there.
  • It is diffable. Two versions of a text file can be compared line by line. Two versions of a proprietary document usually cannot.
  • Migrations are cheap. Moving ten thousand text files between services is a copy. Moving ten thousand records out of an application database is a project.

Markdown, specifically

Markdown is a plain text convention for a handful of formatting marks: # for headings, - for lists, ** for emphasis, and so on. The point is not the syntax. The point is that the file stays readable when the syntax is ignored.

Open a Markdown file in a program that knows nothing about Markdown and you see the content with a few stray asterisks. Nothing is lost, nothing is hidden, and the meaning survives the loss of the renderer. Compare that with a document format where the same file, opened blind, is a stream of binary or a wall of markup that buries the sentences.

Markdown is also small enough to read on a screen without tooling. That matters more than it sounds: a format you can inspect is a format you can trust.

What you give up

This is not a free choice, and pretending otherwise makes the rest of the argument worthless.

  • Layout control. You cannot position things precisely. If your notes are mostly design, plain text is the wrong tool.
  • Embedded structure. Databases, tables with formulas, linked fields — these exist because some notes really are structured data. Markdown represents them poorly.
  • Some convenience. A proprietary app can do things a text file cannot, precisely because it owns the format. That is the trade you are making.

The honest position: plain text is the right default for prose, quotes, research notes, drafts, and records. It is the wrong choice for a spreadsheet or a design file.

The export test

Before committing years of notes to anything, there is one question worth asking, and it takes an afternoon to answer:

If this service disappeared tomorrow, what would I have?

Run the export. Look at the output. Not the description of the export — the actual folder of files.

  • Can you open every item with something you already own?
  • Are the titles, dates, and text preserved, or does the export produce images and a manifest?
  • Do the links between notes survive, or do they point at an identifier that no longer means anything?
  • Can you search the result without the original application?

If the answer to the last one is no, you do not have an archive — you have access to an archive, which is a different thing and revocable.

Attachments are the weak point

Text survives almost anything. Images do not. A note that is text plus a photograph is only half portable: the words move cleanly, while the picture sits in a folder structure, a storage bucket, or a database field that may not be included in an export at all.

Practically, that means two habits. Keep the important information in the text itself rather than only in a screenshot of it. And when you do need an image, check that it leaves with the note — same folder, same export, same lifetime.

A setup that keeps the guarantee

If the argument holds, the practical arrangement is short:

  1. Keep notes as individual text files in one folder.
  2. Give that folder to a sync service you can leave, rather than an application that owns it.
  3. Back it up somewhere you control — an external drive counts.
  4. Prefer tools that edit the files in place over tools that store a copy elsewhere.

None of this is sophisticated. That is the point: a setup you can describe in four lines is a setup you can still run in ten years.

Where Papscroll fits

Papscroll stores notes as Markdown text. That is a deliberate constraint, not a limitation of the editor: it means a note written in the Android app opens in the web app, can be read in any text editor, and does not become inaccessible if a feature is removed or a client is discontinued.

The app adds the parts that make text notes practical day to day — capture from the browser and from Android, sync across clients, search, and an archive you can read without it. The format underneath stays plain, because that is the part that has to survive.

The test in this article applies to Papscroll too. Export your notes, open the files with something else, and confirm they still work. Do that for any tool you intend to keep for a decade.