To remove tracked changes in Word, open the Review tab and accept or reject the revisions you want to resolve. Delete comments separately. Turn off Track Changes if you want later edits to appear without revision marks. Save a separate copy for sharing and reopen it with all markup visible to check that the review items are gone.
No Markup changes what you see. It can leave revisions and comments in the file for someone else to display. If you need a clean delivery copy, resolve the underlying edits, delete comments that should be removed and use Word’s Document Inspector on a copy where supported. Keep the reviewed source if you still need its history.
- Make a separate delivery copy before removing review information.
- Use All Markup and check any reviewer or change-type filters.
- Accept changes you want to keep and reject the ones you want to discard.
- Delete comment threads when they should be removed rather than merely resolved.
- Inspect and reopen the saved copy before sharing it.
Work out what you need to remove
Word review information can include proposed edits and comment threads. An insertion, deletion or formatting change appears as a revision when it was tracked. A comment is a separate note attached to a part of the document. Turning off Track Changes stops future recording in the relevant setting. It does not settle revisions that are already present.
Decide whether the recipient wants review history or a clean copy
A reviewer may need to see every proposal and comment. A teacher grading the final version may want an ordinary document without those marks. If both are required, prepare separate files and use clear names. Make the delivery copy from the approved text and keep the review source in its allowed location.
Recognise the difference between display and removal
No Markup can make a page look like the final version. A reader who changes the view can still see revisions that remain in the document. Hiding review information can be useful for reading the flow, and it does not produce a clean delivery file. Use the actual Accept, Reject and Delete controls for removal.
Identify what the task requires beyond review items
Some submissions specify anonymous marking or forbid private annotations. Check the instructions for names in the visible text, headers, footers, filename and document properties. Resolve review items and verify those other areas separately. A clean paragraph does not establish that the whole file is ready.
Back to contents · Next section
Make a separate copy before changing review information
Use Save As or Save a Copy where available and give the working file a clear name. Confirm which copy is open before removing anything. If the document is shared in OneDrive or SharePoint, use the organisation’s approved route for making a separate delivery copy. Turning an active team review into a clean file can remove material the team still needs.
Preserve the decisions before making the clean copy
Read reviewer comments that require an answer and check whether their requested changes were made. A comment that says “verify this figure” should be resolved as a factual decision before you delete it. If a teacher asks to see how you acted on feedback, keep the approved review record. Use the clean copy for the recipient that should receive it.
Agree which source is current
A group might have a master document and two separate reviews. Confirm which version contains the latest approved wording before cleaning it. If several versions need comparison, run that review first. Removing markup from an old copy can give you a tidy document with outdated content.
Name the delivery copy according to the instructions
If the portal requires an exact name, apply it after the cleanup and keep the working copy in a separate folder. If you can choose, give the approved file a recognisable label. Do not infer from a filename containing “Final” that the file is free of review data. Open and inspect the candidate.
Back to contents · Next section
Show all relevant revisions before you accept or reject them
Open Review and choose an all-markup display in the version you use. Check any controls that filter change types or particular reviewers. A review pane or revision list can help you see what remains where available. Move through the document and read the affected lines in context.
Check the kinds of changes that matter
Insertions and deletions often get the most attention. Formatting changes can matter too. A heading level, bold emphasis or table layout can affect how the final document reads. Review significant edits in headings, footnotes, captions and tables. If the document is long, start with the areas the recipient will rely on and use the available navigation to inspect the rest.
Verify facts before settling a revision
Suppose a reviewer changes a number from 12 to 21. Accept keeps the proposed value. Reject restores the previous wording or value in the tracked context. Neither choice establishes that the number is correct. Check the source evidence or ask the responsible person, then resolve the change.
Recheck filters before using a bulk command
Some controls distinguish all changes from the changes currently shown. Read the action label before using it. If you intend to resolve every revision, check that you are using the command for the full document where your version provides one. Review the result and re-open the full markup view before sharing.
Back to contents · Next section
Accept or reject tracked changes in Word
Use Review and the Accept or Reject controls to settle changes. Review them one by one when proposals differ in quality or consequences. Accept the edit when the proposed content belongs in the final version. Reject it when the prior wording should remain. Read the resulting sentence or table row after making a meaningful change.
Accept all only after approving the revised content
A bulk accept can be appropriate when every proposed change has already been reviewed and approved. Check the underlying document and the scope of the command first. A marked deletion can remove a full paragraph when accepted. If you still need part of it, resolve the proposal deliberately rather than clearing all marks at once.
Reject all only when the earlier content is intended
A bulk reject can discard useful edits. Use it only when the approved outcome calls for it. Save and inspect the result. If the recipient needs one corrected section and the rest of the newer document, handle those edits individually or recover the relevant text using the agreed workflow.
Turn off tracking for later clean edits
After resolving existing revisions, turn off Track Changes if you need subsequent edits to be ordinary untracked edits and your permissions allow it. If tracking is locked or controlled by an organisation, follow the owner’s process. Check the result after any final edits. Existing markup and future tracking are separate controls.
Back to contents · Next section
Delete comments, including resolved threads when appropriate
Review comments as separate items. In modern comments, use the thread’s menu and choose the applicable delete action. Desktop Word can also offer a Delete All Comments in Document command depending on version and interface. Use the exact action that fits the approved scope. Check the comments pane after saving.
A resolved thread can still be present
Resolving a comment records that a discussion is complete. Depending on the view, the resolved thread can still be available in the document. If the delivery requires comments to be removed, delete the relevant threads rather than relying on the resolved state. Verify the saved copy through its comments controls.
Keep needed feedback in the review copy
If a teacher provided comments on an assignment, keep the reviewed original under the school’s rules. If you need a clean revised version, make it from the correct source and apply the feedback before removing the comments. For work with a formal approval trail, use the organisation’s recordkeeping process before deleting review information from the copy you will send.
Inspect comments on tables and captions
Review notes can be attached to a footnote, figure caption or table cell. Opening the first page gives only a partial check. Use the comments pane or available navigation and confirm that the approved output has no threads that should have been removed.
Back to contents · Next section
Use Document Inspector when the delivery needs a hidden-data check
Microsoft documents Document Inspector for supported Windows desktop Word workflows. On a copy, use File, Info, Check for Issues and Inspect Document where available. Choose the categories that fit the task and inspect the results. Review what the inspector found before removing it. Some removals cannot be easily reversed, which is why the editable original matters.
Inspect the categories the brief actually requires
A document can contain comments, revisions, properties or other information beyond the visible body text. The relevant categories depend on the file and app version. If the recipient asks for anonymous marking, review what the brief says about identifying information. Inspect the visible headings and footers too. Removing document properties does not remove a name typed into the text.
Review findings before removing them
The inspector can report content that is required in the deliverable. A footer, for example, may contain both a required page number and identifying text that must be removed. Use the appropriate editing or removal process for the actual requirement. Review the output after applying any changes and run the relevant checks again where supported.
Use a suitable workflow on Mac or the web
Microsoft states that Word for Mac does not have the same Document Inspector. Use the visible review and document-property controls where appropriate. If the task requires the supported Windows inspection workflow, use an approved device or ask the responsible person to run it. A clean view in the web editor does not establish that every hidden-data check was done.
Back to contents · Next section
Check what the recipient will receive
Close the working window and open the saved delivery copy from the folder you intend to use. Switch to a view that shows all relevant markup. Check the comments pane, the first page, any table with revisions and the final page. Review the required filename and document properties where they matter. If a clean PDF is requested, export the approved Word copy and inspect that PDF separately.
Check the actual contents after a bulk action
Compare the final text with the decisions you made. If an edited heading or date is wrong, return to the approved source or working copy and repair it. Do not assume that clearing the marks preserved every intended edit. The final copy should contain the approved material and be usable without relying on the original reviewer’s context.
Recheck after one last correction
A writer can turn tracking back on during a final edit or reintroduce material by copying from a review draft. Reopen the exact file again after changing it. Check the corrected section and the document’s review state. Use the official replacement process if an earlier version was already submitted.
Back to contents · Next section
Work through an anonymous school submission
A student has a report with tracked teacher suggestions, two comments and their name in a footer. The school asks for a clean anonymous Word copy. The student preserves the reviewed source, creates a delivery copy and reads the suggestions. They verify a date before accepting that correction, reject an unrelated change and apply the teacher’s requested revision. They delete the comments in the delivery copy after addressing them.
Next they inspect the visible header and footer, and follow the school’s approved checks for other identifying information. They save the file under the required identifier and reopen it. In a full markup view, there are no remaining revisions or comments intended for removal. They verify the date, footer and filename before uploading.
Change the request and keep both outputs distinct
If the teacher also wants the marked draft, retain it as a separate approved item. Label the two copies clearly and attach each in the correct field. Do not use the clean copy for a question that asks you to show revisions. The recipient’s requirements determine which review information should remain in each file.
Back to contents · Next section
Learn what the same sentence looks like in four review states
Use a test file with a sentence you can safely change. Start with “The display opens at 9.” Turn on Track Changes in the test copy and replace 9 with 10. In a full markup view, Word can show the old and proposed times. In No Markup, the page may display only the proposed wording. Switch back to the full view and notice that the edit is still present.
Stop tracking and check what remains
Turn off tracking in the test file. The 9-to-10 revision remains available until you settle it. Add a new sentence after turning tracking off and compare it with the earlier revision. The new sentence can be ordinary text while the old edit is still marked. This exercise explains why turning off the feature and removing existing marks are separate steps.
Accept and reject in different copies
Make two test copies. Accept the change in one and reject it in the other. The accepted copy says the display opens at 10, while the rejected copy retains the earlier time. Both can look clean afterward. A clean appearance alone cannot tell you whether the correct time was kept. Read the final wording and verify it against the instruction.
Resolve and delete a comment in different copies
Add a harmless comment to the test sentence. Resolve it in one copy and delete it in the other. Look at the comments pane and its available filters. In a version that keeps resolved threads, you may still be able to find the discussion after resolving it. Deletion serves the separate purpose of removing the thread from the delivery copy.
Back to contents · Next section
Resolve edits with more than one possible outcome
A reviewer might propose replacing an entire paragraph even though only one sentence needs repair. Read the old and proposed passages. Decide what the approved wording should say. If neither version is suitable as written, resolve the proposal and make the agreed edit in the working copy. Check the review state afterward so the new wording does not unintentionally create another marked revision.
A deletion contains material you still need
Imagine an edit removes a method paragraph that includes an essential safety note for a classroom exercise. Check the actual approved procedure and determine whether the note belongs elsewhere. Keep the required wording in the correct place before making a clean copy. Accepting the deletion without reading the full paragraph could omit an instruction the reader needs.
An insertion duplicates another section
A colleague adds an explanation near a chart, and the same explanation already appears under a heading elsewhere. Compare both locations. Keep the wording where it fits the final document and check any references. An edit may improve one page and repeat a sentence unnecessarily across the whole report. Review the result as a reader, not only as a list of accepted edits.
A formatting revision changes the hierarchy
A heading may be changed to ordinary text or a list may lose its indentation. Check whether the new format is intentional. If the document uses an automatic contents page, verify the relevant heading and update the contents where needed. Cleaning marks should preserve the structure that lets the recipient navigate the document.
Back to contents · Next section
Check every visible place where review material can appear
Work through the actual file from its cover to the last page. Review headings, tables, image captions, footnotes, headers and footers. Use the review pane or comment navigation to locate items, then open the affected area. A hidden display setting can make the page look clean until you inspect all the relevant markup.
A comment is attached to a table cell
Open the comments controls and locate the thread. Read the cell and the rest of the row. If the comment asked you to confirm a number, compare it with the approved data before deleting the thread. Make the correction if needed. Then reopen the saved document and check that the row and surrounding labels are correct.
A name is visible in a footer and document properties
A student submitting anonymously might remove the name from the title page and miss the footer. Check all sections because they can use different headers or footers. Use the approved document-property check too. If a page number is required, preserve it while removing the identifying text. Verify the final file’s visible pages and filename in addition to the review state.
A note was copied in from a different draft
If you paste from a marked-up version during the last edit, check the result again. The inserted text or accompanying document structure may carry review material depending on the workflow. Use a separate delivery copy and inspect it after the final change. Check which text actually appears, rather than assuming that the earlier cleanup still describes the new file.
Back to contents · Next section
Prepare a clean Word file and a clean PDF as two checks
If the recipient asks for both a DOCX and a PDF, first settle the approved Word text. Resolve revisions, delete comments where required and inspect the delivery copy. Then export from that copy. Review the PDF’s pages, margins and any area that previously contained a comment. Confirm it does not display unintended review marks.
Verify Word’s export choice when markup matters
Supported desktop Word export workflows can distinguish the document from a version showing markup. Use the appropriate choice and verify the result. A reviewer might need an annotated PDF, while a formal submission may require the approved clean text. Save the files with clear names and select the intended one in the portal.
Treat removal in the source and visual output separately
A PDF that looks clean does not establish that the DOCX is clean. Likewise, a clean Word file should still be checked after export because the PDF is the delivered version. Open both from their final location. Confirm that the Word file shows no unwanted review material and that the PDF displays the intended pages.
Check the final upload field
If the task wants an editable Word file, do not substitute a PDF simply because its marks are hidden or absent. If the task asks for a PDF, select the verified export. Read the accepted filename and available preview. Preserve the required review copy and clean delivery separately under the school or organisation’s rules.
Back to contents · Next section
Decide what to do when you cannot remove a mark
A control can be unavailable because you are in a viewing mode, using an app version with limited review features or working in a protected document. Check your role and the file’s intended workflow. Ask the owner for an authorised editable copy when appropriate. If the task requires Windows Document Inspector and you only have Word for Mac or the web, use the approved route for that check.
The comment menu does not offer the expected command
Check whether you are viewing a modern comment thread, a reply or a restricted document. Use the control that applies to the whole thread if the intent is to remove it. If you cannot make the required change, ask the owner or review coordinator. Keep the underlying feedback until the delivery copy has passed its check.
The revision pane still shows entries after a bulk action
Review whether the command acted on all changes or only those shown. Clear filters where appropriate and inspect the remaining items. Check for formatting revisions or changes from another reviewer. Resolve the relevant entries and verify the content after each important decision. A display count is useful, and the final wording still needs review.
The recipient can see a mark that you cannot reproduce
Ask which file they opened and which view they used. Check the actual uploaded or emailed copy where available. It may be the earlier reviewed draft, or it may use a different markup display. Open the same file with the full review view. If it contains material that should have been removed, use the recipient’s approved replacement process and identify the corrected copy.
Back to contents · Next section
Use a final handoff checklist for a team document
Agree which approved version will be cleaned and who is responsible for the delivery copy. Save it in the intended location. Confirm that the required revisions were resolved and that any comments the recipient should not receive have been deleted. Follow the relevant inspection and privacy process for the actual document. Reopen the exact copy from the delivery folder.
Assign responsibility for facts and presentation
The person removing marks may not be the one authorised to approve a figure or a policy statement. Verify substantive changes with the responsible person before accepting them. Once the content is approved, check the formatting and review state. This prevents the cleanup from becoming an unintended decision about what the document says.
Make the file easy to verify
Give the recipient the filename or delivery label required by the task. If separate clean and review files are authorised, distinguish them clearly. Open the clean copy again and look at a known changed passage. Check that the final wording matches the approval and that the comment or revision mark is gone. Confirm the file was actually sent through the intended route.
Preserve the correct history
Keep the approved reviewed source where the process requires it. A clean copy is useful to the reader, and the team may still need the marked version to understand earlier decisions. Follow retention requirements for both. If a correction is later needed, start from the approved source or verified clean copy as appropriate, and check the new deliverable before replacing the previous one.
Back to contents · Next section
Practise the cleanup on a short document before doing it for real
Create a harmless page with a tracked insertion, a tracked deletion and a comment. Make a separate delivery copy. Accept the insertion, reject the deletion and delete the comment. Open the resulting file in a full markup view. Confirm that the sentence you wanted to keep is there and that the rejected deletion did not remove needed wording.
Add a second check for a footer
Put a fictional identifier in the test footer and remove it from the delivery copy. Check whether the page number remains. If you have a supported inspection workflow, see which categories it identifies in the harmless test. Review any removal before applying it. Reopen the file and inspect the footer and review state separately.
Compare the practice result with the required task
If the real assignment requires anonymous marking, review its instructions in addition to applying the practice steps. If the real recipient wants comments retained, use a different delivery copy. The right cleanup scope comes from what the recipient should receive. Test the actual file after each significant change.
Back to contents · Next section
Confirm that cleanup did not change the intended document
Before submitting, reopen the approved file and find two or three important decisions from the review. Check a figure, a heading and any passage you edited during cleanup. Read them as ordinary text. If a large deletion or formatting change was accepted by mistake, return to the preserved working source and resolve that part deliberately. Export a fresh copy only after the content is right.
Where the recipient requires an anonymous or clean file, check the output with the approved review and inspection controls as well. Content and review data are separate checks. Save a new version when you correct either one, and reopen the exact copy you are about to send.
Back to contents · Frequently asked questions
Frequently asked questions
Does No Markup remove tracked changes?
No. It hides them in the current view. Accept or reject the revisions to settle them.
Does turning off Track Changes remove earlier marks?
It changes future tracking behaviour. Resolve existing revisions separately.
Does accepting changes delete comments?
Handle comments separately. Review and delete the comment threads that should not remain.
Can I keep changes while removing the marks?
Accept the approved revisions, then check the final wording and remove comments separately where required.
Is resolving a comment the same as deleting it?
A resolved thread can remain available. Delete it when the delivery requires removal.
Can I use Document Inspector on Word for Mac?
Microsoft says Word for Mac does not have the same inspector. Use the appropriate approved workflow for the checks your task requires.
How do I know the file is ready?
Reopen the exact delivery file, check all relevant markup and comments, and verify any additional hidden-data or anonymity requirements.
Why are there still changes after I accepted the ones I could see?
Check reviewer and change-type filters and whether the command applied only to the displayed changes. Reopen the full markup view and resolve the remaining revisions that belong in the cleanup.
Can I remove review data from a shared file without affecting the team?
Create an authorised delivery copy and clean that copy. Keep the shared review source available for people who still need it.
Will deleting one comment delete every thread?
Use the action that matches your scope. An individual thread action affects that thread, while the supported document-wide command applies more broadly. Check the comments pane afterward.
Helpful reading
- Microsoft Support on accepting revisions and deleting comments
- Microsoft Support on inspecting a Word document
- How to Redact a PDF and Check That the Information Is Gone
- How to Convert Word to PDF Without Changing the Formatting
- How to Convert PDF to Word and Keep the Formatting
- How to Compare Two Word Documents and Find What Changed
- How to Recover an Unsaved Word Document on Windows or Mac
Review the saved file before you send it
Resolve the changes, handle comments separately and check the delivered copy with the appropriate views and inspection controls. Keep the review source where the task requires it.