iOS Print to PDF 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
iOS Print to PDF is the iPhone/iPad equivalent of the macOS Print to PDF pipeline, invoked via the "Save to Files" or share-sheet PDF action.
Documents with iOS Print to PDF as Producer were generated on a mobile Apple device in one pass. Low signal in tampered corpus on its own.
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 iOS Print to PDF in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 33 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions iOS Print to PDF writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.3 (96% of files where iOS Print to PDF is the Producer).
Microsoft Word sits upstream in 74% of cases — read this row as “what kinds of documents end up routed through iOS Print to PDF.”
Related profiles
Other tools that frequently share metadata with iOS Print to PDF in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the iOS Print to PDF 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.