The attachment says .xlsx. Your machine says no Excel — a Chromebook, a locked-down work laptop, or simply no license. The file still needs reading before the meeting. Here are the real options, what each one shows and hides, and the privacy question most people skip.
Useful context before picking a tool: an .xlsx is a zip archive of XML files — one per sheet, plus parts for styles, shared strings, and drawings. Nothing about it is proprietary in the secret sense; the format has been documented (ECMA-376) since 2007, which is why a whole ecosystem of readers exists. A "viewer" is just a program that unzips, parses those XML sheets into a grid of cells, and draws them. The differences between viewers come down to which parts they bother rendering and whether the parsing happens on your machine or someone else's.
| Option | Best for | Loses | Privacy |
|---|---|---|---|
| Browser viewer (local parsing) | Fast look at values & formulas | Charts, conditional formatting, editing | File never leaves the machine |
| LibreOffice Calc (free desktop) | Regular use, editing, printing | Occasional layout shifts; macros need tweaking | Local |
| Google Sheets / cloud | Collaboration, sharing | Some formatting; file is uploaded | Data goes to the cloud |
| Excel mobile / web (free tiers) | Viewing on phone | Feature gating; sign-in required | Microsoft account context |
For the "I need to see what's in this file in the next two minutes" case, the browser viewer wins on speed and privacy. For ongoing work, install LibreOffice Calc once and stop thinking about it.
A local-parsing viewer renders the sheet grid faithfully: every value, every formula's expression and its cached result, sheet tabs, row and column addresses. That covers the large majority of what people actually need from a spreadsheet someone sent them. What it won't do:
Excel sheets run to 1,048,576 rows × 16,384 columns (220 × 214 — column XFD is the last one). A naive viewer that builds one HTML row per spreadsheet row would need a million DOM nodes and freeze the tab. Serious viewers virtualize: they render only the rows near the viewport — about 25 to 31 at a time — over a spacer div that's exactly as tall as the whole sheet (5,000 rows × 28 px = a 140,000-pixel scroll surface). Scrolling just moves the window. That's why file size, not row count, is the practical limit: parsing a 40 MB export takes memory, but rendering its last row costs the same as rendering row 30.
Spreadsheets are quietly the most sensitive files most people handle — payroll tabs, budgets with real numbers, client lists, the password tab that shouldn't exist. Before dropping one into any web tool, ask where the parsing happens. The test is mechanical: a tool that parses in your browser (JavaScript or WebAssembly in the page) works offline once loaded, shows no server-side progress bar, and its network tab stays quiet after the page loads. A tool that uploads shows exactly that — an upload. For anything with names, salaries, or account numbers in it, the local kind is the only reasonable default. Our XLSX Viewer is the local kind: SheetJS running in the page, files read with the browser's File API and never transmitted.
Drop in an XLSX, XLS, XLSB, ODS, or CSV file — sheet tabs, formula view, and a virtualized grid that stays smooth at a million rows. Nothing uploads.
XLSX Viewer →Browser viewer for the quick look, LibreOffice Calc for the long haul, cloud tools when collaboration is the point — and local parsing whenever the sheet contains anything you wouldn't email to a stranger. When a look is all you need, our XLSX Viewer opens the file where it sits; to transform instead of look, CSV to Excel builds workbooks and Excel to PDF prints a sheet without a spreadsheet app at all.