Inspect revision-save markers in a Word document

A Word .docx can contain revision-save identifiers in its XML. This tool groups the identifiers it finds in body markup; it does not recover true revision history or prove who wrote the text.

The file is read in this browser page. Its filename, contents, metadata, markers, counts, and report results are not sent to analytics.

Analyse a document

Drop a .docx here

or

Nothing is uploaded. The file is read here, in this page.

What this is not

Draft Record reports a limited property of one DOCX package. It returns no authorship verdict, does not authenticate the file, and does not determine whether AI assistance was used.

What this cannot tell you

Questions

Does my document leave this browser page?

The current tool reads the selected file in browser memory and has no document-upload request. The two allowed product events are property-free, so they cannot include a filename, document content, marker, count, or result.

Does this prove I wrote my document?

No. Revision-save identifiers do not name an author, authenticate a file, or reconstruct a complete chronology. Treat the output only as a report of markers present in the inspected package.

What does a result with no markers mean?

Only that the inspected body markup contained no revision-save identifiers the parser reports. It is not evidence about authorship, conduct, or the process used to create the file.

Can I use the report in an academic review?

You may decide to include it as one limited artifact, with its caveats attached. Draft Record makes no claim about admissibility, evidential weight, institutional acceptance, or outcome.

What if I wrote in Google Docs?

Use Google Docs' own cloud version-history view. Draft Record cannot retrieve that history from an exported DOCX and makes no universal claim about which markers an export will contain.