You finish a novel draft, save it, and close the laptop feeling good. Ten years later you open that same file and your computer has no idea what to do with it. The program that made it is gone. The file just sits there, full of your words, locked behind a format nobody uses anymore. This happens more often than most writers realize, and it rarely gets talked about until someone loses something they cannot get back.
I’m Rohan Ratnayake, and I have spent the last five years working inside digital writing workflows, moving manuscripts between apps, fixing broken exports, and helping other writers untangle files that stopped opening properly. Somewhere in that stretch I started keeping a private list of formats and tools that quietly died or changed so much that old files broke. That list is longer than I expected, and it changed how I store my own drafts today. None of this comes from guesswork. It comes from watching files fail and figuring out, piece by piece, what actually keeps writing safe over time.
Why Old Writing Files Stop Opening
A file is not just words. It is words wrapped inside a set of rules that a specific program understands. When that program disappears, or a company changes its file format and drops support for the old version, the wrapping becomes a lock with no key. The text is still technically there, sitting inside the file as binary code, but nothing on your computer knows how to translate it back into readable sentences.
This is not a rare glitch. It is a known pattern in computing history, and writers have been hit by it for decades without much warning.
Real Cases of Format Extinction
Word processors from the 1980s and 1990s give the clearest examples. Programs like WordStar, AppleWorks, and early versions of WordPerfect were common tools for serious writers at the time. Each one saved files in its own closed format. When these programs stopped being sold and updated, the files they created became harder and harder to open on modern machines.
A few patterns show up again and again in these cases:
- Files saved in a proprietary format become unreadable once the original software is no longer maintained or sold.
- Floppy disks and other old storage media physically decay or become impossible to read without specialized, aging hardware.
- Font and formatting codes inside old files sometimes survive, but get displayed as garbled symbols instead of proper text.
- Even when a file opens, page breaks, italics, and special characters often shift or vanish entirely.
Archivists working with libraries and universities have dealt with this problem directly. When a writer donates their papers to a research library, those papers increasingly include floppy disks, early hard drives, and USB sticks alongside handwritten notebooks. Archivists have had to build entire recovery labs just to read these old drives: rooms stocked with vintage floppy drives, specialized cable adapters, and format-conversion software written specifically to translate dead file types into something current computers understand. In some documented cases, recovering a single author’s early manuscripts took specialists days of work, running old software inside emulators just to get the text back out in a form anyone could read.
That is the fate a personal writing archive can quietly slide toward if nobody plans ahead. A stack of USB drives with old drafts is not automatically safe just because the drives still physically exist.
A Quick Look at Format Risk Over Time
| Format or Tool | Era of Common Use | Current Status | Risk Level Today |
|---|---|---|---|
| WordStar (.ws) | 1980s | Rarely supported natively | Very high |
| AppleWorks (.cwk) | 1980s–2000s | Discontinued, needs conversion tools | Very high |
| Early WordPerfect (.wp, .wpd) | 1980s–1990s | Limited support, mostly legacy | High |
| Microsoft Word 97-2003 (.doc) | 1997–2007 | Still openable, support fading | Medium |
| Microsoft Word (.docx) | 2007–present | Widely supported | Low |
| Plain text (.txt) | Since the 1960s | Universally supported | Very low |
| Markdown (.md) | 2004–present | Open standard, widely supported | Very low |
| Rich Text Format (.rtf) | 1987–present | Mostly stable, minor quirks | Low |
The pattern across this table is simple. Formats tied tightly to one company’s software carry more risk. Formats that are open, simple, and widely adopted carry less. This is the same lesson digital archivists learned the hard way, and it applies just as much to a personal folder of short stories as it does to a famous author’s donated papers.
What Professional Archives Do Differently
Libraries, museums, and national archives have spent decades figuring out how to keep digital records readable for the long run. Their approach is not complicated once you strip away the technical language. It rests on three ideas, and every one of them can be scaled down to fit a single writer’s habits.
Habit One: Favor Open, Simple Formats
Archivists lean toward formats that are not owned or controlled by a single company, because open formats do not disappear just because one business changes direction or shuts down. Plain text files, Markdown files, and RTF files all fall into this category. They store your words with very little extra wrapping, which means far fewer things can break.
This does not mean you need to give up your favorite writing app. It means your master copy, the one meant to last, should be saved as something plain and open once a project is finished or reaches a stable draft. Fancy formatting can live in your working file. A clean backup should not depend on it.
Habit Two: Keep Redundant Copies in Different Places
Archives never store anything in just one location. A single hard drive, no matter how good, can fail, get lost, or get stolen. Professional preservation practice usually follows something close to a 3-2-1 pattern: three copies of a file, on two different types of storage, with one copy kept somewhere physically separate.
For a writer, this translates easily:
- One working copy on your main computer.
- One backup copy on an external drive or a second device.
- One copy stored somewhere off-site, such as cloud storage or a drive kept at a different location.
The goal is not to be paranoid. It is to make sure that no single accident, whether a spilled coffee, a stolen laptop, or a corrupted drive, can wipe out years of work in one moment.
Habit Three: Migrate Files Periodically Instead of Waiting
Archivists do not wait for a format to die before acting. They schedule regular checks, moving files from aging formats into current ones long before support disappears. This is called migration, and it works far better as routine maintenance than as an emergency rescue.
For a personal writing archive, this can be as simple as opening your old project folders once a year, checking that every file still opens cleanly, and re-saving anything that looks shaky in a more current or more open format. Five minutes of checking, done once a year, is far cheaper than days spent trying to recover a manuscript from a format nobody remembers how to open.
The Stranger in 2050 Test
Institutional rules are useful, but writers need something faster to apply while actually working. I built a simple mental check for this, and I call it the stranger in 2050 test.
The test asks one question: if a stranger, decades from now, sat down at a generic computer with no special software installed, could they open this file, read it clearly, and understand what it says?
That single question cuts through a lot of confusion about which format to trust.
Walking Through the Test
Run this test against a few common writing setups and the risk differences become obvious fast.
- A novel saved only inside a niche writing app’s internal project file. A stranger in 2050 likely cannot open this at all without the exact software, which may no longer exist. This fails the test badly.
- A novel saved as a .docx file from a current version of Word. A stranger has a reasonable shot at opening this, since the format is widely supported and documented. This passes for now, though it depends on Word-compatible software continuing to exist in some form.
- A novel saved as plain text or Markdown. A stranger can open this with almost any text editor, on almost any device, without installing anything unusual. This passes clearly.
- A novel that exists only inside a cloud-based writing platform’s private account. A stranger cannot open this at all unless the account, the company, and the platform are all still around. This fails badly, even if the writing itself is polished and complete.
Running your own drafts through this test takes a minute. Pick a file, imagine handing it to someone with a plain, ordinary computer decades from now, and ask honestly whether they could read it. If the answer is no, that file needs a plainer backup copy sitting alongside it.
Common Writing Tools Scored Against the Test
| Writing Setup | Passes Stranger Test? | Why |
|---|---|---|
| Notes app tied to one phone brand | No | Locked to a specific ecosystem of devices and accounts |
| Proprietary novel-writing software project file | No | Requires the exact software to interpret the file structure |
| Word (.docx) | Mostly yes | Broadly supported, though still owned by one company |
| Google Docs (kept only online) | No | Requires an active account and internet access to reach it |
| Google Docs exported as .docx or .txt | Yes | Removes the account dependency, keeps the format open |
| Plain text (.txt) | Yes | Readable by nearly any device, past or future |
| Markdown (.md) | Yes | Plain text with light, human-readable formatting marks |
| Handwritten notebook | Yes, with caveats | No software needed, but only one physical copy exists unless copied |
A useful pattern shows up here. Cloud tools and specialty apps are often wonderful to write inside, but they are risky as a final resting place for finished work. Exporting a clean, plain copy out of them closes that gap without asking you to give up the tool you like using every day.
Frequently Asked Questions About Long-Term File Safety
Does Saving to the Cloud Count as a Backup?
Cloud storage counts as one useful copy, but not as a complete safety plan by itself. A cloud account can get suspended, a company can shut down a service, or a subscription can lapse without anyone noticing for months. Treat cloud storage as one leg of your backup plan, not the whole plan.
Is Plain Text Really Better Than a Polished Word File?
For long-term safety, yes, plain text carries less risk, since there is almost nothing inside it that can break or become unreadable. For daily writing, a fuller format like .docx or Markdown with formatting is usually more practical, since it keeps italics, headings, and structure intact. Many writers keep a polished working file and a plain text backup side by side, which covers both needs at once.
How Often Should I Check My Old Files?
Once a year is a reasonable rhythm for most personal archives. Set a recurring reminder, open a handful of older project folders, and confirm the files still open cleanly on current software. Catching a problem early, while conversion tools still exist, is far easier than discovering it years after the fact.
What About Files Locked Inside a Specific App or Subscription Service?
Export a copy whenever the option exists, even if you plan to keep using the app day to day. Most writing tools offer some export option, whether that is .docx, .txt, .rtf, or Markdown. Building a habit of exporting a plain copy after finishing a project protects you even if that app disappears or changes its pricing in a way you can no longer afford.
The Part of This That Isn’t Really About File Formats
There is a quieter reason this topic matters, and it has less to do with computers and more to do with what writing means to the person doing it. A finished draft is not just data. It is time, attention, and thought that cannot be recreated the same way twice. Losing a manuscript to a dead format is not like losing a receipt. It is closer to losing a piece of a specific year of your life.
A paper notebook has one advantage that no digital file can fully match: it needs no migration plan. Ink on paper does not become unreadable because a company changes its software. It can fade, burn, or get lost, but it does not become locked behind a format nobody remembers how to open. That is a real kind of stability, even with all of paper’s own physical fragility.
Plain text and open formats sit in an interesting middle ground on this spectrum. They are not as physically permanent as paper, since they still depend on some kind of device existing to display them. But they are far closer to paper’s simplicity than any proprietary app format ever gets. A .txt file from thirty years ago opens on a modern computer with zero effort, the same way a page from an old notebook can still be read by anyone who picks it up. That is not an accident. It is what happens when a format stays plain, open, and boring enough that nothing about it needs constant upkeep to survive.
Writing worth keeping deserves a format that does not ask you to babysit it. Choosing plain, open formats for your finished drafts is not about distrust of modern tools. It is about giving your own words the same quiet durability that a good notebook has always offered, without giving up the convenience of writing on a screen.
Building a Simple Preservation Habit Into Your Writing Life
None of this needs to turn into a complicated system. A short, repeatable routine covers most of what matters.
- Finish a draft, then save a plain text or Markdown copy alongside your main working file.
- Store that copy in at least two separate places, such as a computer and an external drive or cloud folder.
- Once a year, open your older project folders and confirm every file still opens the way it should.
- Whenever you switch writing tools, export your older work into an open format before you fully move on.
- Run the stranger in 2050 test on any file you would genuinely be upset to lose.
Five minutes spent on this routine now is far less costly than the days a professional archivist might spend trying to recover the same file decades later, once the software that made it is long gone.
Your words are worth more than the app you happened to write them in. Apps get sold, shut down, and replaced constantly, but a well-saved file, kept plain and stored in more than one place, can outlast every tool that ever touched it.
What does your own backup routine look like right now, and is there an old file sitting somewhere that you haven’t tried opening in years? I’d like to hear what you find.
