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.

🇫🇮 Made in Finland

Product

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

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.18.2

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875

Status

Algorithm v2.18.2

Tool profile

PDFium

PDFium 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 937 appearances across the HTPBE? corpus.

Modification rate
24%-24pp below baseline
Corpus baseline: 48%
Total appearances
937
4.6% of corpus
Modification rate
24%
-24pp below baseline
Role split
50%C/50%P
Creator vs Producer share of appearances

Corpus profile

How PDFium shows up in HTPBE? corpus

PDFium is the Chromium PDF engine, used for both viewing and (less commonly) emitting PDFs across the Chromium family of browsers and embedded apps.

PDFium as Producer indicates a Chromium-stack render. Low signal for tampering on its own.

The signal
PDFium as Producer indicates a Chromium-stack render.

Role in the workflow

How PDFium 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 · 50%
As Producer · 50%P
CAs Creator
  • Usage
    472
  • Modification rate
    24%
  • Avg file size
    391 KB
PAs Producer
  • Usage
    465
  • Modification rate
    23%
  • Avg file size
    403 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 PDFium

The PDF versions PDFium 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 PDFium is the Producer).

PDF 1.7100.0%

Common Producers when PDFium is the Creator

iOS Print to PDF writes 0% of these files — that pairing is the Adobe-stack default for many institutional pipelines.

iOS Print to PDF0.2%
pdf-lib0.2%

Common Creators when PDFium is the Producer

PDFium sits upstream in 99% of cases — read this row as “what kinds of documents end up routed through PDFium.”

PDFium99.4%
PDF Suite0.4%
IronPdf0.2%

Related profiles

Tools you’ll see next to PDFium

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

P0% co-occurrence
iOS Print to PDF
Appearances306
Mod rate73%
P0% co-occurrence
pdf-lib
Appearances70
Mod rate84%
C0% co-occurrence
PDF Suite
Appearances2
Mod rate100%
C0% co-occurrence
IronPdf
Appearances13
Mod rate46%

Long tail

Notable observations

Smaller cuts of the PDFium corpus — useful context, but treat each row as a single data point rather than a strong signal.

Pages parsed
2,188
Oldest observed
29 Jan 2013 — over 13 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 →