Import-ready · Delimiter your choice

Excel to CSV — exactly the format your importer wants.

Pick delimiter and encoding before exporting. Comma for Mailchimp, semicolon for European Excel, tab for safe DB imports — UTF-8, UTF-8 with BOM, or Windows-1252. Formulas are evaluated, all sheets exportable. Direct in the browser.

4
Delimiters
3
Encodings
0 B
Uploaded

Excel to CSV Converter

Drop the Excel file, pick delimiter and encoding, get a clean CSV.

📗

Drop Excel file here

or click to browse — .xlsx, .xls, .xlsm

Preview

See all CSV tools →

Why this Excel-to-CSV converter?

Surfaces import-pipeline requirements instead of making you guess.

🔧

Delimiter your choice

Other tools blindly write comma. Here you explicitly pick comma, semicolon, tab, or pipe — what your target system actually wants. Default (comma) works for most international pipelines.

📡

Encoding choice, not lottery

UTF-8 without BOM for modern web stacks. UTF-8 with BOM for Excel double-click open. Windows-1252 for legacy software that can't handle Unicode. You decide — we deliver byte-exact.

📋

Sheet picker for workbooks

Your workbook has 5 sheets (Data, Calc, Charts, Pivot, Sheet1)? Pick the right one from a dropdown. No accidental export of helper sheets.

🧮

Formulas are evaluated

=SUM(A1:A10), =VLOOKUP, =IF — all formula results are exported as values. Import systems get numbers, not formula strings. Exactly what databases and APIs want.

✅

RFC 4180 compliant

Delimiters, newlines, and quotes inside values are properly escaped (doubled quotes, wrapped in quotes). PostgreSQL COPY, Python csv, Excel re-import and pandas all read the result correctly.

🔒

Fully local — GDPR-safe

Excel workbooks often contain PII (employee lists, customers, orders). At BrowserCrunch the file never leaves your browser. No data-processor relationship, no cloud, no risk.

How to convert Excel to CSV

Three steps with full output control.

1

Drop Excel

Drag-and-drop or file dialog. Accepts .xlsx, .xls (old BIFF format), .xlsm.

2

Pick options

Sheet, delimiter, encoding — tuned to the target application. Preview shows the selected sheet.

3

Save CSV

Click Convert, the file lands in your Downloads folder — ready for the import.

Real-world use cases

Where Excel-to-CSV is most often needed.

💌

Mailchimp, Klaviyo, Constant Contact

Mailchimp wants comma-CSV in UTF-8. Anyone exporting an Excel list of addresses, first names, and tags can pick that exact format here. Accented first names like "José" or "Müller" stay clean.

🗄️

Database imports (Postgres, MySQL)

For PostgreSQL COPY FROM or MySQL LOAD DATA INFILE, tab-delimited with UTF-8 (no BOM) is most robust. Few values contain tabs and the parser is fast. One option away from the default — done.

☁️

Salesforce, HubSpot, Marketo imports

CRM data loaders expect specific delimiter and encoding combinations. Salesforce Data Loader: comma + UTF-8. HubSpot: comma + UTF-8 strongly. Marketo: comma + UTF-8 or tab — known beforehand, exported correctly the first time.

🐍

Python pandas, R, Jupyter

Data scientists want pd.read_csv() to work without an encoding argument. UTF-8 without BOM is the gold standard, comma the delimiter. That exact combo is a one-click here.

🛒

Shopify, BigCommerce, WooCommerce

Shop systems import product lists, stock updates, and orders via CSV. Shopify wants comma-CSV in UTF-8. With this tool you export the exact format directly from your master Excel.

🧪

Research & open-data publishing

Research datasets and open-government data are typically published as UTF-8 CSV with comma (for machine processing). If you maintain in Excel, export the final, universally-compatible output here.

Frequently asked questions

Rule of thumb: international APIs and SaaS tools (Salesforce, HubSpot, Mailchimp, Shopify) expect comma. European Excel, DATEV, and legacy ERPs expect semicolon. Tab is robust for DB imports because tabs rarely appear in data. Pipe is popular in old database exports.

Rule of thumb: for imports into modern web APIs, Postgres, MySQL, Python pandas, R, and most SaaS pipelines, choose UTF-8 (no BOM) — today's standard. For imports into Microsoft Excel double-click open or legacy Windows tools, choose UTF-8 with BOM (or Windows-1252).

Formulas are evaluated before CSV export. A cell with =SUM(A1:A10) becomes the calculated numeric value, not the formula text. Cross-workbook references use the last value Excel saved.

You pick one sheet per export. For workbooks with multiple sheets, run multiple exports — one CSV per sheet. CSV is a single-sheet format by definition; there is no multi-sheet CSV.

We export raw values: 1234.56 instead of '$1,234.56', 0.15 instead of '15%'. That's exactly what database and API imports expect — formatting belongs in the display layer.

Yes, RFC 4180 compliant: cells containing the delimiter, a quote, or a newline get double-quoted, and embedded quotes are doubled. All standards-compliant parsers will read the output correctly.

Yes. SheetJS supports the old binary BIFF format (.xls from Excel 97–2003) along with .xlsx, .xlsm, and .xlsb. You can drop in any Excel version.

No. SheetJS runs as JavaScript in your browser — the Excel file is loaded into local memory, converted there, and saved locally. No server roundtrip.

Excel to CSV — the knobs Excel itself doesn't offer

Excel's built-in "Save As CSV" has two big shortcomings: zero control over the delimiter (Excel takes it from regional settings) and zero control over the encoding (English Excel saves Windows-1252 by default on Windows, which mangles Unicode). Anyone producing a CSV for a modern database, a cloud API, or another locale really needs those knobs. Our converter provides them — client-side in the browser, no upload.

Delimiter choice — why it matters

Import systems are usually strict: they expect the one delimiter they were told. Comma is the global SaaS standard (Mailchimp, Shopify, GitHub, Notion, Airtable, Salesforce, HubSpot). Semicolon is European tradition because comma is the decimal separator there — DATEV, older Excel versions, and many European ERPs expect it. Tab is the safe bet when values may contain arbitrary characters (addresses with commas, descriptions with quotes). Pipe (|) is preferred in larger DB exports because it's even less likely to appear in data.

Encoding choice — BOM, UTF-8, or Windows-1252

UTF-8 without BOM is today's global standard and works with everything modern: Python, Node.js, Postgres, MySQL, R, all modern editors. UTF-8 with BOM is a quirk that mainly exists so Microsoft software (Excel double-click, older Notepad) opens Unicode files correctly. Windows-1252 is the legacy single-byte encoding of Western Windows — only works if your data is plain ASCII plus a small handful of accented characters.

Formula evaluation — values, not functions

Import systems can do nothing with =SUM() — they want numbers. SheetJS evaluates all formulas before export. Linked-in values from other workbooks use the last value Excel saved. Anyone who needs original formulas exported (rare) should write us.

Multi-sheet workbooks: one sheet per pass

CSV is single-sheet by definition. For multi-tab workbooks, pick one sheet per export. After download, leave the Excel file in the preview, pick the next sheet, export again — multiple CSVs from one workbook in seconds.

GDPR / privacy angle

Typical office Excel workbooks contain employee lists, customer data, sales reports, order DBs — i.e. personally identifiable data. Running them through an unknown cloud converter abroad is risky (GDPR Art. 28 data processor relationship, possibly third-country transfer, joint controllership). With BrowserCrunch none of this happens — the file never leaves your browser. Want the absolute proof: load the page, turn off Wi-Fi, conversion still works.

Related CSV tools on BrowserCrunch

Need the other direction? Our CSV-to-Excel converter solves the Unicode/date problems when opening in Excel. For developers: CSV to JSON or JSON to CSV. For reports: CSV as PDF table.