Markdown tools: free online Markdown converters
A small set of focused, online Markdown converters that run entirely in your
browser — for people who write in Markdown but keep having to hand their work
to systems that do not read it, and for people who receive documents in
formats they would rather edit as plain text.
If you draft in Obsidian or any plain-text editor, you know the friction: the
client wants a Word file, and the archived spec only exists as a PDF. These
tools move text between those formats while keeping the structure that makes
it worth moving.
Compare the tools
Same guarantees, opposite directions.
| | PDF to Markdown | Markdown to DOCX |
| Input | PDF file (.pdf), up to 25 MB / 500 pages | Markdown text, pasted or typed |
| Output | Markdown (.md), editable before you copy or download | Word document (.docx) with native styles |
| Processed in browser | Yes — nothing uploaded | Yes — nothing uploaded |
| Best use case | Recovering the text of a report, spec or paper when the PDF is the only copy you still have. | Handing a Markdown draft to someone who works in Word and expects to track changes. |
| Main limitation | Scanned PDFs produce nothing — there is no text layer to read, so OCR has to come first. | Images become alt-text placeholders — fetching them would mean a network request. |
Why use mdburst Markdown tools
Most online Markdown converters wrap a server-side library: you upload a
file, something happens on a machine you do not control, and a result comes
back. Fine for a blog post; unacceptable for a contract or an unpublished
draft under NDA. These run in your browser instead, which has three
consequences:
- Confidential material stays confidential — not as a
policy you must trust, but because there is no endpoint to send it to.
- They work offline once loaded — useful on a plane or a
locked-down corporate network.
- Your device does the work, which is why size limits
exist. A 500-page PDF is real computation.
They also aim at structure, not visual approximation. Anything can
put Markdown source into a Word file; producing one whose headings are real
Heading styles is the part that saves you an afternoon.
Common workflows
Three patterns account for most of how people use these together:
- Reclaiming an archived document. A spec exists only as a
PDF. Run it through the
PDF to Markdown converter and you have text you can
diff and version-control.
- Delivering to a Word-based reviewer. You write in
Markdown; your client works in Word with tracked changes.
Markdown to DOCX gives them a real document to
mark up.
- PDF to Word, via Markdown. Converting straight to Word
carries the PDF's layout quirks along. Going through Markdown strips it to
structure and text first, so you fix headings and tables while they are
still cheap to edit.
Choosing the right tool
It comes down to which end you are starting from:
-
A file someone sent you, and you want editable text →
PDF to Markdown. Check its
limitations first if the document
is scanned or multi-column — the two cases where it disappoints.
-
Your own Markdown, and someone needs a document →
Markdown to DOCX. See
supported formatting to
confirm the elements you rely on are covered.
-
Neither — the real problem is publishing one draft to several places every
week → that is what mdburst is for.
Privacy and file handling
The same handling applies to every tool here. Your file is read locally
through the browser's File API; parsing and generation happen in the page or
in a worker served from this origin; the result comes back as a local
download or as text on screen. No copy is transmitted, stored or retained,
and nothing persists once you close the tab.
The site does collect anonymous usage analytics — which tool was opened,
whether a conversion succeeded, roughly how large the input was — so we know
which converters are worth maintaining. Never your filenames or content.
Frequently asked questions
Are these Markdown tools really free?
+
Yes — no account, no email, no usage cap, and no paid tier hidden behind the useful part. They are static pages that work in your browser, so each conversion costs us nothing to run.
Do any of these tools upload my files?
+
No. Each converter reads your file with the browser's File API and processes it in the page. There is no upload endpoint, because the site is statically hosted with nothing server-side to receive one. Watch your network panel during a conversion to confirm it.
Which tool should I use to get a PDF into Word?
+
Chain them: convert the PDF to Markdown, correct whatever the layout inference got wrong while it is still plain text, then convert that Markdown to DOCX. The Markdown step is what makes fixing headings and tables cheap.
Why is the output not a perfect match for my original?
+
The formats record different things. A PDF stores glyph positions with no notion of a heading, so converting out of one means inferring structure from geometry. Both directions involve judgement calls, which is why you get an editable result rather than a claim of exactness.
Do the tools work on a phone?
+
Yes — both pages are responsive and conversion runs on the device. Large PDFs are noticeably slower on a phone, because the parsing is real work happening locally rather than on a server.