How to remove tracked changes and their hidden history from Word

Tracked changes don't just mark up your text — they store who edited it, when, and the exact words that were deleted, all inside the file. And clicking "Accept All Changes" doesn't reliably take that out. Here's how to see what's really in there and flatten it for good.

What tracked changes actually store

A Word file is a package of XML, and revisions live in word/document.xml as specific elements: insertions (w:ins), deletions (w:del) and moves (w:moveFrom / w:moveTo). Each one records the editor's name and a timestamp, and — this is the part people miss — the deleted text is kept verbatim inside those elements, not thrown away. The file also carries per-session revision fingerprints (rsids) that can link edits together across drafts.

In other words, a document with tracked changes contains a running record of who changed what, when, and what the text used to say. If you send that file outside your organisation, you may be handing over an edit history you never meant to share.

Why "Accept All Changes" is not enough

The natural instinct is to accept every change so the markup disappears. On screen it works — the revision marks vanish and the document looks final. But accepting a change makes the markup invisible, which is not the same as making the underlying data gone. If the changes aren't truly flattened, the deleted text and author names can still be recovered from the file's XML.

Method 1 — Word's Document Inspector

Word ships with a Document Inspector that can flag and remove some revision data:

1. Open the document and go to File → Info.
2. Select Check for Issues → Inspect Document.
3. Run it, then choose Remove All next to "Comments, Revisions, and Versions".
4. Save the file.

This helps, but the inspector's behaviour varies by version and platform, and the safe path is the same as with any redaction: verify the result rather than trusting it. Reopen the file, turn on Review → All Markup, and confirm nothing remains.

Method 2 — detect and flatten, without uploading

The reason people reach for an online tool is precisely that the file is sensitive — which makes uploading it to someone's server the wrong move. Barecopy solves that by running entirely in your browser: you drop the file on the page, and it tells you exactly how many tracked changes are present and how many distinct authors left their names in the history. That detection is free.

If you choose to clean it, Barecopy flattens the revisions the way accepting them should work: it removes the deletions and move-from content (w:del, w:moveFrom), unwraps insertions and move-to content into plain text (w:ins, w:moveTo), and strips the property-change records and rsid session fingerprints. Then it re-scans the output to confirm the history is actually gone. The file is never transmitted — you can switch off your internet after the page loads and it still works.

Flattening changes the document — so it's opt-in

There's an important honesty point here. Removing tracked changes isn't a silent metadata scrub: like Accept All, it changes the visible document, because the accepted edits become the final text. For that reason Barecopy never does it behind your back. Detection runs automatically and for free; the flattening step is an explicit choice you make, and the re-scan afterwards shows you the history really is gone before you send the file on.

Frequently asked