What is the difference between PrintCSS Cloud and other HTML to PDF APIs?

Other HTML to PDF APIs usually use a headless Chromium (Puppeteer) with minimal CSS Paged Media support. Some of them support the @page rule and nothing else. We support most of the features defined in CSS Paged Media.

Running Headers and Footers

This feature is supported by two of the three rendering tools, WeasyPrint and PagedJS. Have a look at a sample document on printcss.live.

Counters and Cross References

CSS counters and the target-counters property can be used with WeasyPrint and Vivliostyle; again, there is a sample document on printcss.live.

Page Margin Boxes

16 Page Margin Boxes are waiting for your content in all three rendering tools, have a look on printcss.live to see how this is working.

Footnotes

Does your PDF need footnotes? Then it would be best if you rendered with Vivliostyle; this renderer offers basic footnote support. See a sample on the PrintCSS Playground.

Page Selectors and Page Breaks

Best support for page selectors like @page:blank you get with WeasyPrint, but no worries, the other tools support the basics too! See it in action on the PrintCSS Playground.

JavaScript Support

PagedJS and Vivliostyle both handle JavaScript just like your browser would do. Why? Because they also use a headless Chromium in the background but have a layer on top to support the modern CSS Paged Media features.