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

Yes. I’d shortlist these based specifically on HTML → PDF + CSS @media print support:

My recommendation: DocRaptor

If CSS print media queries are a hard requirement, DocRaptor is probably the strongest choice. It explicitly supports CSS media queries and uses print media by default; you can also select screen rendering through its API.

For example:

@media screen {
  .download-button {
    display: block;
  }
}

@media print {
  .download-button {
    display: none;
  }

  .invoice {
    font-size: 10pt;
  }
}

DocRaptor also supports sophisticated paged-media CSS such as @page, custom page sizes, page breaks, headers/footers, page numbers, and printer's marks.

If you want Chromium behavior

PDFShift is particularly attractive if you want a simple API and browser-like rendering. Its conversion API has an explicit use_print: true option to use the print stylesheet, along with CSS injection, JavaScript execution, custom page sizes, margins, etc.

Browserless is another good choice if your HTML depends heavily on modern Chrome behavior or JavaScript. Its PDF endpoint accepts either a URL or raw HTML and generates PDFs using Chrome's print engine; its documentation explicitly says the PDF operation uses the print CSS media type.

If you want to self-host

WeasyPrint is worth considering. It's open source and specifically designed around HTML/CSS-to-PDF rather than being a browser automation service. Its documentation says that, aside from documented exceptions, features applicable to print media are supported.

Bottom line:

• Best overall for sophisticated print PDFs: DocRaptor
• Best simple API: PDFShift
• Best Chrome/browser fidelity: Browserless
• Best self-hosted option: WeasyPrint

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

Here are top web results for exploring this topic:

PrinceXML·https://www.princexml.com Prince - Convert HTML to PDF with CSS Convert HTML documents to PDF. Beautiful printing with CSS. Support for JavaScript and SVG. PDFreactor·https://www.pdfreactor.com PDFreactor - Convert HTML to PDF with CSS , typeset quality PDF Convert HTML to PDF with CSS Paged Media support. Professional printing with CSS, typeset quality PDF, accessible and PDF/A compliant. Aspose·https://forum.aspose.com**HTML** to PDF Conversion with @media print query - Aspose Forums Hi Aspose,. We have your .net HTML to PDF generator running in our web application. It appears to load embedded CSS, as it should. But the client wants a PDF only design, without affecting the web app www.nutrient.io·https://www.nutrient.io/blog/top-ten-ways-to-convert-html-to-pdf/How to convert HTML to PDF : 10 best tools compared - Nutrient 3. Convert HTML to PDF using Puppeteer. Puppeteer logo — Node.js tool to convert HTML to PDF. Puppeteer(opens in a new tab) is a Node.js library from Google that controls Chrome or Chromium. It render onesimpleapi.com·https://onesimpleapi.com/best/pdf-apis Best HTML to PDF APIs in 2026 (Compared) - OneSimpleApi.com OneSimpleAPI. Us. Simple HTML to PDF API with CSS injection and form filling. OneSimpleAPI offers a straightforward HTML to PDF conversion API with unique features like CSS injection and form filling. Reddit·https://www.reddit.com Looking for a PDF generator that supports full HTML/CSS - Reddit I use this: https://pdfshift.io ... with great success. It is hosted, and has some cost to it, but very reliable and easy to work with. verdurakh. •. 4mo ago. We use Puppeteer + @ sparticuz/chromium w DocRaptor·https://docraptor.com**HTML** to PDF API - High-Quality PDF Conversion with PrinceXML Free and powerful HTML to PDF converter with CSS Paged Media support. SOC2 and HIPAA compliant with guaranteed uptime. Iron Software·https://ironsoftware.com The Definitive Guide to HTML to PDF Conversion Tools in 2026 The HTML to PDF landscape splits into five distinct tiers: browser-engine wrappers, commercial CSS engines, programmatic PDF builders, client-side converters, and cloud REST APIs. Each comes with a fu APITemplate.io·https://apitemplate.io Online HTML to PDF Converter - APITemplate.io Our HTML to PDF tool easily convert HTML content, web pages, or URLs into high-quality PDFs. Whether you need to convert HTML code snippets or full web pages, our tool ensures perfectly formatted PDF n8n Community·https://community.n8n.io Any recommendations for robust HTML to PDF conversion (handling ...Marian_Danas December 15, 2025, 7:50am 3. Hi @Michal_Liska , This is a perfect use case for the official PDF Generator API node, which is available directly in n8n. It has a dedicated action called HT

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

My recommendation: DocRaptor

For a service specifically intended for document generation, DocRaptor is probably the strongest fit. It uses the Prince PDF engine and explicitly supports @media print; its API defaults to print media rules. It also has strong support for CSS Paged Media features such as @page, page breaks, headers/footers, page numbers, footnotes, and varying page layouts.

For example:

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

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

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

DocRaptor can explicitly select the print stylesheet with:

{
  "document_type": "pdf",
  "document_content": "<html>...</html>",
  "prince_options": {
    "media": "print"
  }
}

PDFShift

PDFShift is a good choice if you want something closer to a browser-based rendering workflow. It supports modern CSS, including flexbox and grid, and lets you inject CSS and JavaScript. It also supports supplying a dedicated CSS URL for PDF conversion, which is convenient for a print.css stylesheet.

Its free tier currently includes 50 credits/month, with paid plans for higher volume.

Bottom line:

• Best print/PDF fidelity: DocRaptor
• Best modern-web/API simplicity: PDFShift
• Best if you want to self-host: Gotenberg/Chromium

If you tell me your language/framework (Node, Python, Ruby, PHP, .NET, etc.) and approximate PDFs/month, I can narrow this to the best option and show the exact API integration.

When looking for an HTML-to-PDF service that respects CSS print media queries (@media print ) and paged-media specifications (@page ), the market generally splits into two categories: Headless Browser/Chromium APIs (which simulate a browser print preview) and Dedicated Paged-Media Engines (which offer professional, textbook-grade pagination, running headers, and margin boxes).

Top cloud services and APIs categorized by their rendering approach include:

• DocRaptor — Powered by the commercial PrinceXML engine, DocRaptor is the gold standard for heavy-duty paged media. It provides native, robust support for advanced CSS print styles, @page margin boxes, complex multi-page tables, and XML/HTML-to-PDF workflows without requiring you to manage local binaries.
• PrintCSS Cloud — A dedicated API specifically tailored for PrintCSS and paged media. It lets you leverage specialized engines like WeasyPrint, PagedJS , and Vivliostyle via a REST API, granting deep control over @media print , page counters, running headers/footers, and cross-references.
• Microlink PDF — A fast, developer-friendly REST API that explicitly allows you to toggle between screen and print CSS media types (emulate=print or configuring media type parameters) using an underlying automated Chromium architecture.
• PDFShift / API2PDF / Browserless — Popular headless-browser (Chromium) cloud endpoints. Because they use standard browser engines, they automatically respect @media print blocks (handling them just like hitting Ctrl+P or Cmd+P in Google Chrome), making them ideal if your print styles rely on standard web layout adjustments and hiding screen-only elements.

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

• Do you need advanced CSS Paged Media features (like running headers, page numbers, or complex print margin boxes), or just standard @media print rules to hide/show elements and adjust fonts?
• Do you expect a high volume of documents per month?

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

My recommendation

DocRaptor is probably the strongest choice if you want a managed API. It explicitly supports CSS media queries, renders using the print media type by default, and has particularly strong support for paged-media CSS such as @page, page breaks, headers/footers, and print-specific layouts.

If you want self-hosting, Gotenberg is an excellent alternative. It uses Headless Chromium, defaults to print media, supports @media print, @page, CSS page sizing, and lets you explicitly choose emulatedMediaType=print or screen.

For example, your HTML can contain:

@media screen {
  .pdf-only {
    display: none;
  }
}

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

  .invoice {
    color: #000;
  }
}

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

If you tell me your expected volume, language/runtime (Node, Python, Java, etc.), and whether you need a hosted API or self-hosting, I can narrow this to the best 2–3 options and compare pricing, CSS support, and API ergonomics.

When looking for an HTML-to-PDF generation service that properly interprets CSS print media queries (@media print ) and the broader CSS Paged Media standards (@page , page breaks, running headers), your choices generally fall into three categories: dedicated Paged Media Engines (via API), Headless Browser APIs , or Self-Hosted tools.

Top options available for this workflow include:

• DocRaptor - Powered by the commercial Prince XML engine, DocRaptor is widely considered the gold standard for CSS paged media and print styling. It supports advanced @media print, @page rules, generated content for headers/footers, and complex multi-page layouts.
• PrintCSS Cloud - A specialized API built specifically around native print engines like WeasyPrint, Paged.js, and Vivliostyle. It allows you to explicitly choose and test against engines that treat print CSS as a first-class citizen rather than an afterthought.
• Microlink PDF API - A fast, edge-compute headless browser option that lets you explicitly toggle between screen and print CSS media types (emulate=print ) via simple REST parameters.
• Browserless - A cloud-hosted or self-hostable headless Chromium service. Because it runs actual Chrome instances, you can use standard CDP (Chrome DevTools Protocol) print commands or pass print media emulation flags directly through the API.
• Gotenberg (Self-Hosted) - If you prefer an open-source, self-hosted Docker solution, Gotenberg wraps Chromium and allows you to pass local HTML files and assets, naturally honoring standard Chrome print options and print style sheets.

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

• Are you looking for a managed cloud API or a self-hosted solution?
• Do you need support for heavy JavaScript rendering (like charts/React) prior to printing, or is it pure static HTML/CSS?

Yes. If CSS print media queries are a hard requirement, I’d focus on services that render with a real browser or a print-focused CSS engine.

Good options

My first choice: urlHTMLPDF.devturn0search4. It explicitly supports switching between CSS print and screen media types, uses pooled headless Chromium, and accepts either raw HTML or a URL.

For example, your CSS can use:

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

  .page-break {
    break-before: page;
  }

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

If you need browser-level fidelity—JavaScript, modern Flexbox/Grid, web fonts, etc.—urlPDFShotturn0search3 is another strong fit; it specifically advertises CSS3, Flexbox, Grid, media queries, print styles, and JavaScript rendering.

If your documents are more like invoices, reports, or contracts and you don't need JavaScript, WeasyPrint is particularly well suited because its layout engine is specifically focused on print standards, pagination, and CSS.

Bottom line:

• Hosted API + modern web CSS/JS: HTMLPDF.dev or PDFShot
• Hosted API + accessibility/PDF-A requirements: pdfRelay
• Maximum print-CSS control / self-hosting: WeasyPrint

When looking for an HTML-to-PDF service that supports CSS print media rules (@media print ) and pagination control, options generally fall into two categories: Headless Chromium-based APIs (which emulate a browser's print engine) and Dedicated Paged-Media Engines (which give you absolute, print-grade control via specialized CSS modules).

The top services handling these workflows vary by your exact requirements:

• 1. DocRaptor
  • Engine: PrinceXML
  • Best For: Enterprise-grade print accuracy, complex multi-page reports, books, and invoices.
  • Why it fits: It is widely considered the gold standard for CSS paged media . It natively supports @media print , advanced page breaks, running headers/footers, and margins using pure CSS without relying on a web browser hack. You can explore their capabilities directly on the DocRaptor HTML to PDF API page.
• 1. PrintCSS Cloud
  • Engine: WeasyPrint, PagedJS, and Vivliostyle
  • Best For: Direct execution of advanced CSS Paged Media standards.
  • Why it fits: Built specifically for developers leveraging print-specific CSS toolsets, allowing deep compliance with paged media modules via an accessible API. More details can be found via PrintCSS Cloud API.
• 1. PDFShift / PDFPort / API2PDF
  • Engine: Headless Chromium / Blink
  • Best For: Standard web-to-print parity (what you see when pressing "Print to PDF" in Google Chrome).
  • Why it fits: Because they spin up a real Chromium instance, they naturally honor @media print blocks, custom print stylesheets, and modern layout features like Flexbox or Grid. They are straightforward, developer-friendly REST endpoints if your print styling isn't overly complex. Check out options like the PDFCrowd HTML to PDF API for quick implementation.
• 1. Nutrient DWS (formerly PDF.sdk / PSPDFKit)
  • Engine: Custom / Browser-based hybrid
  • Best For: Secure, multi-step enterprise document pipelines and complex form filling.
  • Why it fits: Offers robust REST endpoints for HTML-to-PDF generation supporting external CSS, assets, and custom page layouts. You can review their endpoints at the Nutrient HTML-to-PDF API.

To help narrow down the best choice, tell me:

• Do you need advanced print features like running headers/footers, page numbering (X of Y) , or complex forced page breaks?
• Are you looking for a managed cloud REST API or a self-hosted Docker/library solution?

When looking for a cloud service or API that converts HTML to PDF while fully honoring CSS print media queries (@media print ) and advanced paged media, the options generally fall into two categories: Dedicated Print-Engine APIs (which offer the highest fidelity for print rules) and Headless Browser APIs (which use Chromium and let you toggle the media type emulation).

Top-tier services that explicitly support print styling include:

• • The Engine: Powered by PrinceXML, which is widely considered the gold standard for CSS Paged Media (@page, @media print , complex multi-page layouts, running headers/footers, and precise pagination).
  • Best for: Complex business reports, invoices, books, and legal documents where print fidelity and strict pagination matter more than raw speed.
  • Integration: REST API with robust support for asynchronous generation and webhooks.
• • The Engine: A commercial, high-end CSS-to-PDF engine supporting advanced CSS3, print media queries, grid/flexbox, and paged media extensions.
  • Best for: Enterprise document pipelines requiring typeset-quality output and precise compliance support (PDF/A, PDF/UA).
  • Integration: Available as a cloud API or self-hosted server component.
• • The Engine: Specifically built around dedicated print CSS rendering tools like WeasyPrint, PagedJS, and Vivliostyle.
  • Best for: Developers deeply utilizing PrintCSS standards and looking to test or deploy specialized paged-media stylesheets.
  • Integration: Accessible directly via REST or through marketplaces like RapidAPI.
• • The Engine: Chromium-based rendering.
  • Best for: Modern web features, charts, and JavaScript-heavy layouts. It features a specific page environment setting allowing you to switch explicitly between screen and print media emulation in the API request.
  • Integration: Simple REST endpoints.
• • The Engine: Headless browser with screen/print media parameter toggles.
  • Best for: Lightweight, fast, edge-cached REST conversions where you can pass a flag to target your print stylesheet instead of the default screen rules.
  • Integration: Zero-SDK REST calls.

If you can share:

• Expected volume (number of PDFs per month)
• Whether you need complex paged media features (like running headers, custom page numbers, or strict page breaks) versus a straightforward responsive layout capture

I can help you narrow down the best service and estimate costs.

If your main requirement is accurate HTML-to-PDF rendering with CSS print media queries (@media print), you should choose a service backed by a modern Chromium rendering engine. These generally provide the best compatibility with modern CSS (Flexbox, Grid, custom fonts, @page, page breaks, etc.).

Here are some strong options:

All of these advertise support for modern Chromium rendering, including CSS print features.

Features to verify

For document-heavy applications (invoices, reports, labels), it's worth confirming the service supports:

• @media print
• @page rules
• CSS page breaks (break-before, break-after, break-inside)
• Flexbox and CSS Grid
• Custom web fonts
• Background colors/images (printBackground)
• Headers and footers
• JavaScript execution before rendering

Recommendation

• Best overall: urlHTMLPDF.devturn0search1 — exposes Chromium PDF options, including switching between print and screen media, making it ideal when you rely on print-specific CSS.
• Best for advanced PDF features: urlpdfRelayturn0search3 — adds accessibility (PDF/UA), archival (PDF/A), encryption, and extensive page configuration while supporting print stylesheets.
• Best if you just need reliable rendering: urlPDFShotturn0search0 or urlPresaturn0search4 — both use Chromium and explicitly support print media queries.

If you're building a SaaS product and need high-fidelity document output, I'd recommend choosing a Chromium-based service over one that uses older rendering engines, as Chromium offers the broadest compatibility with modern HTML and CSS.