Skip to content

reStructuredText to Markdown converter

reStructuredText to Markdown rewrites RST document structure as GitHub-style Markdown while simplifying RST directives into portable text blocks.

  • Converted with Document engine · input deleted within 24 h
  • Free: 5 conversions a day · 5 MB each
  • Higher limits →

From real runs

What you get — and what changes

  • Title and sections Changed

    The underlined document title became # Release notes γ, and the next RST heading became ## Changes.

  • Inline emphasis Kept

    RST strong, emphasis, and inline literal markup became Markdown bold, italic, and backtick code spans.

  • Bullet lists Kept

    The unordered items stayed as Markdown dash bullets and preserved the UTF-8 café text.

  • Numbered lists Changed

    Auto-numbered RST items became explicit 1 and 2 ordered-list markers in the Markdown output.

  • Grid tables Changed

    The grid table was converted to a pipe table with padded cells and a separator row.

  • Admonitions Changed

    The RST note directive became a GitHub-style note callout inside a Markdown blockquote.

  • External links Kept

    The RST inline link converted to Markdown link syntax with the same https://example.com/docs target.

Sample conversions

RST release note

Input
RST file containing a title, Changes section, inline literal make test, accented bullet text, numbered list, grid table, note directive, and external link.
Output
434-byte Markdown file with # and ## headings, bold and italic spans, backtick code, dash bullets, explicit ordered-list numbers, a pipe table, note callout, and Markdown link.

Grid table migration

Input
Two-row RST grid table with Field, Status, and Note headers plus values Title/kept/ok and Warning/lost/no.
Output
The Markdown table kept the cell text and header row. RST box drawing was gone, replaced by a pipe separator line and padded cells.

A real reStructuredText → Markdown run

We converted our reStructuredText sample (237 B) with Document engine on 2026-09-11. It took 14 ms and produced a 191 B Markdown file, 19% smaller than the input. The engine raised no warnings.

Input · sample.rst · 237 B

7 non-empty lines, 32 words

Lines
7
Words
32

Output · sample.md · 191 B

2 headings, 0 tables, 2 list items, 0 code blocks, 0 image references

Headings
2
Tables
0
List items
2
Code blocks
0
Images
0
Lines
5

First lines of the output

md
# Feedback Atlas — Q3 activity trail

**Prepared for:** Board of Directors

## What went well

- Enterprise pipeline doubled after the SOC 2 report shipped.
- Support CSAT held at **94%**.

Options and when to change them

md_flavour
Use when the Markdown writer must be gfm, commonmark, or our document engine markdown for a downstream parser.

Do it yourself

pandoc

bash
pandoc notes.rst -f rst -t gfm -o notes.md

Sphinx-specific roles and directives may need manual cleanup because pandoc writes portable Markdown, not a Sphinx project.

reStructuredText to Markdown by API or MCP

The HTTP API and the MCP server run the exact engine this page uses (Document engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=rst&to=md.

curl
curl -X POST https://filetypeconverters.com/api/v1/convert \
  -H "Authorization: Bearer $FTC_API_KEY" \
  -F "file=@input.rst" -F "from=rst" -F "to=md" \
  --output output.md
API reference

When this is the wrong conversion

  • If the final target is a website page, use /convert/rst-to-html and inspect the generated semantic elements.
  • If the RST is part of a Sphinx documentation tree, build with Sphinx when custom roles, cross-references, or extensions matter.
  • If you need a fixed review copy, convert RST to PDF rather than Markdown.

reStructuredText to Markdown questions

What happens to RST admonitions in Markdown?

The tested note directive became a GitHub-style note callout inside a blockquote. That is readable on GitHub but may be plain quoted text in other Markdown renderers.

Are RST grid tables preserved as tables?

The table data survived as a pipe table. The original grid border characters and exact width hints were removed.

Does RST auto-numbering stay automatic?

No. Our document engine wrote concrete ordered-list numbers, so later inserts may require your Markdown formatter to renumber them.

Will Sphinx roles convert cleanly?

Basic RST structure converts well, but this route is not a Sphinx build. Check any custom roles or cross-reference syntax after conversion.

Related conversions