HTML to DOCX

Document title

Written into the Word file's properties. Prefilled from the page's <title>, else its first heading, else the file name.

Paste HTML on the left, or drop a .html file, to see what the Word file will contain.

Works in your browser

•No uploads to servers

Preview

What the Word file will contain: structure only, no CSS, sandboxed.

The preview of the Word file's content appears here.

Your HTML stays on your device

The HTML is read and the .docx is built in your browser. Nothing is sent to FindUtils or anywhere else, and no remote image, stylesheet or script is fetched — you can confirm it in your browser's network panel while converting.

Why Use Our HTML to DOCX Converter?

The article lives in the CMS, the newsletter lives in the email tool, the page lives on the site — and a client, a reviewer or a legal team wants a Word file. Opening HTML in Word is layout roulette, pasting through a browser drags styles along, and online converters upload the page. This page reads the HTML in the tab and writes a real .docx with Word's own structure: Heading styles for headings, bulleted and numbered lists with their nesting, tables with a header row, hyperlinks, bold, italic, underline, strikethrough and code. CSS layout is not cloned, on purpose; the result is a document someone can edit.

This converter reads HTML into a small block model — headings, paragraphs, list items with a nesting level, tables with header rows, code blocks, quotes, rules and images — with formatted runs for bold, italic, underline, strikethrough, inline code and links. It then writes that model with the docx package into an ordinary .docx: h1 to h6 become Word's Heading 1 to Heading 6 styles, ul and ol become bulleted and numbered lists with up to eight nesting levels, tables become full-width Word tables with a shaded header row, http, https and mailto links become real hyperlinks, pre becomes a shaded monospace block, blockquote an indented italic paragraph, hr a rule.

What is dropped is dropped deliberately. Scripts, styles, hidden elements and form controls are ignored. CSS is never interpreted: classes, inline styles, floats, grids and columns have no effect, because a Word file that tries to imitate a web layout is neither a good page nor a good document. Relative links and javascript links become plain text. Only images already embedded as data URLs in PNG, JPEG, GIF or BMP are placed, at their pixel size and at most 550 pixels wide; a remote image is left out and counted, because the page fetches nothing.

Everything runs in the browser. The HTML is not uploaded, and no remote resource is requested during the conversion. The preview frame is sandboxed and shows the block model itself, so what it shows is what the Word file holds.

How it compares

Opening an HTML file directly in Word works for a simple page and turns into a layout puzzle for anything with a stylesheet. Copying from a browser and pasting into Word carries fonts, colours and spacing that then have to be cleared. Online converters upload the page, and the page may be an unpublished article or a client's draft. This converter keeps the job to one paste and keeps the markup in the tab, and it is the reverse of the DOCX to HTML page, so an article can make the round trip without leaving FindUtils.

HTML to DOCX Tips

Paste the article body, not the whole site page. Navigation, sidebars and cookie banners are content to the converter and end up in the Word file.
Use real HTML lists. A paragraph that starts with a typed bullet character stays a paragraph;
Images must already be embedded as data URLs to be placed. A remote image is left out and counted, because the page never fetches anything; download it and insert it in Word afterwards.
Put the header row in , or make its cells . Either one becomes a shaded, bold header row that Word repeats across page breaks.
Do not expect columns, floats or grids. CSS is not read; the document flows top to bottom the way the HTML does, which is what an editable Word file needs.

Frequently Asked Questions

What HTML becomes what in the Word file?

h1 to h6 become Heading 1 to Heading 6; p becomes a paragraph; ul and ol become bulleted and numbered lists with their nesting; table becomes a Word table with a shaded header row; a becomes a hyperlink; b, strong, i, em, u, s, del and code become bold, italic, underline, strikethrough and monospace runs; pre becomes a shaded monospace block; blockquote an indented italic paragraph; hr a rule; br a line break.

Why does my page's layout not survive?

Because CSS is never read. Classes, inline styles, floats, grids, columns and media queries have no effect; the document flows from top to bottom in the order of the HTML. That is deliberate: the goal is an editable Word document with real headings and lists, not a picture of a web page. For a visual copy, print the page to PDF instead.

Why are some images left out?

The page never fetches anything, so an image with a remote address cannot be placed; it is left out and counted in the conversion notes. Images already embedded as data URLs in PNG, JPEG, GIF or BMP are placed at their pixel size, capped at 550 pixels wide. Other embedded formats, such as SVG and WebP, are left out and counted separately.

Can I paste a whole web page?

Yes, and when the HTML has a <body>, only the body is read. Navigation, sidebars, footers and cookie banners are content to the converter, though, and end up in the Word file, so paste the article body when you can. Scripts, styles, hidden elements and form controls are always dropped.

Which links become hyperlinks?

Links with an http, https or mailto address become real Word hyperlinks. Relative links such as /pricing/ and javascript links become plain text, because a Word file has no page to resolve them against.

Is my HTML uploaded?

No. The HTML is read and the .docx is built in your browser. Nothing is sent to FindUtils or to any other server, and no remote image, stylesheet or script is requested during the conversion. The preview frame is sandboxed and is not allowed to load anything from the network.

What is the document title for?

It is written into the Word file's properties, where Word and file managers show it. The field is prefilled from the page's <title>, else its first heading, else the file name, and you can change it before downloading.

How are nested lists handled?

A list inside a list item becomes a deeper level of the same Word list, up to eight levels. Bulleted and numbered lists keep their kind at every level, so a numbered list nested in a bulleted one stays numbered.

What happens with broken or partial HTML?

It is read best-effort: unclosed tags are closed the way a browser would close them, and a fragment without html or body tags is fine. Empty input shows a tip, not an error.

Can I go the other way, from Word to HTML?

Yes. The DOCX to HTML converter on FindUtils reads a .docx and writes clean semantic HTML for a CMS, a blog or an email editor. Together the two pages make the round trip without leaving the site. For Markdown source instead of HTML, use Markdown to Word.