Guide

Markdown to DOCX - when the recipient needs to edit

A free in-browser converter that emits real .docx files. Same Markdown source, same templates and themes as the PDF flow - output is a Word document instead of a PDF.

·4 min read
Open the converter

PDF or DOCX - the question is who has the next move

PDF locks the layout. The reader can comment, but cannot edit. That is right when the document is final, signed, or going on the record.

DOCX hands the editor over. Track Changes, comments, accept / reject - all of it. That is right when the document is a draft going to legal, a client redlining a contract, a recruiter dropping you into their template, or a peer review.

Both flows emit from the same Markdown and the same template choice, so writing the source does not commit you to the format. The toggle in the bottom-left of the sidebar picks the export at the moment you click.

How to convert

  1. Open the converter.
  2. Pick a template. Paste your Markdown.
  3. Pick a design and font pairing.
  4. Switch the export toggle from PDF to DOCX. Click Export DOCX.

What the DOCX preserves

  • Heading levels - H1 to H6 map to Word's native heading styles, so outline view and ToC fields work.
  • Inline formatting - bold, italic, strikethrough, inline code, links - all rendered as native character runs.
  • Tables with header rows and column alignment.
  • Lists - bulleted and numbered, including nesting.
  • Blockquotes - left border, italic body, accent colour from the design.
  • Code blocks - tinted background, mono font.
  • Cover page (when enabled) as a separate first-page section with the full layout.
  • Page numbers in the footer (when enabled).

What the DOCX does not preserve yet

Inline body images render as text placeholders - [image alt] - because browser-side image embedding for DOCX is a separate workstream. If the document leans on inline images, export to PDF instead.

The header logo is text-only in DOCX. The cover page still renders with the full layout including the logo.

How fonts map for DOCX

Each font-family pairing in the sidebar maps to a Microsoft-native equivalent for the DOCX output - Calibri, Cambria, Verdana, Tahoma, Consolas, Courier New, Garamond, Impact. That keeps the file rendering correctly on every Word install, including machines that do not have our bundled fonts.

Common questions

Does the DOCX open in Microsoft Word?

Yes. The output is a standards-compliant OOXML .docx file. Word, Apple Pages, Google Docs (after upload), LibreOffice and WPS Office all open it without conversion warnings.

Which Word styles does it use?

Headings map to Word's native Heading 1 through Heading 6 so the reader's outline view works. Body text, bold, italic, strikethrough, inline code, blockquotes, bulleted and numbered lists, tables and code blocks all map to native runs or paragraph styles.

Word converts Markdown directly now - why use this?

Word's built-in Markdown import is uneven. Tables drop alignment, code blocks lose their background, list nesting flattens. This converter gives you the same Markdown source plus a real template and theme, with output sized for what you actually send.

Does the converter upload my Markdown?

The public flow runs client-side: the Markdown stays in your browser. If you sign in, your project state syncs to our database so you can reopen it on another device - useful, but not the default.

Related