Spreadsheet Workbook Inspector & Repair Studio

XLSX is the default spreadsheet file format introduced in Microsoft Excel 2007 based on the Open Packaging Conventions (OOXML / ISO/IEC 29500). An XLSX file is essentially a ZIP archive containing XML documents, relationships, styles, and shared strings.

XLSM is a macro-enabled Excel workbook format. Unlike XLSX, which strictly forbids macro code, an XLSM workbook contains a binary VBA container (xl/vbaProject.bin) that stores Visual Basic for Applications scripts.

Legacy binary BIFF8 files (.xls from Excel 97-2003) are not supported for client-side structural OOXML inspection. Solasu will honestly display 'Unsupported format'. Please convert your file to .xlsx or .xlsm before auditing.

No. Zero bytes are uploaded to external servers, cloud processing services, or remote conversion APIs. All extraction, XML parsing, and clean/repair generation happen purely in your browser's local memory.

No. Solasu employs zero persistent storage. It never writes workbook data, cell values, formulas, filenames, or metadata to localStorage, IndexedDB, cookies, or cache storage. Data exists only in volatile browser RAM.

A hidden worksheet has its state set to 'hidden' in xl/workbook.xml. While invisible in standard tab bars, all of its formulas, cell values, and potential confidential records remain fully accessible in the underlying XML.

A Very Hidden sheet has state='veryHidden' in the workbook XML. It does not appear in Excel's standard 'Unhide' dialog box and normally requires VBA script to reveal. Solasu detects and highlights it directly from package structures.

Yes. Solasu scans worksheet XML definitions for hidden='1' and hidden='true' attributes on <row> and <col> tags, reporting counts and locations across all sheets.

Solasu parses all cell formula tags (<f>) and cached value tags (<v>) across worksheets, categorizing standard error tokens including #REF!, #DIV/0!, #VALUE!, #NAME?, #N/A!, #NUM!, and #NULL!.

A broken reference occurs when a formula points to deleted cells (#REF!) or references a worksheet that no longer exists in the workbook (e.g. ='DeletedSheet'!A1).

Solasu catalogs defined names from xl/workbook.xml, analyzing their scope (workbook-wide or sheet-specific) and referring formulas, flagging broken named ranges that resolve to #REF!.

External links represent relationships connecting the workbook to external Excel files, remote URLs, or OLE data sources. Solasu lists them statically without contacting remote servers.

Solasu never initiates network requests to external links, connections, or hyperlink URLs discovered inside a workbook. External queries and database connections are strictly catalogued, never executed.

Comments are stored in separate package parts such as xl/comments*.xml along with author identifiers. Solasu indexes all comments so you can review drafting notes before sharing.

Core document properties (docProps/core.xml) store author names, last modified by, creation and modification timestamps, and titles. Solasu flags these as potentially identifying metadata.

Solasu never executes VBA macro code in the browser. It inspects the presence of xl/vbaProject.bin for preservation and security audit purposes while completely preventing script execution.

Solasu inspects formula syntax and reference structures independently; it does not replicate Microsoft Excel's complete calculation engine. Stored cached values (<v>) are displayed as recorded by Excel.

A hardcoded value candidate is a constant numeric cell positioned inside a sequence of continuous formulas within the same column, suggesting a potential formula gap or manual override.

When neighboring rows in a column follow an established calculation pattern (e.g. multiplying by 10) but a specific row uses a different formula structure, Solasu flags it as a pattern deviation candidate for verification.

A Clean Copy is a newly generated workbook where user-selected sensitive components—such as author metadata, comments, external hyperlinks, or hidden sheets—have been safely removed while preserving untouched cell data.

A Repair Copy cleans broken relationship definitions that reference non-existent package parts, removes invalid #REF! named ranges, and normalizes sheet state attributes.

This is expected and normal. Applying clean or repair operations modifies internal XML structures, relationship tables, and re-compresses parts, resulting in a distinct cryptographic hash.