There are two reasons I have with wkhtmltopdf that still have me fall back to my own printing stuff I've done in 2004 in order to create PDFs for our users: *

There are two reasons I have with wkhtmltopdf that still have me fall back to my own printing stuff I've done in 2004 in order to create PDFs for our users: * WebKit's support for printing is a bit behind the times and stuff like "display: table-header-group;" isn't quite supported, so whenever you have to print big lists across multiple pages, you are practically forced to do your own page breaking. * Due to an issue somewhere between qt and webkit, it's not possible to hyphenate text. Well. It is possible, but it causes the hyphen not to be painted in most cases. Having not to deal with manual page breaks or being able to hyphenate (and thus do real justification) were the two reasons for me to move off my home-grown solution, but as those two are the things missing in wkhtmltopdf, I'm staying with my own solution. Aside of that: If you can live with these shortcomings and with the fact that you are for all intents and purposes forced into using their static build (patched qt, kerning issues for everybody trying a build with the same qt patches), then this might be the perfect solution for PDF generation. It feels great to use CSS with mm measurements and getting exactly what you need. Or creating barcodes by just embedding SVG or being able to use the full capabilities of HTML, CSS and even JS when building your page.