Step 1: Submit your RTF files using the button above or by pull and release.
Step 2: Click the 'Transform' button to start the transformation.
Step 3: Save your converted Markdown files.
RTF to Markdown Transformation FAQ
How do I convert RTF to clean Markdown?
+
Upload the RTF and the converter maps its structure to Markdown syntax: headings become `#` levels, bold/italic become `**`/`*`, lists become `-`/`1.`, and links become `[text](url)`. The result is portable plain-text Markdown you can drop into a README, a static-site post, a wiki, or any Markdown editor.
Will headings and lists from my RTF map to Markdown syntax?
+
Yes — heading levels in the RTF convert to the matching number of `#` characters, and bulleted / numbered / nested lists convert to `-` and `1.` markers with correct indentation. The Markdown preserves the document outline so the structure is immediately readable as plain text.
How are tables from my RTF represented in Markdown?
+
Tables convert to GitHub-Flavored Markdown pipe tables (`| col | col |` with a `---` separator row), which render correctly on GitHub, GitLab, and most static-site generators. Very wide or merged-cell tables that exceed Markdown's simple grid are simplified, since Markdown has no merged-cell syntax.
What happens to images when converting RTF to Markdown?
+
Embedded images from the RTF are extracted to a sibling folder and referenced with `` syntax in the Markdown, so the Markdown points at real image files. You can also choose to keep absolute URLs if the images are already hosted online.
Does RTF to Markdown add YAML front-matter?
+
Optionally — the converter can emit a YAML front-matter block (`---` title / author / date `---`) at the top of the Markdown from the RTF's metadata, which is exactly what Jekyll, Hugo, and other static-site generators expect. Turn it off for a clean body-only Markdown.
Will the Markdown use ATX (`#`) or Setext headings?
+
The Markdown uses ATX-style `#` headings by default — the modern, widely-supported convention that works in every Markdown flavor and scales to all six heading levels. Setext (underlined) headings only support two levels, so ATX is the safer, more portable choice.
Does RTF to Markdown preserve links and footnotes?
+
Hyperlinks become inline `[text](url)` links and, where the RTF marks real footnotes, they convert to `[^1]` reference-style footnotes that render correctly on platforms supporting the extension. Plain superscript notes are kept as inline text.
Can I convert RTF to Markdown for my GitHub README or wiki?
+
Yes — the output is GitHub-Flavored Markdown, so it renders correctly as a README, wiki page, issue, or PR description on GitHub and GitLab. Pipe tables, task lists, fenced code blocks, and `#` headings all display as intended once you paste or commit the Markdown.
Is my RTF private during conversion?
+
Yes — uploaded RTF files are processed in isolated workers and deleted within minutes. We never read, store, or share the contents. See /privacy/.
Why does my Markdown have stray HTML tags mixed in?
+
Markdown can't express every feature a rich document has (colored text, complex tables, text boxes), so the converter falls back to inline HTML for those fragments rather than dropping them — Markdown allows embedded HTML. If you want pure Markdown, simplify the formatting in the RTF first, or enable the "strip HTML fallback" option.
Does RTF to Markdown handle code blocks?
+
Yes — monospaced / pre-formatted text in the RTF becomes a fenced ```code block``` in the Markdown, preserving whitespace and, where detectable, the language hint for syntax highlighting. This is essential when converting technical documents and tutorials to Markdown.
Can I convert RTF to Markdown for a static-site generator like Hugo or Jekyll?
+
Yes — enable YAML front-matter and the Markdown comes out ready to drop into a `content/` or `_posts/` folder: title and date in the front-matter, body as clean Markdown, images in a sibling folder. The converter targets exactly the shape Hugo, Jekyll, Eleventy, and Gatsby expect.