The Document That's Almost a Word Doc
Someone sends you a file ending in `.rtf`. You double-click it, and — relief — it actually opens. There's your text, more or less where it should be, in something that looks a lot like a Word document.
Then you notice the problems. The photo that was supposed to be on page two is gone, or it's been blown up to the size of a billboard. The neat table has slumped sideways. The fonts aren't quite right. And when you check the file size, this three-page memo is somehow 8 MB — bigger than the actual photos that were in it.
An RTF file isn't broken. It's doing exactly what it was designed to do back when "the internet" meant a modem screaming at a phone line. It's just showing its age. Here's what an RTF file really is, why it behaves so strangely, and how to turn it into a document that actually works in 2026.
What an RTF File Actually Is
RTF stands for Rich Text Format. Microsoft created it in 1987 as a way to move formatted documents between different programs and different computers without everything falling apart.
That was a real problem at the time. Every word processor — WordPerfect, WordStar, Microsoft Word, and a dozen others — saved files in its own secret, incompatible format. Open a WordPerfect file in Word and you'd get a screen full of garbage. RTF was the peace treaty: a single, openly-documented format that any program could read and write, so a document could survive the trip from one app to another with its bold, italics, fonts, and basic layout intact. Hence "rich" text — as opposed to "plain" text, which carries no formatting at all.
Under the hood, an RTF file is surprisingly readable. Unlike a modern `.docx` (which is a zipped bundle of XML) or an old `.doc` (which is dense binary code), an RTF file is just plain text with formatting instructions written inline as commands. If you open one in Notepad, you'll see your words wrapped in markup like `\b` for bold and `\i` for italic. It's almost human-readable, which is part of why it lasted so long.
Why Your RTF File Is So Strangely Large
Here's the thing that confuses everyone: a short RTF document can be enormous. There are two reasons.
1. Images are stored as text. RTF can't hold a raw photo the way a `.docx` can. Instead, it converts every embedded image into a giant block of hexadecimal text — basically spelling out the picture one character at a time. This roughly *doubles* the storage each image needs. Drop two phone photos into an RTF and your file balloons into the multiple-megabyte range almost instantly.
2. Formatting is verbose. Every style change is written out as an explicit command, repeated over and over. A heavily formatted document carries a lot of overhead.
So an RTF file is often several times larger than the equivalent `.docx` holding the exact same content. If you've been emailed an RTF that's too big to send back, that's not a mistake — it's just how the format works.
Why the Formatting Looks Off
RTF was built to carry *basic* formatting reliably. The problem is that documents stopped being basic decades ago.
Modern documents lean on things RTF was never designed for: floating images with text wrapping, complex multi-column tables, tracked changes, comments, embedded charts, and fancy text effects. When a program saves one of these as RTF, it has to either approximate those features or drop them. The text survives. The sophisticated layout often doesn't.
That's why your images jump around, your tables collapse, and your careful design "drifts." You're squeezing a 2026 document through a format frozen in roughly 2008 (RTF's last official update). It's not corruption — it's compression of *capability*.
Why You Got an RTF in the First Place
A few usual suspects:
None of these are wrong. You've just received a format that prioritizes *compatibility* over *fidelity* — and now you want the fidelity back.
How to Fix It: Convert the File
You don't need to install anything or reply asking for a "real" version. Convert the RTF into a format that fits what you're actually trying to do.
RTF → DOCX (when you need to edit it in Word or Google Docs)
This is the right move most of the time. Converting to `.docx` gives you a genuine, modern Word document — editable in Word, Google Docs, or Pages — that can finally hold images and complex layout properly. It also shrinks the file dramatically, since DOCX stores pictures efficiently instead of spelling them out as text. Run it through RTF to DOCX and you're editing a normal document in under a minute.
RTF → PDF (when you just need to read, print, or send it)
If you don't need to edit the document — only read it, print it, or attach it somewhere — convert it to PDF. A PDF locks the layout in place so nothing shifts on someone else's screen, opens on every device, and is accepted by every upload portal that's ever rejected an oddball format. Drop your file into RTF to PDF and it'll look the same everywhere.
RTF → TXT (when you only want the words)
Sometimes the formatting is the enemy. If you just want clean, raw text to paste into a script, a CMS, or an email — with all the markup stripped away — use RTF to TXT to pull out the words and throw away everything else.
And if you're going the *other* direction — you have a Word file and a system that demands an RTF — DOCX to RTF handles that too.
Should You Ever Save as RTF on Purpose?
Occasionally, yes. If you need a *lightweight, text-only document* that's guaranteed to open in any program ever made, and you don't care about images or fancy layout, RTF is a reasonable, license-free choice. It's also handy for plain formatted notes you want to keep portable for decades.
But for anything modern — a résumé, a report with images, a client deliverable — skip it. Save as `.docx` to edit or `.pdf` to share. RTF's universality isn't worth the lost formatting and bloated file size when better options are one click away.
Bottom Line
An RTF file is a nearly-40-year-old peace treaty between word processors — a format designed to carry your words and basic styling safely from any program to any other. It still does that job. It just can't keep up with modern images, layouts, and the documents we actually make today, which is why it looks slightly off and weighs so much.
If you need to edit it, convert it to DOCX. If you just need to read or send it, turn it into a PDF. And if you only want the text, strip it down to TXT. Each conversion takes about as long as it took to read this sentence — and then your almost-a-Word-doc finally becomes the real thing.