Over the past few months, I noticed a small but recurring annoyance in my workflow.
Most of my writing starts in Markdown — specs, notes, drafts, even internal docs. It’s fast, readable, version-friendly.
But at some point, someone inevitably asks for a Word file. Not a PDF. Not Markdown. A .docx.
I tried the usual options:
Copy-paste into Word (formatting breaks)
Pandoc locally (great tool, but not always installed where I’m working)
Online converters (many are cluttered, gated, or inject weird styles)
What I really wanted was something boring and predictable:
paste Markdown → get a clean Word document → done.
So I built a small web tool for myself that does exactly that. No login, no uploads saved, no “AI rewrite”, just a straightforward Markdown-to-Word conversion that preserves headings, lists, code blocks, tables, etc.
Not trying to turn this into a startup — just scratching a personal itch and sharing it in case others here deal with the same Markdown ↔ Word friction.
Happy to hear how others handle this, or what edge cases usually break your docs.
Most of my writing starts in Markdown — specs, notes, drafts, even internal docs. It’s fast, readable, version-friendly. But at some point, someone inevitably asks for a Word file. Not a PDF. Not Markdown. A .docx.
I tried the usual options:
Copy-paste into Word (formatting breaks)
Pandoc locally (great tool, but not always installed where I’m working)
Online converters (many are cluttered, gated, or inject weird styles)
What I really wanted was something boring and predictable: paste Markdown → get a clean Word document → done.
So I built a small web tool for myself that does exactly that. No login, no uploads saved, no “AI rewrite”, just a straightforward Markdown-to-Word conversion that preserves headings, lists, code blocks, tables, etc.
I’ve been using it daily, and a few colleagues asked for the link, so I put it online: https://www.markdown-to-word.online
Not trying to turn this into a startup — just scratching a personal itch and sharing it in case others here deal with the same Markdown ↔ Word friction. Happy to hear how others handle this, or what edge cases usually break your docs.
reply