Is this a real .docx file, or HTML renamed to .docx?

A real .docx file, built with the `docx` library's Open XML document model (headings, paragraphs, and runs assembled into an actual Word package), not an HTML file with a `.docx` extension slapped on. It opens correctly in Microsoft Word, Google Docs, and LibreOffice Writer.

Are tables and images supported?

Not in this version. Tables and images have no mapping to a Word structure here and pass through as their raw Markdown/HTML text instead of being rendered, since silently dropping them would be worse than being visible about the gap. See the tool's limitations for the full list of what isn't converted.

How are ordered (numbered) lists handled?

As plain paragraphs manually prefixed with their number ("1. ", "2. ", and so on), rather than Word's native auto-numbering field. This keeps the converter simple and avoids a class of renumbering bugs that come with wiring up Word's numbering definitions, at the cost of the numbers not auto-renumbering if you edit the list afterward in Word. Unordered lists do use Word's native bullet formatting.

Markdown to Word Converter - Download a Real .docx File

Overview

Introduction

Markdown is great to write in, but plenty of downstream readers, reviewers, clients, forms, still expect a Word document. Getting there usually means opening a desktop word processor and reformatting everything by hand, or routing the file through a server-side conversion service.

This does the conversion directly in your browser: Markdown in, a real, structured .docx file out, with no upload step.

What Is Markdown to Word (DOCX) Converter?

A Markdown-to-DOCX converter that parses Markdown into a token tree and maps each block and inline construct to the closest Word equivalent: headings to Word heading styles, emphasis to bold/italic/strikethrough runs, lists to bulleted or numbered paragraphs, and code to monospaced text.

It targets a well-defined, honestly-scoped subset of Markdown (see limitations) rather than attempting a lossless conversion of every possible construct, since some Markdown features, tables and images especially, don't have a clean one-to-one Word mapping worth guessing at.

How Markdown to Word (DOCX) Converter Works

Your Markdown is parsed with `marked`'s lexer into a token tree, the same tree-based approach (not line-by-line regex) the rest of this category's converters use, so nested formatting like `**bold with *italic* inside**` is handled correctly.

Each block token becomes one or more `docx` `Paragraph` objects: headings map to Word's `HEADING_1` through `HEADING_6` styles, list items become bulleted (or manually numbered) paragraphs, and inline tokens (bold, italic, strikethrough, inline code) become styled `TextRun`s within each paragraph.

The resulting `docx.Document` is packaged into real .docx bytes with `docx`'s `Packer.toBlob()`, entirely in your browser, and downloaded directly; nothing is ever uploaded to a server.

When To Use Markdown to Word (DOCX) Converter

Use it when a Markdown README, report, or set of notes needs to become a Word document for a reviewer, client, or system that specifically expects .docx.

It's also useful for getting a reasonable, editable Word starting point from Markdown notes, rather than manually reformatting everything from scratch in Word.

Often used alongside Markdown to HTML Converter, Markdown to PDF Converter and Markdown Formatter & Pretty Printer.

Features

Advantages

Produces a real, structured .docx file (proper heading styles, bold/italic runs, bulleted lists), not HTML with a renamed extension.
Runs entirely client-side; your Markdown source is never uploaded to a server to generate the file.
Handles nested inline formatting correctly (e.g. bold text containing italic text) via a real token tree, not regex substitution.

Limitations

Tables and images aren't converted to Word tables or embedded images; they pass through as their raw source text instead of being silently dropped or mangled.
Ordered lists are rendered as plain paragraphs with a manually written number prefix, not Word's native auto-numbering field, so renumbering after editing in Word won't happen automatically.
Links keep their visible text but aren't turned into clickable Word hyperlinks; the URL itself isn't included in the output.
Deeply nested blockquotes-within-lists or lists-within-blockquotes fall back to a simplified, flatter structure rather than exactly mirroring the source nesting.

Examples

Headings, emphasis, and a list

Input

# Report

Some **bold** and *italic* text.

- Point one
- Point two

Output

A .docx file with a Heading 1 styled "Report" paragraph, a paragraph with bold and italic runs, and two bulleted paragraphs.

Each block token becomes one Word paragraph, with inline emphasis preserved as bold/italic runs inside it.

Best Practices & Notes

Best Practices

Check the paragraph count summary before downloading, an unexpectedly low count often means the Markdown didn't parse the way you expected.
Avoid relying on tables or embedded images in the source if the .docx needs to be complete on its own; add them manually in Word afterward instead.
Keep list nesting shallow (one or two levels) for the most predictable results, since very deep nesting simplifies during conversion.

Developer Notes

Token-to-DOCX mapping covers: `heading` -> `HeadingLevel.HEADING_1..6`; `paragraph` -> a plain `Paragraph`; `strong`/`em`/`del`/`codespan` inline tokens -> `TextRun`s with `bold`/`italics`/`strike`/monospace `font`, recursively, so nesting composes correctly; `list` -> one `Paragraph` per item using `docx`'s built-in `bullet: { level }` for unordered lists and a manual `"N. "` text prefix for ordered ones (no custom numbering definition is registered); `blockquote` -> its inner paragraphs re-emitted with additional left `indent`; `code` -> one monospaced `Paragraph` per source line. Tables, images, and raw inline HTML fall back to their raw Markdown/HTML text in a plain paragraph rather than being dropped, since a visible imperfect result is more useful than a silent gap.

Markdown to Word (DOCX) Converter Use Cases

Converting a Markdown report or README into a Word document for a client or reviewer
Producing an editable .docx starting point from Markdown meeting notes
Generating Word documents from Markdown content in a documentation pipeline without a server-side conversion step

Common Mistakes

Expecting Markdown tables or images to appear as real Word tables or embedded pictures; they currently pass through as raw text instead.
Assuming ordered lists will auto-renumber in Word after edits, since they're written as literal numbered text, not a numbering field.

Tips

If you need real Word tables or embedded images, add them manually after opening the downloaded .docx rather than relying on the Markdown source.
Use unordered (`-`/`*`) lists over ordered ones if you plan to reorder items after the fact in Word, since bullets don't have a renumbering problem.

Markdown to Word (DOCX) Converter