RST to Word Converter - Sphinx Docs to DOCX

Convert reStructuredText RST files to Word DOCX. Perfect for Sphinx documentation, Python projects, and technical manuals.

Note: First conversion initializes Pandoc WebAssembly (~55MB download). Subsequent conversions are instant and work offline.

Drop RST file here or click to browse

Accepts .rst, .txt files

reStructuredText Input

Raw Preview

Enter RST or upload a file to see raw text preview

Standalone document with metadata

Document Metadata

Title

Author

Date

Subject

reStructuredText Syntax Quick Reference

reStructuredText	Description	Word Output
`Heading ========`	Section title	Title style
`Subsection ----------`	Subsection heading	Heading 1 style
`bold`	Strong emphasis	Bold formatting
`italic`	Emphasis	Italic formatting
``code``	Inline literal	Monospace font
`:: code block`	Literal block	Monospace paragraph
`* List item`	Bullet list	Bulleted list
`1. Item 2. Item`	Enumerated list	Numbered list
`link <url>`_	External hyperlink	Blue underlined link
`+-----+-----+ \| A \| B \|`	Grid table	Word table

DOCX file downloaded

Security: Only process files from sources you trust. All processing happens locally in your browser.

Word to Org Mode - DOCX to Emacs Format

RST to LibreOffice - Python Docs to ODT …

DOCX to ODT Converter - Word to OpenDocu…

ODF to PDF Converter - OpenDocument to P…

DocBook to Word Converter - XML Docs to …

View all Document converters →

Frequently Asked Questions

reStructuredText is a plain text markup language widely used in Python documentation, Sphinx projects, and technical writing. It's more powerful than Markdown with support for cross-references, footnotes, citations, and extensible directives for complex documentation needs.

Converting RST to Word format allows sharing Sphinx documentation with non-technical stakeholders, submitting documentation to publishers requiring Word format, creating offline documentation packages, or incorporating technical docs into business reports and proposals.

All standard RST elements: section headers with underlines (====, ----, ~~~~), bullet and enumerated lists, inline formatting (bold, italic, code), code blocks with :: notation, tables (grid and simple), hyperlinks, images, footnotes, citations, and blockquotes.

Standard Sphinx directives like code-block, note, warning, and figure are converted to Word equivalents. Custom directives and roles may not convert perfectly. For publication-ready output, review and adjust complex directives manually in Word after conversion.

Code blocks introduced with :: are converted to monospace paragraphs in Word. Syntax highlighting is not preserved, but indentation and structure remain intact. For Python documentation with many code examples, this maintains readability.

Yes. Many Python projects use RST in docstrings. Extract your docstrings to RST files, then convert to Word for documentation deliverables, API reference manuals, or training materials that require Word format.

Both grid tables and simple tables in RST convert to native Word tables with borders and proper alignment. Complex tables with merged cells or nested content may need manual adjustment in Word for optimal presentation.

Excellent for individual Sphinx RST files. For full Sphinx projects with toctrees and cross-references, consider converting files individually or using Sphinx's built-in builders first. This tool is ideal for single-file technical documents and module documentation.

RST is more powerful with better support for complex documents, citations, and extensible directives. It's the standard for Python projects using Sphinx. Markdown is simpler but less feature-rich. This converter bridges RST's technical power with Word's business compatibility.

Yes. Enable 'Standalone document' and configure metadata fields. You can set title, author, date, and subject that appear in Word's document properties panel. Essential for professional documentation deliverables and compliance requirements.

Document Metadata

reStructuredText Syntax Quick Reference

Related Tools