Neatbo.

Finalize DOCX text revisions and classic comments

Accept or reject supported DOCX run-level text revisions, delete classic comment structures and stop future revision tracking.

Browser-local processingInputLocal DOCX review copyOutputFinal DOCX / full change reportUp to 30 MiB per file · File limit: 1
  1. 1Add input
  2. 2Adjust settings
  3. 3Get your result

Tool input and files are processed in this browser without being uploaded.

Your input

Inputs are kept temporarily in this tab when switching tools. Refreshing or closing clears them; large results may need to be regenerated.

⌘ / Ctrl + Enter to run

or drag and drop it here

Files stay on this device. Your originals stay unchanged.

.docx

Up to 30 MiB per file · File limit: 1

    Options

    Complete the required options first. You can keep the defaults for the rest.

    Preparing the tool…

    Before you start

    Choose an ordinary DOCX and a finalization policy. Accept keeps inserted text and removes deleted text; reject keeps deleted text as ordinary text and removes insertions. Classic comments, their actual relationship targets and content-type declarations are removed. Keep original files for review.

    How to use this tool

    1. Choose DOCX and accept or reject all supported text revisions.
    2. Review full story counts, removed comment parts and tracking settings.
    3. Download the real final DOCX and complete change JSON/CSV.

    Supported inputs and limits

    One30MiB unsigned/nonmacro/nonencrypted DOCX; ZIP≤80MiB expanded/10,000 entries, total XML20MiB/1,000,000 elements; each XML≤200,000 elements/depth128 and UTF8 XML1.0. Whole-package preflight runs before any output.

    Only direct paragraph wrappers around ordinary text runs in main/header/footer/footnotes/endnotes stories. Complex field/property/paragraph-mark/table-cell/move/customXML/conflict or nested revisions, wrapper-local namespace bindings, nontext revised run objects and modern comments/people cause whole-package refusal. Ordinary unrevised parts retain bytes. Stopping tracking is not metadata anonymity or forensic erasure; no universal Word pagination claim.

    Worked example

    Example input

    Real DOCX body,header,footer,footnotes,endnotes each contain one insertion and one deletion, plus classic comments and active tracking.
    Example options
    {"policy":"accept"}

    Example output

    Accept:5 insertions retained/5 deletions removed;3 classic comment markers removed,1 tracking setting removed. Reject restores previous body/header/footer/note text.

    When something does not work

    Open complex files in a full document editor, resolve unsupported revisions/comments, then provide an ordinary supported DOCX. Correct malformed package targets/CRC or budgets and rerun.

    Frequently asked questions

    Does hiding markup finalize the file?

    No. This tool changes supported XML text revisions and deletes classic comment parts/relationships. Hiding a review display leaves revision history; complex or modern review structures are rejected instead of silently retained.

    Documentation & further reading

    Finalize local file deliveries with complete evidence →Make file edits auditable →

    Related tools