filehugger.comMetadata & Privacy Inspector
Find supported EXIF, PNG text and PDF document properties before a file is published, emailed or handed to a client.
Analyse your own file
Choose a PDF, JPEG and PNG file
Drop it here or browse this device
Your original file is analysed in this browser and is not uploaded. This tool has no AI or server-processing step.
What happens to the file
- Default processing
- Browser-only JavaScript, PDF.js, pdf-lib and Tesseract where the task needs them
- Accepted input
- PDF, JPEG and PNG
- Report contract
- File Intelligence JSON schema 1.0 plus a flattened CSV view
- Optional AI
- Not used by this tool
Sample PDF exposes an author name, producer and creation date. The report masks values in the overview and lists exact evidence only on the user’s device.
How the result is calculated
The browser scans JPEG APP1 markers, PNG ancillary chunks and PDF Info/catalog dictionaries. Findings show the field, a bounded preview and the container that supplied the evidence.
Privacy risk uses evidenced field categories: location/identity markers are high, author/device/time/software context is medium, and container-only markers are low. Confidence is parser coverage, never a guarantee of absence.
Supported and unsupported cases
| Input or situation | What version 1.0.0 checks | What it does not claim |
|---|---|---|
| JPEG | APP1/EXIF presence, common camera/software/date/GPS markers | Complete maker-note decoding or authenticity |
| PNG | tEXt, iTXt, zTXt, eXIf and tIME chunk inventory | Decompression of every vendor-specific compressed field |
| Title, author, creator, producer, dates, language and XMP marker | All compressed object streams or attachment metadata | |
| Other files | Basic identity can be shown by the health tool | Metadata inspection on this page |
What the confidence score means
Confidence describes how much of the file the published parser could inspect and how specific the evidence was. It is deliberately separate from the result score. A 95/100 confidence value does not mean “95% likely to be true,” and a high health/readiness score does not certify safety, compliance or factual correctness.
Comparison with other approaches
| Approach | Useful strength | Important limitation |
|---|---|---|
| Local metadata inspector | Browser-only, evidence source, exportable inventory | Focused parser coverage |
| EXIF command-line utilities | Much deeper tag coverage | Installation and command-line knowledge required |
| Removing file properties in an OS | Convenient for supported types | May not show or remove every field |
| Screenshot/export copy | Often strips document structure | Can reduce quality and still retain new metadata |
4/4 fixtures passed (100%)
Dataset: FH-INT-SYNTH-2026-07. Scope: PDF Info fields, PNG text chunks, JPEG EXIF marker and clean-file control. Fixtures contain generated data only; no visitor file or personal record is collected.
When this result can be wrong
Metadata can exist in compressed, encrypted, malformed or proprietary structures the lightweight parser cannot decode. “No supported metadata found” means no match in the published coverage—not proof of zero metadata.
Keep the original file, test the output in the receiving application and escalate high-stakes legal, financial, medical, accessibility or security decisions to a qualified reviewer.
Version and accuracy change log
| Release | Date | Calculation/coverage change | Re-test requirement |
|---|---|---|---|
| 1.0.0 | 2026-07-29 | Initial public engine, report schema, thresholds, synthetic fixtures and sample files. | All published fixtures and one browser sample per tool. |
Downloadable evidence, not a black-box verdict
After analysis, use Download JSON report for structured evidence or Download CSV report for review in a spreadsheet. Both include engine version, timestamp, score, confidence, metrics, findings, recommendations and limitations. Sensitive-data reports mask candidate values and no report includes the complete extracted document text.
Related tools and independent checks
Method or accuracy correction? Read the testing methodology and contact info@brothers.net.tr. Material scoring changes are published in the change log.