Skip to content

Convert HTML to DOCX

Turn an HTML file or pasted markup into a Word document you can actually edit — real headings, numbered lists, tables and pictures, styled the way the page looks in a browser.

  • Never stored
  • No queue, no waiting
  • No signup, no watermark

How it works

1

Add HTML

Drop an .html file, or paste your markup into the box.

2

Choose the page

Page size, orientation and margins for the Word document.

3

Convert and download

An editable .docx that opens in Word, Google Docs, Pages and LibreOffice.

A page pinned in place becoming a document that flows

HTML positions things; a Word document flows them. That is the central difference and the source of every surprise here. A web page can pin a sidebar to the left and a panel to the right and let them sit there regardless of length; a .docx is a stream of paragraphs that push each other down the page. So layouts built with CSS positioning, flexbox columns or grids are written as a single flowing column in reading order — not because the layout could not be measured, but because pinning boxes into a Word document produces something nobody can edit, which defeats the purpose of converting at all.

What maps cleanly is everything that was already document-shaped. Headings become Word heading styles — so the navigation pane works and a table of contents can be generated — and paragraphs, bold and italic, lists, block quotes, tables with their borders, and hyperlinks all have direct equivalents. Images are embedded so the document is self-contained. A blog post, an article or a report converts almost perfectly; a landing page does not.

Images have to be reachable at conversion time. A path pointing at your own computer cannot be read — a page in a browser has no access to your filesystem — and a web address only works if that server allows other sites to fetch the file, which many deliberately do not. The fix is to embed pictures as data URIs, or to use addresses you know are publicly fetchable. Any image that could not be included is reported rather than silently missing.

Two smaller omissions worth expecting. Web fonts are not embedded, so text is set in whatever Word has and the look shifts; and CSS background images are not carried, since Word has no equivalent concept for a paragraph background picture. Scripts never run, so a page that builds itself with JavaScript converts as whatever its markup says beforehand.

When you want something else

Pandoc is better at this than any converter that works from rendered markup: pandoc page.html -o page.docx --extract-media=. maps HTML structure onto Word styles properly, pulls the images out, and accepts a reference document so the output matches your own template — headings, fonts and spacing all in house style rather than Word's defaults. That last part is what makes it worth installing.

For a live web page rather than a file, save it first — "Save Page As → Web Page, Complete" — or fetch it with curl and convert the result, since nothing here reaches out to the network. And if what you want is a faithful copy of how the page looks rather than something editable, converting to PDF is the right tool, because a PDF can pin boxes where a Word document cannot.

Frequently asked questions

Does it keep my CSS styling?

Yes. Your browser renders the page first, so styles from stylesheets, classes and inline CSS are all resolved — fonts, sizes, colours, alignment, spacing, borders and backgrounds are written into the document as Word formatting.

Is the result really editable?

Yes. Headings use Word's heading styles (so the navigation pane and a table of contents work), lists are real numbered and bulleted lists, and tables are real Word tables with merged cells — not text boxes pinned in place.

Is my HTML stored anywhere?

No. The page is rendered and the document written here; nothing is sent anywhere and nothing is stored.

What happens to images?

Embedded images (data URIs) are always included. Images linked from the web are included when their server allows it; the result tells you how many could not be fetched. SVG and WebP images are converted so Word can display them.

Is JavaScript run?

No, never. The page is rendered from its markup and styles only, in a sandbox where scripts cannot run.

Do links still work?

Yes. Links to websites stay clickable, and links to a section of the same page become internal links to a bookmark at that heading.

Good to know: Layouts built with CSS positioning, flexbox columns or grids are written as a single flowing column, because an editable Word document flows rather than pinning boxes in place. Background images and web fonts are not embedded, and images referenced by a path on your own computer cannot be read — embed them as data URIs or use full web addresses.

Put this tool on your website

Free for any blog, class page or help article. Paste one snippet and your visitors can use it right on your page.