XLSX Deep Inspector & Cleaner

An .xlsx file is a ZIP archive of XML parts. Data persists in places the grid never shows: pivot cache records keep a full snapshot of a source table even after you delete the sheet it came from; data connections and Power Query store connection strings and SQL; external links embed the full file path of another workbook on your disk or network; document properties carry author and last-modified-by names; and hidden or very-hidden sheets stay in the file. Deleting the visible cells removes none of this.

Yes. When a macro-enabled file contains a vbaProject.bin, the tool parses the OLE compound file and decompresses the VBA module streams (MS-OVBA) to recover the macro source directly in your browser, so you can review exactly what the macros do before deciding to strip them.

No. The file is read, inspected, and rebuilt entirely in your browser with JavaScript. Nothing is sent to mlab or any server. Closing the tab discards everything.

Yes. When you purge a part the tool also prunes its relationships and content-type overrides so the package stays valid. Because purging removes features (macros, connections, pivot cache), Excel may show a one-time notice that it removed unreadable content the first time you open the file. Saving once in Excel finalises the clean workbook.

A PivotTable keeps its own copy of the source rows (the pivot cache) so it can recompute without re-reading the source. That cached snapshot lives in the file even if you delete or restrict the original data sheet, so a workbook that looks summarised can still carry every underlying row. This tool empties the pivot cache records so only the summary remains.