Skia/PDF reads as a institutional generator — its modification rate in our corpus does not sit meaningfully above the baseline. 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
Skia/PDF is the Google Skia graphics library’s PDF backend, used by Chrome, ChromeOS print, Android Print Framework, and several embedded Google products.
Skia/PDF marks a render from the Chrome and Chromium family, usually HTML turned into PDF. Its name is one input among many in HTPBE?’s analysis.
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 Skia/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 Skia/PDF in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 69 different metadata strings – version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions Skia/PDF writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.4 (89% of files where Skia/PDF is the Producer).
Chrome (Print to PDF) sits upstream in 65% of cases — read this row as “what kinds of documents end up routed through Skia/PDF.”
Related profiles
Other tools that frequently share metadata with Skia/PDF in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Skia/PDF 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
FAQ
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.