The argument isn’t markdown versus Word, or markdown versus PDF — markdown wins both of those on its own merits. The argument is what you send the reader. Five questions decide it, and most documents end up shipping both.
TL;DR — the direct answer in 30 seconds
Convert markdown to Word (.docx) when the recipient needs to edit, redline, or merge the document. Convert markdown to PDF when the document is final, designed, or printed. When in doubt, do both: write once in markdown, export to both formats, send PDF as the deliverable and offer Word for revision.
- Send Word when: contracts requiring redline, collaborative drafting, corporate templates with track changes, journal submission that requires .docx, internal team review.
- Send PDF when:client-facing proposals, finished reports, anything that’ll be printed, designed deliverables, long-term archival.
- Send both when:you’re not sure which they want, or the doc has both a review cycle and a final delivery moment.
The five questions that decide it
Every “Word or PDF?” choice reduces to five questions. We answer them in order; the format usually decides itself by question three.
1. Who reviews it?
If the reviewer is a lawyer, an editor, a co-author, or anyone whose job is to mark up the text, send Word. Review → Track Changes is the protocol of that profession; PDF annotation is a clumsy substitute. If the reviewer is a client, a customer, a procurement officer, or anyone whose job is to approve or reject the document as-is, send PDF. The presence of a redline workflow is the strongest signal in the decision.
2. Do they need to edit it?
Even without formal track changes, some recipients open documents to do something with them — copy text into a CMS, merge sections into a master file, change the date and resend. If editing is part of the use, send Word. If the document gets consumed and filed without modification, send PDF.
3. Is it final?
Final means: this is the version of record. No more changes before someone makes a decision based on it. Final documents belong as PDF. Drafts, working copies, and revision-cycle documents belong as Word. Sending a draft as PDF signals certainty you don’t have, and the recipient often reads it as such — “you sent me a PDF, I assumed it was done.”
4. Will it be printed?
Printed documents must be PDF. Word documents print, but they render slightly differently on every printer, every driver, every OS. PDF was invented in 1993 specifically to solve this — Adobe called it the “portable document format” for a reason. If the document might end up on paper, ship PDF.
5. Will it be archived?
Long-term archival (more than five years) belongs in PDF/A, an ISO-standardized subset of PDF that embeds all fonts and forbids external dependencies. National archives, regulated industries, and compliance systems require it. .docx archival works in practice but depends on Microsoft Word being able to read the format in twenty years — a reasonable bet, but a bet. PDF/A is the safer archive format.
Run through the five questions in order and one format usually wins by question two or three. When the answers split — “reviewers edit it, but the final goes to a client” — the answer is both: Word for the review cycle, PDF for the final delivery.
When PDF wins
PDF is the right export when the document needs to land looking designed and stay that way. Five common cases:
Client proposals and pitches
A proposal sent as .docx invites the recipient to redline it before they’ve made a decision. A proposal sent as PDF is a finished artifact — they read it, they decide, they reply. The psychological framing is different. Every consultant we’ve talked to ships proposals as PDF first and offers Word only if the client asks. mdclaudy’s Sales Proposal template is designed for this moment.
Reports and whitepapers
A research report, a market analysis, a quarterly update — these are read-once artifacts. The reader wants the cover page, the table of contents, the page numbers, the designed pull-quotes. PDF preserves all of it across every device. mdclaudy’s Research Report and Whitepaper templates target this case directly.
Résumés and portfolios
Every recruiter has seen the .docx résumé that opens in Word with the wrong fonts, indented bullets, and a layout that visibly shifts on second open. PDF kills that risk: the recruiter sees exactly what you designed, every time. The standard advice in 2026 is the same as in 2006: ship the PDF version.
Printed deliverables
Anything that might end up on paper — a thesis, a printed brochure, a board pack — has to be PDF. Print engineers won’t accept .docx because the rendering risk is too high. PDF guarantees the printer outputs what the designer sees.
Compliance archival
Regulated industries (finance, healthcare, legal, government) often require PDF/A for long-term storage. The format embeds fonts, forbids external dependencies, and is ISO-standardized. Word archival doesn’t meet the spec.
PDF is the format you send when the document is done. Word is the format you send when the document is still becoming itself.
When Word wins
Word is the right export when the document is still alive — going to be edited, redlined, merged, or restyled by the recipient. Five cases:
Contracts and legal documents
Contracts go through redline cycles. Review → Track Changes is the medium of contract negotiation, and PDF doesn’t offer an equivalent. Send the contract as .docx. If you’re the one drafting it from markdown, mdclaudy’s .docx export with the Memo or Legal-style template handles this.
Academic journal submission
Many journals require .docx submission despite Pandoc and LaTeX existing for decades. The publisher’s typesetting workflow runs on Word files. If you’re submitting a paper, send the .docx the publisher specified, even if you wrote it in markdown with KaTeX equations. The conversion is the cost of the publication channel.
Corporate template enforcement
Some teams require everything to ship inside a branded .docx template — specific fonts, header logo, footer page numbers, approved heading styles. Word is the medium. Convert your markdown to .docx with a reference template applied (Pandoc with --reference-doc, or mdclaudy with a custom template when that ships).
Collaborative drafting
Documents written by a team in real time — internal memos, cross-functional specs, shared briefs — usually live in either Word or Google Docs. If the team uses Word, send your markdown draft as .docx and let the collaboration happen there.
Internal team review
Even when the final deliverable will be PDF, the internal review round before that often happens in Word. The reviewer adds comments, edits sections, suggests rewrites. The .docx makes that natural. The final PDF gets generated after the review wraps.
The hybrid workflow — both, from one source
The honest answer to most “Word or PDF?” questions is both, at different stages. The workflow we recommend:
1. Write in markdown
The .md file is the source of truth. Keep it in your library, in git, or in a notes folder you actually back up. Every export downstream starts here.
2. Export to .docx for the review cycle
Send the reviewer a styled Word document. They mark it up, track changes, comment, return it. You read the suggestions, bring the edits back into the markdown source, ignore the Word file afterward.
3. Export to PDF for final delivery
After the review wraps, generate a fresh PDF from the updated markdown. The PDF goes to the client, the customer, the archive, the print shop. The .docx is now history.
4. Keep markdown as the master
The .md file is the version of record. If you ever need to revise — a year later, a contract amendment, a new client edit — you edit the markdown and re-export. Word and PDF are disposable; markdown is durable.
This is the entire pitch for treating markdown as a publishing source. The export is not a one-way trip. mdclaudy is designed around this loop: write once, export to .docx or PDF on demand, keep the .md as the master.
Word vs PDF — side by side
| Criterion | Word (.docx) | |
|---|---|---|
| Editing by recipient | Easy | Hard |
| Track changes | Native | Comments only |
| Rendering consistency | Varies by app | Identical everywhere |
| Font embedding | Optional | Standard |
| Print fidelity | Good | Excellent |
| Long-term archival | Acceptable | PDF/A is the standard |
| File size | Smaller | Larger (with embedded fonts) |
| Math (KaTeX/LaTeX) | Editable OOXML | Vector text |
| Screen reader support | Native if styled | Requires tagged PDF |
| Designed templates | 3 in mdclaudy | 15 in mdclaudy |
The mdclaudy take — one source, both exports
We built mdclaudy on the conviction that markdown should be the source of truth and the export should be a question, not a constraint. The same .md file can ship as a Word document for the redline cycle, and as a designed PDF for the final delivery, without retyping a sentence.
- Three .docx templates— Memo, Report, Proposal — for Word exports that don’t look like default Word.
- Fifteen PDF templates — Editorial, Manuscript, Sales Proposal, Whitepaper, Research Report, Academic Paper, Thesis, Résumé, Legal Brief, Magazine, Newspaper, Zine, Memo, Corporate, Technical Report — for PDF deliverables that look designed.
- Markdown stays markdown. Export to either format on demand; the .md file is always exportable as plain .md too. No lock-in.
If you’re currently writing in Word and sending PDFs by printing, the markdown-first loop saves you a step on both ends. And if you’re writing in markdown and fighting your export, you’re the audience we built for.
Related guides
- Markdown to Word: convert .md to .docx with templates — for the Word export path in depth.
- Markdown to PDF: the complete guide — for the PDF export path in depth.
- Convert markdown to Word: 5 methods compared — the method-by-method comparison.
- Notion PDF export looks bad? Here’s why — and the fix — the wedge case for designed PDFs.
- 15 designed PDF templates for markdown writers — the template gallery, for picking your PDF style.
Frequently asked questions
The honest final word
The question is rarely “Word or PDF?” in the abstract. The question is what stage your document is in and what the reader needs to do with it. Documents in motion — being reviewed, redlined, restyled — belong as Word. Documents at rest — final, designed, printed, archived — belong as PDF. The markdown stays the source through both.
That’s the loop we built mdclaudy around. Write once, export twice, keep the master. The export argument doesn’t have to be a choice — it can be a question of timing.