PDF Forensic Info Report
Upload a PDF to see its creation/modification dates, producer software, how many times it was saved after being created, and whether it contains embedded JavaScript - all read directly from the file's own structure and metadata.
Preguntas frecuentes
Does this tell me if a document is fake or has been tampered with?
No. This reports plain facts read from the file itself - dates recorded in its metadata, the software that created/last saved it, and how many incremental save operations its raw structure shows - not a verdict on authenticity. Metadata can also be missing, incomplete, or edited by other tools, so treat these as clues to look into, not proof of anything.
What's an "incremental update" and why does the count matter?
Many PDF editors append changes to the end of a file rather than rewriting it, leaving multiple end-of-file markers in the raw bytes. Counting these tells you how many times a file was saved after it was first created - useful context, for example, when checking whether a document you received has been modified since it was supposedly finalized.
Why flag embedded JavaScript?
PDF JavaScript is a known vector for malicious behavior, and most everyday documents (contracts, forms, scans) have no legitimate reason to contain any. Finding some doesn't necessarily mean a file is dangerous, but it's worth knowing about before opening it in a full-featured PDF reader.
Is my file uploaded anywhere?
No, the entire analysis runs in your browser by reading the file's own bytes and metadata directly.