Home · Blog · Plain text

The quiet power of plain text

20 Sep 2026 · Text · 6 min read

Plain text is the least impressive format on your computer. No bold, no italics, no embedded images, no comments in the margin — just characters in a row, the way text looked in 1970. And yet it keeps outliving everything. Files written as plain text forty years ago open perfectly today, while documents from ambitious formats of the 1990s need archaeological tools. Programmers run their lives on it. Writers who care about longevity swear by it. Scientists archive data in it. This article is about why the humblest format keeps winning, and the workflows where it quietly beats everything fancier.

Readable in fifty years

Formats die; plain text doesn't. A .txt file from 1985 opens in every editor on earth, because there's nothing to interpret — the bytes are the content. Contrast that with the graveyard of proprietary formats: word processor files from the 90s that only open in emulators, presentation files whose animations died with their plugins, note apps whose databases are inscrutable blobs. Every layer of formatting is a bet that some future software will understand it. Plain text makes no bets.

This isn't nostalgia; it's risk management. If you're writing a journal, a novel draft, lab notes, or anything you might want in twenty years, plain text is the only format with a proven multi-decade record of simply working. Archivists have a saying: if you want it to survive, store it as text.

No lock-in, no ransom

Your notes are hostages of whatever app holds them — until they're plain text. A folder of .md files can move between a dozen editors in an afternoon; a database inside a note app moves when the vendor permits an export, in the format they choose, minus the features they don't feel like supporting. People discover this the expensive way: the app raises its price, gets acquired, or shuts down, and suddenly years of thinking are behind a paywall or a dead login.

Plain text inverts the power dynamic. The files are yours in the most literal sense — readable by everything, owned by no one. You can switch tools on a whim because the tool was never holding anything. That freedom changes how you choose software: you pick tools for what they do, not for where your data is trapped.

Small, fast, searchable

A novel is about a megabyte as plain text. The same novel in a word processor format is several times that, and in a scanned PDF, hundreds of times. Small means fast: instant opens, instant saves, instant syncs — on a phone from 2016 as happily as on a new laptop. And because the content is just characters, the entire corpus is searchable with tools from the 1970s — grep can find a phrase across ten thousand files in under a second, something no proprietary format can promise without its own application running. When your archive grows to decades of journals, drafts and notes, that speed difference stops being a nicety and becomes the reason the archive stays usable at all.

Diff-friendly: version control loves text

Here's the superpower most people never notice. Version control systems like Git track line-by-line changes — but only in text. Keep a project plan as plain text and every edit is visible: who changed what, when, with the ability to undo any of it. Keep it in a binary document format and version control sees only "file changed", an opaque blob. Writers who keep drafts in text get a time machine for their manuscript; teams who keep specs in text get an audit trail for free. The diff tools of the previous article in this series exist because text is diffable — it's the property the whole collaborative world runs on.

Markdown: plain text with manners

"But I need headings and bold." You can have them without leaving text. Markdown is a set of lightweight conventions — # for headings, ** for bold, - for lists — that read naturally as plain text and render beautifully when processed. A Markdown file is perfectly legible in Notepad and perfectly formatted on a website. It's the reason READMEs, documentation, and increasingly books are written this way: one source, readable everywhere, publishable anywhere. All the formatting you need for 95% of documents, with zero lock-in.

Where it earns its keep

  • Notes and journals. A folder of dated text files, searchable instantly, readable forever. No app required — though good apps make it nicer.
  • Writing drafts. Novelists and academics draft in text to separate writing from formatting; the layout happens once, at the end.
  • Data. CSV and TSV are plain text with commas — openable in every spreadsheet ever made, processable by every language, archivable without a second thought.
  • Configuration. Every serious system stores its settings as text files, because text can be reviewed, diffed, backed up and regenerated.
  • Task lists. One line per task, done is a deletion or a prefix. Syncs anywhere, never needs a subscription.
Plain textMarkdownWord processorPDF
Readable in 2050YesYesProbablyLikely
Diffable / versionableYesYesNoNo
Searchable with simple toolsYesYesNeeds the appNeeds OCR sometimes
Typical size (10k words)~60 KB~65 KB~200 KB~300 KB+
Rich layoutNoBasicFullFull

The plain-text toolkit

Text's power multiplies with a few small tools, all free, all ancient by software standards. grep (or its faster modern cousin ripgrep) searches thousands of files instantly — your notes become a personal search engine. diff shows exactly what changed between any two versions. pandoc converts Markdown into Word documents, PDFs, HTML, ebooks and slide decks, so you can write in text and publish in whatever format the recipient demands — the "write once, output anything" trick that ends the format debate entirely. Add Git for version history and a sync service for backup, and you have a writing and note-taking system with no subscription, no vendor, and no feature that can be taken away. Each tool does one thing and they compose beautifully, which is precisely the philosophy plain text was built for.

When plain text isn't enough

Honesty, as always. Plain text can't do precise page layout — if you're designing a brochure, use a layout tool. It can't hold images except by reference. Track-changes collaboration with non-technical colleagues is genuinely smoother in a word processor, and complex tables with merged cells are miserable in text. The rule isn't "always text"; it's "text by default, richer formats when the job actually needs them". Most documents don't need what the richer formats sell — they just default to them out of habit.

The quiet power of plain text is that it asks nothing of the future. No license, no application, no cloud account — just characters, readable by anything, forever. In an industry that reinvents everything every five years, that's the most radical property a format can have.

Start small: move one project — your notes, your drafts, your task list — into text files this week, and notice how little you miss the app that used to hold them. The files will still open in 2050, whatever happens to everything else.

Count words in your text