Convert HTML to DOC
The .doc format is Word's binary format from before 2007, and almost nobody chooses it any more. What keeps it alive is systems that were built around it and never updated: old case management, some government upload forms, and templates nobody dares touch. This conversion exists for those, and the honest framing is compatibility rather than quality.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your HTML file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- Headings, paragraphs, lists, tables and links become Word structures
- CSS layout, columns and positioned elements are not carried
- Output opens in Word, LibreOffice and anything that reads legacy .doc
How to use HTML to DOC
- 1
Upload the HTML
A saved page, an export, or a fragment. Complete documents and body fragments are both accepted.
- 2
Structure is mapped to Word constructs
A heading becomes a heading style, a list becomes a list, a table becomes a table. That is the part that transfers reliably.
- 3
Open it before you send it
Legacy .doc is a lossy destination for anything designed in a browser. Check tables and any page that relied on CSS positioning.
How it works
The HTML is parsed and its structure is walked. Each element that has a word-processing equivalent is emitted as one: headings become heading styles, paragraphs become paragraphs, lists become numbered or bulleted lists, tables become tables, and anchors become hyperlinks. The result is written in the legacy binary .doc container.
Anything without an equivalent is unwrapped. A div exists to be styled, and styling is what does not survive, so its children are emitted directly.
Why anyone still wants .doc
Not preference. Systems. A surprising number of internal tools, upload forms and document templates were built when .doc was the only format that mattered, and were never revisited. When one of those refuses your file, the format is the blocker and this conversion is the way past it.
If nothing is forcing your hand, .docx is the better target in every respect: smaller, better supported, and less likely to be flagged by a mail filter, since the old binary format has a long history of carrying macros.
What transfers well
Documents that read as documents. An article, a policy, a set of instructions, a report with headings and lists: everything in these has a direct Word construct and comes through cleanly enough to edit afterwards.
What does not
Anything that was designed rather than written. Multi-column layouts, cards, overlapping elements and pages whose meaning depends on where things sit will flatten into one column in source order. For those, PDF is the correct destination, because it preserves what the page looked like instead of trying to translate how it was built.
Structure survives, appearance does not
Headings, paragraphs, lists, tables and links become Word's own equivalents, so the document is properly structured and can be edited normally. That is the useful part.
CSS does not come with it. Layout driven by stylesheets — columns, grids, positioning, web fonts, anything responsive — has no equivalent in a word processor page, and what arrives is the content in document order with default styling.
That is usually the right outcome. A page converted to a document is being turned into something to read and edit rather than something to look at, and carrying the web design across would produce neither.
Examples
A policy page for an old document system
Prose with headings and lists is the ideal case: everything in it has a Word equivalent. The system that refused HTML will accept this without complaint.
A marketing page built on CSS grid
The columns are gone because the layout lived in CSS and .doc has no equivalent. The text is all present, in the order it appeared in the source, which is rarely the reading order the design implied.
Frequently asked questions
Should I use .doc or .docx?
Use .docx unless something specifically demands otherwise. It is the current format, it is better supported, and it produces smaller and more reliable files. The only reason to choose .doc is a receiving system that rejects the newer format, which still happens with older internal tools and some upload forms. If you have a choice, convert to .docx instead.
Why did my page layout collapse?
Because the layout was CSS and there is no CSS in a Word document. Columns, grids, absolutely positioned elements and anything sized in viewport units have no Word equivalent, so the content is emitted in source order in a single flow. This is expected for any browser-designed page. If the appearance has to survive, convert to PDF, which records the rendered result rather than reinterpreting the structure.
Do images in the HTML come across?
Images referenced by the document are embedded where the converter can resolve them. An image that lives at an external address the converter cannot reach will not appear, which is common when a page is saved without its assets. Saving the page complete, with its images alongside it, gives a much better result than saving the HTML file alone.