Skip to main content
🇪🇸 Español 🇧🇷 Português 🇩🇪 Deutsch
Image Converter Video Converter Audio Converter Document Converter
Tools Guides Formats Pricing API
Log In
RST file
rst
File format

About RST Files

reStructuredText

Released 2002 By David Goodger

RST (reStructuredText) is a lightweight markup language used in Python documentation.

Family

Documents & Text

Extension

.rst

MIME Type

text/x-rst

Can Use As

Input Output
The story

HOW RST
CAME TO BE.

2002
2008

reStructuredText was created by David Goodger in 2002 as part of the Docutils project, which aimed to provide a lightweight text markup for Python documentation. Python’s Python Enhancement Proposal (PEP) system adopted RST; Sphinx, launched in 2008 by Georg Brandl, built a rich documentation generator on top of RST that became the standard for Python project docs — Python’s own docs, NumPy, SciPy, Django, Flask, requests, most major Python projects.

RST’s syntax is denser than Markdown but more structured: cross-references work out of the box, auto-generated table of contents, admonitions (note, warning, tip), code blocks with language hinting, and a rich directive system for complex elements. For a decade Python documentation was synonymous with Sphinx-rendered RST. In recent years Markdown + MyST has eroded some of RST’s dominance even in the Python world, but RST remains the canonical format for Python PEPs and most foundational libraries.

CURIOSITIES &
TRIVIA.

01

Every Python PEP (Python Enhancement Proposal) since 2002 has been written in RST — the language's entire governance documentation.

02

Sphinx, built on RST by Georg Brandl in 2008, renders the official Python documentation at docs.python.org.

03

RST supports "directives" (`.. note::`, `.. warning::`) — a plugin system for custom rich content.

04

The `Read the Docs` hosting platform, built on Sphinx, hosts tens of thousands of open-source Python projects rendered from RST.

05

RST cross-reference targets — `:ref:\`label\``, `:doc:\`../other\`` — let long technical docs have clickable internal links without a separate URL scheme.

STRENGTHS &
LIMITATIONS.

Strengths

  • Rich directives for admonitions, code, math, and custom elements.
  • Cross-references work within and across documents.
  • Sphinx ecosystem offers best-in-class Python docs output.
  • Standardized as part of Python PEP infrastructure.
  • Plain text, version-controllable.

Limitations

  • Syntax denser than Markdown — higher learning curve.
  • Less widely adopted than Markdown outside Python world.
  • Multiple directive dialects (Sphinx, Docutils, custom) create fragmentation.
  • MyST (Markdown + Sphinx) has pulled many Python projects toward Markdown.

Typical Sizes & Weights

API reference page

5-50 KB

Sphinx project chapter

20-100 KB

Full library documentation

500 KB - 10 MB

Technical Specifications

MIME type
text/x-rst
Extension
.rst
Toolchain
Docutils, Sphinx, Read the Docs
Encoding
UTF-8
Related formats
MyST (Markdown + RST directives)

CONVERT FROM
RST

Common Use Cases

Python docs, Sphinx projects

Related Formats

Popular comparisons

Popular RST conversions

The most-requested destinations when starting from RST.

Frequently Asked Questions about RST

Frequently Asked Questions

RST (reStructuredText) is a document format used to store paginated text, with optional formatting, tables, images, hyperlinks, headers and footers. It sits in the documents & text family and is typically associated with a specific office suite or publishing pipeline that defined the format and ships the canonical reader.

Modern office suites — Microsoft Word, Google Docs, LibreOffice Writer, Apple Pages — open most RST files with reasonable fidelity. If your installed software does not support RST, convert to DOCX or PDF first using KaijuConverter; both open in virtually every reader, including free online viewers.

Upload the RST to KaijuConverter and pick DOCX, PDF, ODT, RTF, HTML, Markdown, or plain text. Our pipeline runs LibreOffice headlessly plus pandoc for text formats — the same engines behind professional document pipelines. Styles, tables, images, and hyperlinks survive the conversion intact.

Yes, to a high degree. Standard fonts, headings, lists, tables, images, hyperlinks and page structure transfer cleanly. Custom fonts substitute to the closest match if not embedded; obscure layout features unique to RST (frames, legacy macros) may flatten to static content in the target format.

We use cookies and similar technologies to personalise content and ads, and to analyse traffic. Learn more about cookies.