Hi, Sam.
As others say, it's not part of the app. In fact, despite the need, I hadn't even thought of doing it from wkhtmltopdf -- which would be the most logical.
I'm building a web app from the ground up in which the results need to be printed in high resolution. So I've built the CSS to do the crop marks (and bleed) and also to easily render everything (with a class) at about 4.5 times the normal size when I run wkhtmltopdf on it (via css, not --zoom). It's working pretty well, but can get convoluted (especially the bleed stuff, which requires some page elements to extend beyond the cropped area while some have margin to be within the cropped area). At this 4.5x size, I then run -Size A0 to get a huge PDF which inevitably has a lot of white space.
One of the issues I'm running into, though, is when I try to fill up a page exactly. My 1x size is some arbitrary pixel amount and I find that it only fills up with top left of the PDF. At about 1.4x it's more or less correct, but not exact. I assume if you plan (or achieved) adding the crop marks in a second step, you must be getting a consistent sized output. How are you doing this?
I also appreciate any other tips you have since it sounds like you're about 6 months ahead of me on this path.
Thanks,
James