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.

đŸ‡«đŸ‡ź Made in Finland

Product

  • How It Works
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.18.2

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875

Status

Algorithm v2.18.2

Back to FAQ
FAQ

Does the PDF checker read my document content?

No, our PDF authenticity checker does not read or store your document content. While we temporarily load the PDF file into memory for technical analysis, we only examine file structure, metadata, and PDF formatting information—never extracting or reading the actual text, images, or content within your PDF files.

This privacy-focused approach means sensitive documents remain completely confidential. The PDF tamper detection process examines file structure, creation/modification dates, creator/producer information, digital signatures, and structural elements like xref tables and incremental updates.

We extract metadata such as filename, file size, page count, and PDF version, but never access or extract document content. This makes our PDF modification detection service safe for confidential documents including contracts, financial statements, personal records, and proprietary information. Your document content is never read, extracted, or stored—only technical metadata and structural information that helps determine PDF authenticity.

← Previous

What is the difference between Creator and Producer in PDF metadata?

Next →

What are incremental updates in PDF and why do they matter?

Related questions

Keep reading

3 answers

What are incremental updates in PDF and why do they matter?

Incremental updates in PDF files occur when changes are saved to a PDF without rewriting the entire file. Instead, modifications are appended to the end of the file, creating multiple versions within a single PDF.

This is significant for PDF authenticity checking because incremental updates can indicate document modification history. Our PDF modification detection system analyzes these incremental updates to identify when and how a PDF was changed.

Multiple incremental updates may suggest frequent editing or tampering attempts. However, some legitimate PDF creation workflows also use incremental updates, so our PDF tamper detection considers context when interpreting these findings.

The presence of incremental updates doesn’t automatically mean tampering—it’s one factor in our comprehensive PDF authenticity analysis that helps build a complete picture of document integrity and modification history.

Can a PDF be modified without detection?

While our PDF authenticity checker detects most common modification methods, sophisticated PDF editing techniques using specialized tools may sometimes evade detection. Advanced users with deep PDF knowledge could potentially modify documents in ways that minimize metadata changes or structural anomalies.

However, such modifications typically require significant technical expertise and specialized software. Our multi-layer PDF tamper detection approach analyzes multiple detection vectors including metadata consistency, structural integrity, signature fraud detection, and modification traces—making it difficult to modify PDFs without leaving some evidence.

For critical documents, we recommend using our PDF modification detection alongside other fraud detection methods. The detailed findings help identify suspicious patterns even when modifications are sophisticated. No PDF authenticity checking system is 100% foolproof, but our comprehensive analysis provides strong protection against most common tampering attempts.

How should I interpret PDF analysis results?

Results come in three states:

  • Intact — no signs of post-creation modification were found. The PDF file structure matches what you would expect from a freshly generated document.
  • Modified — the analysis found signs that the file was changed after it was originally created.
  • Cannot Determine — the PDF was created with consumer software such as Microsoft Word, Google Docs, LibreOffice, or a print-to-PDF driver. Anyone can create a document from scratch with these tools, so the integrity check result is not meaningful in this context.

Important: “Intact” does not mean “authentic.” It means the PDF was not modified after it was created. A document created from scratch with false data will also show as Intact — because it was never modified, it was simply created with false content. To understand this limitation fully, see: Can someone create a fake document from scratch?

On the result page you also see detailed metadata (creation date, modification date, creator, producer) and structural findings. These help you understand why the service gave a particular result. If the result seems unexpected, consider the PDF’s creation workflow and whether any modifications were authorized.

For important decisions, use this result as part of a broader fraud-detection strategy rather than the sole factor.