Qt appears on both unmodified and modified documents in our corpus. The name alone is never the verdict; each file is judged on its own structure.
Back to all statisticsForensic verdictBased on this tool’s share of the HTPBE? corpus.
Corpus profile
Qt’s PDF backend ships with the Qt application framework and is used by a wide range of desktop apps that emit PDFs. It is also used by some PDF-editing utilities.
Qt’s PDF backend appears inside a wide range of desktop applications, including some PDF editors. HTPBE? never reads a tool name in isolation.
Reading guide
Every PDF stores two software labels: the Creator, which names the application that first produced the document, and the Producer, which names the software that last wrote the file out. This page counts the files HTPBE? has analysed where Qt fills one of those labels, and shows how often those files carry modification markers, which PDF versions they use and which other tools sit next to them.
A tool name tells you where a file passed through, not whether anyone changed its content. A Creator and Producer that agree usually point to a single pass; a Producer that differs from the Creator means the file was written out again by another program, which has many ordinary explanations such as compression, merging or a print-to-PDF step.
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 Qt 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 Qt writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.4 (94% of files where Qt is the Producer).
wkhtmltopdf sits upstream in 100% of cases — read this row as “what kinds of documents end up routed through Qt.”
Related profiles
Other tools that frequently share metadata with Qt in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Qt 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
FAQ
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.