Plain Text Is a Writing Decision, Not a Tech Decision

Ask someone why they write in plain text files instead of Word or Google Docs, and you will almost always get a tech answer. They will talk about file size, software that might disappear in ten years, or how a .txt file opens on any device without breaking. These answers are true. But they miss the point. The real reason plain text changes your writing has almost nothing to do with computers. It has to do with what happens in your head when the screen stops offering you choices.

When you open a blank Word document, you are handed a stack of small decisions before you write a single sentence. Font. Size. Line spacing. Heading style. A plain text file gives you none of that. There is one font, one size, and nothing to adjust. The page looks the same whether you just started or you are on your fifth revision. That sameness is the actual benefit. It forces the words to carry all the weight, because there is nothing else on the page to lean on.

I’m Rohan Ratnayake, and I have spent the last five years working inside writing workflows, testing different tools, and watching how small interface choices change output speed and quality. Somewhere around my second year of doing this daily, I noticed a pattern I could not shake: my roughest, most honest drafts almost always came from the plainest tools I used, and my most polished-looking but weakest drafts came from documents dressed up with headers and colors before the writing was even finished. That observation is what pushed me to dig into why this happens instead of just accepting it as a personal quirk. What follows is what I found, mixed with what I have tested myself.

The Real Argument for Plain Text Isn’t About Technology

Most articles about plain text writing lead with portability and file longevity. Those points are real, but they are secondary. A .txt or .md file will open in fifty years the same way it opens today, and that matters if you are archiving decades of work. But that is a storage argument, not a writing argument. It explains why you should keep your old drafts as plain text. It does not explain why you should draft in plain text in the first place.

The drafting argument is different, and it comes down to one idea: a blank page with no formatting removes the option to fake progress. In a formatted document, you can spend forty minutes making a document look finished without writing a single new idea. You can center a title, add bold text, insert a table of contents, and feel like you accomplished something. None of that happened in a plain text file, because there is nothing to format. You either write words or you do not.

This is not a small psychological trick. It changes what “done” looks like while you draft. In a word processor, a messy draft looks messy, and that visual mess can feel discouraging, even embarrassing, even though messy drafts are normal and needed. In plain text, a rough draft and a clean draft look almost identical on the screen. There is no visual signal telling you the work is unfinished, so you keep writing instead of stopping to fix the look of something that was never meant to look finished yet.

A Short History of Writers Who Chose Constraint on Purpose

Writers picking limited tools on purpose is not a new habit. It shows up across decades, and the reasons line up more than most people expect.

Typewriter loyalists are the clearest example. Long after word processors became common, some writers kept using manual typewriters. Cormac McCarthy famously wrote on the same Olivetti typewriter for decades, buying an identical replacement model when his first one wore out rather than switching to a computer. A typewriter cannot format text. It cannot delete a paragraph and rearrange it with a few keystrokes. Every choice you make sticks, at least on that page, which pushes a writer to think through a sentence before typing it rather than typing loosely and cleaning it up later.

Then there are novelists who kept using software that looked outdated to everyone else. George R.R. Martin has talked openly about writing his novels on WordStar, a DOS-based word processor from the 1980s, running on a computer with no internet connection. He has said plainly that he likes it because it does exactly what he needs and nothing more. No spell-check interrupting his flow, no auto-formatting changing his intent, no notifications pulling his attention away.

Line these examples up and a shared logic appears. It is not nostalgia, and it is not being bad with technology. Each of these writers chose a tool that could not offer them side quests. A typewriter cannot tempt you into font shopping. WordStar in 1985 cannot tempt you into scrolling through a document theme gallery. The constraint is the entire point. It removes a category of decision that has nothing to do with the actual sentence you are trying to write.

Plain text on a modern computer does the same job through a different route. You are not using old hardware. You are using a text editor that simply refuses to offer formatting tools, which puts you in the same position as a writer with a typewriter: the only decision left is what word comes next.

The Psychology of Formatting as Procrastination

Formatting a document feels like writing. It uses the same hands, the same screen, and often the same document. But it is not writing, and the brain has a hard time telling the difference in the moment. This shows up in three common stages, and once you can name them, you start noticing them happening in real time.

Font Shopping

This is the most obvious stage. You open a new document and, before typing a word, you scroll through font options. Serif or sans-serif. Something that “feels right” for the piece. This can eat ten or fifteen minutes on a task that has zero connection to the actual content. The font will not make an idea clearer. It will not make an argument stronger. But it feels productive because you are actively doing something inside the writing tool.

Margin Fiddling

Once the font is picked, some writers move to spacing and margins. Single space or double space. Standard margins or slightly wider ones for a cleaner look. Again, none of this touches the content. A reader on the other end, especially if the piece will be pasted into a blog platform, an email, or a script, will never see these margins. They exist only inside the document you are drafting in, and they vanish the moment the text moves anywhere else.

Style Tweaking

The final stage, and often the sneakiest, is style tweaking. Bolding a phrase that feels important. Adding a header style before you know if that section will survive the next revision. Building a table of contents for a document that is still half-written. This stage feels the most like real progress because it touches the actual words. But it is still avoidance, because you are polishing sentences that might get cut entirely once the full draft exists.

Each of these stages borrows time from the drafting process and returns almost nothing. A plain text file removes all three options at once. There is no font menu, no margin setting, no bold button. The only tool left is the sentence.

What Changes When the Screen Looks the Same Every Day

One thing I noticed early in my own drafting, once I moved rough drafts into plain text files, is that I stopped rereading my work with a critical eye too early. In a formatted document, a paragraph with a heading and clean spacing looks finished, even if the ideas inside it are still half-formed. That visual polish tricks your brain into judging the content as more complete than it is, which leads to premature editing. You start trimming sentences and second-guessing word choices before the section is even fully drafted.

In a plain text file, every paragraph looks equally unfinished, because nothing about the format signals completion. This keeps you in drafting mode longer, which for most writing tasks is exactly where you want to stay until the full first pass is done. Editing too early, before the whole piece exists, tends to produce writing that is locally polished but structurally weak, because you spent effort perfecting a section that might not even survive once you see the full shape of the piece.

There is also a smaller but real benefit around distraction. Word processors are full of small movement: a cursor blinking inside a styled heading, a sidebar showing word count and readability scores, sometimes even suggestions popping up mid-sentence. A plain text editor, especially a minimal one, has almost none of this. The screen is quiet. For writers who get pulled off task by visual noise, that quiet is not a minor comfort. It is the difference between finishing a page in twenty minutes or finishing it in an hour with three unplanned breaks.

Plain Text vs Word Processors: A Side-by-Side Comparison

Here is how the two approaches actually compare across the parts of drafting that matter most.

This table is not meant to declare a winner. It is meant to show that the two approaches are strong in different places. Plain text wins almost everywhere that matters during the actual drafting stage. Word processors win almost everywhere that matters once a piece needs to be shared, reviewed, or laid out for final publication. Knowing this makes the choice easier: many writers benefit from using both, just at different points in the process.

What Plain Text Actually Costs You

A fair look at plain text has to include what you lose, because pretending there is no downside would not match how writing actually gets finished and published. I have gone back to formatted documents plenty of times mid-project, and it is worth being honest about why.

• Editor comments and suggestions. If you work with an editor who leaves comments in the margin or suggests specific line edits, plain text cannot hold that conversation. You end up copying text back and forth or switching tools entirely for the review stage.
• Tracked changes. Formal editing processes, especially for longer projects, often rely on tracked changes so both writer and editor can see exactly what moved or got cut. Plain text has no native version of this. You would need a separate tool like version control software, which most writers outside of software fields have never used and do not want to learn.
• Layout work. At some point, most writing needs to look like something: a formatted blog post, a PDF, a printed page. Plain text holds none of that information. Every bit of layout has to be added afterward, in a different tool, which adds a step that formatted documents skip.
• Collaboration with non-technical readers. If you are sharing a draft with someone who is not comfortable opening a .txt or .md file in a code editor, plain text can feel foreign to them, even though the file itself is about as simple as a file can get.
• Spell-check and grammar tools. Many plain text editors do not include built-in spell-check or grammar suggestions, meaning you either add that step manually or move the text elsewhere before publishing.

None of these costs cancel out the drafting benefits. They just mean plain text works best as a drafting tool, not necessarily a finishing tool. Most of the writers I have watched succeed with this approach treat it as stage one of a two-stage process, not the entire process.

Tools and Formats for Plain Text Drafting

If the idea of trying this appeals to you, it helps to know what your actual options look like, since “plain text” is not one single format.

• .txt files — the simplest option, opens anywhere, holds nothing but raw words with no structure at all.
• Markdown (.md) files — plain text with light structure added using simple symbols for headings, bold, and lists, which many writers prefer because it adds just enough organization without turning into a formatted document.
• Minimal text editors — tools built specifically for distraction-free writing, often with a full-screen mode that hides menus and file structure while you work.
• Code editors used for writing — some writers repurpose simple code editors because they are fast, lightweight, and strip away every formatting option by default.
• Note-taking apps with a plain mode — several popular note apps include a distraction-free or plain text mode that gives the same drafting benefit without leaving the app you already use daily.

None of these require any technical skill beyond typing. The barrier people expect, that plain text is somehow a “developer thing,” does not really hold up. The learning curve is close to zero, since you are removing tools, not adding them.

How to Try Plain-Text Drafting Without Blowing Up Your Workflow

You do not need to abandon your current tools to test this out. A gradual approach tends to work better than switching everything at once.

1. Pick one project, not everything you write. Choose a single article, chapter, or piece and draft only that one in plain text, so you are testing the approach rather than committing to it blindly.
2. Turn off formatting entirely for the first draft. Even if you stay in your usual word processor, disable styles, headers, and font choices until the full draft is done. This gives you a partial version of the same benefit.
3. Move to a real plain text tool for the second attempt. Once you have a feel for drafting without formatting, try an actual .txt or markdown file for your next piece, so you get the full quiet-screen effect.
4. Add formatting only after the draft is complete. Move your finished plain text into your usual tool for the layout stage, so you keep the collaboration and publishing benefits while still getting the drafting benefits earlier on.
5. Track how long the draft takes compared to your usual process. This is the part most people skip. Comparing actual time and how many times you stopped to fix formatting gives you real evidence instead of a vague feeling about which method worked better.

Troubleshooting Common Plain-Text Problems

My plain text file looks too plain and it’s throwing me off. This is common at first because you are used to visual cues telling you a document is “real.” Give it a few sessions. Most writers report the flat look stops feeling strange within a week of steady use.

I miss having headings to organize long pieces. Switch to markdown instead of raw .txt. Markdown lets you mark headings with simple symbols, so you keep a light structure without opening the door to full formatting.

My editor can’t work with a plain text file. Keep drafting in plain text, then move the finished draft into a word processor before sending it out. You get the drafting benefit and still hand off a file your editor can mark up normally.

I keep switching back to my old formatted document out of habit. Try closing your usual writing app entirely while drafting, so the temptation to switch back is not one click away. Physical friction, even something this small, changes behavior more than willpower does.

Nothing autosaves and I’m worried about losing work. Most plain text editors do support autosave, but check your specific tool’s settings before you start a long session. If it does not, save manually every few minutes until it becomes a habit.

Bringing It Together

Plain text is not a tool for people who dislike technology, and it is not a badge of seriousness either. It is a drafting choice that removes a specific kind of distraction: the kind that dresses itself up as writing while producing nothing you will keep. Portability and file safety are real reasons to store your work as plain text long term, but they are not the reason drafting in it feels different. That difference comes from a blank screen that refuses to give you anything to hide behind except the next sentence.

None of this means formatting is the enemy. Layout, styles, and tracked changes all earn their place once a piece is ready for readers, editors, or a final published form. The point is timing. Save the formatting decisions for after the words exist, not before.

If you have tried drafting in plain text, or if the idea of a blank, formatting-free screen sounds more stressful than freeing to you, I would like to hear which side of that you land on and why. Drop a comment with your experience.