reStructuredText to HTML produces a standalone our document engine HTML document with generated CSS and semantic body elements from the RST structure.
From real runs
| Element | Result | What happens |
|---|---|---|
| Document title | Kept | The top underlined RST heading became both the HTML title metadata and an h1 inside the title-block header. |
| Section headings | Changed | The Changes subsection became an h1 with id changes after the document title was lifted into the header block. |
| Bullet lists | Kept | The two bullet items became normal ul/li elements and preserved the accented café text. |
| Numbered lists | Kept | The auto-numbered RST list became an ordered HTML list with concrete li elements in source order. |
| Grid tables | Changed | The RST grid table became an HTML table with colgroup widths and a compact inline width value. |
| Admonitions | Changed | The RST note directive became a div class note with a nested title block and paragraph text. |
| Links and literals | Kept | The external link became an href anchor, and the inline literal make test became a code element. |
| Document CSS | Changed | Our document engine added its default responsive CSS, including max-width, print rules, table styling, and task-list rules. |
The top underlined RST heading became both the HTML title metadata and an h1 inside the title-block header.
The Changes subsection became an h1 with id changes after the document title was lifted into the header block.
The two bullet items became normal ul/li elements and preserved the accented café text.
The auto-numbered RST list became an ordered HTML list with concrete li elements in source order.
The RST grid table became an HTML table with colgroup widths and a compact inline width value.
The RST note directive became a div class note with a nested title block and paragraph text.
The external link became an href anchor, and the inline literal make test became a code element.
Our document engine added its default responsive CSS, including max-width, print rules, table styling, and task-list rules.
We converted our reStructuredText sample (237 B) with Document engine on 2026-09-11. It took 26 ms and produced a 4 KB HTML file, 17× larger than the input. The engine raised no warnings.
Input · sample.rst · 237 B
7 non-empty lines, 32 words
Output · sample.html · 4 KB
Standalone document with 2 headings, 1 paragraph, 0 tables, 0 links, 0 images, 1 style block
First lines of the output
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>Feedback Atlas — Q3 activity trail</title>
<style>
html {
color: #1a1a1a;
background-color: #fdfdfd;
}
body {
margin: 0 auto;
max-width: 36em;
padding-left: 50px;
padding-right: 50px;
padding-top: 50px;
…pandoc
pandoc notes.rst -f rst -t html --standalone --toc -o notes.htmlPandoc CSS is generic, so apply your own stylesheet after conversion if the HTML must match a site design.
The HTTP API and the MCP server run the exact engine this page uses (Document engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=rst&to=html.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.rst" -F "from=rst" -F "to=html" \
--output output.html/convert/rst-to-md and review the Markdown.Yes. The tested title appeared in the title-block header as h1 and also populated the HTML title element.
Our document engine wrote the note as div class note with a nested title that says Note, followed by the directive body paragraph.
Yes. The grid table became a table with colgroup and th/td cells, though our document engine chose compact inline widths from the source structure.
In the tested file, the TOC contained the Changes section only. The top document title stayed outside the TOC as the title block.