Worksheet visibility
Check whether a sheet moved between visible, hidden, or very hidden states, or whether the sheet was added or removed.
Workbook structure review
Audit Hidden Rows, Columns, and Sheets Between XLSX Versions
Compare visibility and used-range signals across an original and updated workbook so structural changes do not disappear behind an ordinary cell diff.
Short answer
Compare visibility state as its own review layer
WorkbookDiff records supported sheet, row, column, and used-range changes separately from cell values. That makes it easier to notice when content becomes hidden, visible, added, or removed between coordinate-aligned `.xlsx` versions.
Signals to inspect
Four structural changes that deserve deliberate review
Hidden rows
See row positions whose hidden state changed. A hidden row is a visibility signal, not proof of a problem.
Hidden columns
Review coordinate-aligned column positions that became hidden or visible between versions.
Used range
Notice when the populated boundary of a worksheet expands or contracts, then inspect related cell findings for context.
Practical workflow
Turn structural signals into a review checklist
- Compare the original and updated files.Use two versions with stable sheet names and mostly stable row order.
- Filter by structure category.Start with worksheet, hidden-row, hidden-column, and used-range findings.
- Inspect nearby cell changes.Use values and formula-expression findings to understand the structural signal.
- Export supported findings.Send the filtered CSV to the workbook owner for confirmation.
Interpretation guide
A change signal is not a risk verdict
| Finding | Possible explanation | Question to ask |
|---|---|---|
| Sheet became hidden | Presentation cleanup or concealed working data | Should reviewers still see this worksheet? |
| Column became hidden | Optional detail removed from view | Does the hidden field affect the decision? |
| Used range contracted | Rows cleared, removed, or normalized | Do related cell findings explain the contraction? |
Honest scope
Review supported structure without claiming a complete workbook audit
Supported
Two `.xlsx` files up to 20 MiB each; coordinate-aligned values, formula expressions, worksheets and visibility, hidden rows and columns, used ranges, filtering, and CSV export.
Not supported
`.xls`, `.xlsm`, `.xlsb`, CSV input, passwords, key-based or row-reordered reconciliation, formatting, charts, pivot tables, comments, named ranges, macros, recalculation, or external-link resolution.
WorkbookDiff cannot identify who hid an item, when it happened, or whether approval was granted. Its CSV is not a complete audit trail and is not a forensic or compliance audit.
Structure review FAQ
What the signals do and do not prove
Does WorkbookDiff reveal the contents of hidden cells?
WorkbookDiff compares supported cell values and formula expressions at coordinate-aligned positions, including positions in hidden rows or columns, but it does not decide whether hidden content is sensitive or inappropriate.
Does a used-range change prove that data was deleted?
No. A used-range expansion or contraction is a structural signal. Review the related cell and worksheet findings to understand what changed and whether it was intentional.