Microsoft Print to 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
Microsoft Print to PDF is the system PDF printer built into Windows 10+. It is what you get when you "Print" any application to PDF on Windows without a third-party driver installed.
Microsoft Print to PDF as Producer indicates a single-pass Windows render. Low signal for tampering on its own — relevance is contextual (e.g. when the original Creator is an institutional bank/SaaS tool that does not normally route through Windows print).
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.
Distributions
The PDF versions Microsoft Print to PDF writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.7 (100% of files where Microsoft Print to PDF is the Producer).
JasperReports sits upstream in 50% of cases — read this row as “what kinds of documents end up routed through Microsoft Print to PDF.”
Related profiles
Other tools that frequently share metadata with Microsoft Print to PDF in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Microsoft 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.