logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • API
logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • API
HTPBE?

Structural PDF tamper detection API. Catches edits your KYC stack misses.

Product

  • How It Works
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.23.1

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · Made in Finland 🇫🇮

Status

Algorithm v2.23.1

Tool profile

Microsoft Print to PDF

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 statistics
Forensic verdict

Legitimate origin

Based on 195 appearances across the HTPBE? corpus.

Modification rate
21%-27pp below baseline
Corpus baseline: 48%
Total appearances
195
0.9% of corpus
Modification rate
21%
-27pp below baseline
Role split
0%C/100%P
Creator vs Producer share of appearances

Corpus profile

How Microsoft Print to PDF shows up in HTPBE? corpus

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).

The signal
Microsoft Print to PDF as Producer indicates a single-pass Windows render.

Role in the workflow

How Microsoft Print to PDF shows up in metadata

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.

CAs Creator · 0%
As Producer · 100%P
CAs Creator
  • Usage
    0
  • Modification rate
    0%
PAs Producer
  • Usage
    195
  • Modification rate
    21%
  • Avg file size
    704 KB

How to read this

The Creator slot typically reflects where a document started life. The Producer slot reflects whatever wrote the bytes — and is the field that gets overwritten when a PDF is opened, edited, and saved by a downstream tool.

A higher modification rate as Producer than as Creator usually means the tool is acting as a re-saver on documents that originated elsewhere. A higher rate as Creator points to fragile workflows around the original authoring app.

Distributions

What ships alongside Microsoft Print to PDF

The PDF versions Microsoft Print to PDF writes when acting as Producer, and the other tools that appear in the same documents.

PDF versions written

Most output is PDF 1.7 (100% of files where Microsoft Print to PDF is the Producer).

PDF 1.7100.0%

Common Creators when Microsoft Print to PDF is the Producer

Adobe Illustrator sits upstream in 50% of cases — read this row as “what kinds of documents end up routed through Microsoft Print to PDF.”

Adobe Illustrator50.0%
JasperReports50.0%

Related profiles

Tools you’ll see next to Microsoft Print to PDF

Other tools that frequently share metadata with Microsoft Print to PDF in the same documents. Each card links to its own forensic profile.

C1% co-occurrence
Adobe Illustrator
Appearances405
Mod rate84%
C1% co-occurrence
JasperReports
Appearances482
Mod rate14%

Long tail

Notable observations

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.

Pages parsed
350
Oldest observed
28 Mar 2024 — about 2 years ago

Secure your workflow

Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.

Start free — close the structural fraud gapSee pricing
Read API docs →