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

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

Product

  • How It Works
  • Use Cases
  • Metadata Viewer
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.44.3

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

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

Status

Algorithm v2.44.3

Tool profile

PDF Expert

PDF Expert appears on both legitimate first-generation output and downstream re-save flows — context (the other tool on the same document) is what flips the signal.

Back to all statistics
Forensic verdict

Mixed signal

Based on this tool’s share of the HTPBE? corpus.

Modification rate
50%on baseline
Corpus baseline: 49%
Corpus share
0.10%
Share of all analyzed appearances
Modification rate
50%
on baseline
Role split
75%C/25%P
Creator vs Producer share of appearances

Corpus profile

How PDF Expert shows up in HTPBE? corpus

PDF Expert is one of the PDF-handling tools surfaced in the HTPBE? corpus. PDF Expert appears predominantly as the original Creator (75% of its occurrences) — i.e. on documents that started life inside PDF Expert rather than passing through it as a downstream re-saver.

In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when PDF Expert appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.

On documents where PDF Expert acts as Creator, 33% carry modification markers; on documents where it acts as Producer, 100% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against PDF Expert or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when PDF Expert appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.

Role in the workflow

How PDF Expert 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 · 75%
As Producer · 25%P
CAs Creator
  • Share of appearances
    75%
  • Modification rate
    33%
  • Avg file size
    70 KB
PAs Producer
  • Share of appearances
    25%
  • Modification rate
    100%
  • Avg file size
    259 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.

Name fingerprints

Also goes by

Different version strings and spellings observed for PDF Expert in the wild. All are merged into the same canonical profile.

PDF Expert75.0%
PDF Expert 3.11.2 Mac25.0%

Why variants matter

The same tool publishes itself under 2 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.

Most common
PDF Expert
75.0% of appearances
Variant spread
2 distinct strings
Long-tail share: 25.0%
Observed range
16.03.2026 → 08.07.2026

Distributions

What ships alongside PDF Expert

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

PDF versions written

Most output is PDF 1.4 (100% of files where PDF Expert is the Producer).

PDF 1.4100.0%

Common Producers when PDF Expert is the Creator

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

iOS Print to PDF66.7%
macOS Print to PDF33.3%

Related profiles

Tools you’ll see next to PDF Expert

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

P50% co-occurrence
iOS Print to PDF
Corpus share1.7%
Mod rate64%
P25% co-occurrence
macOS Print to PDF
Corpus share3.4%
Mod rate64%
C25% co-occurrence
Scanner Xerox
Corpus share1.2%
Mod rate6%

Long tail

Notable observations

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

Avg pages per document
4.0
Oldest observed
16.03.2026 — 5 months ago

Secure your workflow

Create your account — check PDFs on the web or with an API key, both ready on signup.
From $15/mo. No sales call. Cancel any time.

Start Free — Close the Structural Fraud GapSee Pricing
Read API Docs →