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

Aspose

Aspose appears on both unmodified and modified documents in our corpus. The name alone is never the verdict; each file is judged on its own structure.

Back to all statistics
Forensic verdict

Mixed signal

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

Modification rate
39%-10pp below baseline
Corpus baseline: 49%
Corpus share
3.3%
Share of all analyzed appearances
Modification rate
39%
-10pp below baseline
Role split
56%C/44%P
Creator vs Producer share of appearances

Corpus profile

How Aspose shows up in HTPBE? corpus

Aspose is a commercial component suite (Aspose.PDF, Aspose.Words) used both for legitimate server-side document generation in enterprise apps and for programmatic editing/conversion of existing PDFs.

Aspose appears on both server-generated documents and converted or edited files. HTPBE? weighs it together with the rest of the file’s structure.

The signal
Aspose appears on both server-generated documents and converted or edited 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 Aspose 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 929 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 Aspose.
  • 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 Aspose 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 · 56%
As Producer · 44%P
CAs creator
  • Share of appearances
    56%
  • Modification rate
    47%
  • Avg file size
    697 KB
PAs producer
  • Share of appearances
    44%
  • Modification rate
    29%
  • Avg file size
    834 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 Aspose in the wild. All are merged into the same canonical profile.

Aspose Pty Ltd.40.0%
Aspose.PDF for .NET 22.12.026.8%
Aspose Ltd.15.4%
Aspose.PDF for .NET 21.9.07.2%
Aspose.Pdf 8.3.11.8%
Aspose.PDF for .NET 25.6.01.5%
Aspose.PDF for .NET 26.4.00.6%
Aspose.PDF for .NET 23.5.00.6%
Aspose.Words for Java 22.9.00.5%
Aspose.Words for .NET 22.12.00.5%
Aspose.Words for .NET 16.4.0.00.5%
Aspose.Words for Java 20.11.00.4%
Aspose.Words for Java 14.9.0.00.3%
Aspose.Words for Java 18.120.3%
Aspose.Words for .NET 11.9.0.00.2%
Aspose.Words for .NET 26.5.00.2%
Aspose.Pdf for .NET 9.8.00.2%
Aspose.Pdf for .NET 17.4.00.2%
Aspose.Words for Java 23.8.0; modified using qys-sign® 2.0.0 ©2000-20260.2%
Aspose0.1%
Aspose.Cells0.1%
Aspose.Words for .NET 19.80.1%
Aspose.Words for .NET 15.10.0.00.1%
Aspose.PDF for .NET 24.10.00.1%
Aspose.PDF for .NET 24.6.00.1%
Aspose.Words for .NET 23.9.00.1%
Aspose.Words for .NET 19.60.1%
Aspose.Words for .NET 25.1.00.1%
Aspose.Cells v8.4.1.00.1%
Aspose.Words for .NET 22.11.00.1%
Aspose.PDF for .NET 25.9.00.1%
Aspose.Words for Java 15.10.0.00.1%
Aspose.Words for .NET 18.110.1%
Aspose.PDF for .NET 24.2.00.1%
Aspose.Words for .NET 23.8.00.1%
Aspose.Words for Java 19.80.1%
Aspose.PDF for .NET 19.100.1%
Aspose.Words for Java 15.8.0.00.1%
Aspose.Words for .NET 16.1.0.00.1%

Why variants matter

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

Most common
Aspose Pty Ltd.
40.0% of appearances
Variant spread
39 distinct strings
Long-tail share: 60.0%
Observed range
21.05.2015 → 13.10.2026

Distributions

What ships alongside Aspose

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

PDF versions written

Most output is PDF 1.7 (90% of files where Aspose is the Producer).

PDF 1.790.4%
PDF 1.44.6%
PDF 1.54.1%
PDF 1.60.8%
PDF 1.30.3%

Common Producers when Aspose is the Creator

iText writes 18% of these files – read this row as ‘what these documents most often pass through on the way out’.

iText18.1%
macOS Print to PDF13.5%

Common Creators when Aspose is the Producer

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

Aspose91.4%
Microsoft Word7.8%
Jan Piet Vermaas0.5%
WPS Office0.3%

Related profiles

Tools you’ll see next to Aspose

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

P10% co-occurrence
iText
Corpus share7.3%
Mod rate48%
P8% co-occurrence
macOS Print to PDF
Corpus share3.4%
Mod rate62%
C3% co-occurrence
Microsoft Word
Corpus share9.0%
Mod rate74%
C<1% co-occurrence
Jan Piet Vermaas
Corpus share0.01%
Mod rate100%
C<1% co-occurrence
WPS Office
Corpus share0.33%
Mod rate23%

Long tail

Notable observations

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

Digitally signed
<1%

Of files carry at least one digital signature

Avg pages per document
3.0
Largest document
107 pages
Oldest observed
21.05.2015 — over 11 years ago

FAQ

Aspose in PDF metadata: common questions

What is Aspose?

Aspose is a commercial component suite (Aspose.PDF, Aspose.Words) used both for legitimate server-side document generation in enterprise apps and for programmatic editing/conversion of existing PDFs.

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

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

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

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

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 →