Print breaks honored
page-break-before, page-break-after, avoid-inside — all respected. The PDF paginates the way you laid the page out.
In your browser, CSS print media queries are honored, web fonts embedded, no server, no API key, no monthly tax. Free for everything that runs on your device; AI is paid in credits.
The same engine that paints the page paints the PDF. CSS, web fonts, print media queries — the page in the file matches the page on the screen.
Page size, margins, headers, footers — all controllable via CSS @page. Letter, A4, custom dimensions, all supported.
page-break-before, page-break-after, avoid-inside — all respected. The PDF paginates the way you laid the page out.
Drop a folder of .html files. Each one becomes its own PDF. Free tier has no limit.
Every "convert HTML to PDF" tutorial on the internet ends in one of three places: "npm install a headless browser", "sign up for a rendering API", or "good luck, you'll spend a Saturday on it." Morph cuts the chain. The browser is already a rendering engine, so use it. CSS, fonts, page breaks, print media queries — all respected, because the engine printing the file is the same engine that painted the page.
Those require an API key (the rendering services) or a heavy local install (a headless browser). Morph runs the renderer in your browser — no key, no install, no monthly fee.
Yes. @page rules, page-break-before/after/inside, print-only stylesheets — all honored.
Embedded into the PDF. Custom fonts render in the file the same way they render on screen.
The renderer waits for the page to settle before printing. Most JS frameworks (React, Vue, Svelte) render correctly.
Yes. Drop a folder of .html files, get a folder of PDFs. Free tier has no batch limit.
Yes. Everything that runs on your device is free with no cap. AI and server work is paid in credits, about a cent each.