Word to RST Converter - DOCX to reStructuredText

Convert Microsoft Word DOCX files to reStructuredText format. Prepare content for Sphinx documentation and Python projects.

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

Drop DOCX file here or click to browse

Convert Word documents to reStructuredText for Sphinx

File: ()

RST Output

Preview Raw RST Source

Upload a DOCX file to see reStructuredText preview

Standalone document

Common Sphinx/RST Use Cases

Use Case	Documentation System	Typical Workflow
Python Package Docs	Sphinx + ReadTheDocs	Convert Word guides, add to docs/source/, build with autodoc
API Documentation	Sphinx	Combine converted RST with autodoc/autosummary directives
Technical Manuals	Sphinx → PDF/HTML	Convert chapters to RST, organize with toctree, build LaTeX/PDF
Developer Guides	ReadTheDocs	Convert existing Word docs, add code-block directives, publish
Open Source Projects	Sphinx + GitHub Pages	Migrate README/docs from Word to RST, version control

RST Syntax Reference

Word Element	RST Output	Notes
Heading 1	`Title ======`	Double underline for document title
Heading 2	`Section -------`	Single underline for sections
Heading 3	`Subsection ~~~~~~~~~~`	Tilde underline for subsections
Bold text	`bold`	Strong emphasis
Italic text	`italic`	Light emphasis
Monospace/Code	``code``	Inline code with double backticks
Code block	`.. code-block:: python`	Directive for syntax highlighted blocks
Bullet list	`* Item`	Unordered lists
Numbered list	`#. Item`	Auto-numbered ordered lists
Hyperlink	`text <url>`_	External links
Table	`+-----+-----+`	Grid or simple table format

Common RST Directives (Add Manually Post-Conversion)

Directive	Syntax	Purpose
Note	`.. note:: Important note text`	Highlighted notes/callouts
Warning	`.. warning:: Warning text`	Warning callouts
Code Block	`.. code-block:: python def example():`	Syntax-highlighted code
Image	`.. image:: path/to/image.png :alt: Description`	Images with options
Table of Contents	`.. toctree:: :maxdepth: 2`	Document tree navigation

Copied to clipboard

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

JATS XML to Word - Journal Article to DO…

Word to Org Mode - DOCX to Emacs Format

RTF to HTML Converter - Rich Text to Web…

Org Mode to EPUB - Create Ebooks from Em…

ODP to PPTX Converter - OpenDocument to …

View all Document converters →

Frequently Asked Questions

reStructuredText is a markup language used by Sphinx documentation generator, ReadTheDocs, and Python projects. Converting Word documents to RST lets you migrate documentation to professional documentation systems with cross-references, code highlighting, and automatic API docs. RST is the standard for Python project documentation.

RST is more powerful than Markdown with support for directives (.. note::, .. code-block::), roles (:ref:, :class:), and complex cross-referencing. It's designed for technical documentation with features like footnotes, citations, tables with cell spanning, and extensible through Sphinx plugins. Markdown is simpler; RST is more structured.

Sphinx (the primary tool), ReadTheDocs, Python docutils, Pelican static site generator, Nikola, and various Python documentation tools. Sphinx converts RST to HTML, PDF, ePub, and LaTeX. Most Python open-source projects on ReadTheDocs use RST as their documentation format.

Heading styles become RST headers with underlines (====, ----, ~~~~), bold becomes **bold**, italic becomes *italic*, bullet lists become * items, and numbered lists become #. items. Code blocks use .. code-block:: directive, and tables convert to RST grid or simple table format.

Absolutely. This tool is ideal for migrating existing Word documentation to a Python package's docs/ folder. After conversion, add RST to your Sphinx project, use autodoc for API documentation, and publish to ReadTheDocs. Common workflow for open-source Python projects documenting features, guides, and tutorials.

RST directives are special blocks like .. note::, .. warning::, .. code-block:: python that provide semantic meaning. Word text boxes or highlighted paragraphs can manually become directives post-conversion. Code snippets in monospace font convert to .. code-block:: with automatic language detection where possible.

RST supports powerful cross-referencing with :ref:, :doc:, and custom roles. After conversion, you can add labels above headings (.. _label-name:) and reference them with :ref:`label-name`. This creates clickable links in HTML output and resolves to page numbers in PDF. Essential for large documentation projects.

Yes. Word paragraphs in monospace/Courier font become RST code blocks (.. code-block::). For syntax highlighting in Sphinx, specify the language: .. code-block:: python. Ideal for migrating API documentation, developer guides, and tutorials from Word to Sphinx/ReadTheDocs with proper code formatting.

Simple Word tables convert to RST simple table format using = separators. Complex tables become grid tables with +---+ borders. RST supports cell spanning and alignment. For very complex tables with heavy formatting, consider simplifying in Word first or using list-table directive manually.

Place converted .rst files in your Sphinx source directory (usually docs/source/), add them to index.rst's toctree directive, then run 'sphinx-build' or 'make html'. Update conf.py for theme, extensions, and project metadata. Sphinx will handle cross-references, table of contents, and build HTML/PDF documentation automatically.

Drop DOCX file here or click to browse

Common Sphinx/RST Use Cases

RST Syntax Reference

Common RST Directives (Add Manually Post-Conversion)

Related Tools