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
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.37.1

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

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

Status

Algorithm v2.37.1

Tool profile

iLovePDF

iLovePDF reads as a downstream re-saver — it surfaces disproportionately on documents whose original Creator was a different, often institutional, application.

Back to all statistics
Forensic verdict

Anomaly profile

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

Modification rate
89%+41pp above baseline
Corpus baseline: 48%
Corpus share
2.7%
Share of all analyzed appearances
Modification rate
89%
+41pp above baseline
Role split
0%C/100%P
Creator vs Producer share of appearances

Corpus profile

How iLovePDF shows up in HTPBE? corpus

iLovePDF is a popular online PDF editor and toolkit (merge, split, edit, fill, sign). It is consumer-facing and operates by re-saving an uploaded PDF after the requested operation.

iLovePDF as Producer means the document was uploaded, processed, and re-emitted by the iLovePDF service. When iLovePDF is the latest Producer on a document whose original Creator was an institutional source (a bank statement, a payslip, a utility bill), the producer/creator mismatch is a marker we surface — alongside whatever incremental-update or signature-removal evidence the file carries.

The signal
iLovePDF as Producer means the document was uploaded, processed, and re-emitted by the iLovePDF service.

Role in the workflow

How iLovePDF 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
  • Share of appearances
    0%
  • Modification rate
    0%
PAs Producer
  • Share of appearances
    100%
  • Modification rate
    89%
  • Avg file size
    902 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 iLovePDF in the wild. All are merged into the same canonical profile.

iLovePDF92.6%
www.ilovepdf.com7.4%

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
iLovePDF
92.6% of appearances
Variant spread
2 distinct strings
Long-tail share: 7.4%
Observed range
28.04.2021 → 04.07.2026

Distributions

What ships alongside iLovePDF

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

PDF versions written

Most output is PDF 1.7 (70% of files where iLovePDF is the Producer).

PDF 1.769.9%
PDF 1.622.6%
PDF 1.55.1%
PDF 1.42.1%
PDF 1.30.4%

Common Creators when iLovePDF is the Producer

Microsoft Word sits upstream in 81% of cases — read this row as “what kinds of documents end up routed through iLovePDF.”

Microsoft Word80.8%
EXCEL.EXE5.8%
CorelDRAW3.8%
Adobe Photoshop3.8%
Office To PDF Conversion1.9%
Chrome (Print to PDF)1.9%
Dropbox1.9%

Related profiles

Tools you’ll see next to iLovePDF

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

C7% co-occurrence
Microsoft Word
Corpus share9.8%
Mod rate79%
C0% co-occurrence
EXCEL.EXE
Corpus share0.01%
Mod rate100%
C0% co-occurrence
CorelDRAW
Corpus share0.11%
Mod rate8%
C0% co-occurrence
Adobe Photoshop
Corpus share0.27%
Mod rate75%
C0% co-occurrence
Office To PDF Conversion
Corpus share0.00%
Mod rate100%

Long tail

Notable observations

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

Avg pages per document
16.2
Oldest observed
28.04.2021 — about 5 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 →