How to Remove Metadata From a Word Document

When you create or edit a Word document, Microsoft Office quietly records a surprising amount of information behind the scenes. Author names, revision history, comments, company details, file paths, and even deleted text can all travel with your document when you share it. Knowing how to strip that data out — and understanding what you're actually removing — matters whether you're sending a contract to a client, submitting a job application, or publishing a report.

What Is Metadata in a Word Document?

Metadata is information about your document, not the content itself. Word embeds two broad types:

Document properties — the structured fields visible when you check File > Info. These include:

• Author name and company
• Creation and last-modified dates
• Manager and organization fields
• Keywords and subject tags

Hidden content — data embedded in the document's structure that isn't visible on the page:

• Track Changes markup and revision history
• Comments (including deleted or resolved ones)
• Personal information in custom XML data
• Printer path information
• Embedded document versions
• Invisible text or hidden formatting layers

Both types can reveal details you didn't intend to share. A famous real-world example: legal briefs have exposed confidential edits because lawyers forgot to accept tracked changes before filing.

Method 1: Use the Built-In Document Inspector 🔍

The most thorough approach within Word itself is the Document Inspector, available in Word 2010 through Microsoft 365.

1. Go to File > Info
2. Click Check for Issues
3. Select Inspect Document
4. A dialog box lists categories — check or uncheck based on what you want to scan
5. Click Inspect, then Remove All next to any category you want to clear

Categories the Inspector covers include:

• Comments, revisions, versions, and annotations
• Document properties and personal information
• Hidden text
• Invisible content
• Embedded documents or linked data

One important caveat: removing metadata through the Inspector is often irreversible within that session. Word will warn you that some data cannot be restored once removed. Save a copy before you run it if the original matters.

Method 2: Accept All Changes and Delete Comments Manually

If your concern is specifically Track Changes and comments — common when collaborating on drafts — you can handle these directly:

• Go to Review > Accept > Accept All Changes
• Then go to Review > Delete > Delete All Comments in Document

This approach gives you more control than the Inspector if you want to preserve some comments or review changes before accepting them. It's also the method to use when you need to audit what's being removed rather than wiping everything at once.

Method 3: Adjust AutoSave Metadata Settings

Word has a setting that automatically removes personal information when saving. To enable it:

1. Go to File > Options > Trust Center
2. Click Trust Center Settings
3. Select Privacy Options
4. Check Remove personal information from file properties on save

This is useful as a default practice rather than a one-time cleanup. It won't retroactively clean an existing document's history, but it reduces what accumulates going forward.

Method 4: Save as a Different Format

A more aggressive approach is converting the file to a format that strips most embedded metadata by design. Saving as PDF via File > Save As (or Export) removes Track Changes, comments, and most document property fields — the PDF captures the visual output, not the edit history.

Saving as plain text (.txt) removes virtually all formatting and metadata, though it also strips tables, images, and styled text — making it appropriate only when content is all that matters.

Variables That Affect What Gets Removed

Not every method works the same across every setup. Several factors change the outcome:

This last point is particularly relevant for teams using cloud-based collaboration. Stripping metadata from a local copy of a file doesn't necessarily remove the revision history stored in OneDrive or SharePoint's version control — that's managed at the platform level, separately from the document file itself. ☁️

What the Inspector Doesn't Catch

The Document Inspector is thorough but not exhaustive. A few things it typically won't address:

• File system metadata — the creation and modification timestamps recorded by your operating system, not Word
• Server-side version history — as noted above, cloud platforms keep their own records
• Custom XML data added by third-party applications integrated with Word
• Embedded fonts that may carry licensing or origin information

For high-stakes situations — legal discovery, sensitive business negotiations, or publishing documents where attribution must be scrubbed — a single pass through the Inspector may not be sufficient. ⚠️

How Skill Level and Use Case Shape the Right Approach

A casual user sharing a draft with a colleague needs a different level of diligence than a paralegal preparing court filings or an HR professional sending offer letters. The Inspector covers most everyday scenarios. Manual review of Track Changes is appropriate when you need to know exactly what's being removed. A format conversion to PDF handles the broadest range of recipients without requiring them to have Word at all.

What the right approach looks like in practice depends on the sensitivity of the information in your document, the platform you're sharing through, the version of Word you're running, and how much of the document's edit history is relevant to keep — even internally. Those specifics live on your side of the screen, not in any general guide.