Markdown to PDF/Word

How it works

Type or paste Markdown directly into the editor, or load a .md, .markdown or .txt file from your device, and the tool renders it live using the Marked parser. From there you can export the result two ways: a PDF, produced with jsPDF so it paginates cleanly across A4 pages, or a Word document, produced by wrapping the rendered HTML in a format Microsoft Word opens directly. Both run entirely in your browser — nothing you write is uploaded — and the preview always shows exactly what will be exported.

What Markdown is supported

The tool understands standard and GitHub-flavoured Markdown: headings, bold and italic text, ordered and unordered lists, links, images, blockquotes, inline code and fenced code blocks, and tables. The live preview reflects your formatting as you type, so you can fix a stray asterisk or a broken table before exporting. Because the export is built from the same rendered HTML, the PDF and the Word file match the preview rather than being a separate conversion.

Choosing PDF or Word

Pick PDF when you want a fixed, print-ready document that looks identical everywhere and can't be easily edited — ideal for sharing notes, a README or documentation. Pick Word when the recipient needs to keep editing the text, for example to add comments or continue writing. The Word export keeps the structure — headings, lists, tables — as editable content rather than a flattened image, and it opens with a clean base style (Calibri body text, bordered tables, monospace code).

A concrete example

Imagine you keep a project changelog as a Markdown file with a heading, a few bullet points and a small table of versions. After the last release you paste the file's contents into the editor, check the live preview to make sure the table columns line up, then click Download PDF to email a read-only snapshot to stakeholders. Later, a colleague asks for an editable copy: you load the same source and pick Download Word instead, so they can keep writing in the table without retyping anything. Both files come from the exact same text you typed, and neither ever left your computer.

Common problems and fixes

If a fenced code block or an inline range of code isn't highlighted, that's expected — code is shown in a monospace font, not syntax-coloured; the export keeps it readable rather than styled, so check your indentation instead. If your tables look collapsed in the preview, make sure every row has the same number of | separators and a header row, since GitHub-flavoured tables need that structure to render. If the exported PDF cuts a long line off the page, break very wide lines or long URL-only links into shorter lines, because the PDF follows the rendered layout. And if a page break lands in an awkward spot, accept the automatic A4 pagination rather than expecting manual control — the tool pages your content for you.

Frequently asked questions