Chrome 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 212 appearances across the HTPBE? corpus.
Corpus profile
Chrome’s "Save as PDF" target inside the print dialog uses Skia/PDF under the hood. Common for web-page captures and many SaaS "Download PDF" buttons that drive a hidden Chrome render.
Chrome Print to PDF appears on first-pass HTML-to-PDF renders. 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 Chrome in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 30 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions Chrome writes when acting as Producer, and the other tools that appear in the same documents.
Related profiles
Other tools that frequently share metadata with Chrome in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Chrome 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.