mPDF reads as a downstream re-saver — it surfaces disproportionately on documents whose original Creator was a different, often institutional, application.
Back to all statisticsForensic verdictBased on this tool’s share of the HTPBE? corpus.
Corpus profile
mPDF is a PHP library for converting HTML/CSS to PDF, common in PHP-stack invoice generation.
Often the original generator. Contextual signal: producer/creator mismatch on institutional-Creator documents.
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 mPDF in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 9 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions mPDF writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.4 (97% of files where mPDF is the Producer).
Adobe Illustrator sits upstream in 97% of cases — read this row as “what kinds of documents end up routed through mPDF.”
Related profiles
Other tools that frequently share metadata with mPDF in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the mPDF corpus — useful context, but treat each row as a single data point rather than a strong signal.
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.