Skia/PDF reads as a institutional generator — its modification rate sits at or below the corpus baseline, consistent with single-pass institutional output.
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 as Producer indicates a Chrome/Chromium-stack render — single-pass HTML-to-PDF. Low signal for tampering 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 Skia/PDF in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 54 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 (91% of files where Skia/PDF is the Producer).
Chrome (Print to PDF) sits upstream in 71% 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.
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.