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

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

ยฉ 2024โ€“2026 TMI Iurii Rogulia ยท VAT ID: FI29845875 ยท Made in Finland ๐Ÿ‡ซ๐Ÿ‡ฎ

Status

Algorithm v2.23.3

Tool profile

Acrobat PDFMaker

Acrobat PDFMaker 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 29 appearances across the HTPBE? corpus.

Modification rate
86%+38pp above baseline
Corpus baseline: 48%
Total appearances
29
0.14% of corpus
Modification rate
86%
+38pp above baseline
Role split
100%C/0%P
Creator vs Producer share of appearances

Corpus profile

How Acrobat PDFMaker shows up in HTPBE? corpus

Acrobat PDFMaker is one of the PDF-handling tools surfaced in the HTPBE? corpus. Acrobat PDFMaker appears predominantly as the original Creator (100% of its occurrences) โ€” i.e. on documents that started life inside Acrobat PDFMaker 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 Acrobat PDFMaker 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 Acrobat PDFMaker acts as Creator, 86% carry modification markers; on documents where it acts as Producer, 0% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against Acrobat PDFMaker or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Acrobat PDFMaker 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 Acrobat PDFMaker 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 ยท 100%
As Producer ยท 0%P
CAs Creator
  • Usage
    29
  • Modification rate
    86%
  • Avg file size
    421 KB
PAs Producer
  • Usage
    0
  • Modification rate
    0%

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 Acrobat PDFMaker in the wild. All are merged into the same canonical profile.

Acrobat PDFMaker 25 for Word55.2%
Acrobat PDFMaker 11 for Wordille13.8%
Acrobat PDFMaker 26 for Word13.8%
Acrobat PDFMaker 24 for Word6.9%
Acrobat PDFMaker 25 for Excel3.4%
Acrobat PDFMaker 22 for Word3.4%
Acrobat PDFMaker 19 for Word3.4%

Why variants matter

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

Most common
Acrobat PDFMaker 25 for Word
55.2% of appearances
Variant spread
7 distinct strings
Long-tail share: 44.8%
Observed range
25 May 2015 โ†’ 28 Apr 2026

Distributions

What ships alongside Acrobat PDFMaker

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

Common Producers when Acrobat PDFMaker is the Creator

Adobe PDF Library writes 62% of these files โ€” that pairing is the Adobe-stack default for many institutional pipelines.

Adobe PDF Library62.1%
Acrobat Distiller31.0%
pdf-lib3.4%
macOS Print to PDF3.4%

Related profiles

Tools youโ€™ll see next to Acrobat PDFMaker

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

P62% co-occurrence
Adobe PDF Library
Appearances340
Mod rate73%
P31% co-occurrence
Acrobat Distiller
Appearances303
Mod rate55%
P3% co-occurrence
pdf-lib
Appearances74
Mod rate85%
P3% co-occurrence
macOS Print to PDF
Appearances750
Mod rate64%

Long tail

Notable observations

Smaller cuts of the Acrobat PDFMaker corpus โ€” useful context, but treat each row as a single data point rather than a strong signal.

Digitally signed
1

PDFs carrying at least one digital signature

Pages parsed
180
Oldest observed
25 May 2015 โ€” about 11 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 โ†’