The measurements

17 documents beside Chrome's own PDFs measured 2026-11-07

Documents of the kind people print, each compared with Chrome 156's PDF of it: the number of pages, every element's box (within half a pixel), every line of text, and the PDF's text. A score of 100% prints as Chrome prints.

• An invoice100%
• A bank statement100%
• A letter100%
• A newsletter100%
• A Bootstrap invoice100%
• A Tailwind dashboard100%
• A React app (Northwind)100%
• A Chart.js report100%
• Tables100%
• Flexbox100%
• Grid100%
• SVG and pictures100%
• Paged media: headers, footers, page numbers100%
• Inline text100%
• CSS 2.1 blocks100%
• Backgrounds and borders100%
• International text: Arabic, Hebrew, Thai, Hindi, Chinese, Japanese, emoji100%

The web's own tests, area by area measured 2026-11-07

The Web Platform Tests are what browsers are checked against. In each area: Weblitz passes X of the Y rendering tests that Chrome 156 passes when it prints.

Complete in every area. In each of the 54 areas below, Weblitz passes every rendering test Chrome 156 passes when it prints. The 622 tests a printed page cannot have are left out, each listed with its reason.

* Some of these tests Chrome 156 passes only with its experimental web platform features on. Weblitz passes them the same way: with ExperimentalWebFeatures on (off by default, like a stable Chrome). Without it, Weblitz renders these features as stable Chrome does.

How we count: every rendering test of these suites that Chrome 156 passes when it prints, its experimental features on. A feature Weblitz does not support yet counts as failed, never as left out. Left out: only what a printed page cannot have (view transitions, media playback, permission prompts, scrolling and scroll-driven animations, editing, selection, validation bubbles, windows and navigation), and the few tests Chrome itself fails on our machine when run again. The list of every test left out, with its reason. Script tests are not in this table: in their areas too, every subtest that applies agrees with Chrome's, measured the same day.

Beside other HTML to PDF libraries scores measured 2026-11-04 times and sizes 2026-11-07

The same 17 documents, the same fonts for every library, each scored against Chrome 156's PDF (headless Chrome, driven by Puppeteer): 100% prints as Chrome prints. "Exact" counts only what did not move at all. Each library ran in the licence mode shown, on an Apple M4 Pro laptop with .NET 10; the evaluation modes' marks were left out of the scores.

Timed 2026-11-07 on the same Mac, every library warm (started first, then a warm-up), in its trial or evaluation mode, Weblitz unlicensed too: "A one-page PDF" is the median time per document over 200 one-page letters, one after another on one thread; "The 17 documents" the median time for the bench's documents, one after another. Engine size: what the library puts on a Linux x64 server, measured 2026-11-07: what dotnet publish -r linux-x64 adds to an application, plus the browser it downloads (Puppeteer: Chrome; Playwright: Chrome and Chrome's headless shell) or the program it installs (Prince). Weblitz's size includes its fonts, V8 and the parts of SSRS2's engine it prints with. Aspose.HTML's evaluation mode converts the first 4 pages of a document: its score and its time count those pages; on Linux it also needs libgdiplus. iText pdfHTML runs no JavaScript. Prince, Aspose.HTML and iText printed fewer pages or less text than Chrome on 2, 5 and 6 of the documents. Syncfusion's package for Macs carries an Intel Chromium, which ran translated by Rosetta 2.

Where each runs, and what it costs read 2026-11-07

What each vendor's own pages say, read 2026-11-07: each cell links the page it comes from. List prices in US dollars, excluding tax; a licence sold once includes a year of updates. On Alpine, Weblitz needs the gcompat package (Platforms).

Azure App Service on Windows measured 2026-11-06

Weblitz ran inside App Service's Windows sandbox (a B1 plan): the 17 bench documents and a Chart.js page printed there score what they score on our Mac, page for page. Nothing to install on the plan, and no browser process for the sandbox to refuse. Some Chromium-based libraries now say they run there too, from a Basic plan (where each runs).