Client Side Forensic Utility With Zero Data Upload
Free Metadata Comparison
Two copies of the same document rarely tell the same story. Everything runs in your browser and nothing is uploaded.
Choose the copies to compare
The executive triage, the per copy scorecard, the metadata side by side and the report downloads appear here once you choose two to four copies and start the comparison. Your files stay on this device.
Compare two to four copies side by side and see at once which metadata fields changed, whether the extracted text or decoded pixels still match and exactly where the bytes diverge.
Select the baseline, then every copy you were given
Choose two to four copies of the same document or image. Their names may differ, such as a Bates numbered production copy and the shared drive original, but each must be the same kind of file. File 1 is the baseline and every other copy is measured against it. Label each copy with where it came from, the opposing production, the shared drive or the email attachment, so the report reads the way you will present it.
The first metadata inspection downloads about 28 MiB of parser files to your browser. Each copy may be up to 20 MiB.
Zero Upload Local Browser Processing
Supported formatsPDF, DOCX, XLSX, PPTX, JPEG, PNG, WebP and any format ExifTool recognizes
Size limitTwo to four copies, 20 MiB each
EngineExifTool 13.59 plus bounded PDF.js, Office and pixel comparisons
No file upload. Files are inspected on your device. Optional usage measurement stays off unless you allow Analytics. It sends GDF only the tool name and fixed action labels, such as analysis completed or report prepared. No input, result, filename or visitor identifier is sent. Google and advertising scripts do not load on this page. Use Cookie settings below to change your choice.
Metadata differences come first
The comparison collects every grouped tag ExifTool reads from each copy, including document properties, author and software fields, dates, camera settings, GPS, XMP, IPTC and repeated instances, then pairs them field by field against the baseline. The delta scorecard at the top of the results states for each copy how many embedded fields changed, appeared or went missing, whether the bytes are identical and whether the supported content still matches.
The table below it starts with changed or unknown embedded metadata. Turn off that filter to show matching fields, or search for a name or value. Readable values and numeric parser values are compared separately, so a value that merely displays differently is distinguished from one that actually changed.
Browser file names and last modified times, container properties, derived values and parser information sit in their own categories and never inflate the embedded metadata change count. A browser timestamp is not an original disk creation time. When extraction is partial the report says so, and an absent field in incomplete results is unknown rather than evidence that someone removed it.
Content and file bytes are separate checks
For PDF files the tool compares native text extracted in page order; there is no OCR, so scanned pages, images, layout, signatures, annotations and attachments are outside the text comparison. DOCX copies are compared on their main document text including table paragraphs, XLSX copies on their stored cell records, shared strings, formulas and cached values without recalculation, and PPTX copies on their slide text. Headers, footers, comments, tracked change meaning, embedded objects and formatting remain outside those text comparisons.
JPEG, PNG and supported WebP copies are compared on their browser decoded pixels within the image limits, where browser color conversion and orientation can affect the result. For any other format ExifTool recognizes, metadata and the exact file bytes are still compared and content extraction is marked unavailable.
Matching extracted text or decoded pixels does not mean that every byte is identical, which is why byte equality is reported separately. A changed byte count describes differing positions, not how many edits were made.
Your copies stay on your computer
Your selected files, labels, metadata and extracted content are not uploaded to GDF or an outside analysis service. The page, parsers, fonts and code download to your browser; inspection and comparison run locally. The tool does not query AI services, DNS, location services or remote document converters, and no account or email address is needed.
Clear removes the displayed comparison and stops its workers without touching your original files. Downloaded reports remain wherever you save them and may contain private information.
Save the comparison
Download the PDF or HTML report, an Excel ready CSV or the lossless JSON. Display filters never filter the downloads. The PDF and HTML reports open with the side by side delta scorecard, the identity and SHA 256 of every copy and the triage observations, then the interpretation guide, the complete comparison table and the evidentiary scope advisory. The JSON retains each collected inspection and the extracted text.
Using the comparison in an examination
Work on copies and preserve the originals with their collection context. Each input receives a SHA 256 hash so you can document exactly which bytes were compared. Changes in metadata do not identify who made them, establish when they occurred or prove tampering, and matching metadata does not prove that two copies have the same content. Those questions are answered by the custody record and, where the stakes justify it, a full examination.
The tool uses the same extraction settings for every copy. It does not decrypt password protected files, recover deleted records or validate certificates.
Browser limits
Two to four files, up to 20 MiB each. Metadata keeps its 60 second parser loading, 45 second inspection and 4 MiB engine output limits. Content has a separate 25 second deadline and bounded page, pixel, XML and text limits recorded with each file. The comparison stops rather than silently discard records above 25,000 combined collected metadata records. The table displays 100 rows per page and text changes show up to 2,000 lines on screen, with the complete collected text in the JSON. PDF generation stops with an explanation rather than a shortened file above 25,000 export records, 500 pages, 25 MiB or 60 seconds.
Copies from different sources
A document saved from an email attachment, downloaded from shared storage or produced by another party can carry the same name while holding different bytes or properties. Finding those differences before a deposition or a production dispute is the point of the comparison. For a single file, use the Free Metadata Analyzer. For a disputed message, use the Email Header Analyzer. Neither tool replaces the records needed to establish the original source and handling.
Methods and versions
Metadata extraction uses ExifTool by Phil Harvey. Supported PDF text uses the locally pinned PDF.js parser. Office text is read from selected package parts and image comparisons use this browser’s decoder. The report records the parser versions and limits, and the per file warnings call out scanned or encrypted PDFs, unsupported codecs, partial records and embedded objects.
Version 1.1.0. Free to use. Browse all free tools. © 2026 Global Digital Forensics, Inc. All rights reserved.
Free consultation
Do two versions of the same document disagree
When the copies differ, the next questions are who held each one, when it changed and which version can be relied upon. A senior examiner can tell you on the first call which records to preserve and how to transfer the originals securely. Our examiners have testified in federal and state courts on document authenticity. Your files and comparison report are never attached to this inquiry.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .