PixelOkay
/Document Metadata InspectorUTILITY STUDIO● Local-only analysis
Tools
FILE INSPECTION

Explore document properties

Add a file to inspect its available metadata.

Your documents have a story.

Inspect PDF document fields, Word properties and image EXIF—including dates, camera details and embedded location metadata where readable.

How to inspect a document

1. Add files. Choose PDF, DOCX or supported images, or drop them into the Files panel. Files are inspected locally, without a server.

2. Read fields. Group and search the extracted properties. Each field lists its source; partial/unsupported structures carry warnings.

3. Compare. Choose two files, then switch to Compare files to see matching, changed and unreported fields.

4. Export. Download JSON, CSV or a printable HTML report; print from this page to save as PDF. Sensitive metadata, file names, fingerprints and file timestamps are omitted from exports by default.

Limits. Up to 24 files, 85 MB each, and 180 MB per import batch. PDF extraction is lightweight and cannot fully decode compressed object streams or encrypted metadata; some XMP and image maker tags are unsupported. DOCX XML properties and common image EXIF fields are supported. SHA-256 requires Web Crypto. Original file contents are not preserved in reports.

Using Document Metadata Inspector

Inspect supported PDF, DOCX, and image metadata, compare two files, and export source-labeled reports with default-on best-effort redaction.

Workflow

  1. Choose supported files and inspect the fields each format parser can extract; note the source file and parser coverage for each result.
  2. Compare two selected files semantically and review any sensitive field before preparing a report.
  3. Export redacted JSON, CSV, or HTML, or print the report after checking the included fields; the source documents are not edited.

Worked example

Inspect a copied JPEG and DOCX document, compare their available metadata fields, and prepare a redacted HTML report. Review the report for personal names, paths, or other sensitive details before sharing.

Limits and data handling

Format parsers are incomplete. PDF inspection may miss object streams, indirect or compressed metadata, encrypted content, and bytes outside scanned ranges. Redaction applies to reports, not the source file, and does not guarantee de-identification. Metadata or a checksum does not prove provenance. Real-world document corpora and print/report privacy remain unverified.

Frequently asked questions

Does redaction remove metadata from the original file?

No. Redaction applies to exported reports; the original PDF, DOCX, or image is not modified.

Does it extract every field from every PDF?

No. PDF parsing is intentionally incomplete and can miss object streams, indirect/compressed fields, encrypted content, or data outside scanned ranges.

Related tools