CobaltPDF (Chromium edition)

CobaltPDF.WebKit's sibling library renders with Chromium instead of WebKit. It is the same fluent API — CobaltEngine, PdfDocument, every With… method — and the same license key activates both.

dotnet add package CobaltPDF

using CobaltPdf;                         // the only line that differs

var pdf = await new CobaltEngine().RenderUrlAsPdfAsync("https://example.com");

Full documentation: cobaltpdf.com/docs — including the feature articles (wait strategies, watermarks, headers/footers, encryption, cookies, custom JS, page numbering, splitting/merging) that apply to both engines.

When to choose which

Prefer WebKit (this library) when…	Prefer Chromium when…
Deploying to stock Azure Linux plans (no containers)	You need Chromium-exact rendering behaviour
Memory is the constraint (96% lower idle RSS)	Production hosting is Windows servers/containers
High-volume Linux rendering (57% faster warm renders)	Your HTML relies on bleeding-edge Chromium CSS/JS features

Both engines accept the same PdfRequest wire model, so a PDF microservice can swap engines without changing its clients.