How is the .docx file produced in the browser?

The tool builds the OOXML structure of a Word document directly in JavaScript and packages it into the .docx archive on the client side.

Are tables and code blocks preserved?

Yes. Tables render as Word tables and code blocks use a monospaced paragraph style with a light background.

Will the file open in Google Docs and LibreOffice?

Yes. The .docx output follows the standard OOXML specification, so any modern word processor can open it.

Is the document sent to a server first?

No. The .docx is assembled in your browser and downloaded directly — your content never leaves the page.

docx library · headings · lists · code · client-side build

Markdown to Word DOCX

Builds a real .docx in the browser with the docx library — headings, paragraphs, bullet lists, and fenced code blocks become Word styles.

Markdown → DOCX

Source

122 B

17 lines

Headings

H1–H3

Paragraphs

body text

Bullets / Code

3 / 1

list · pre

input · markdown

outline · 9 blocks

h1My Document

pA paragraph of body text.

h2Section

liOne

liTwo

liThree

h3Subsection

pMore prose.

codecode block

Quick Start

How to export Markdown to DOCX

The docx library builds a valid Word document from your Markdown outline — entirely client-side.

01
Write Markdown
Use # / ## / ### for headings, - for bullets, ``` for code.
Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.
mdGFMmarkedCommonMarklive
src · markdownmd · GFM
```
# Title
## Section
```
loaded · GFMGFM · ready
02
Pick filename
Defaults to document.docx. Include the .docx extension.
Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.
namesoft-breaksoptionsconfiglive
file · options.docx · live
```
document.docx
```
options applied · livelive
03
Click Download
docx library serializes paragraphs and styles, then triggers download.
The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.
buildpreviewscoped CSSrenderstable
build · renderedok · ready
```
packer → blob
```
rendered · liverendered
04
Open in Word
Heading and bullet styles are preserved. Edit further as needed.
Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.
wordclipboard.md.htmlblob
✓ · exporteddocx · done
```
✓ Saved
```
shipped · ready to shipsuccess

Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Use Cases

When to export to DOCX

Stakeholders, reviews, archives.

Non-tech reviewers

Send the doc to legal/PM in Word format. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

Tracked changes

Word's review mode is unmatched for collab edits. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

Templates

Drop into a corporate Word template post-export. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Resumes

ATS systems often parse DOCX more reliably than PDF. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Reports

Quarterly reports that need Word formatting downstream. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Compliance

Some audits require editable Word source files. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly

FAQ

Frequently asked questions

Inline bold/italic?

Currently preserved as plain text with the ** markers visible. Open the DOCX and use Find & Replace if needed.

Tables and images?

Not yet — the docx library supports them; this tool focuses on the common 90%.

Which Word versions?

DOCX (Office Open XML, .docx) opens in Word 2007+, LibreOffice, Google Docs.

Custom styles?

Default heading styles are used. Override after opening in Word.

Is anything sent to a server?

No — docx is built and served entirely in your browser.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!