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

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · [email protected] · Made in Finland

Status

Algorithm v2.49.0

Tool profile

Apache PDFBox

Apache PDFBox reads as a downstream re-saver — its modification rate in our corpus does not sit meaningfully below the baseline. The name alone is never the verdict; each file is judged on its own structure.

Back to all statistics
Forensic verdict

Anomaly profile

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

Modification rate
60%+11pp above baseline
Corpus baseline: 49%
Corpus share
0.10%
Share of all analyzed appearances
Modification rate
60%
+11pp above baseline
Role split
0%C/100%P
Creator vs Producer share of appearances

Corpus profile

How Apache PDFBox shows up in HTPBE? corpus

Apache PDFBox is a Java PDF library used in many enterprise pipelines for both generation and post-processing (merging, signing, text extraction with re-emit).

PDFBox appears throughout Java enterprise pipelines, both for generation and for merging or signing existing files. The verdict comes from the file as a whole, with the tool name as one part of the picture.

The signal
PDFBox appears throughout Java enterprise pipelines, both for generation and for merging or signing existing files.

Reading guide

How to read this page

Every PDF stores two software labels: the Creator, which names the application that first produced the document, and the Producer, which names the software that last wrote the file out. This page counts the files HTPBE? has analysed where Apache PDFBox fills one of those labels, and shows how often those files carry modification markers, which PDF versions they use and which other tools sit next to them.

A tool name tells you where a file passed through, not whether anyone changed its content. A Creator and Producer that agree usually point to a single pass; a Producer that differs from the Creator means the file was written out again by another program, which has many ordinary explanations such as compression, merging or a print-to-PDF step.

Caveats

  • Only 5 files list Apache PDFBox, so every percentage here moves a lot with each additional file.
  • The statistics describe files HTPBE? analysed. They are not a judgement of the quality or trustworthiness of Apache PDFBox.
  • Submitted files lean towards documents that someone wanted checked, so rates here can sit higher than in everyday document flows.
  • Metadata can be rewritten by anyone, so a producer name on its own is never treated as proof either way.
Read a PDF’s metadata for freeAll tool statisticsCreator vs Producer explainedPDF metadata fields referenceCheck PDFs through the API

Role in the workflow

How Apache PDFBox 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
    60%
  • Avg file size
    242 KB

How to read this

The Creator slot typically reflects where a document started life. The Producer slot reflects whatever wrote the final file, which is not always the same software.

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 Apache PDFBox

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

PDF versions written

Most output is PDF 1.4 (67% of files where Apache PDFBox is the Producer).

PDF 1.466.7%
PDF 1.633.3%

Related profiles

Tools you’ll see next to Apache PDFBox

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

C100% co-occurrence
Dropbox
Corpus share0.06%
Mod rate69%

Long tail

Notable observations

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

Digitally signed
40%

Of files carry at least one digital signature

Avg pages per document
6.8
Oldest observed
11.02.2026 — 9 months ago

FAQ

Apache PDFBox in PDF metadata: common questions

What is Apache PDFBox?

Apache PDFBox is a Java PDF library used in many enterprise pipelines for both generation and post-processing (merging, signing, text extraction with re-emit).

Why does Apache PDFBox appear in the metadata of a PDF?

A PDF can record the software that created it (Creator) and the software that last wrote the file out (Producer). When Apache PDFBox generated the file, or re-saved it, it can leave its name in one of those fields. The field is filled in by software, not checked by anyone, so it is a hint about the file’s history rather than a guarantee.

Does Apache PDFBox in the metadata mean the PDF was edited?

No. A producer name alone proves nothing about whether a document was changed. Many Apache PDFBox files are original output, and a file that was edited can name any tool at all. What matters is the whole picture: how the file is built, how its dates and structure line up, and whether the Creator and Producer fit together.

How should I read the Apache PDFBox statistics?

The figures describe the 5 files in the HTPBE? corpus that list Apache PDFBox as Creator or Producer. The modification rate is the share of those files that carry modification markers. It is a base rate for this particular set of files, not a property of Apache PDFBox and not a prediction for any single document.

Can I compare Apache PDFBox with other tools using these numbers?

Only loosely. The corpus consists of PDFs people chose to submit for checking, which skews towards documents someone had a reason to doubt. A tool popular for legitimate bulk output can still show a high rate here, and a rarely seen tool can show an extreme rate from a handful of files. These pages are not a quality ranking of the tools themselves.

How do I check a PDF that lists Apache PDFBox?

Upload it to HTPBE? for a modification check, or open it in the free PDF Metadata Viewer to see the Creator, Producer and dates stored in the file. The same check is available through the HTPBE? API.

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.

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