PDFlib 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
PDFlib is a commercial cross-platform PDF generation library used both in legitimate server-side document pipelines and for programmatic PDF assembly.
PDFlib is legitimate inside enterprise pipelines. Contextual signal: producer/creator mismatch when it is the latest Producer on a document whose Creator pointed to a different institutional source.
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 PDFlib in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 14 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions PDFlib writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.7 (53% of files where PDFlib is the Producer).
PTC Arbortext sits upstream in 68% of cases — read this row as “what kinds of documents end up routed through PDFlib.”
Related profiles
Other tools that frequently share metadata with PDFlib in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the PDFlib 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
Of files have attachments inside
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.