Converting single or multi-sheet XLSX workbooks to CSV
Turning a spreadsheet into plain delimited text makes financial tables, inventory lists, and CRM exports portable across databases and scripts. When you convert Excel to CSV in this browser worker, the tool reads your .xlsx or .xlsm XML directly and writes standardized output under the IANA text/csv Media Type Registration.
Exporting one worksheet or all sheets in a ZIP
As soon as you drop a workbook, the inspector reads xl/workbook.xml and counts the rows on every tab. Single-sheet files default to exporting one <name>.csv file, while multi-sheet workbooks let you pick a specific tab or export all sheets together in a <name>-csv.zip bundle.
If you need to bundle exported CSVs into a single ZIP with other project reports or documentation, you can package them right after downloading. Selecting one tab from a multi-sheet workbook automatically appends the sanitized sheet name to the output filename.
Legacy .xls binary files and workbook size caps
Older .xls files and password-protected workbooks use the binary OLE2 compound document format (D0 CF 11 E0). Because those containers cannot be parsed safely as lightweight XML, the tool detects their header and prompts you to save an unlocked .xlsx copy first.
To protect browser memory on laptops and tablets, the parser enforces a 180 MB total uncompressed XML cap, a 100 MB per-entry limit, and a 250,000-row ceiling per worksheet. Empty formatted rows far below your real data table are automatically skipped so stray cell styling does not inflate the output.
Why do European Excel locales use semicolons instead of commas?
Many European and Latin American Windows locales use the comma as a decimal separator (12,50), so Excel expects semicolons (;) to separate columns instead of commas. Picking Semicolon under Separator prevents desktop Excel from cramming every column into column A when you double-click the exported file.
Under the IETF RFC 4180 CSV Format Specification, standard CSV uses commas, CRLF (\r\n) line endings, and double quotes around fields containing delimiters or line breaks. Database importers, Python csv, and analytics tools almost always expect comma-delimited UTF-8 without a Byte Order Mark, whereas Windows Excel expects a UTF-8 BOM to display accents like é, ü, or ñ properly.
If you receive a semicolon-delimited file later and want to convert it back into a formatted spreadsheet, CSV to Excel detects commas, semicolons, and tabs automatically.
| Option or scenario | Recommended Separator | Mark as UTF-8 (BOM) | Best target software |
|---|---|---|---|
| US / UK Excel double-click | Comma (,) |
Checked (on) | Microsoft Excel (en-US, en-GB) |
| European Excel double-click | Semicolon (;) |
Checked (on) | Microsoft Excel (de-DE, fr-FR, es-ES) |
SQL, Python, or Postgres COPY |
Comma (,) |
Unchecked (off) | Databases, pandas, DuckDB, CLI tools |
| Copy-paste or TSV pipelines | Tab (\t) |
Unchecked (off) | Shell scripts, R, legacy importers |
| Multi-tab workbook export | Comma or Semicolon | Checked (on) | Batch archive (<name>-csv.zip) |
Date serials, time cells, and CWE-1236 formula safety
Excel stores dates and times internally as floating-point serial numbers rather than text strings, and raw spreadsheet cells can also contain characters that trigger formula execution when reopened. Converting those values deterministically keeps your CSV accurate and safe to share.
ISO 8601 date output for 1900 and 1904 workbooks
The parser inspects xl/styles.xml to distinguish numeric cells from built-in and custom date or time formats, while also checking whether the workbook uses the legacy Mac date1904 epoch. Dates export as YYYY-MM-DD (or YYYY-MM-DD HH:MM when fractional time is present), and time-only cells export as HH:MM or HH:MM:SS.
Neutralizing formula injection while keeping negative numbers
Spreadsheet programs evaluate cells starting with =, +, -, @, or | as formulas, which creates a security risk known as MITRE CWE-1236 Formula Injection Definition. On all data rows below the header, toCsv() prefixes risky leading characters with a single apostrophe (') while leaving valid negative numbers such as -42.5 untouched.
If your pipeline also ingests XML feeds alongside spreadsheets, you can turn XML records into rows using the same formula-safe CSV writer.
Tip: Uncheck Mark as UTF-8, so Excel shows accents properly when feeding CSVs into strict Unix CLI parsers or
COPYloaders that treat the three-byte UTF-8 BOM as part of the first column header name.
Preparing clean CSV exports for databases and downstream tools
Inconsistent row lengths and unescaped quotes are the most common reasons CSV imports fail in databases and BI dashboards. Every row emitted by this converter is normalized before download so downstream tools ingest it cleanly.
Uniform column widths and quoted field escaping
The CSV writer measures the widest row in the worksheet and pads shorter rows with empty cells so every line contains the exact same number of columns. Any field containing the active delimiter, quotation marks, line breaks, or leading or trailing whitespace is wrapped in double quotes with internal quotes doubled ("").
Combining workbook exports with XML and spreadsheet workflows
When your reporting pipeline mixes structured feeds and spreadsheets, this client-side private Excel to CSV converter pairs naturally with the XML to Excel converter for multi-step transformations. All processing stays inside your local Web Worker so sensitive payroll, customer, or tax sheets never leave your device.