Long before DOCX became the office standard, before PDF was everywhere, and when exchanging a formatted Word document between a Windows PC and a Mac was a genuine gamble, there was RTF. The Rich Text Format solved a real problem for its era and left a legacy that quietly persists to this day — even if most users have no idea it’s still running behind the scenes.
Microsoft invented RTF in 1987, initially as an internal format for transferring documents between different word processors. In 1992, Microsoft published the RTF specification openly, allowing any developer to implement it without licensing fees. That decision was consequential: throughout the 1990s and early 2000s, RTF became the de facto lingua franca of document exchange across different operating systems and applications.
If you needed to send a formatted document from Word on Windows to a colleague running Word on a Mac — or to someone using WordPerfect, or a Linux word processor — saving as RTF was the safest bet. It preserved bold, italic, font sizes, paragraph alignment, and basic tables, and virtually every text application could read it correctly.
Microsoft continued updating the RTF specification through version 1.9.1, then stopped in 2008. The format has been effectively frozen since then.
RTF has an unusual technical characteristic: it is a plain text format. Unlike DOCX (which is a binary ZIP archive) or the old DOC (which was a binary blob), an RTF file is human-readable text. It uses “control words” — keywords preceded by a backslash — to describe formatting instructions.
If you open an RTF file in Notepad, you’ll see something like:
{rtf1ansideff0
{fonttbl{f0 Times New Roman;}}
f0fs24 This is b boldb0 text.
}
Here, b starts bold formatting and b0 ends it. fs24 sets the font size to 24 half-points (12pt). This design made RTF relatively easy for different applications to implement — you don’t need a binary parser, just a text parser with knowledge of the control word vocabulary.
RTF usage has dropped dramatically, but the format hasn’t disappeared entirely:
RTF support is nearly universal across operating systems:
Honestly, there are very few situations where RTF is the right choice for new documents in the 2020s. For editable formatted documents, DOCX offers better compatibility, more features, and an actively maintained standard. For fixed-layout distribution, PDF is the correct tool. For pure text, a .txt file is lighter and simpler.
RTF’s modern value is primarily in two scenarios: reading old files that were created in RTF, and interfacing with legacy systems that specifically require RTF input. If you have RTF files that need to be converted, or need to produce RTF output for a system that demands it, a conversion tool makes the process quick and painless.
Do it in your browser — the file never leaves your device: PDF Tools