DOCX to HTML writes a standalone our document engine HTML document with generated CSS and semantic body elements.
From real runs
| Element | Result | What happens |
|---|---|---|
| Document shell | Changed | Our document engine added a full HTML wrapper, viewport metadata, generator metadata, and default CSS. |
| Headings | Kept | Heading 1 and Heading 2 became h1 and h2 elements with generated id attributes. |
| Tables | Kept | Word tables became HTML tables with colgroup widths and right-aligned numeric cells where observed. |
| Footnotes | Kept | The DOCX footnote became a footnotes section with noteref and backlink roles in the HTML. |
| Images | Changed | The test PNG was referenced as media/rId21.png, so the HTML alone does not contain the image bytes. |
| Inline code | Kept | The retryAfter token became a code element rather than plain text or a styled span. |
| Block quotes | Kept | The finance note was emitted as a blockquote with a paragraph inside the generated body. |
Our document engine added a full HTML wrapper, viewport metadata, generator metadata, and default CSS.
Heading 1 and Heading 2 became h1 and h2 elements with generated id attributes.
Word tables became HTML tables with colgroup widths and right-aligned numeric cells where observed.
The DOCX footnote became a footnotes section with noteref and backlink roles in the HTML.
The test PNG was referenced as media/rId21.png, so the HTML alone does not contain the image bytes.
The retryAfter token became a code element rather than plain text or a styled span.
The finance note was emitted as a blockquote with a paragraph inside the generated body.
We converted our Word DOCX sample (11 KB) with Document engine on 2026-09-11. It took 31 ms and produced a 5 KB HTML file, 59% smaller than the input. The engine raised no warnings.
Input · sample.docx · 11 KB
Word document: 18 paragraphs, 3 headings, 1 table, 0 embedded images; fonts Consolas
Output · sample.html · 5 KB
Standalone document with 3 headings, 2 paragraphs, 1 table, 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>sample</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 input.docx -t html --standalone -o output.htmlUse --extract-media if you run pandoc yourself and need image files copied beside the HTML.
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=docx&to=html.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.docx" -F "from=docx" -F "to=html" \
--output output.htmlNo in the observed run. Our document engine referenced the image as a media path, so the HTML file must be packaged with extracted media if images matter.
Yes, when our document engine sees real footnotes. The output used a footnotes section with a backlink instead of Word's footnote field model.
The document engine writes standalone HTML for this target. Our document engine includes default CSS for tables, lists, code, block quotes, and print behavior.