iOS Print to PDF 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
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.
iOS Print to PDF appears on documents saved from iPhones and iPads through the share sheet. As with every tool on these pages, HTPBE? judges the document, not the software.
Producer string
Quartz PDFContext is the PDF writer named in the Producer field of files saved or printed to PDF on iPhones, iPads and Macs. The field also records the system version and build, for example iOS Version 26.1 (Build 23B85) Quartz PDFContext. The HTPBE? corpus contains 508 files that list iOS Print to PDF.
The Quartz string alone does not show that a file was edited. It says which system wrote the file. Anything added after it, such as the name of another program, is a separate signal, and HTPBE? reads the whole file, including its structure, its dates and how Creator and Producer fit together, before reaching a verdict.
The same writer appears on the other Apple platforms: macOS Print to PDF statistics.
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 iOS Print to PDF 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 iOS Print to PDF in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 58 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 (94% of files where iOS Print to PDF is the Producer).
Microsoft Word sits upstream in 59% 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.
Of files contain JavaScript code
Of files carry at least one digital signature
Of files have attachments inside
FAQ
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.