Document metadata scrubber

What does the document metadata scrubber produce?

Remove selected hidden properties from a separate supported DOCX or PDF working copy.

Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.

What do you need before you start?

• Define the authorized source population and your review rules.
• Keep the unchanged original files and record the snapshot and exclusions.
• Review missing and invalid inputs before preparing the finalized pack.

What information do you enter?

Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.

• Exact source records. Supported document source.
• Review reference. Customer-controlled review identifier.
• Responsible reviewer. Owner of the supplied facts and selected method.
• Observation date. Real YYYY-MM-DD date.
• Source and version scope. Name actual population, selected source versions and known omissions.
• Remove author and organization properties. Choose the explicit working rule.
• Remove title, subject and keywords. Choose the explicit working rule.
• Remove creation and modification dates. Choose the explicit working rule.
• Remove custom properties. Choose the explicit working rule.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.

How does the document metadata scrubber work?

1. 1
   Select the actual sources

   Exact source records. Supported document source.

2. 2
   Freeze the review rules

   Inspect actual package or PDF metadata, remove only selected property categories, and inspect the resulting working copy again. Retain exact original bytes. DOCX changes only supported core, application and custom property parts. PDF supports unencrypted classic cross-reference documents with a single revision and directly bounded metadata. Unsupported signatures, revisions, compressed object tables or metadata structures are rejected before producing a copy. Content, comments, revisions, attachments and visible author text are outside this metadata operation.

3. 3
   Inspect complete findings

   Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.

4. 4
   Keep recoverable work

   Original files and exact input strings save in this browser. Restore validates identity, schema and actual file hashes before replacing current work. Earlier browser work and historical purchases remain separate.

5. 5
   Prepare the finalized pack

   Prepare seven core files and the exact selected attachments, then download them free. Review the fictional sample below.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• Office Open XML file formatsSupports inspection of ordinary DOCX property parts only. Body text, revisions, comments, images and signatures are outside the operation. Part 2 specifies Open Packaging Conventions. Core, extended and custom property parts contain the supported DOCX document metadata.Ecma International. Reviewed 2026-10-09.
• PDF Reference 1.7Supports the declared PDF 1.x classic cross-reference subset only. XMP, signed, encrypted, incremental and object-stream PDFs are rejected. Section 10.2.1 describes the document information dictionary. Classic cross-reference tables and indirect objects identify the supported Info metadata.Adobe. Reviewed 2026-10-09.

Common questions

What still needs review?

Working results use exact local sources and explicitly selected versions. Originals remain unchanged in this browser. No source authenticity, population completeness, vulnerability exploitability, legal applicability, license conclusion, consent validity, food safety or external submission is established.

Choose at least one category. Digital signatures are not preserved by a metadata edit and signed documents are rejected. PDF supports classic Info dictionaries only. XMP metadata, encryption, incremental revisions and compressed object streams are rejected.

Each source supports at most 10 MB. Table sources support 5000 rows, 50 fields, 100000 cells and 5000000 parsed characters. JSON documents support depth 40 and 100000 nodes.

Working artifacts are produced only when their required named checks pass. Complete findings remain available even when an artifact is withheld.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all privacy and data rights tools.

• Structured-data redactorCreate a new dataset by retaining, masking, replacing or removing each field under your explicit rules. Review the result.
• Redaction verification toolCheck whether redactions remain recoverable in exported files. Try a free example. Review your inputs and result. No account or payment required.
• Pseudonymization utilityReplace identifiers using a controlled mapping. Try a free example, then review your inputs and the result. No account or payment required.
• Dataset minimization checkerCompare collected fields against a minimum. Try a free example, then review your inputs and the result. No account or payment required.
• Re-identification assessment preparationAssemble linkage risks and testing evidence. Try a free example, then review your inputs and the result. No account or payment required.