Client Side Forensic Utility With Zero Data Upload
Free Metadata Analyzer
Read what a file says about itself before the other side does. Your file never leaves your device.
Analyze your file
The executive triage, the readable metadata fields, the extraction coverage and the report downloads appear here once you choose a file or load the sample. Your file stays on this device.
ExifTool runs inside your browser, surfaces the chronology, authorship and location fields counsel asks about first, and hands you a full report carrying the file’s SHA 256 identity.
Choose the document or image you need to understand
The analyzer reads PDF, JPEG, PNG, WebP, TIFF, HEIC, DOCX, XLSX and PPTX files along with the audio, video and camera RAW formats that ExifTool recognizes. It detects the real format from the bytes, flags a name whose extension disagrees with its contents, and reports encrypted or password protected containers as such rather than failing silently.
The first analysis downloads about 28 MiB of parser files to your browser with a live byte counter. Later runs in the same session start at once.
Zero Upload Local Browser Processing
Supported formatsPDF, images, Office documents, audio, video and camera RAW
Size limitOne file up to 20 MiB
EngineExifTool 13.59 compiled to WebAssembly
No uploads. Your file stays on your device. This tool reads metadata in your browser. Your file and its metadata are not sent to GDF or an outside service. 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. Clear removes this page’s input and results; downloaded reports remain on your device.
Local Browser Execution With Zero Data Upload
GDF Free Tools analyze files and email headers in your browser on your own computer. Your selected files, pasted headers and extracted results are not uploaded to GDF or an outside analysis service. The page and parser download to your browser; inspection runs locally.
No account, email address or payment is needed to analyze a file or download its report. Reports can carry names, locations and internal paths from the file, so treat them as you would the file itself.
Applying Tool Outputs in Defensible Forensic Workflows
Use a working copy for inspection and preserve the original evidence. The report records the inspected input hash, inspection time and tool version so you can document what you examined. Check important findings and the tool’s limits as part of your examination. Metadata and email headers alone do not establish authenticity.
The inspection time comes from your browser clock and the local time zone offset is printed beside it. Embedded timestamps are shown exactly as the file recorded them, with any time zone they carry, so a camera clock value is never silently converted into a local time.
What the analyzer reads
Images give up their EXIF, GPS, IPTC and XMP records, camera maker notes, color profiles and file properties. PDF and Office documents surface their document properties, custom fields and XMP packets, including the creator, producer, author, revision and editing time fields that decide whether a contract is the version a party says it is. ExifTool also reads audio, video and camera RAW containers, so a voicemail attachment or a dashcam clip can be triaged with the same report.
The executive triage at the top of the results states the file identity and SHA 256, the key chronology, the author and creating software, whether location data is present, and any discrepancy worth a second look: a modify date before a create date, a producer that differs from the creating application, editing software, an XMP edit history or an extension that does not match the detected format. Every collected tag remains below it, grouped and searchable, with readable values beside the parser’s numeric values where they differ.
Binary metadata is listed with its size rather than extracted. A file may contain few tags, none, unreadable records or more data than one browser session can hold, and the report says which.
How to read the results
Names, dates, software and location fields can be edited, and their presence or absence alone does not establish authorship, a complete editing history or tampering. What the triage gives you is the file’s own account of itself, organized the way an examiner reads it, so you know which questions to put to the custodian and which records to preserve next.
The browser’s file name and last modified date are reported separately from embedded metadata. Temporary inspection paths, permissions and timestamps from the browser environment are excluded because they describe this session, not your original file system. No digital signature, certificate trust or authenticity verdict is produced, and password protected content is not decrypted.
Inputs are limited to 20 MiB and the analysis stops after 45 seconds with an explanation. Download the PDF or HTML report, an Excel ready CSV or the lossless JSON. Filtering the on page display never filters the downloads. Metadata extraction uses ExifTool by Phil Harvey, running locally through a WebAssembly port. The report records the engine version and extraction options. Engine and license details.
Free consultation
Does this file decide something
When a document or image carries legal or financial weight, a senior examiner can tell you on the first call what the metadata means for your position, what to preserve and how to transfer the original securely. Global Digital Forensics has supported counsel since 1992 and our examiners have testified in federal and state courts. Your file and report are never attached to this inquiry.
Version 1.2.0. Free Metadata Analyzer is free to use. Browse free tools. © 2026 Global Digital Forensics, Inc. All rights reserved.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .