Remove personal information from Word documents before sharing
Check comments, tracked changes, author details and hidden content in a Word sharing copy without damaging your original document.
A clean-looking Word document can still contain comments, revision history inside the file, author information or text that is hidden from the current view. That matters when a draft moves outside the group that created it.
Think of the document you send as a separate publication copy. Keep the editable working version, then make a deliberate sharing copy with only the information the recipient needs. This avoids destroying useful internal notes while reducing the chance of sending them by mistake.
The workflow below is mainly for desktop Word. Features differ in Word for the web, Mac versions and managed installations, so use the relevant Microsoft instructions for your edition.
Start with a copy and a purpose
Save a new file before removing anything. Microsoft specifically recommends inspecting a copy because some removed information cannot easily be restored. Its Document Inspector guide explains what the tool can find and the limits of automatic cleanup.
Name the copy clearly without exposing extra personal information. proposal-client-copy.docx is more useful than a filename containing a private discussion, full home address or account number.
Decide whether the recipient needs to edit the document, comment on it or simply read it. An editable draft may legitimately need tracked changes. A final public handout probably does not. Do not remove collaboration information automatically when it is part of the intended exchange.
If the document belongs to an employer or client, follow the approved review process. A personal preference for minimal metadata does not override a requirement to retain records or attribution.
Resolve tracked changes instead of hiding them
Changing the review display to hide markup does not necessarily remove the underlying revisions. Review each change and accept or reject it according to the intended final text.
Microsoft's tracked-changes documentation distinguishes displaying revisions from resolving them. Use that distinction when preparing the sharing copy. The goal is not merely a screen with fewer colored marks; it is a file whose revision state matches what you intend to disclose.
Pay special attention to deleted text. A sentence removed from the visible draft may still be present as a tracked deletion. Also check changes in tables, headers and footnotes rather than reviewing only the main paragraphs.
After resolving changes, read the document normally. Accepting everything in one click can preserve an edit you meant to reject or remove a clarification the reader still needs.
Review comments and collaboration notes
Open the comments pane and inspect the full list. A comment can contain a person's name, an internal decision, a client's details or a link to another document. Deleting the visible text it refers to does not guarantee the comment is gone.
For a final copy, remove comments that do not belong with the recipient. For a collaborative copy, keep only the discussion that serves the task and check the names or context it exposes.
Do not move private comments into the main text as a workaround. If you need to preserve a decision for your team, retain it in the internal working version or another approved record.
A second person reading the sharing copy can be useful here. They may notice a note that feels ordinary to the writer but makes little sense outside the original team.
Run Document Inspector deliberately
In supported desktop versions, the inspection controls are under File, Info, Check for Issues, then Inspect Document. Review the available inspection categories rather than clicking every removal button automatically.
The inspector may identify properties, personal information, comments, revisions, hidden text and other elements depending on the file and version. Read each result and decide whether the content should remain.
Headers and footers deserve particular care. They may contain a private draft label, but they may also contain required page numbers, legal wording or the recipient's reference. Automatic removal can make the document less useful.
Run the inspection again after cleaning and saving. Treat it as one layer of review, not a promise that every meaningful disclosure has been found. The words on the page can reveal more than the author property ever did.
Check visible clues the inspector cannot judge for you
Read the title page, signature blocks, sample data, embedded screenshots and example filenames. A template may still contain another client's name. An image can show browser tabs, usernames or a desktop notification.
Follow the screenshot-sharing checklist for embedded images. For a photo, check photo metadata and visible details before inserting it into the document.
Review hyperlinks as well. The visible words may be harmless while the destination includes a private workspace, document identifier or access token. Link only to material the recipient is supposed to reach.
Check alternate versions in the same folder. Preparing one clean document is not enough if the attachment picker makes it easy to select the original draft beside it.
Choose the final format based on the task
Send an editable Word file when the recipient genuinely needs to edit it. For a fixed reading copy, a PDF may be appropriate, but conversion is not a substitute for inspecting the source and output.
After exporting, open the PDF separately and check its metadata, comments and attachments. If you need to remove specific sensitive text, use the PDF redaction workflow. A black shape in Word or a covered passage in a PDF is not automatically permanent redaction.
Avoid converting confidential documents through an unknown website simply because it appears first in search. The online converter privacy guide explains how to check whether a tool uploads the file and whether a local workflow would be more suitable.
For formal applications, follow the recipient's accepted formats and size limits. A beautifully cleaned file is not useful if the portal rejects it.
Inspect the attachment as the recipient will receive it
Close the editor, open the saved sharing copy and read it without relying on the previous editing session. Confirm that the filename, revision state and content all match the intended version.
Attach that file to a draft message, then open the attachment preview or downloaded copy before sending. Check the recipient address and remove any unrelated file left in the draft.
Keep the original working document separate from the final copy. That gives you a clear record of what was shared and preserves the internal material you deliberately left out.
The Photos & metadata topic covers the same principle across other file types: cleanup should be a repeatable handoff step, not a last-second attempt to make a document look tidy.
Sources and further reading
- Microsoft Support: Inspect documents for hidden data and personal information Consulted 28 September 2026.
- Microsoft Support: Track changes in Word Consulted 28 September 2026.
Consult the linked documentation for current details. Settings, availability and interface labels may change.
Spotted something that needs correcting? Send a correction with this article’s title and the relevant source.