Before sharing an Excel workbook, inspect a copy for metadata and hidden content, then review the visible cells, charts, comments, and identifiers separately. Document Inspector does not turn a workbook into an anonymous file, and a text-masking page cannot inspect or edit an Office package.
Start with a copy in a supported desktop version of Excel
Use Excel's built-in Document Inspector before any browser helper. Microsoft recommends working on a copy because some information removed by the inspector cannot be restored, even with Undo.
The current Microsoft Support page lists Excel for Microsoft 365, Excel 2024, Excel 2021, Excel 2019, and Excel 2016. The steps below are verified for those Windows desktop editions. Menu paths on Mac or the web should not be assumed to match; use the documentation for that edition or open the file in a supported desktop app.
For example, suppose a vendor workbook contains public price totals on the first sheet, hidden cost calculations on another sheet, reviewer comments, and customer email addresses in a sample row. Save a clearly named copy such as vendor-summary-share-copy.xlsx. Keep the original outside the folder used for outgoing attachments.
In the copy, choose File > Info > Check for Issues > Inspect Document. Select the categories that apply, run Inspect, and read each result before choosing Remove All. Reinspect after making changes. Clicking every removal button without understanding the result can damage useful information or change calculations.
Review what Document Inspector can remove and what it only reports
Document Inspector can check several types of hidden workbook information, but each result needs a decision. Microsoft lists comments and annotations, document properties and personal information, headers and footers, hidden rows and columns, hidden worksheets, custom XML, and invisible content among the Excel categories.
Hidden rows, columns, and worksheets deserve special care. Microsoft warns that removing them can change formulas or calculation results. If you do not know why a hidden area exists, close the inspector, unhide that area, and review its contents before removing anything. A hidden calculation sheet may contain confidential assumptions, but deleting it may also break the visible totals.
Some findings are not removed automatically because doing so could stop the workbook from working. Microsoft says the inspector can report items such as external links, embedded files or objects, VBA or macros, cached BI data, scenarios, filters, and hidden names. These need manual review. It also does not detect every shape, chart, control, picture, or covered object that might sit in a hidden column or behind another object.
Treat an inspector result as a map, not a privacy certificate. Record what you removed, what you kept, and why. If a macro, link, or embedded object is required, consider whether the recipient needs the original workbook at all or whether an approved static export would satisfy the request.
Inspect visible personal information as a separate pass
After hidden-content inspection, read the visible workbook as if you were the recipient. Names, email addresses, employee IDs, account references, free-text notes, chart labels, and project codes can remain in ordinary visible cells; removing document properties does not remove that content.
Use a concrete route through the workbook:
- Check every visible sheet tab, including sheets that look like instructions or cover pages.
- Search for known email domains, phone prefixes, customer-name fields, and identifier labels.
- Inspect chart titles, data labels, text boxes, headers, footers, comments, and validation messages.
- Look for filtered-out rows and collapsed outline groups rather than relying on the current view.
- Review filenames, sheet names, named ranges, links, and print areas for internal terms.
The PII Masking Tool can help with a copied text excerpt. Paste only the text you are allowed to process, select the name, phone, ID, email, and address rules, then review the masked output line by line. Its rules identify possible patterns; they can miss unusual identifiers and can also mask text that is not personal data.
The tool accepts pasted text only. It does not open XLSX or DOCX, remove metadata, edit cells, save a workbook, or prove that a file is safe to share. If you use its output, make the actual change in the Excel copy yourself and check formulas, formatting, and references afterward.
Use spreadsheet preview only as an extra visual check
A browser preview can help you notice a wrong sheet or an obvious row that survived cleanup, but it cannot replace Excel's inspection workflow. The current ToolboxHub component reads CSV, TSV, XLSX, and XLS files in the browser, lets you choose a sheet, searches displayed values, and renders up to 500 matching rows.
The CSV and Excel Preview tool is preview-only for Office files. It does not edit an XLSX workbook. Its CSV export creates a separate CSV representation of the opened sheet; that output is not a sanitized workbook and does not preserve the workbook's formulas, formatting, multiple sheets, macros, or hidden package content.
Use only non-sensitive or approved data in any optional browser review. For instance, a team can make a test workbook containing fake names such as Sample Customer and verify its handoff checklist before applying the same process inside the approved desktop environment. A preview of a few hundred rows is a sampling aid, not evidence that every row or hidden object was examined.
If two reviewers create different visible-text drafts, the Text Diff tool can compare pasted, non-sensitive excerpts by line, word, or character. It cannot compare Office packages, inspect metadata, or confirm that formulas and hidden sheets are unchanged.
Verify the exact copy that will leave your control
Reopen the outgoing copy and run Document Inspector again. Then repeat the visible-content review on that same file, not on the original or an earlier draft. This catches cases where saving, refreshing a connection, or making a final edit added information after the first inspection.
Check that formulas still return expected results, required charts open, and approved links still work. Unhide each row, column, and worksheet you decided to keep, then confirm it contains nothing the recipient should not receive. Review any inspector findings that could not be removed and document the decision.
Microsoft notes extra limits for legacy Shared Workbooks: some comment, annotation, property, and personal-information inspectors cannot be used until a copy is made and sharing is turned off. It also says an .ods file must be inspected again every time it is saved in that format. These are workflow limits, not optional cleanup tips.
Finally, confirm the recipient, attachment name, and sharing channel. For medical, legal, financial, employment, or other regulated records, follow the organization's official source and professional advice. This checklist is not legal advice, and neither Document Inspector nor ToolboxHub can decide whether disclosure is permitted.
Frequently asked questions
Does Document Inspector remove visible names and email addresses from cells?
No. It can remove or report specific hidden-data categories and document properties, but ordinary visible workbook content still needs a separate review. Search the copy, inspect every sheet, and make approved edits in Excel.
Which Excel versions does this workflow cover?
Microsoft's current page lists Excel for Microsoft 365, Excel 2024, Excel 2021, Excel 2019, and Excel 2016. The menu path in this article is scoped to Windows desktop Excel; do not assume the same controls appear on Mac or the web.
Can I safely remove every hidden row and worksheet?
No. Microsoft warns that removing hidden rows, columns, or worksheets can change calculations or formulas. Unhide unknown content, understand its role, and work only on a recoverable copy.
Can ToolboxHub clean an XLSX or DOCX file for me?
No. PII Masking Tool handles pasted text, while CSV and Excel Preview displays spreadsheet data for review. Neither tool removes Office metadata, edits an XLSX or DOCX package, or certifies a file for sharing.
Is a clean Document Inspector result enough?
No. Some items are only reported, some objects are not detected in every situation, and visible personal information remains outside a metadata-only pass. Reinspect the outgoing copy and complete a manual visible-content review.