Where does the conversion run. On a server or in my browser?

Entirely in your browser. Markdown is parsed in the tab, the result is rendered in the same tab or handed back as a file. There is no server path.

Pick the images your markdown references (e.g. `assets/diagram.png`) when you convert. External URLs (https://...) stay as links, we never fetch them in the background.

Does GitHub-Flavored Markdown work fully?

Tables, task lists, strikethrough, fenced code with language and autolinks: yes. Math (KaTeX), diagrams (Mermaid) and custom containers come in phase two, only if you actually ask for them.

Why does the PDF open a print dialog instead of downloading directly?

Because the print path produces real vector PDF with our fonts. Choose “Save as PDF” and you get a file that looks the same in Acrobat as on paper, without shipping a 200 KB PDF library.

How do I force a page break?

Write ` ` in your markdown. The PDF starts a new page there. Optionally, the profile picker also offers automatic page breaks before every H1 or H2.

Do internal links still work in the PDF?

Yes. Headings get auto IDs, the table of contents (at the start) and in-body anchors (`[label](#anchor)`) still point to the right place, even after printing.

Are the DOCX files good for Word, Pages and LibreOffice?

Yes. Headings are proper style references, tables generate proper table objects. Open XML is an open format; all three apps read the result.

What about YAML frontmatter in the markdown?

If your file starts with a `---` frontmatter block, it gets detected and stripped from the body. The `title` field becomes the document title; the other fields are left alone.

Can I use raw HTML in the markdown?

Yes, but the HTML export sanitises by default (` `, `on*` handlers removed). That keeps your output safe to paste into a third-party system. Power users can toggle the switch off.

Nothing. No money, no account, no email. Ads are optional and consent-gated, nothing runs until you say yes in the cookie banner.

Markdown export, PDF, Word and HTML in the browser

Three tools, one workflow

Target format	Output	Best for	Notable
Markdown to HTML	standalone .html or body fragment	CMS entry, newsletter article, static HTML for a landing page.	GFM, tables, code blocks; sanitised by default.
Markdown to PDF	PDF via browser print path (vector)	Reports, papers, client documents, four profiles, page breaks via marker.	Print dialog → “Save as PDF”. Live internal links + table of contents.
Markdown to DOCX	Word DOCX with real heading styles	Word files for collaboration, tracked changes, editorial workflow.	Headings as style refs, tables with repeating header rows, embedded images.

When to pick which

Markdown is raw and portable. Which final form you need depends on who reads it.

HTML for a CMSDrop the body fragment into WordPress, Ghost or Astro — sanitised, ready to paste.
PDF for printingLong code lines wrap softly, tables repeat their header, page breaks land where you put the marker.
DOCX for a coworkerReal Word heading styles instead of bold text. Tracked changes work, layout stays Word-native.
Print AI output fastFrom chat to tool, pick a profile, open the print dialog. Three clicks to a hand-out.
Term paper or reportThe academic profile uses Times typography, justified text and a page break before every H1.
Bring imagesLocal images referenced in your markdown? Add them here — relative paths get embedded automatically.

Pick a format

Markdown to HTMLCMS entry, newsletter article, static HTML for a landing page.Open Markdown to PDFReports, papers, client documents, four profiles, page breaks via marker.Open Markdown to DOCXWord files for collaboration, tracked changes, editorial workflow.Open

Privacy

Every conversion runs locally in your browser. No file, no markdown snippet and no image leaves your device. No account, no cookie banner, no upfront trust required.

FAQ

Where does the conversion run. On a server or in my browser?: Entirely in your browser. Markdown is parsed in the tab, the result is rendered in the same tab or handed back as a file. There is no server path.
How do images work?: Pick the images your markdown references (e.g. `assets/diagram.png`) when you convert. External URLs (https://...) stay as links, we never fetch them in the background.
Does GitHub-Flavored Markdown work fully?: Tables, task lists, strikethrough, fenced code with language and autolinks: yes. Math (KaTeX), diagrams (Mermaid) and custom containers come in phase two, only if you actually ask for them.
Why does the PDF open a print dialog instead of downloading directly?: Because the print path produces real vector PDF with our fonts. Choose “Save as PDF” and you get a file that looks the same in Acrobat as on paper, without shipping a 200 KB PDF library.
How do I force a page break?: Write `` in your markdown. The PDF starts a new page there. Optionally, the profile picker also offers automatic page breaks before every H1 or H2.
Do internal links still work in the PDF?: Yes. Headings get auto IDs, the table of contents (at the start) and in-body anchors (`[label](#anchor)`) still point to the right place, even after printing.
Are the DOCX files good for Word, Pages and LibreOffice?: Yes. Headings are proper style references, tables generate proper table objects. Open XML is an open format; all three apps read the result.
What about YAML frontmatter in the markdown?: If your file starts with a `---` frontmatter block, it gets detected and stripped from the body. The `title` field becomes the document title; the other fields are left alone.
Can I use raw HTML in the markdown?: Yes, but the HTML export sanitises by default (`<script>`, `on*` handlers removed). That keeps your output safe to paste into a third-party system. Power users can toggle the switch off.
What does it cost?: Nothing. No money, no account, no email. Ads are optional and consent-gated, nothing runs until you say yes in the cookie banner.