I need a PDF generation service that supports HTML-to-PDF conversion with CSS print media queries.

When looking for an HTML-to-PDF service that supports CSS print media queries (@media print ) and advanced paged media (@page ), your options generally split into two architectural categories: Dedicated Print Engines (which build PDFs directly from CSS paged media standards) and Headless Browser APIs (which use Chromium/Puppeteer under the hood).screenshotengine.com+1

Top-tier PDF generation services with robust print-media support include:

• DocRaptor : Built on the industry-leading PrinceXML engine, DocRaptor is specifically designed for paged media and complex print styling. It natively defaults to the print media type and gives you comprehensive, granular control over @media print blocks, @page rules, page numbers, running headers/footers, and multi-page layouts. Check out the details on DocRaptor Media Queries Documentation.screenshotengine.com+2
• Browserless : If you prefer a Chromium-based headless browser approach (which accurately mirrors how a modern web browser handles print stylesheets), Browserless lets you execute Puppeteer-style scripts or GraphQL commands via API. Its PDF generation endpoints explicitly emulate the print media CSS type so your @media print rules apply automatically. Explore their approach on Browserless PDF Generation with Puppeteer.docs.browserless.io+1
• Nutrient (DWS HTML-to-PDF API) : Formerly active under specialized document suites, Nutrient offers a robust REST API for converting HTML/CSS assets into professional invoices and business reports. It handles external CSS and layout printing rules seamlessly via developer-friendly API workflows. Learn more at the Nutrient HTML-to-PDF API.nutrient.io
• WeasyPrint (Open-Source / Self-Hosted Alternative) : If you are open to running a service yourself rather than using a paid cloud API, WeasyPrint is a native Python document compiler built strictly around W3C paged media specifications. It interprets CSS @page and print directives directly without relying on a bulky browser binary, though it lacks JavaScript execution. Read more about it on the Apryse HTML to PDF Comparison Blog.apryse.com

To help narrow down the best fit, could you tell me:

• Do you need JavaScript support (e.g., rendering charts or dynamic web components on load) or is it pure static HTML/CSS?
• Are you looking for a managed cloud API or a self-hosted open-source library?

Yes. If CSS print media queries are a hard requirement, I’d look for a service backed by Chromium/Puppeteer, rather than older HTML-to-PDF engines.

Good options

• pdfshift.io — Hosted API. Uses Chromium and supports HTML/CSS, custom CSS, JavaScript, headers/footers, and web fonts. It specifically supports injecting CSS, making it suitable for @media print workflows.PDFShift+1
• gotenberg.dev — Excellent if you can self-host. It's a Dockerized HTTP API built around Headless Chromium. Its HTML-to-PDF endpoint explicitly defaults to the print media type and supports @media print, @page, page breaks, and switching between print and screen media.Gotenberg+1
• Puppeteer directly — Best if you want maximum control and can run your own Node service. page.pdf() uses the CSS print media type by default, and you can explicitly switch to screen with page.emulateMediaType('screen').Puppeteer

What I would choose

For example, this should behave as expected with Gotenberg/Chromium:

@media print {
  .navigation,
  .actions {
    display: none;
  }

  .invoice {
    break-inside: avoid;
  }
}

@page {
  size: Letter;
  margin: 0.5in;
}

Gotenberg also exposes an emulatedMediaType option, so you can deliberately choose whether the conversion uses print or screen CSS.Gotenberg

If you tell me whether you want SaaS vs self-hosted, and your approximate PDF volume/month, I can narrow this down to 2–3 services and compare pricing, API ergonomics, CSS fidelity, and security.

Yes. For HTML → PDF with CSS @media print support, look for a Chromium-based service.

• Doppio — managed API using Chromium; supports CSS Paged Media, HTML, custom margins/sizes, fonts, and JavaScript.Doppio
• Cloudflare Browser Run — generates PDFs through real browser automation with Puppeteer/Playwright, giving you strong CSS/JS compatibility.Cloudflare Docs
• RenderKit — explicitly supports Chromium’s print pipeline and @media print, with HTML/URL input.RenderKit
• Self-hosted Puppeteer/Playwright — maximum control; both generate PDFs using the browser's print CSS media type.GitHub+1

For a straightforward hosted API, Doppio or RenderKit are worth evaluating first.

When you need robust HTML-to-PDF conversion heavily reliant on CSS print media queries and CSS Paged Media (such as @page rules, running headers/footers, and precise page breaks), standard headless browser wrappers (like basic Puppeteer setups) often fall short.screenshotengine.com+1

Instead, you want specialized PDF generation APIs built specifically for print-quality document rendering. Top options supporting advanced print CSS features include:ironsoftware.com+1

1. DocRaptor
   • The Engine: Powered by the industry-leading PrinceXML engine.
   • Why it fits: It is purpose-built for advanced CSS Paged Media, complex multi-page layouts, and @media print styling. It handles complex print definitions, dynamic page numbering, margin boxes, and XML/HTML data natively without hacking around standard browser limitations.
   • Best for: Enterprise invoices, financial reports, and structured multi-page documents. It also includes an unlimited testing mode.docraptor.com+2
2. PrintCSS Cloud
   • The Engine: Offers specialized rendering tools like WeasyPrint, PagedJS , and Vivliostyle via a unified REST API.
   • Why it fits: Specifically designed for the PrintCSS ecosystem. You can explicitly choose your preferred rendering engine in your API JSON request to leverage advanced features like page margin boxes, running headers/footers, and specific CSS print selectors.
   • Best for: Developers testing or utilizing modern paged-media frameworks (WeasyPrint/Paged.js) via the cloud without maintaining local binaries.printcss.net+2
3. Nutrient HTML-to-PDF API (formerly PSPDFKit)
   • The Engine: High-fidelity enterprise web-to-PDF rendering infrastructure.
   • Why it fits: Fully supports CSS print media queries, external/embedded stylesheets, custom fonts, and explicit page setups meant for production-ready documents.
   • Best for: Scalable business workflows requiring strict compliance (like SOC 2 Type 2 infrastructure).nutrient.io

To help narrow down the best choice, tell me:

• What is your expected monthly volume of PDFs?
• Do you need complex features like running headers/footers, generated page numbers, or charts , or just standard print media query styling?

Yes. If HTML → PDF with real CSS print media support is the key requirement, I’d shortlist these:

• docraptor.com — Strongest fit if you need sophisticated print/PDF CSS. It uses the Prince PDF engine, supports @media print, and has extensive CSS Paged Media support including @page, page breaks, headers/footers, and page-specific styling.DocRaptor+1
• pdfshift.io — Good API-oriented option with HTML/CSS support, JavaScript, custom CSS, and an explicit use_print option for using the print stylesheet.PDFShift+1
• browserless.io — Good choice if you want Chrome/Chromium rendering rather than a specialized publishing engine. Its PDF API accepts raw HTML or URLs and exposes Chromium-style PDF options.Browserless Docs+1

My recommendation

If your HTML contains things like:

@media print {
  .no-print { display: none; }
  .print-only { display: block; }
}

@page {
  size: A4;
  margin: 15mm;
}

I'd start with DocRaptor. Its documentation explicitly says documents render using the print media type by default, and you can explicitly select media: "print". It also has considerably deeper support for paginated-document CSS than a basic browser screenshot/PDF service.DocRaptor+1

If you tell me your language/framework (Node, Python, PHP, Java, .NET, etc.) and whether you need JavaScript execution, custom fonts, headers/footers, or high-volume generation, I can narrow this to the most appropriate service and show the API call.

If CSS print media queries are a hard requirement, I’d shortlist these:

• docraptor.com — best for print-oriented PDFs. It uses Prince, supports @media print, @page, custom page sizes, headers/footers, page numbering, and sophisticated print layout. Its API explicitly lets you select print or screen media.DocRaptor+1
• pdfshift.io — good managed API alternative. It advertises modern CSS support including CSS3, flexbox, grid, responsive design, custom CSS, and JavaScript.PDFShift
• pptr.dev — best if you can self-host. It generates PDFs through Chromium and page.pdf() uses the print CSS media type by default, so ordinary @media print { ... } rules work naturally.Puppeteer

My recommendation

For a SaaS/API service, I'd start with DocRaptor if PDF layout quality is more important than pixel-perfect browser compatibility. Its underlying Prince engine is particularly strong for traditional document generation—reports, invoices, contracts, books, etc.DocRaptor

If your HTML is essentially a web page that you want Chromium to print, choose a Puppeteer-based service instead. That gives you browser-level CSS compatibility and JavaScript behavior.

If you tell me your language/framework (Node, Python, PHP, .NET, etc.) and approximate PDFs/month, I can narrow this down to the best 2–3 options, including pricing.

When looking for a PDF generation service that handles CSS print media queries and advanced pagination (\text{@page}, page breaks, running headers/footers), options generally split into two categories: Dedicated XML/HTML-to-PDF engines (built specifically for print specifications) and Headless Browser APIs (which use Chromium's built-in print engine).

Top choices supporting robust print media and CSS styling include:

• DocRaptor : Powered by the Prince XML engine, DocRaptor is purpose-built for CSS Paged Media and print stylesheets. It natively defaults to the print media type, offering top-tier support for @media print , complex multi-page layouts, running headers/footers, and precise page numbering. You can test or sign up via the DocRaptor Website.docraptor.com+2
• Nutrient (DWS HTML-to-PDF API) : Offers a developer-friendly REST API and robust SDK workflows explicitly designed for converting HTML and CSS templates into clean invoices, reports, and statements with full external CSS and font support. Check out the details on the Nutrient HTML-to-PDF API.nutrient.io
• Doppio : A dedicated API for generating PDFs via headless Chromium that fully respects @page rules, print backgrounds, and CSS page sizing out-of-the-box (preferCSSPageSize: true ). Learn more at Doppio.doppio.sh
• PDFShift : A fast, reliable cloud API that handles modern CSS (flexbox, grid) and lets you inject custom print stylesheets or target specific print rules during conversion. You can evaluate integration details at PDFShift.pdfshift.io+1
• Self-Hosted Headless Browser (Playwright / Puppeteer) : If you prefer managing your own infrastructure rather than using a cloud API, running a headless instance of Chrome/Chromium gives you pixel-perfect rendering of standard CSS @media print blocks, though it has higher RAM overhead.apryse.com+1

To help narrow down the best fit, let me know:

• Are you rendering simple documents, or complex multi-page reports with custom page numbers and dynamic tables?
• Do you prefer a managed cloud API or a self-hosted library?