How to Convert RTF to Text or Markdown (2026 Guide)

Rich Text Format (RTF) was Microsoft's portable document format from the late 1980s, and against all expectations it's still in active use forty years later — particularly in legal practice management systems, government document workflows, and a long tail of legacy enterprise software. If you've received an RTF file in 2026 and need to extract the content for modern use, here are the methods that actually work, with honest tradeoffs for each.

Why RTF still exists in 2026

RTF was designed as a format that could move documents between Microsoft Word and other word processors when neither supported the other's native format. It's plain ASCII text with formatting encoded in escape codes — meaning any text editor can read it, and any tool that understands the escape codes can render it formatted.

That portability is exactly why RTF stuck around in specific industries:

• Legal practice management. Time-and-billing systems and document assembly tools (HotDocs, ContractExpress, even some modern legal tech) use RTF for templates and merge documents. The format is stable, well-documented, and trivially scriptable.
• Government and regulatory. Many government document workflows specify RTF as an acceptable submission format because of its long-term stability and lack of dependence on a specific Office version.
• Email automation. Some enterprise email systems generate RTF email bodies for compatibility with older Outlook versions.
• Embedded systems and electronic medical records. EMR vendors sometimes export documents as RTF for compatibility across hospital systems.
• Older Windows applications. WordPad's native format was RTF until Windows 11 deprecated it; RTF files from the past three decades remain in personal and corporate archives.

The format is fully specified in Microsoft's RTF Specification document, which has been frozen at version 1.9.1 since 2008. There's no active development, but there's also no instability — RTF files written in 2008 still parse correctly in 2026.

What's inside an RTF file

RTF is a plain-text format where formatting is encoded as backslash-prefixed control words. A simple paragraph of "Hello world" with bold formatting on "world" looks like this in raw RTF:

{\rtf1\ansi\ansicpg1252\cocoartf2580
{\fonttbl\f0\fnil\fcharset0 Helvetica;}
{\colortbl;\red255\green255\blue255;}
\paperw12240\paperh15840\margl1440\margr1440\vieww11520\viewh8400\viewkind0
\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural\partightenfactor0

\f0\fs24 \cf0 Hello \b world\b0 .}

You can open any RTF file in a plain text editor and see this kind of structure directly. The control words handle font tables, colour tables, paragraph properties, character formatting, lists, tables, and embedded images. The complexity grows quickly with the document — a real RTF file with images, tables, and multiple styles can be tens of thousands of lines of escape codes wrapping a few thousand words of actual content.

Method 1: Microsoft Word (highest fidelity)

Word reads and writes RTF natively. If you have Word installed, the simplest path is to open the RTF, then save in your target format.

How to use:

1. Double-click the .rtf file — Word opens it.
2. File → Save As.
3. For plain text: choose Plain Text (.txt). For Word format: choose Word Document (.docx). Click Save.

Pros: highest fidelity round-trip, all RTF features supported, mature implementation.

Cons: requires Word license. Saving as plain text loses all formatting. Saving as DOCX gives you a Word document, which has its own AI-input issues (covered in Word documents are AI-hostile) — for AI use, you'll want a further conversion step to Markdown.

Method 2: LibreOffice Writer (free, offline)

LibreOffice handles RTF cleanly and is the free equivalent of Method 1 for users without Word.

How to use:

1. Install LibreOffice from libreoffice.org.
2. Double-click the .rtf file — it opens in Writer.
3. File → Save As, choose your target format (Plain Text, DOCX, PDF, HTML, ODT).

Pros: free, offline, supports RTF features comparably to Word.

Cons: requires install. Some highly Word-specific RTF features (certain Microsoft-specific control word extensions) may render with minor differences.

Method 3: Pandoc CLI (gold standard for conversion)

Pandoc converts RTF to a long list of target formats — plain text, Markdown, HTML, DOCX, PDF, LaTeX, ePub, and many others. It's the right tool for power users and bulk conversions.

How to use:

# Install
brew install pandoc        # macOS
choco install pandoc        # Windows
sudo apt install pandoc     # Linux

# RTF to plain text
pandoc -f rtf -t plain input.rtf -o output.txt

# RTF to Markdown
pandoc -f rtf -t gfm input.rtf -o output.md

# RTF to HTML
pandoc -f rtf -t html5 -s input.rtf -o output.html

# RTF to DOCX
pandoc -f rtf -t docx input.rtf -o output.docx

# Bulk: convert every RTF in a directory to Markdown
for f in *.rtf; do pandoc -f rtf -t gfm "$f" -o "${f%.rtf}.md"; done

Pros: free, fast, handles every common RTF feature, scriptable for batch use, outputs to many formats.

Cons: requires CLI comfort. RTF is one of Pandoc's older input formats and has occasional edge cases on very complex documents — usually fine for typical content, occasionally needs post-processing.

Method 4: mdisbetter web tool (no setup, structured Markdown)

The web tool at /convert/word-to-markdown accepts RTF files alongside DOCX (RTF is a related format with similar structural concepts) and converts to Markdown directly.

How to use:

1. Open /convert/word-to-markdown.
2. Drop the .rtf file into the upload area.
3. Click Convert.
4. Download the resulting .md file.

Pros: no install, works in any browser, structured Markdown output (headings, lists, tables preserved). Good for one-off conversions and for non-developers.

Cons: one file at a time. For batch RTF conversion, Pandoc local is the right tool.

Method 5: Convert RTF to DOCX first, then convert

If you have a stash of RTF files and you want to consolidate them into a modern format, a useful pattern is to convert RTF to DOCX first (using LibreOffice headless mode in batch, or Pandoc), then run the DOCX-to-Markdown conversion on the result. This is sometimes useful when your RTF files have unusual encoding issues or vendor-specific extensions that handle better through the DOCX intermediate.

How to use (LibreOffice headless mode for batch):

# Convert all RTFs in a directory to DOCX
libreoffice --headless --convert-to docx *.rtf

# Then convert the DOCX files to Markdown with Pandoc
for f in *.docx; do pandoc -f docx -t gfm "$f" -o "${f%.docx}.md"; done

This two-step path can produce slightly different output than direct RTF-to-Markdown conversion because LibreOffice's RTF parser handles certain edge cases differently than Pandoc's. For documents from legal or government systems with non-standard RTF extensions, this two-step path is sometimes more reliable.

Comparison table

How to choose

• Have Word and just need a quick conversion? Word's Save As is the simplest.
• Don't have Word, need GUI? LibreOffice.
• Comfortable with CLI, doing bulk? Pandoc.
• Want Markdown without installing anything? /convert/word-to-markdown.
• Difficult vendor-specific RTF that's failing in direct converters? The RTF → DOCX → Markdown two-step often handles edge cases better.

RTF-specific considerations

A few things to know about RTF that affect conversion:

Encoding. RTF files specify their character encoding internally (the \ansicpg control word). Older RTF files often use code pages other than UTF-8 (CP1252 for Western European, CP932 for Japanese, etc.). Most modern converters handle this transparently, but if you see garbled characters in the output, the source encoding is the likely culprit. Word and LibreOffice handle encoding cleanly; Pandoc reads the encoding declaration correctly in most cases.

Embedded objects. RTF supports embedded OLE objects — Excel sheets, PowerPoint slides, equations, images. Conversion to plain text or Markdown drops these. Conversion to DOCX or HTML preserves them, sometimes as image references rather than as the original interactive object.

Tables. RTF tables convert reasonably well to Markdown tables in most cases. Complex tables with merged cells, nested tables, or unusual formatting may require post-processing — if the resulting Markdown table is malformed, Pandoc's -t html output sometimes preserves the structure better, and you can convert HTML to Markdown as a second step.

Form fields. RTF supports form fields (Word's legacy form feature). These don't have clean Markdown equivalents and are typically dropped or rendered as placeholder text.

The AI-input case for converting old RTF archives

If you have an archive of legal, government, or legacy enterprise RTF files and you're considering bringing them into a modern AI workflow, the conversion to Markdown is the right move. RTF is even more hostile than DOCX to direct LLM ingestion — many AI platforms don't accept RTF as an upload format at all, and those that do typically run it through an extraction pass that's even less mature than the DOCX equivalent.

Convert the archive to Markdown (Pandoc local for bulk, web tool for the curated set), embed the Markdown into your RAG pipeline, and the legacy archive becomes queryable AI material. The same logic applies as in you can't feed 500 Word docs to AI: the format is the bottleneck; conversion is the fix.

Cross-format pattern

RTF is one of several legacy text-bearing formats that linger in specific industries. Similar logic applies to .doc (the legacy Word format pre-2007), .wpd (WordPerfect), .odt (OpenDocument Text), and .pages (Apple Pages source files). Pandoc reads most of them; LibreOffice handles a wider range; specialised converters exist for the most exotic cases. The conversion-to-Markdown pattern works the same way for all of them.

For users converting Word documents specifically, see how to extract text from a Word document and how to convert DOCX to HTML. For the broader case for using Markdown as the modern document format, see Word vs Markdown: which format should you use. For the PDF parallel of the same legacy-archive question, see how to extract text from PDF.

The summary

RTF is still alive in 2026 in specific industries, and converting it to modern formats is straightforward when you pick the right tool. Word for highest fidelity, LibreOffice for the free GUI option, Pandoc for power users and bulk, the mdisbetter web tool for one-offs without setup. The conversion to Markdown opens up the legacy archive for modern uses — search, AI, version control, web publishing — that the original RTF format made impossible.