MD to RST converter
Convert Markdown to reStructuredText free online. Migrate docs to Sphinx and Python documentation workflows. No signup, instant conversion.
Drop a file to convert here
or click to browse
About reStructuredText Document
Common Use Cases
- Migrating Markdown documentation to Sphinx projects
- Converting README files for Python package docs
- Adapting content for reStructuredText-based workflows
Many Python projects and Sphinx documentation sites require reStructuredText as the source format. If you have existing content in Markdown, converting to RST lets you integrate it into a Sphinx build without rewriting from scratch. Pandoc handles the syntax mapping between the two formats.
Markdown is a widely used lightweight markup format, while reStructuredText is a more powerful markup language with built-in support for directives, roles, and cross-references that Sphinx relies on.
Why Convert Markdown to RST?
Integrate with Sphinx documentation
Sphinx is the standard documentation tool for Python projects, and it works best with reStructuredText. Converting your Markdown gives you compatible source files.
Access RST-specific features
reStructuredText supports directives, roles, admonitions, and cross-references that Markdown does not have. Converting is the first step toward using these features.
Match project conventions
If the rest of your documentation is in RST, converting Markdown files keeps the project consistent and avoids mixing formats.
Faster than manual rewriting
Headings, lists, links, code blocks, and images all map between the formats. Automated conversion handles the mechanical work, leaving you to add RST-specific enhancements.
When to use each
Keep as Markdown when...
- Your project uses a Markdown-based SSG
- Collaborators prefer Markdown simplicity
- GitHub rendering is the primary output
- Content does not need cross-references
- The toolchain already handles Markdown
Convert to RST when...
- Integrating into a Sphinx documentation project
- The Python project standard requires RST
- You need Sphinx directives and roles
- Read the Docs expects RST input
- Consistency with existing RST files
Common use cases
- Migrating Markdown documentation to Sphinx projects
- Converting README files for Python package docs
- Adapting content for reStructuredText-based workflows
How to use
- Upload your Markdown file. Drag and drop a .md file, or click to browse. Files up to 500 MB are supported.
- Convert to RST. Click Convert File. Pandoc maps Markdown headings, lists, links, code blocks, and tables to their reStructuredText equivalents.
- Download your RST file. Save the .rst file and add it to your Sphinx project. Files are deleted from our servers within 1 hour.
Frequently asked questions
- Will headings convert to RST format?
- Yes. Markdown headings are converted to RST headings with proper underline characters matching the heading level.
- Are code blocks preserved?
- Yes. Fenced code blocks are converted to RST code-block directives with language hints preserved.
- What about Markdown tables?
- Markdown pipe tables are converted to RST grid tables or simple tables depending on complexity.
- Will I need to add Sphinx directives manually?
- Yes. Sphinx-specific features like toctree, cross-references, and custom roles have no Markdown equivalent and need to be added after conversion.
- Is this free?
- Yes. Free users get a daily conversion allowance. Registered accounts get higher limits, and Premium or Lifetime members get unlimited conversions.