Tooling

Markdown to PDF in your browser

Every machine you sit in front of already has a Markdown-to-PDF converter installed: the browser. The infrastructure exists; the tool is the one you choose to open in it.

By Elia Kuratli

Updated June 18, 2026·2 min read

Open the converter

Browser support

Chrome / Chromium (90+) - full support.
Safari (15+) - full support including iPad Safari.
Firefox (90+) - full support.
Edge (Chromium-based) - full support.
Brave / Arc / Vivaldi - full support (all Chromium-based).
Mobile browsers - the converter works on iOS Safari and Android Chrome but the three-pane layout collapses to single-column.

What runs in the browser

The Markdown parser is `marked`, the PDF engine is `@react-pdf/renderer`, the inline preview uses `pdfjs-dist`. All bundled into the page; total weight ~3MB compressed.

First load: 1.5–3s on a fast connection. Cached subsequently - typically ~200ms to interactive on return visits.

Why a desktop app would be worse

A desktop app would mean a download, a code-signing process, an installer, an auto-updater, OS-specific bundles. For a tool that runs in milliseconds and updates weekly, that's overkill - the browser is the package manager.

The cases where a desktop app would win: large documents (the browser caps practical size around 200 pages), no internet on first run, integration with a file manager. None apply to most Markdown-to-PDF workflows.

FAQ

Does it work on a Chromebook / iPad?

Yes. Chromebooks run a full Chrome; the converter behaves the same as on any other Chrome. iPads run iPad Safari, which is a full WebKit; works.

Can I install the converter as a PWA?

Not yet. PWA-style 'add to home screen' is on the roadmap; in the meantime, bookmark the site.

Does the browser cache the conversion?

The fonts and the JavaScript bundle cache aggressively (1 year). Your document state does not - close the tab and the document is gone unless you Save Configuration to file.

← All guides