What this checks. Everything the CMS/WET genuinely cannot represent β€” custom styles, dynamic fields, missing alt text, unmarked table headers, text boxes, tracked changes, and more β€” with plain-language fix instructions. This is the last stop before the document goes to a coder: if anything below is red, the Converter tool will refuse to run against this file. Use "Flatten for Coding" to auto-resolve the mechanical subset.

Everything runs locally in this browser tab β€” the file is never uploaded anywhere.
πŸ“„
Drop a .docx file here
or click to browse β€” everything runs locally, nothing is uploaded
βš™
ANALYSING…
βœ– Error
πŸ“„
πŸ§ͺ
Try Beta Auto-Resolve
Experimental: takes a best-guess position on EVERY blocker above (including footnotes, outline numbering, equations, custom styles, nested tables) β€” not just the mechanical ones Flatten below handles. Re-upload this file there.
Open Beta Tool β†’
πŸ”§
Flatten for Coding
Automatically resolve mechanical issues β€” outputs a new .docx
β–Ά
What this does and doesn't do. Resolves mechanical, unambiguous issues only β€” accepts tracked changes, strips comments, resolves cached field values to static text, removes page breaks, strips dynamic bibliography containers. Outputs a new .docx plus a plain-English changelog.

It cannot make editorial decisions. Items marked Needs human decision are skipped and stay flagged in the report.

Always review the output. Cached field values may be stale if the document wasn't refreshed before submission.