How to wipe author, company, and edit history from excel files
- Step 1Finalise and save as .xlsx — Make your last edit and save. Note that saving itself rewrites `cp:lastModifiedBy` to your name — so wipe metadata as the final step, after the last save.
.xlsmmacro workbooks carry the samedocPropsstructure and can be wiped the same way. - Step 2Open the wiper — The Excel Core Metadata Wiper opens the Office Doc Property Wiper (Pro tier). It accepts
.docx,.xlsx, and.pptx, and can take multiple files at once for batch wiping a folder of deliverables. - Step 3Drop the workbook in — JSZip unpacks the OOXML container in your browser. Nothing is transmitted — the parse, the deletions, and the repack all happen on your machine.
- Step 4Run the wipe — The tool matches
docProps/(core|app|custom).xml,docProps/thumbnail.(jpeg|png), and any Excel comment/person XML against its removal patterns and deletes every match from the archive. The result reportsremovedEntries— the count of XML files actually pulled out. - Step 5Download the cleaned workbook — The repacked
.xlsxdownloads as a blob. Because the property files are gone (not zeroed), there is nothing for a recipient to recover from the container — Excel regenerates emptydocPropson next save. - Step 6Verify in File → Info — Open the file and check File → Info → Properties: Author, Last Modified By, Company, and any custom properties read blank. Cross-check the Windows Explorer Details tab too — its Author column reads from the same
docProps/core.xmlyou just removed.
What the wiper does to each metadata source
The Office Doc Property Wiper removes whole XML entries from the OOXML ZIP rather than editing fields. This table maps each Excel-visible metadata source to its file inside the container and whether the wiper touches it.
| Metadata you see in Excel | Lives in (OOXML path) | Wiper action | Recoverable after? |
|---|---|---|---|
Author (dc:creator) | docProps/core.xml | Entry deleted from the ZIP | No — file removed, not blanked |
Last Modified By (cp:lastModifiedBy) | docProps/core.xml | Entry deleted | No |
| Created / Modified / Last Printed dates | docProps/core.xml | Entry deleted | No |
| Company, Manager, Application, AppVersion | docProps/app.xml | Entry deleted | No |
| Custom properties (SharePoint, scripts) | docProps/custom.xml | Entry deleted | No |
| Thumbnail preview of last-active sheet | docProps/thumbnail.(jpeg|png) | Entry deleted | No |
| Cell comments / threaded comments / authors | xl/comments*.xml, xl/threadedComments/, xl/persons/ | Entry deleted (also see Comment Purger) | No |
| Cell values, formulas, charts, named ranges | xl/worksheets/, xl/charts/, xl/workbook.xml | Untouched | Preserved exactly |
| VBA macros | xl/vbaProject.bin | Untouched (use VBA Macro Stripper) | Preserved |
Tier limits for the wiper
The Core Metadata Wiper requires Pro tier. File-size and batch limits follow the JAD excel family. Processing is in-browser, so the practical ceiling is your machine's RAM, not a server quota.
| Tier | Max file size | Files per batch | Available? |
|---|---|---|---|
| Free | 5 MB | 1 | No — wiper needs Pro |
| Pro | 50 MB | 5 | Yes |
| Pro-media | 200 MB | 20 | Yes |
| Developer | 500 MB | Unlimited | Yes |
Cookbook
Real File → Info states from workbooks before and after wiping. Names anonymised; the XML field names are the literal OOXML element names.
What a client sees in an unwiped model
Before wiping, the raw docProps/core.xml exposes the full reviewer chain. Anyone who unzips the .xlsx (or just opens File → Info) reads it. The wiper deletes the entire file.
docProps/core.xml (before): <cp:coreProperties> <dc:creator>j.harrington@acme-internal.com</dc:creator> <cp:lastModifiedBy>Priya Nair (Senior Reviewer)</cp:lastModifiedBy> <dcterms:created>2026-01-14T09:02:00Z</dcterms:created> <dcterms:modified>2026-06-09T17:41:00Z</dcterms:modified> <cp:revision>47</cp:revision> </cp:coreProperties> After wiping: docProps/core.xml → (file no longer present in the ZIP) removedEntries: 3 (core.xml, app.xml, thumbnail.jpeg)
Company name hiding in app.xml
Most people clean the Author and forget docProps/app.xml, which carries the Company field and the exact Excel build. The wiper removes app.xml in the same pass.
docProps/app.xml (before): <Properties> <Application>Microsoft Excel</Application> <AppVersion>16.0300</AppVersion> <Company>Acme Capital Partners LLP</Company> <Manager>D. Okafor</Manager> </Properties> After wiping: docProps/app.xml → removed Excel regenerates a minimal app.xml on the recipient's next save.
Custom properties from a document-management system
SharePoint, iManage, and template macros stamp custom properties into docProps/custom.xml — internal matter numbers, classification labels, template IDs. These are invisible in the standard Properties panel but visible to anyone who unzips the file.
docProps/custom.xml (before): <Properties> <property name="_dlc_DocId">ACME-FIN-2026-00412</property> <property name="Classification">INTERNAL — RESTRICTED</property> <property name="TemplateId">fin-model-v9</property> </Properties> After wiping: docProps/custom.xml → removed (one of the removedEntries)
Batch-wiping a folder of deliverables
The Office Doc Property Wiper accepts multiple files. Drop a quarter's worth of workbooks and each is unpacked, stripped, and repacked independently. Pro tier allows 5 files per batch; Developer is unlimited.
Selected (Pro tier, batch of 5): q2-revenue-model.xlsx q2-cohort-analysis.xlsx q2-headcount.xlsx q2-scenario-deck.pptx (PowerPoint — also OOXML, also wiped) q2-board-memo.docx (Word — also wiped) Each output: removedEntries: 2-4 (varies by which docProps files existed) All five download as cleaned blobs.
Last-saved-by reappears after you re-edit
A common trap: wipe the file, then open it and make one more tweak. Excel writes your name back into a fresh core.xml on save. Always wipe AFTER the final save.
Workflow that LEAKS:
1. wipe model.xlsx → core.xml removed, Author blank
2. open in Excel, fix a typo
3. Ctrl+S → Excel writes new core.xml:
<cp:lastModifiedBy>your.name</cp:lastModifiedBy>
4. send → recipient sees your.name
Correct order:
1. open, fix typo, Ctrl+S
2. wipe model.xlsx → last step
3. send → Author/Last Modified By blankEdge cases and what actually happens
Password-protected (encrypted) .xlsx
Cannot processA workbook saved with Excel's File → Info → Protect Workbook → Encrypt with Password is wrapped in a CFB/OLE encryption envelope — the inner OOXML ZIP is encrypted, so JSZip cannot read docProps/ to remove it. The wipe fails on load. Remove the open-password in Excel first (File → Info → Protect Workbook → Encrypt, clear the password, save), wipe, then re-apply protection if needed.
Re-saving after wipe re-stamps your name
ExpectedThe wiper deletes core.xml, but Excel regenerates docProps/core.xml with cp:lastModifiedBy = your account name the moment you save again. This is Excel behaviour, not a wiper bug. Always make the wipe the final step before distribution, and never re-open-and-save the cleaned copy.
Old-format .xls (BIFF8) file
Unsupported formatLegacy .xls files use the binary BIFF8 format, not the OOXML ZIP container. There is no docProps/ folder to unzip, so the wiper has nothing to act on. Open the file in Excel and Save As .xlsx first, then wipe the converted copy.
Author name embedded inside a cell or sheet name
Out of scopeThe wiper only removes property XML files. If a creator's name appears in a cell value, a header, a sheet tab name, or a chart title, that text lives in xl/worksheets/ and survives untouched. Use a find-and-replace pass — for example CSV Find & Replace on an exported sheet — to scrub names from content.
Cell comments and threaded comments
RemovedComment author names live in xl/comments*.xml, xl/threadedComments/, and xl/persons/. The Office Doc Property Wiper's patterns include these, so they are removed alongside docProps. If you specifically want to purge only comments while keeping document properties, use the dedicated Comment & Note Purger instead.
VBA macro module author
PreservedVBA project metadata (including the macro author and module names) is stored in xl/vbaProject.bin, a binary blob the wiper deliberately leaves intact so your automation keeps working. If the macro project itself is sensitive, remove it with the VBA Macro Stripper (Developer tier).
File over the tier size limit
413-style rejectPro tier caps each file at 50 MB, Pro-media at 200 MB, Developer at 500 MB. A workbook past your tier's ceiling is rejected before processing with an upgrade prompt. Most metadata-laden models are well under these — a 50 MB workbook is unusual unless it embeds large images or many sheets.
Tracked changes / revision marks
Not removedPer the tool's own FAQ, change-tracking nodes are not stripped — in Excel they live in the shared-workbook revision log, not in docProps. Turn off and accept all tracked changes in Excel (Review → Track Changes) before wiping if revision history must not leak.
Workbook digitally signed
Signature invalidatedRemoving files from the OOXML container changes the package, which invalidates any digital signature (xl/_xmlsignatures/). This is correct cryptographic behaviour — the signature covered the original bytes. Re-sign the cleaned workbook in Excel if a signature is required for the recipient.
Frequently asked questions
Does this actually delete the metadata or just hide it?
It deletes it. The wiper uses JSZip to remove the docProps/core.xml, docProps/app.xml, and docProps/custom.xml entries from the ZIP entirely — the files are no longer present in the archive, not blanked or zeroed. There is nothing for a recipient to undo or recover; the result reports removedEntries as the count of XML files pulled out.
Will the file content, formulas, or formatting change?
No. The wiper only touches files under docProps/ and the comment/person XML. Worksheet data (xl/worksheets/), formulas, charts, conditional formatting, named ranges, and pivot caches are left byte-for-byte intact. Open the cleaned file and every cell behaves exactly as before.
Why does the Author field come back after I edit the file again?
Excel regenerates docProps/core.xml with your account name in cp:lastModifiedBy every time you save. The wipe is correct at the moment you run it; re-opening and saving re-stamps the metadata. Make the wipe the final step before you share, and don't re-save the cleaned copy.
Does this work on .xlsm macro-enabled workbooks?
Yes. .xlsm uses the same OOXML ZIP container and the same docProps/ structure, so the property files are removed identically. The macro project in xl/vbaProject.bin is preserved — if you also want the macros gone, run the VBA Macro Stripper afterward.
Is the file uploaded anywhere?
No. JSZip unpacks, edits, and repacks the workbook entirely in your browser. Confidential cell data never reaches a JAD server. The tool does emit a local audit-log entry (file processed, no content) for compliance dashboards, which you can review in your account.
What tier do I need?
Pro. The Core Metadata Wiper runs through the Office Doc Property Wiper, which requires Pro tier. Pro allows files up to 50 MB and 5 files per batch; Pro-media raises that to 200 MB / 20 files; Developer to 500 MB / unlimited.
Does it remove cell comments and the names attached to them?
Yes. The wiper's removal patterns include xl/comments*.xml, xl/threadedComments/, and xl/persons/, so comment text and the author names attached to threaded comments are deleted in the same pass. For comment-only removal that keeps document properties, use the Comment & Note Purger.
Can a recipient recover the original Author with forensic tools?
Not from the file. Because the XML entries are deleted from the archive (not overwritten with spaces), there is no residual property data in the cleaned .xlsx. The only way the original name resurfaces is if the recipient has an older copy of the file, or if you re-saved the workbook in Excel after wiping.
Does it also clear the Author shown in Windows File Explorer?
Yes. The Author/Title columns in Explorer's Details pane and the right-click → Properties → Details tab read directly from docProps/core.xml. Once the wiper removes that file, Explorer shows the Author as empty.
What about the thumbnail preview image?
It is removed. docProps/thumbnail.jpeg (or .png) is a snapshot of the active sheet at last save — it can leak a view of data you thought was hidden in a collapsed group or off-screen. The wiper's patterns match and delete it.
Will a digital signature survive the wipe?
No, and that is correct. Removing entries changes the package bytes, which invalidates any embedded digital signature because the signature covered the original content. Wipe first, then re-sign the cleaned workbook in Excel if the recipient requires a signature.
Can I run this in an automated pipeline?
Yes. Pair the @jadapps local runner once, then dispatch the office-doc-property-wiper job from your machine — the workbook is processed locally by the runner, so content never leaves your network. A common flow is a pre-send hook that wipes every .xlsx in an outbound folder before it reaches the client.
Privacy first
Every JAD Excel tool runs entirely in your browser using SheetJS and ExcelJS. Your spreadsheets, formulas, and data never leave your device — verified by zero outbound network requests during processing.