History Lesson: What Is an .rtf File? Rich Text Format

What is an .rtf file?

An .rtf file is a Rich Text Format document — spell RTF as Microsoft’s published language for moving formatted text (and related document features) between word processors and other programs. On disk the extension is .rtf (also .RTF). Library of Congress format notes and Microsoft’s own specifications describe RTF as a proprietary format with a published specification: readable enough that many non-Microsoft apps learned to import and export it, yet still owned and versioned by Microsoft through 2008.

Open a genuine .rtf in a plain text editor and you usually see markup that starts with {\rtf1 (or an older {\rtf0), then character-set hints such as \ansi, optional code-page tags such as \ansicpg1252, font tables, and runs of text mixed with backslash commands. That readable skeleton is why RTF became the everyday “save something Word-ish that another program might open” choice long before .docx was the default.

Is RTF the same as a Word .doc?

No — and that mix-up still fills search boxes. Classic .doc is Microsoft Word’s older binary document format (the Word 97–2003 default many people still mean). .docx is Office Open XML: a ZIP package of XML parts that became Word’s default from Word 2007 onward. RTF is a separate markup interchange. Microsoft’s Office file-format reference still lists .rtf as Rich Text Format for transferring documents between operating systems and applications — alongside .doc and .docx, not as a synonym for either.

People sometimes rename .rtf to .doc hoping Word will “just treat it as Word.” Renaming does not convert the bytes. A real .rtf still begins with RTF markup; a classic binary .doc does not. Word may open both through different loaders, but the on-disk contracts differ — the same lesson as renaming .doc to .docx without converting.

A second confusion sits in the mail client. Outlook and Exchange expose a compose option labeled Rich Text Format. Microsoft’s Exchange documentation is explicit: that rich text message path is synonymous with TNEF (Transport Neutral Encapsulation Format) packaging for MAPI mail properties — and it is completely different from the rich text document format available in Word. A .rtf attachment on disk is the document interchange file; Outlook “Rich Text” email is a different packaging story (often involving Winmail.dat when recipients cannot decode TNEF). Do not assume an old mail body’s “Rich Text” setting means the attachment was a Word .rtf save.

Where RTF came from (Microsoft, ~1987, and the interchange era)

Microsoft introduced RTF in the mid-to-late 1980s as a transfer format for formatted text. Library of Congress chronology and Microsoft Systems Journal indexes point to Nancy Andrews’s March 1987 article “Rich Text Format Standard Makes Transferring Text Easier” as an early public description — later specs treat that moment as the Version 0 / first-description era. Wikipedia and product histories place the first shipping RTF reader/writer with Microsoft Word 3.0 for Macintosh in 1987. Hedge any single “invented on day X by one person” claim; the public record is a team format that Microsoft published and kept extending.

Why it spread is practical: the 1980s–2000s office world was a patchwork of Word, WordPerfect, Works, Ami Pro, and countless Windows apps that needed clipboard paste with bold and fonts intact. RTF was easier for many programs to emit than a full Word binary, and more formatting-friendly than plain .txt. Windows WinHelp used RTF for textual help content for years; WordPad (from Windows 95) treated RTF as a native save path; developers pasted Rich Text Format onto the clipboard so Word and peers could keep styles. Cross-vendor handoffs — including WordPerfect-era “save something the other side might open” workflows — leaned on RTF as a shared dialect even when neither side promised pixel-perfect fidelity.

Microsoft kept publishing numbered RTF specifications as Word grew: formal 1.0 in June 1992, then 1.x updates through the Word 95 / 97 / 2000 / 2002 / 2003 / 2007 line. Version 1.5 (April 1997, Word 97-era) is the often-cited turn that moved beyond 7-bit-only textual content and added Unicode-oriented control words such as \u plus \ansicpgN. The last published specification is 1.9.1 (March 2008, Word 2007-era). After that Microsoft froze enhancement: Word 2010 notes state RTF is no longer enhanced for new Word features, so Save As RTF can drop newer layout and functionality. The interchange era did not vanish overnight — it just stopped getting new control words.

How RTF is distinctive (control words, groups, and readable markup)

Spell the machinery plainly. An RTF file is mostly 7-bit ASCII plain text (later versions also allow richer character handling). It is built from three kinds of tokens: control words (a backslash plus letters, such as \b for bold on and \b0 for bold off), control symbols (a backslash plus one non-letter, such as \~ for a nonbreaking space), and groups (brace-delimited { ... } scopes that apply formatting or hold tables of fonts, colors, styles, pictures, and document info). A file typically has a header (starting \rtf0 / \rtf1, character set, font table, and related setup) and a document body of paragraphs and runs. Magic-number checks look for {\rtf at the start.

That design is why RTF feels different from Word’s native binaries: you can open many .rtf files in Notepad and still see human-readable words between the backslashes. It is also why fidelity varies. Apps implement subsets of control words; a WordPerfect or third-party writer may ignore Word-only groups; embedded pictures may be hex-encoded blobs inside the text stream. RTF tried to carry a lot of a Word document — including, in later specs, comments and tracked changes — but “can open” never meant “looks identical everywhere.”

Why .rtf files still sit on disks and in email archives in 2026

By 2026, .rtf still turns up in old mail attachments, legal and school hand-ins that asked for “Word or RTF,” WordPad saves, exported notes, clipboard-era archives, help-authoring leftovers, and folders labeled “for WordPerfect / Works / exchange.” Library of Congress holdings alone show large RTF counts in personal and organizational papers — a reminder that interchange copies accumulate even after the format stops evolving. These are legacy files in the everyday sense: still useful documents from an era when RTF was the portable middle ground, sitting beside .doc and .docx without being either.

Legacy File Converter lists Rich Text Format / .rtf among supported documents on Supported File Types and converts .rtf locally on Windows. Nothing is uploaded. This article stays the history. For neighboring word-processor lessons, see History Lesson: What Is a .doc File?, History Lesson: WordPerfect (.wpd), History Lesson: Microsoft Works (.wps), History Lesson: Ami Pro (.sam), and the practical companion Old Word Documents That Won't Open.