⌘ K
GFM → RTF 1 · headings · bold · italic · monospace · bullets

Export Markdown as Rich Text Format (.rtf)

Convert Markdown to a self-contained RTF document — opens in WordPad, TextEdit, classic Word, and any rich-text capable email composer.

Markdown → RTF
Input
229 B
16 lines
Output
397 B
16 lines
Status
ready
live
Ratio
1.73×
out/in
input · markdown
output · rtf source
{\rtf1\ansi\deff0{\fonttbl{\f0 Helvetica;}{\f1 Courier New;}}\fs22
{\b\fs40 Quarterly report}\par\par
\par
**Bold** and *italic* with {\f1 inline code}.\par
\par
{\b\fs32 Highlights}\par\par
\par
•\tab Shipped new feature flag\par
•\tab Cut p99 latency by 22%\par
•\tab Onboarded two contractors\par
\par
{\f1 revenue: up 14%}\par
{\f1 churn:   down 0.3pt}\par
\par
See attached spreadsheet.\par
}
Quick Start

How to export Markdown as RTF

Each line is mapped to RTF control words — headings to bold runs at scaled font sizes, emphasis to b/i groups, fences to a monospace font. Output is valid RTF 1.

  1. 01

    Paste Markdown

    From your README, report, or letter.

    Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.

    inputGFMmarkedCommonMarklive
    input · markdownmd · GFM
    # Title
    loaded · GFMGFM · ready
  2. 02

    Map structure

    Headings, emphasis, fences, and bullets become RTF control words.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    mapsoft-breaksoptionsconfiglive
    fix · optionsrtf · live
    \b\fs40
    options applied · livelive
  3. 03

    Wrap document

    Adds a font table and the rtf1/ansi header.

    The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.

    wrappreviewscoped CSSrenderstable
    out · renderedrtf · ready
    {\rtf1\ansi…}
    rendered · liverendered
  4. 04

    Open or download

    Save as .rtf and open in WordPad/Word/TextEdit.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    exportclipboard.md.htmlblob
    OK · exportedrtf · done
    shipped
    shipped · ready to shipsuccess
Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Related toolsMD → DOCXMD → HTMLMD → PDFMD → LaTeXMD → EPUBEditor
Use Cases

When to export as RTF

Legacy editors, email composers, cross-platform docs.

Legacy Word

Open Markdown drafts in older Word versions. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

WordPad

Drop content into the default Windows editor. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

Email signatures

Paste formatted text into rich-text email composers. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Print prep

Format documents before a quick print job. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Archive

Save documents in a long-stable, portable format. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Cross-platform

RTF opens on Windows, macOS, and Linux out of the box. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly
FAQ

Frequently asked questions

RTF 1 (\rtf1\ansi) with a minimal font table — Helvetica for body and Courier New for code. Most editors accept this.
Yes — characters above 0x7F are escaped as \uNNNN? sequences per the RTF spec.
Not yet — only inline formatting, headings, lists, and code. Use MD → DOCX for richer documents.
Yes — upload the .rtf to Drive and it converts to a Google Doc.
No. Conversion runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!