Convert to reStructuredText
Turn 14 document formats into Sphinx-ready reStructuredText. Pandoc's RST writer handles directives, roles and tables — ideal for Python documentation projects.
Click to start converting
Go to Pandoc engine — reStructuredText output selected automatically
Supported input formats
| 格式 | 扩展名 | 说明 |
|---|---|---|
| Word (docx) | .docx | Headings, tables, footnotes, images, tracked changes |
| LibreOffice (odt) | .odt | Paragraph styles, master pages, embedded media |
| E-book (epub) | .epub | Chapter structure, book metadata, images |
| HTML | .html | Headings, lists, tables, links — genuine HTML reader |
| LaTeX | .tex | Math, environments, citations |
| reStructuredText | .rst | Directives, roles, tables |
| Org-mode | .org | Headlines, properties, drawers |
| CSV | .csv | Pandoc renders as GFM pipe tables |
| TSV | .tsv | Tab-separated, rendered as pipe tables |
| MediaWiki | .mediawiki | Templates, links, tables |
| DocBook | .docbook | Articles, sections, media objects |
| OPML outlines | .opml | Nested outlines → heading hierarchy |
| Jupyter notebook | .ipynb | Code cells, outputs, markdown cells |
How the conversion works
Pandoc's RST writer maps the document tree to reStructuredText conventions: heading levels become consistent underline styles, bullet lists become dashes, definition lists keep their structure, and tables are emitted in grid or simple syntax depending on their complexity.
Because the writer targets standard RST, the output drops straight into Sphinx projects — toctrees, code-block directives and notes all process without manual fixing. This is the fastest route from a Word specification to a Read the Docs page.
The conversion runs entirely in your browser via WebAssembly. Nothing is uploaded.
Common issues and how to fix them
RST is stricter than Markdown about heading underlines, but Pandoc generates them consistently — if you restructure heading levels by hand afterwards, keep the underline lengths at least as long as the title text.
Word content carries no cross-reference semantics, so roles like :ref: or :doc: are not invented for you — add them after conversion. Code blocks may need an explicit language after the code-block directive for Pygments to highlight them.
Very wide Word tables can exceed RST's readable grid width; consider splitting them or converting the section to a list-table afterwards.
Who uses this page
Python teams migrating requirement documents and design docs into Sphinx, maintainers moving wiki exports to Read the Docs, and technical writers preparing reStructuredText for projects that standardize on docutils rather than Markdown.
Convert to RST FAQ
+Is the output compatible with Sphinx?
Yes. Pandoc's RST writer produces standard reStructuredText that Sphinx processes directly — directives, roles and code blocks all work.
+Can I convert Word documents to RST?
Yes. Drop a .docx, select reStructuredText output, and get Sphinx-ready .rst files. Headings, tables and footnotes are preserved.
+Why would I want RST instead of Markdown?
RST supports directives (.. note::, .. code-block::), roles (:ref:, :doc:) and extended tables — features Markdown lacks. It's the standard for Python and scientific documentation.