Remove Tracked Changes and Comments in Word Before Sharing

Guides & Tutorials / Microsoft Word / Document handoff

To remove tracked changes and comments from Word before sharing, finalize the edits in a separate copy, delete the review threads, inspect the document for unwanted hidden information, and reopen the saved deliverable. A tidy-looking page is not sufficient: display settings can hide review material without removing it.

This guide focuses on Word’s Windows desktop workflow, including Word for Microsoft 365 and Word 2024. Ribbon labels can vary with the interface and version. The goal is a reviewed distribution copy while preserving the working document and its review record where your normal retention rules require them.

01 / Preserve the working file and identify the final source

Start with the version the responsible reviewer has approved. Check its location and contents rather than relying on a filename such as “final-final.” If several files are circulating, establish which one includes the agreed changes before doing cleanup.

Create a separately named distribution copy in the appropriate location. A hypothetical naming scheme could distinguish “proposal-review” from “proposal-client-copy,” with a date or version identifier your team understands. The names are examples, not a required Word convention.

Keep the source and the deliverable easy to distinguish. Avoid cleaning a file in one folder and attaching an older similarly named file from Downloads. At the end of this process, the file you verify should be the file you actually send.

If you need to reconcile two candidates first, use our guide to comparing Word documents without overwriting originals. Comparison helps identify differences; it does not decide which wording the business has approved.

For a collaborative document, agree on a cutoff for preparing the release copy. A reviewer continuing to revise the source after your copy was made creates a version-control question that no markup-removal button can solve.

02 / Reveal the material you need to review

On the Review tab, select All Markup. Under Show Markup, check the relevant edit types and select all reviewers under Specific People. Microsoft’s tracking documentation explains that filtering changes affects their display, not their removal.

Use the Reviewing Pane as a supporting summary, with filters checked. Its counts concern visible material, so an empty-looking view is not the only acceptance check. Open the comments area separately as well.

For a hypothetical proposal, a deleted pricing note might disappear in the clean reading view while remaining in the review record. That is why visual neatness and a finished distribution file need separate checks.

Do not use print preview as the entire review process. Decide which text belongs in the final document, then verify the particular output you intend to distribute.

03 / Accept or reject edits based on the intended text

Microsoft’s acceptance guidance requires accepting or rejecting tracked changes to remove them. Start at the beginning of the document and use the Review tab’s Accept or Reject controls to work through the revisions.

Acceptance incorporates the proposed edit; rejection declines it. Read the surrounding sentence after each consequential decision. Accepting a deletion means the deleted wording is absent from the final text, so “accept everything” is not a neutral cleanup command.

Use a bulk command only when all remaining edits have already been approved. Word offers Accept All Changes and Reject All Changes; choose the action that matches the review decision. A command limited to changes shown is not the same scope as all changes in the document.

When finalization is complete, stop tracking if the distribution copy should no longer record further editing. Microsoft also documents combined actions such as Accept All Changes and Stop Tracking. Check the exact command before selecting it.

A hypothetical reviewer may approve spelling fixes but reject a changed delivery date. That calls for individual decisions, not a bulk acceptance followed by hoping the date is correct. Keep an approval note outside the distribution copy if your process requires one.

If tracking is locked or the shared review permissions prevent finalization, ask the document owner for the appropriate access or an approved final copy. Do not bypass the protection just to finish a handoff.

04 / Delete comment threads that should not travel

Comments are a separate cleanup task. Microsoft’s feedback guidance explains that resolved threads remain in the document until deleted. A resolved discussion may still contain names, internal questions, or an earlier negotiating position.

In modern comments, open the thread’s More thread actions (…) menu and choose its deletion action. The modern-comments guide describes the thread menu and a List view containing both active and resolved comments. Review that broader list instead of checking only bubbles beside the text.

Where your ribbon exposes a Delete menu with Delete All Comments in Document, use it only after deciding that no discussion needs to remain in this copy. Microsoft’s comment-deletion guidance also covers individual comments, threads, and deleting all comments.

Before deletion, transfer any unresolved action to the proper working record. For example, “confirm the installation date” belongs in an assigned task or the continuing review copy if it has not actually been answered. Deleting its comment does not complete that task.

Recheck the comments area after cleanup. Keep the evidence of approval in the approved internal system rather than retaining an internal discussion in a file meant for a different audience.

05 / Inspect the copy for unwanted hidden information

Microsoft recommends using Document Inspector on a copy, because removed information cannot always be restored. Run it after the editorial decisions so a cleanup operation does not stand in for reviewing the intended text.

1. In the distribution copy, open File > Info > Check for Issues > Inspect Document.
2. Select the content types to inspect and choose Inspect.
3. Read the findings and use Remove All only for categories you intend to remove.
4. Choose Reinspect where available, then review the document again.

The inspector covers multiple kinds of information, including review material and personal document information, but Microsoft documents limitations. A clean result is not a substitute for checking visible names, confidential wording, or inappropriate content in the body.

Do not select every removal option mechanically. Some document elements may be required for the deliverable. If you do not understand a finding, investigate it on the copy before removing it.

Microsoft’s Inspector framework documentation notes that an error leaves the affected module’s data unchanged. It also describes restrictions involving signed, protected, and rights-managed documents. Treat errors as unresolved checks and involve the responsible owner when protection is relevant.

06 / Choose an editable file or a reviewed PDF

Send DOCX when the recipient needs editable Word content. Send a PDF when that format fits the agreed purpose. A PDF is a separate output to inspect, not a way to avoid finalizing the source copy.

In Word’s desktop PDF options, Microsoft distinguishes Document from Document showing markup under Publish what. For a clean PDF, confirm the intended choice and inspect the generated file. Review document-property inclusion and accessibility options as appropriate.

Our Word-to-PDF verification guide covers layout, links, and the exported result in more depth. Here, concentrate on whether review material or an unintended version reached the deliverable.

If the recipient needs both formats, verify both. Matching filenames do not establish matching content. A last-minute correction should trigger fresh checks of every file that will be distributed.

For a cloud link, confirm what object the link opens. A link to the ongoing working document and an attachment containing a prepared distribution copy are different handoff choices.

07 / Reopen the saved deliverable and check the result

Save the finished file, close it, and reopen it from the intended delivery location. Use this suggested checklist; it is a verification plan, not a claim that a sample document was tested for this article.

• Confirm the filename, location, and intended recipient version.
• Read consequential dates, amounts, names, and commitments in context.
• For DOCX, review all markup and the full comments list again.
• Confirm Inspector checks completed without unresolved errors.
• For PDF, inspect the output pages and any comments or annotations.
• Check headers, footers, tables, page breaks, and final attachments.
• Send or link the verified deliverable, keeping the working source separate.

For important handoffs, ask a second authorized person to check both the wording and the file identity. Someone familiar with the document may spot the wrong version more readily than a formatting check alone.

If review resumes afterward, return to the working process and prepare a new distribution copy when ready. Avoid treating a previously cleaned file as permanently approved regardless of later edits.

Frequently asked questions