Does WordCraft Keep Word Comments and Tracked Changes? I Tested It

By Si Fisher · Published October 13, 2026 · Tested and sources checked October 13, 2026

WordCraft is a free, open-source word processor. When someone sends you a reviewed Word document, comments are their notes and tracked changes show edits you can accept or reject. Will those notes and edits still be there after you work on the file? In my one-file test of WordCraft’s 0.6.1 browser build, yes. I opened an already reviewed document, made an unrelated edit, saved it and reopened it. The comment and both tracked edits survived.

That is a reason to try WordCraft on a copy, not a promise that every client document will work. My sample was synthetic and simple. If a review handoff matters, rehearse the exact file with the person who will receive it.

What did I put through WordCraft?

The developer says WordCraft can read and write Word’s DOCX files, show comments and handle tracked changes. That feature list does not tell you whether incoming review marks survive a round trip. I used the official 0.6.1 browser release from October 12, verified its downloaded file against the developer’s checksum and opened it locally.

My one-page test document was made for this article, with no real client information. “Morgan Reviewer” is a fictional reviewer in that file, with a comment attached to “Awaiting client approval” and a proposed delivery day changed from Friday to Monday. I added only “Local trial edit completed.” to a separate internal note. I did not accept, reject or deliberately alter the review marks.

The distinction matters because HeroicSteps’ October 11 video showed comments and tracked edits created inside WordCraft 0.5.0 for Mac and seen after export to Word. My test starts with another person’s marks already in the DOCX and uses a later browser build.

Did the comment and changes survive?

Yes, for this file. I checked more than whether the final paragraph looked right. A flattened page can display the words while losing who commented or which edits are still pending.

Opened with review marks

WordCraft displayed Morgan’s comment alongside the document and showed Friday struck through with Monday inserted.

Saved copy reopened

The saved DOCX reopened in WordCraft with the same comment, tracked date edit and my one new sentence visible.

Word recognized the history

An independent read-only check in Microsoft Word found one comment and two pending revisions, with Morgan’s name and the original text intact.

Reopened WordCraft document shows Friday struck through and Monday inserted in the proposed delivery dateMorgan Reviewer comment balloon in the same reopened WordCraft screenshot
Tight authentic crops of the tracked date edit and the fictional reviewer note in my reopened synthetic document. Open either for the full view. Independent Word and file checks support the saved-file finding.

I also inspected the saved DOCX’s internal review records. The comment still had its anchor, text and reviewer; the deletion and insertion still had their original words and reviewer. WordCraft changed internal revision ID numbers while saving, which is normal for a rewritten file and did not remove the review content. I am not calling the output byte-for-byte identical or promising identical layout in every document.

How should you check your own reviewed Word file?

If a colleague expects to keep approving changes or answering comments, test the actual handoff before changing the team’s editor. A successful open is only the first half of the check.

  1. Make a copy of the original DOCX. Keep the untouched file outside the experiment.
  2. Note a real comment and pending edit. Record the reviewer, comment text and a changed phrase you can recognize later.
  3. Edit somewhere else, then save and reopen. Use a new filename. Do not accept or reject the review marks just to make the test pass.
  4. Compare the review trail. Check the reopened file and, if you share it, open that saved copy in the exact app your recipient uses. Confirm the comment, author, changed words and ordinary edit. Keep using your current editor for this handoff if any important mark is missing.
Four-step reviewed DOCX check: copy the original, note an existing comment and edit, save and reopen, then compare the review trail
Use this sequence on a copy of your own file. Repeat the final check in your recipient’s exact app and version; my independent read-only check used Microsoft Word 16.0.

Does this mean WordCraft can replace Word for your team?

Not from one small file. I tested a synthetic comment and one deletion/insertion pair in the 0.6.1 WebAssembly build. I did not test a real client’s long document, threaded replies, tracked formatting, complex tables, accessibility, collaboration, layout fidelity or the Windows/Mac/Linux installers. Those are reasons to try the copy-first check on the file that matters, not to dismiss a result that did work.

There is one browser-method wrinkle. In this controlled browser session, the normal save-location picker stayed active and did not return a file I could inspect. I kept that failed attempt on record. For the fresh run, my local test page disabled that picker so WordCraft would use its own built-in download fallback. The editor code and the test document were unchanged; the saved copy passed the reopen and independent checks above. I did not verify the normal picker experience in this browser, and a browser-host glitch alone says nothing about the DOCX content.

If your own reviewed file passes and the recipient can still work with the comments and changes, WordCraft may suit that job. If you’re choosing an entire office suite rather than testing one handoff, see my broader Office 2024, Microsoft 365 and free-tools comparison. Keep the original DOCX either way; there is no prize for making a client document your first compatibility experiment.

Quick questions

Can WordCraft keep every Word comment and tracked change?

I cannot conclude that from one synthetic file. This test preserved one pre-existing anchored comment and a Friday-to-Monday tracked edit through the official 0.6.1 browser build. Check a copy of your actual document, especially if its review history is more complex.

Did you test the desktop WordCraft app?

No. I used the official WebAssembly package served locally in a browser. The developer offers native downloads, but this result is limited to the browser build and the saved file described here.

Sources and test method

I checked sources and tested on October 13, 2026. The browser test used the official 0.6.1 web archive with a checksum matching the developer’s published file. The synthetic input was validated before the run with a read-only Word check. I kept the input, first blocked save attempt, successful downloaded DOCX, screenshots and independent file/Word readbacks. Only the successful fallback run supports the preservation result. Corrections or materially different file results can be sent to hello@theprotoolkit.com.

Leave a Comment