wkhtmltopdf appears on both legitimate first-generation output and downstream re-save flows — context (the other tool on the same document) is what flips the signal.
Back to all statisticsForensic verdictBased on this tool’s share of the HTPBE? corpus.
Corpus profile
wkhtmltopdf is an open-source HTML-to-PDF converter built on the WebKit rendering engine. It is used by many internal tools to generate reports from HTML templates.
wkhtmltopdf is genuinely the original generator for many small-business invoices and reports. The signal arises only when wkhtmltopdf is the latest Producer on a document whose Creator was an institutional source (banks, payroll providers, government forms) — that combination does not occur in legitimate first-generation output.
Role in the workflow
Every PDF carries a Creator (the application that produced the original document) and a Producer (the engine that wrote the PDF). The same tool can appear in either slot, with very different modification profiles.
Name fingerprints
Different version strings and spellings observed for wkhtmltopdf in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 6 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions wkhtmltopdf writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.6 (100% of files where wkhtmltopdf is the Producer).
Related profiles
Other tools that frequently share metadata with wkhtmltopdf in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the wkhtmltopdf corpus — useful context, but treat each row as a single data point rather than a strong signal.
Of files carry at least one digital signature
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.