Visualizador de planilhas gratuito

When You Reach for a Spreadsheet Viewer

A viewer is a different tool from an editor. Excel, Google Sheets, and Numbers all do everything, open, edit, calculate, format, share. But there are moments when you just need to look at the data without launching a heavy app or signing into someone else's cloud:

• QA / engineering: confirming a CSV exported by a server endpoint is well-formed before pushing it through a downstream pipeline.
• Customer support: opening a customer's uploaded file to inspect a problem without needing Excel installed locally.
• Auditing: spot-checking a large CSV from a SQL export or analytics dashboard. Sorting and searching are usually enough; you don't need full editing.
• Mobile inspection: opening a CSV attachment on a phone without an Office or Sheets app.
• Privacy-sensitive review: examining customer / employee / financial data without uploading it to Google Sheets, OneDrive, or another cloud service.
• Quick comparison: opening two files side by side in browser tabs is faster than launching Excel twice.
• One-off CSV inspection on a machine that doesn't have Excel, Linux servers, Chromebooks, kiosk machines.

CSV: A Format Without a Spec

CSV (comma-separated values) is the lowest-common-denominator interchange format for tabular data. There's no formal standard; the closest thing is RFC 4180 (October 2005), which is informational rather than normative. The rules everyone agrees on:

• One record per line, separated by line breaks (the RFC specifies CRLF; most parsers also accept LF).
• Fields are separated by a single delimiter character, comma is the default.
• Header row is optional; if present, it's the first line.
• Fields containing commas, line breaks, or double quotes must be enclosed in double quotes.
• Embedded double quotes are escaped by doubling them: "She said ""hello""".
• The MIME type is text/csv.

In practice, "CSV" can also mean tab-separated (TSV), semicolon-separated (common in continental Europe where the comma is the decimal separator), or pipe-separated. This viewer auto-detects the most likely delimiter and parses accordingly.

The Excel Encoding Trap

A common reason CSVs look broken when opened in Excel: the file is UTF-8 encoded but lacks a Byte Order Mark (BOM), and Windows Excel defaults to Windows-1252 for text files. The result is mojibake on non-ASCII characters, accented letters, currency symbols, Asian scripts all display as garbage. Browser-based viewers like this one read UTF-8 correctly without needing the BOM, so a CSV that looks broken in Excel may display perfectly here. The flip side: a CSV with a UTF-8 BOM displays correctly in both, so adding the BOM is generally the safer authoring choice.

XLSX: A Zip of XML

Office Open XML (the format behind .xlsx) was standardised as ECMA-376 and ISO/IEC 29500. Despite the binary appearance, an .xlsx file is actually a ZIP archive containing XML documents, workbook definition, sheet contents, shared strings, styles, and so on. Renaming a .xlsx to .zip and unzipping it reveals the structure: xl/workbook.xml, xl/worksheets/sheet1.xml, xl/sharedStrings.xml, xl/styles.xml. This viewer uses the JSZip library to unzip the archive locally and then parses the relevant XML parts to reconstruct the table.

A practical scope note: this is a viewer, not a parser of every Excel feature. The current implementation reads the first sheet of the workbook and the cell values themselves, it doesn't parse styles, conditional formatting, charts, named ranges, formulas (the cached value is shown, not the formula expression), or pivot tables. For full Excel feature support, open the file in Excel, LibreOffice Calc, or Google Sheets. For quick "what's in this file" inspection, the viewer is enough.

XLS (Legacy Binary Format)

The older .xls format used in Excel 97–2003 is a binary BIFF (Binary Interchange File Format) document, not a ZIP archive. It needs a different parser entirely than XLSX. If you have an old .xls file the cleanest path is to open it in Excel, LibreOffice, or Google Sheets and re-save as .xlsx: the modern format works everywhere and unlocks the broader ecosystem of tooling.

Privacy Matters Here

Spreadsheets are some of the most privacy-sensitive files an organisation handles. Customer lists with email addresses and order histories. Employee data with salaries, performance ratings, home addresses. Financial reports with revenue figures, vendor terms, M&A pipelines. Healthcare data with patient identifiers. Server-side viewers receive every cell of every uploaded spreadsheet, and once on a server, the data lives in transit logs, processing caches, and backup snapshots regardless of the privacy policy.

This viewer runs entirely in your browser. The file goes from your file system into local memory, gets parsed by JSZip and a CSV reader running in JavaScript on your device, and renders into an HTML table. Nothing is uploaded; no analytics endpoint sees the cells; closing the tab releases the memory. The same workflow that protects you from upload-leak risks also means there's no "recently viewed" history, bookmark or save the original file if you need to return to it.

What the Viewer Doesn't Do

Being honest about scope:

• No editing. Read-only by design. To modify cells, save changes back, or share with others, use Excel / Sheets / Numbers / LibreOffice Calc.
• No formula evaluation. XLSX cells with formulas show the cached value Excel last computed before the file was saved. Open the file in a real spreadsheet app to recalculate.
• No charts, shapes, conditional formatting. Visual elements stored in the XLSX aren't rendered, you see the underlying cell values, not the visual treatment Excel would apply.
• Single sheet for XLSX. The viewer reads the first sheet of multi-sheet workbooks. Tab through the file in a real spreadsheet app for sheets 2+.
• No styles parsing. Currency, date, and percentage cells display as raw underlying numbers, a date stored as the integer 45,657 displays as 45657 rather than the styled date Excel would show.
• No write / export. The viewer can't save back to a file. Use the original spreadsheet app for that.

Performance Notes

Files up to a few tens of megabytes parse and render in a second or two on a modern device. Past that (say, a 200-MB CSV from a SQL export) browser memory becomes the bottleneck. For genuinely massive datasets, command-line tools are better: csvkit, q, miller, or just head/cut/awk/sort on a Linux box. The viewer is built for "quick inspection", not analytical workloads on multi-million-row data.

Common Mistakes

1. Expecting Excel-style formatting. The viewer reads the underlying cell values, not Excel's display formatting. A date stored as 45657 shows as 45657, not as "January 30, 2025".
2. Looking for sheets 2+. Single-sheet by design. Open the file in a real spreadsheet app for multi-sheet navigation.
3. Trying to use it as an editor. Read-only. The whole point is fast inspection without launching a full app.
4. Loading huge files. Parse-and-render in a browser tab has practical limits around a few tens of MB. For multi-million-row CSVs, use command-line tooling.
5. Confusing CSV-with-comma and CSV-with-semicolon. European Excel often saves CSV with semicolons because comma is the decimal separator. The viewer auto-detects most cases but if your file looks like a single column, the wrong delimiter is the usual culprit.
6. Assuming the BOM is irrelevant. The BOM determines whether Excel reads UTF-8 correctly; this viewer reads UTF-8 cleanly with or without one. If the same file looks fine here but garbled in Excel, the missing BOM is the cause.

More Frequently Asked Questions

Why does my XLSX show numbers instead of dates?

Because Excel stores dates as serial numbers (the count of days since 30 December 1899) and uses cell styles to render them as "January 15, 2024". The viewer reads the underlying number but doesn't apply Excel's date-formatting style, so you see the raw 45657. To see the formatted date, open the file in Excel, Google Sheets, or LibreOffice Calc.

Can I edit cells in the viewer?

No, read-only by design. The viewer is for fast inspection of data files; for editing, use a full spreadsheet app. The trade-off is intentional: a read-only viewer is much faster to load and runs reliably from any browser without needing Microsoft 365, Google account sign-in, or app installation.

Is my file uploaded anywhere?

No. The file goes from your local file system into JavaScript memory, gets parsed by JSZip (for XLSX) or a CSV parser (for CSV/TSV) directly in the browser, and renders into an HTML table. Nothing crosses the network. This matters because spreadsheets routinely contain customer PII, employee records, or financial figures that you don't want flowing through a third-party server.

What's the size limit?

No hard limit; the practical ceiling is your browser's memory. Files up to a few tens of MB load comfortably on a typical laptop. Past 100 MB you'll hit memory pressure and parse times stretch into seconds. For the SQL-export-with-multimillion-rows use case, command-line tools (csvkit, miller, q) are designed for the job and won't fight your browser tab.

Why is my CSV showing one column when it should be many?

Almost always a delimiter mismatch. CSV files saved by European Excel often use semicolons (because comma is the decimal separator in those locales). The viewer auto-detects the delimiter from the first line of data; if detection fails, the file may need to be re-exported with a different delimiter, or opened in a tool that lets you specify the delimiter explicitly.

Can I download the data after viewing?

The original file you uploaded is still on your device, you don't need to re-download it. The viewer doesn't currently emit a re-formatted CSV or convert between formats. For format conversions, the Conversor de JSON para CSV and Conversor gratuito de XML para CSV tools handle other input directions.