DOCX vs PDF: which export format should you choose for your Markdown?

The honest answer is that DOCX and PDF solve different problems. The mistake is picking based on habit instead of based on what you're going to do with the file. Here's a working rule:choose by what happens to the document next.

What DOCX is good at

DOCX is the working format. It opens cleanly in Word, in Google Docs (drag it in and Docs converts to a Doc), in LibreOffice, in Pages. It preserves headings as headings — so outlines, the navigation pane, and table-of-contents tools all work. It is friendly to track-changes, comments and review. The text reflows when the reader resizes a window, which is what you want in a draft.

Pick DOCX when:

• The document is still being edited — by you, or by whoever you're sending it to.
• You want collaborators to leave comments or suggested edits.
• You'll re-open it in Google Docs (importing DOCX is the cleanest path into Docs — much better than pasting Markdown).
• The reader will copy chunks out of it into other documents.

What PDF is good at

PDF is the delivery format. It locks pagination, fonts and layout, so the document looks identical on every device and to every reader. It's hard to edit by accident. It's what clients, partners, regulators and "the lawyer" expect for a final, signed-off document.

Pick PDF when:

• The document is finished and you don't want anyone to "tweak" it.
• You're sending it externally — to clients, prospects, journalists, your board.
• Visual fidelity matters: a branded report, a proposal, a deliverable, a portfolio piece.
• It's going on the public web or being archived.

Common pitfalls when converting Markdown to either

Markdown converts cleanly to both formats, but only if the Markdown itself is well-formed. The most common surprises:

• Ragged tables become messy table objects. If your Markdown table has uneven column counts, the converted DOCX or PDF will silently fix it in a way you didn't ask for. Repair the table in the Markdown first.
• Unclosed code fences spill over. A stray``` turns paragraphs that follow into a single giant code block in the output.
• Smart quotes survive the conversion. Curly quotes in body text are fine, but smart quotes inside code samples will break copy-paste for any reader trying to run the code.
• Fonts get substituted in PDF. If your design system uses a font the renderer can't find, the PDF will fall back, often badly. This matters a lot for documents with Japanese, Chinese or Korean.

One source, both formats

The reason to keep your source as clean Markdown — not as a Word document or a PDF — is that you don't have to pick once. The same source can be exported to DOCXand PDF (and HTML, and Google Doc, and PNG). When someone asks for the document in a different format two weeks later, it's a two-click regeneration, not a manual conversion through three tools.

That's the workflowMarkdown Tidy is built around: paste, clean, repair, pick a design system, then export to whatever the situation calls for.

A simple rule of thumb

If you're going to look at the file again to edit it — pick DOCX. If you're going to look at the file again to read it — pick PDF. If you're not sure, pick DOCX; downgrading from DOCX to PDF later is one click, upgrading from PDF back to an editable document is a small ordeal.

Related reading:Why ChatGPT Markdown breaks in Google Docs ·Paste vs convert: getting Markdown into a real document