Read-only Office sharing inventory

What might travel with your Office file?

Check a DOCX, XLSX or PPTX before you share it. Get an inventory of hidden sheets, rows and columns; comments; tracked changes; author, company and last-modified-by properties; external relationships and data; embedded objects and VBA projects. Every finding has an exact OOXML part path and location.

Nothing is removed. No findings does not mean safe to share. Unsupported content is reported as unknown, never passed. Review the whole report and your original in Office before deciding what to send.

One report ZIP uses one existing file unlock or credit at existing pricing. No new subscription or tariff; the free single-PDF allowance does not apply. Only the private report, including original_sha256 (a fingerprint of the source), is retained and deleted after 1 hour. Original files are not retained. Failed or unsupported package inspections create no report and require no credit. Part paths themselves can be sensitive: keep the downloaded report private.

One file, up to 10 MB; 1,500 ZIP entries, 8 MB per expanded entry, 40 MB expanded total, 300,000 XML nodes, 600,000 XML attributes (4,096 per element), depth 64, 2,000 findings and a 12-second child budget. No extraction to disk, network fetching, Office rendering, macro execution or recursive inspection of nested archives. Embedded objects, unsupported extensions, custom XML, hidden text, visual concealment, images and media remain unknown. Legacy, encrypted, invalid or incompletely inspected packages are rejected without a report. Fields and formulas are not evaluated; external-link checks remain unknown when they are present. Comment text, names, property values, field/formula text and link targets are omitted from the report. Supported check states mean detected, not_detected in the supported XML scope, or unknown, not safe/unsafe certification.

Choose a file you are authorized to inspect

The result uses the workspace's existing private download and payment flow. The ZIP contains report.json and a limitations note, not a cleaned file or the original. Locations use positional XPath such as /*[1]/*[2], with #part and #package for part/package findings. A human must review and remove anything unwanted in their own copy.