RTF: The Cross-Platform Document Format That Refuses to Die

Rich Text Format was published by Microsoft in 1987 as a way to exchange formatted documents between different word processors. Nearly four decades later, it's still around — not because anyone loves it, but because it occupies a useful niche that no other format fills. RTF is readable by virtually every text application ever made, it can't execute code, and it's human-readable (if you don't mind parsing control codes).

Microsoft quietly stopped updating the RTF specification after version 1.9.1 in 2008. They've actively discouraged its use in favor of DOCX. Yet RTF persists in email clients, legacy systems, legal software, embedded applications, and anywhere that needs formatted text without the complexity or security risks of modern document formats.

How RTF Works: Control Codes in Plain Text

RTF is a plain-text format. Open an RTF file in a text editor and you'll see content like:

{\rtf1\ansi{\fonttbl{\f0 Times New Roman;}}
{\pard\f0\fs24 This is a paragraph.\par}
{\pard\b Bold text.\b0 Normal text.\par}
}

Every RTF command starts with a backslash: \b for bold, \i for italic, \fs24 for 12pt font (size is in half-points), \par for paragraph break. Curly braces { } create groups that scope formatting changes. The format is entirely text-based — no binary data, no ZIP compression, no XML.

This design has consequences. RTF files are larger than DOCX for equivalent content because there's no compression. A document with many formatting changes generates verbose control codes. But the format is trivially parseable, debuggable, and recoverable — if an RTF file is corrupted, you can often fix it in a text editor by finding the mismatched brace or broken control code.

The Security Advantage: No Macros, No Scripts

RTF's most compelling feature in 2026 is what it can't do. RTF has no macro capability, no scripting engine, no embedded executables, and no auto-executing content. You cannot embed VBA macros, JavaScript, ActiveX controls, or any other executable code in an RTF file. This makes RTF inherently safer than DOC, DOCX, or even PDF (which supports JavaScript).

This is why some organizations require RTF for email attachments, why certain legal systems accept only RTF submissions, and why RTF remains common in regulated industries where document security is mandatory. A malicious RTF file can exploit vulnerabilities in the RTF parser (and these have existed — CVE-2017-11882, CVE-2012-0158), but the format itself cannot contain executable code.

Caveat: some applications treat .rtf files as a trigger to launch Word, which then interprets OLE objects embedded via control codes. A deliberately crafted RTF file can contain OLE objects that exploit Word's OLE handling. This is a Word vulnerability, not an RTF feature, but it means "RTF is safe" has caveats when opened in Microsoft Word specifically. Opening RTF in WordPad, LibreOffice, or any basic RTF reader doesn't have this issue.

What RTF Can and Can't Format

RTF supports: fonts (name, size, color), bold, italic, underline, strikethrough, superscript/subscript, paragraph alignment (left, center, right, justify), indentation, line spacing, tabs, bullet lists, numbered lists, tables (basic), page breaks, headers and footers, images (WMF, EMF, PNG, JPEG — embedded as hex data), and hyperlinks.

RTF does not support: track changes, comments, drawing objects (SmartArt, shapes), embedded charts, themes, master styles/style inheritance, table of contents (as a live field), bibliographies, advanced table features (merged cells work but are unreliable), equations (MathML/OMML), and any features introduced after the 2008 spec freeze.

The practical ceiling: RTF handles business letters, memos, simple reports, and any document that could have been written on a 1990s word processor. It falls apart for complex layouts, academic papers with citations, documents requiring change tracking, or anything that needs visual design beyond basic formatting.

When RTF Is Actually the Right Choice

Cross-platform exchange with unknown recipients: You don't know what software the recipient has. DOCX requires a word processor. PDF requires a viewer. RTF opens in WordPad (included with every Windows installation), TextEdit (macOS), LibreOffice, and literally hundreds of other applications. It's the closest thing to a universal document format.

Legacy system integration: Many enterprise systems from the 1990s and 2000s (legal case management, medical records, government databases) generate and consume RTF. These systems won't be updated. RTF is their interface format, and it works.

Email-safe formatting: Attaching an RTF file to an email is safer than attaching DOCX (no macros) and more formatting-rich than plain text. Some email gateways strip or quarantine DOCX attachments but pass RTF through.

Programmatic document generation: Generating RTF from code is straightforward because it's text-based. You don't need a library — just string concatenation with the right control codes. For simple reports, invoices, or templated documents, RTF generation is trivial compared to generating DOCX (ZIP of XML) or PDF (binary page description).

Data interchange between applications: Many applications use RTF as a rich-text clipboard format. When you copy formatted text between applications, the clipboard often carries RTF as one of the available formats. Rich text editors in desktop applications frequently use RTF as their native format.

Converting RTF to Modern Formats

RTF to DOCX (/rtf-to-docx): Clean conversion. All RTF formatting maps directly to DOCX equivalents. Images, tables, and basic formatting survive intact. The resulting DOCX file will be significantly smaller due to ZIP compression. This is the recommended migration path for RTF archives.

RTF to PDF (/rtf-to-pdf): Reliable. LibreOffice renders RTF to PDF with full fidelity. The limited formatting vocabulary of RTF means there's less to go wrong compared to DOCX-to-PDF conversion.

RTF to ODT (/rtf-to-odt): Good conversion quality. RTF's formatting model maps cleanly to ODT's style system. Some RTF-specific control codes may not have direct ODT equivalents, but these are edge cases.

RTF to HTML (/rtf-to-html): Basic formatting converts well. RTF's limited feature set is actually an advantage here — there's less complex formatting to break during conversion. Tables, lists, fonts, and text formatting all map to HTML elements.

RTF to TXT (/rtf-to-txt): Strips all formatting and extracts plain text. Trivial and reliable.

Going the other direction: DOCX to RTF, DOC to RTF, and ODT to RTF all work but lose any features that RTF doesn't support — track changes, comments, equations, SmartArt, and advanced formatting are silently dropped.

RTF vs. the Competition

RTF vs. DOCX: DOCX is superior in every way except universality and security. Use DOCX for anything requiring modern features. Use RTF when you need guaranteed compatibility or macro-free safety.

RTF vs. Plain Text: RTF adds formatting (fonts, bold, tables, images) over plain text. If you need any visual formatting, RTF is the simplest format that provides it. If text content is all that matters, plain text is simpler and smaller.

RTF vs. HTML: HTML is more powerful for formatting and is natively web-compatible. RTF is better for print-oriented documents. If the document will be viewed in a browser, use HTML. If it will be printed or opened in a word processor, RTF is more appropriate.

RTF vs. Markdown: Markdown is simpler, more readable in source form, and better for technical content. RTF supports richer formatting (fonts, colors, precise spacing). Markdown is for content-first workflows; RTF is for formatting-matters workflows.

RTF is a survivor. It's not the best format for anything in particular, but it's good enough for a surprising number of use cases and it works everywhere. Its inability to carry executable code — once a limitation — is now a genuine security advantage in an era of macro-based malware.

For new documents, use DOCX or ODT. But when you need a formatted document that opens reliably on any system, can't carry malware, and doesn't require the recipient to install specific software, RTF is still the pragmatic choice. It's been around since 1987, and it'll be around long after the current generation of "modern" formats has been superseded.