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

iText

iText 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
48%on baseline
Corpus baseline: 49%
Corpus share
7.3%
Share of all analyzed appearances
Modification rate
48%
on baseline
Role split
<1%C/>99%P
Creator vs Producer share of appearances

Corpus profile

How iText shows up in HTPBE? corpus

iText is a Java/.NET PDF library used both for legitimate server-side document generation (custom invoicing, archival workflows) and for programmatic post-processing such as merging, stamping, and field-flattening.

iText turns up in the HTPBE? corpus on both server-generated documents and programmatically processed ones. HTPBE? reads it alongside every other layer of the file.

The signal
iText turns up in the HTPBE? corpus on both server-generated documents and programmatically processed ones.

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 iText 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

  • The figures cover 2,058 files. Larger than a handful, but still a sample of what was submitted, not of all PDFs in the world.
  • The statistics describe files HTPBE? analysed. They are not a judgement of the quality or trustworthiness of iText.
  • 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 iText 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 · <1%
As Producer · >99%P
CAs creator
  • Share of appearances
    <1%
  • Modification rate
    89%
  • Avg file size
    201 KB
PAs producer
  • Share of appearances
    >99%
  • Modification rate
    48%
  • Avg file size
    227 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.

Name fingerprints

Also goes by

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

iText 2.1.7 by 1T3XT48.2%
iText® Core 8.0.5 (AGPL version), pdfHTML 5.0.5 (AGPL version) ©2000-2024 Apryse Group NV10.2%
iTextSharp.LGPLv2.Core 3.7.1.06.9%
iText® 7.1.1 ©2000-2018 iText Group NV (Macquarie Group Services Australia; licensed version)6.3%
iTextSharp™ 5.5.10 ©2000-2016 iText Group NV (AGPL-version)4.4%
iTextSharp 4.1.6 by 1T3XT3.8%
iText 2.1.2 (by lowagie.com)2.7%
iText 2.0.8 (by lowagie.com)1.7%
iText 2.1.5 (by lowagie.com)1.6%
iText® 5.5.13.3 ©2000-2022 iText Group NV (AGPL-version)0.7%
iText® 5.5.0 ©2000-2013 iText Group NV (AGPL-version)0.6%
iText® Core 8.0.5 (AGPL version) ©2000-2024 Apryse Group NV0.6%
iText® 7.0.5 ©2000-2017 iText Group NV (AGPL-version); modified using iText® 5.5.13.3 ©2000-2022 iText Group NV (AGPL-version)0.5%
iText® Core 7.2.5 (AGPL version) ©2000-2023 iText Group NV0.5%
iText® Core 9.5.0 (AGPL version) ©2000-2025 Apryse Group NV0.5%
iText® 5.3.1 ©2000-2012 1T3XT BVBA (AGPL-version)0.5%
iText® 5.5.13 ©2000-2018 iText Group NV (AGPL-version)0.4%
iText 1.4 (by lowagie.com)0.3%
iText® 5.5.11 ©2000-2017 iText Group NV (AGPL-version)0.3%
iText 2.1.0 (by lowagie.com)0.3%
iText® 5.5.8 ©2000-2015 iText Group NV (AGPL-version)0.3%
iText® 7.1.10 ©2000-2020 iText Group NV (AGPL-version)0.2%
iText 5.5.2, iText Group NV0.2%
iTextSharp™ 5.5.13.2 ©2000-2020 iText Group NV (AGPL-version); modified using iTextSharp™ 5.5.13.2 ©2000-2020 iText Group NV (AGPL-version)0.2%
iText® 5.5.13 ©2000-2018 iText Group NV (AGPL-version); modified using iText® 5.5.13 ©2000-2018 iText Group NV (AGPL-version)0.2%
iText® 7.1.14 ©2000-2020 iText Group NV (AGPL-version)0.2%
iText® 7.1.9-SNAPSHOT ©2000-2019 iText Group NV (MICROSOFT; licensed version)0.2%
iText® Core 7.2.1 (AGPL version) ©2000-2021 iText Group NV; modified using CFCA® 6.0.0 ©2016-20190.2%
iText® Core 7.2.5 (production version) ©2000-2023 Apryse Group NV, MAC D4005-0100.2%
itext-paulo-155 (itextpdf.sf.net-lowagie.com)0.2%
iText® 5.5.13 ©2000-2018 iText Group NV (PayPal, Inc.; licensed version)0.2%
iText® 5.5.2 ©2000-2014 iText Group NV (AGPL-version)0.2%
iText® 5.5.13.2 ©2000-2020 iText Group NV (AGPL-version)0.2%
iText® Core 7.2.5 (AGPL version) ©2000-2023 Apryse Group NV0.2%
iText 2.0.4 (by lowagie.com)0.1%
iText® Core 9.7.0 (AGPL version) ©2000-2026 Apryse Group NV0.1%
iText® 5.4.1 ©2000-2012 1T3XT BVBA (AGPL-version)0.1%
iText® Core 7.2.3 (production version) ©2000-2022 Apryse Group NV, Flipkart Internet Private Limited0.1%
iText® Core 8.0.2 (AGPL version) ©2000-2023 Apryse Group NV0.1%
iText® 7.1.14 ©2000-2020 iText Group NV (APPLE, INC.; licensed version)0.1%
iText® 7.1.12 ©2000-2020 iText Group NV (Tata Consultancy Services Limited; licensed version); modified using iText® 7.1.12 ©2000-2020 iText Group NV (Tata Consultancy Services Limited; licensed version); modified using emBridge0.1%
iText 4.2.0 by 1T3XT0.1%
iText® Core 9.1.0 (AGPL version), pdfHTML 6.1.0 (AGPL version) ©2000-2025 Apryse Group NV0.1%
iText® 7.1.19 ©2000-2022 iText Group NV (PT Bank Central Asia, Tbk; licensed version)0.1%
iText® Core 8.0.0 (AGPL version), pdfHTML 4.0.2 (AGPL version) ©2000-2023 Apryse Group NV0.1%
iText 5.5.130.1%
iText 2.1.7 by 1T3XT; modified using iText® 7.1.12 ©2000-2020 iText Group NV (AGPL-version)0.1%
iText® 5.5.13.3 ©2000-2022 iText Group NV (PayPal, Inc.; licensed version)0.1%
iText® 7.0.5 ©2000-2017 iText Group NV (AGPL-version); modified using iText® 5.5.13.3 ©2000-2022 iText Group NV (AGPL-version); modified using OpenPDF 1.3.430.1%
iText® 5.5.5 ©2000-2014 iText Group NV (AGPL-version)0.1%
iText® 5.2.0 ©2000-2012 1T3XT BVBA0.1%
iText 1.4.8 (by lowagie.com)0.1%
iText® 7.1.11 ©2000-2020 iText Group NV (AGPL-version); modified using SealSADK® 3.1.1.90.1%
iText® Core 7.2.3 (production version) ©2000-2022 Apryse Group NV, Flipkart Internet Private Limited; modified using OpenPDF UNKNOWN0.1%
iText 2.1.6 by 1T3XT; modified using iText® 5.2.1 ©2000-2012 1T3XT BVBA0.1%
itext-paulo-155 (itextpdf.sf.net - lowagie.com)0.1%
iText® 5.5.4 ©2000-2014 iText Group NV (AGPL-version)0.1%
iText® 5.5.13.3 ©20퀃   逅䀆倇耇䀂瀇 倇一嘀 ⠀倀愀礀倀愀氀Ⰰ 䤀渀挀⸀㬀 氀椀ذِِ۠ܰـȀݠِܠܰڐ۰۠ʐ0.1%
iText® 5.5.4 ©2000-2014 iText Group NV (AGPL-version); modified using iText® 5.5.4 ©2000-2014 iText Group NV (AGPL-version)0.1%
iTextSharp™ 5.5.13 ©2000-2018 iText Group NV (AGPL-version)0.1%
iText® 5.5.2 ©2000- ဃ䀂逅䀆倇耇䀂瀇 倇怂⠀䄀䜀倀䰀ⴀ瘀攀爀猀椀漀渀�0.1%
iText 2.1.7-snk by 1T3XT patched by Sankhya0.1%
iText by lowagie.com (r1.02b;p128)0.1%
iText® 7.1.4 ©2000-2018 iText Group NV (Fuji Xerox Document Management Solutions; licensed version)0.1%
iText 5.0.1 (c) 1T3XT BVBA0.1%
iText® Core 9.2.0 (AGPL version) ©2000-2025 Apryse Group NV0.1%
iTextSharp 4.1.2 (based on iText 2.1.2u)0.1%
iTextSharp 5.1.3 (c) 1T3XT BVBA0.1%
iText® Core 9.7.1 (AGPL version) ©2000-2026 Apryse Group NV0.1%
iTextSharp™ 5.5.13 ©2000-2018 iText Group NV (AGPL-version); modified using iTextSharp™ 5.5.13 ©2000-2018 iText Group NV (AGPL-version)<0.1%
iText 5.5.13.4 2000-2024 iText Group NV (AGPL-version)<0.1%
iTextSharp™ 5.5.13.3 ©2000-2022 iText Group NV (AGPL-version)<0.1%
iText® 5.5.1 ©2000-2014 iText Group NV (AGPL-version)<0.1%
iText® 5.5.12 ©2000-2017 iText Group NV (AGPL-version) (AGPL-version)<0.1%
iTextSharp 5.3.0 (c) 1T3XT BVBA<0.1%
iText 2.0.5 (by lowagie.com)<0.1%
iText® 5.5.13.4 ©2000-2024 iText Group NV (AGPL-version)<0.1%
iText® 5.2.1 ©2000-2012 1T3XT BVBA<0.1%
iText 2.1.0 (by lowagie.com); modified using iText® 5.5.0 ©2000-2013 iText Group NV (AGPL-version)<0.1%
iText® 5.5.6 ©2000-2015 iText Group NV (AGPL-version)<0.1%
iTextSharp™ 5.5.13.1 ©2000-2019 iText Group NV (AGPL-version)<0.1%
iTextSharp 5.2.1 (c) 1T3XT BVBA<0.1%
iTextSharp™ 5.3.5 ©2000-2012 1T3XT BVBA (AGPL-version)<0.1%
iTextSharp™ 5.4.0 ©2000-2012 1T3XT BVBA (AGPL-version)<0.1%
iText® 7.1.4 ©2000-2018 iText Group NV (AGPL-version)<0.1%
iText® 5.5.11 ©2000-2017 iText Group NV (AGPL-version); modified using iText® 5.5.11 ©2000-2017 iText Group NV (AGPL-version)<0.1%
iTextSharp™ 5.5.13.3 ©2000-2022 iText Group NV (Ceridian Dayforce Inc.; licensed version)<0.1%
iTextSharp™ 5.5.2 ©2000-2014 iText Group NV (AGPL-version)<0.1%
iText® 5.1.1 ©2000-2011 1T3XT BVBA<0.1%
iTextSharp 5.0.2 (c) 1T3XT BVBA<0.1%
iText 2.1.4 (by lowagie.com)<0.1%
iText® 5.5.13 ©2000-2018 iText Group NV (PayPal, Inc.; licensed version) (PayPal, Inc.; licensed version)<0.1%
iText 2.1.7 by 1T3XT; modified using iText® 5.5.14-SNAPSHOT ©2000-2020 iText Group NV (AGPL-version)<0.1%
iText® pdfHTML 5.0.2 (AGPL version) ©2000-2023 Apryse Group NV<0.1%
iText® 7.1.13 ©2000-2020 iText Group NV (AGPL-version)<0.1%
iText® Core 9.4.0 (AGPL version) ©2000-2025 Apryse Group NV<0.1%
iText® pdfHTML 4.0.4 (AGPL version) ©2000-2022 iText Group NV<0.1%
iText® 5.5.10 ©2000-2015 iText Group NV (AGPL-version)<0.1%
iText® 5<0.1%
iTextSharp™ 5.4.4 ©2000-2013 1T3XT BVBA (AGPL-version)<0.1%
iText® 5.5.12 ©2000-2017 iText Group NV (APPLE, INC.; licensed version) (APPLE, INC.; licensed version) (APPLE, INC.; licensed version) (APPLE, INC.; licensed version) (APPLE, INC.; licensed version)<0.1%
iTextSharp™ 5.4.2 ©2000-2012 1T3XT BVBA (AGPL-version)<0.1%
iText® Core 7.2.6 (production version) ©2000-2024 Apryse Group NV, Paysafe Bulgaria ltd<0.1%
iText® 5.3.4 ©2000-2012 1T3XT BVBA (AGPL-version)<0.1%
iText® pdfHTML 4.0.2 (AGPL version) ©2000-2022 iText Group NV<0.1%
iText® Core 9.0.0 (production version) ©2000-2024 Apryse Group NV, KUBRA Data Transfer Ltd<0.1%
iText&#x00ae; Core 8.0.5 (AGPL version), pdfHTML 5.0.5 (AGPL version) &#x00a9;2000-2024 Apryse Group NV<0.1%
iTextSharp™ 5.5.11 ©2000-2017 iText Group NV (AGPL-version); modified using iTextSharp™ 5.5.11 ©2000-2017 iText Group NV (AGPL-version)<0.1%
iText 2.1.3 (by lowagie.com)<0.1%
iText® 5.1.0 ©2000-2011 1T3XT BVBA<0.1%

Why variants matter

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

Most common
iText 2.1.7 by 1T3XT
48.2% of appearances
Variant spread
110 distinct strings
Long-tail share: 51.8%
Observed range
05.04.2019 → 17.11.2026

Distributions

What ships alongside iText

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

PDF versions written

Most output is PDF 1.4 (42% of files where iText is the Producer).

PDF 1.441.9%
PDF 1.730.9%
PDF 1.518.4%
PDF 1.36.3%
PDF 1.62.3%
PDF 2.00.1%

Common Creators when iText is the Producer

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

JasperReports45.6%
Altiuz Reports35.0%
Aspose13.8%
Adobe Photoshop1.3%
AlbatrossCloud0.9%
Intuit Inc. FPS Engine v4 (5.0.7 10/01/2025 01:36 AM)0.7%
Adobe Illustrator0.7%
BBVA0.7%
BIRT Report Engine0.6%
ESTAT0.6%

Related profiles

Tools you’ll see next to iText

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

P<1% co-occurrence
iOS Print to PDF
Corpus share1.8%
Mod rate60%
C15% co-occurrence
JasperReports
Corpus share2.2%
Mod rate22%
C12% co-occurrence
Altiuz Reports
Corpus share1.3%
Mod rate100%
C5% co-occurrence
Aspose
Corpus share3.3%
Mod rate39%
C<1% co-occurrence
Adobe Photoshop
Corpus share0.34%
Mod rate82%

Long tail

Notable observations

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

Embedded JavaScript
<1%

Of files contain JavaScript code

Digitally signed
2%

Of files carry at least one digital signature

Embedded files
<1%

Of files have attachments inside

Avg pages per document
2.0
Largest document
105 pages
Oldest observed
05.04.2019 — over 7 years ago

FAQ

iText in PDF metadata: common questions

What is iText?

iText is a Java/.NET PDF library used both for legitimate server-side document generation (custom invoicing, archival workflows) and for programmatic post-processing such as merging, stamping, and field-flattening.

Why does iText 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 iText 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 iText in the metadata mean the PDF was edited?

No. A producer name alone proves nothing about whether a document was changed. Many iText 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 iText statistics?

The figures describe the 2,058 files in the HTPBE? corpus that list iText 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 iText and not a prediction for any single document.

Can I compare iText 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 iText?

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 →