Which file types do we support?
We currently support JPG/JPEG, PNG, WebP, PDF, DOCX, XLSX, and PPTX for local metadata inspection, supported cleanup, clean-copy download, and audit reports.
Support matrix
Supported file types
We support the file types below for local inspection, supported metadata cleanup, clean-copy download, and verification reports.
| Format | Inspect | Remove supported metadata | Important limits |
|---|---|---|---|
| JPG/JPEG | Yes | Yes | We preserve C2PA/provenance by default. |
| PNG | Yes | Yes | Supported ancillary metadata chunks only. |
| WebP | Yes | Yes | We clean EXIF/XMP chunks and preserve provenance by default. |
| Yes | Yes | We refuse signed PDFs by default and flag hidden content for review. | |
| DOCX/XLSX/PPTX | Yes | Yes | We clean document properties and flag hidden content for review. |
Related tools
Choose the right metadata workflow
If you already know the file type you want to clean, these focused pages explain exactly what we inspect, remove, preserve, and flag for review.
Metadata RemoverUse the main workspace when you want one browser-only tool for images, PDFs, and Office files.Image Metadata RemoverClean supported EXIF, GPS, XMP, IPTC, comments, and image metadata.PDF Metadata RemoverRemove supported PDF Author, Creator, Producer, date, and XMP-style properties.Document Properties RemoverClean supported Word, Excel, PowerPoint, and PDF document properties.Metadata ViewerInspect file metadata first when you only need to understand what a file contains.Privacy-First ProcessingRead how we keep selected files in this browser only.
Supported file questions
What we can safely handle
Can we remove every hidden file detail automatically?
No. We remove supported metadata safely in the browser and report riskier hidden content as review signals instead of making unsafe cleanup promises.
What happens with signed PDFs?
We refuse signed PDFs by default because changing a signed PDF can invalidate its signature.
Do Office comments and tracked changes get removed automatically?
We report comments, tracked changes, macros, notes, embedded objects, and similar signals for review because they can change document meaning or behavior.