Cleanup is not available
This planned page does not scan media, strip revisions, or repack a ZIP.
Client-side · zero upload · OpenXML
Saving a file needs JavaScript. The explanation below is in the page HTML.
This planned page does not scan media, strip revisions, or repack a ZIP.
No cleanup drop. A file left here is not uploaded and is not cleaned.
| Topic | This browser | Server upload | By hand |
|---|---|---|---|
| Status | Not currently available as its own tool. | No cleanup package is uploaded. | Word can accept or reject changes itself. |
| Unreferenced media | A future scan could list media no relationship reaches. It does not run now. | An upload cleaner would need the file. This page does not send it. | You can inspect pictures in Word. |
| Comments | The splitter removes comments when it saves a chapter. This cleaner does not. | No comment file is uploaded here. | Word has its own comment review. |
| Revisions | Deleting w:ins or w:del markup can change visible text. That action is not offered. | A server could change text too. This page does not send the file. | Accepting a revision in Word changes the text you see. |
| Fields | TOC fields are not rewritten. Word may need F9. No ZIP repack runs here. | A remote fixer might refresh fields after upload. | Press F9 in Word to refresh a field. |
How this page works
Read that cleanup is planned
The page is not a working cleaner and it is not the splitter in disguise.
Leave the file unprocessed
The button does not remove media, comments, or revisions, and it does not upload the document.
Remember the revision boundary
If a later tool deletes revision markup, the visible words can change. It must not claim otherwise.
Under the hood
A cleaner is not currently available. This is a conditional design: the button does not edit or upload a file. A later JavaScript pass, not WebAssembly, could walk word/_rels/document.xml.rels and header, footer, and chart relationships, then list media nothing reaches. It could flag a contents field in word/document.xml without rewriting a correct cross-chapter directory. Word may still need F9. The splitter already removes comments when it saves a chapter. This separate cleaner does not. Revisions are stored as w:ins and w:del. Deleting that markup can change visible words, because kept text and deleted text differ. A future tool must say so and must not claim it never changes body text. Repacking the ZIP and [Content_Types].xml would belong to that later save. Charts and fields would remain stored markup. Until then, this page does not scan, clean, or repack anything.
Questions
Will this page clean my document?
No. Cleanup is not currently available. Clicking the button does not edit or upload a file.
Can revision cleanup avoid changing words?
No. Stored insertions and deletions are different text. Removing that markup can change the visible paragraph, so a future tool must say so.
Does the splitter already remove comments?
When the splitter saves a chapter, it removes comment markers from that saved part. This cleaner page does not run that save.
Are table-of-contents fields refreshed?
No. Fields stay as stored markup. A directory may need F9 in Word. This page does not promise a correct cross-chapter contents list.