Convert Excel to CSV in One Click
Turn an Excel sheet into a clean CSV file that opens in any app — processed locally, right in your browser.
Drop your file here or click to browse
Excel files (.xlsx, .xls)
Your data never leaves your device
Nothing to delete later
Safe for payroll and customer data
Works in every modern browser
How it works
- 1
Add your workbook
Drop the .xlsx or .xls file onto the page, or click to browse and select it.
- 2
Pick the sheet
Choose which tab becomes the CSV, since the format holds exactly one table.
- 3
Download the CSV
Save the file, ready to feed into an import form, a script, or a database load.
Why use this tool
UTF-8 output, always
Excel’s own "Save as CSV" can still write a legacy code page. Here the output is UTF-8, which is what import forms expect.
One sheet at a time
CSV holds a single table by definition — the sheet you want is extracted rather than silently taking whichever tab was active.
Values, not formulas
Each cell exports as the value it displays, which is what a receiving system needs.
Nothing is uploaded
The workbook is read and the CSV written in your browser — the data never reaches a server.
No row limit
Bound only by your device’s memory, not a free-tier cap on rows or file size.
Free with no account
No sign-up, no watermark, and no limit on how many files you convert.
Why an import form rejects the CSV Excel gave you
The usual sequence is: export from Excel with "Save as CSV", upload to a system, and get told the file is invalid or the characters are wrong. Two things cause it. First, Excel on Windows has historically written CSV in the regional legacy code page rather than UTF-8, so any accented, Arabic or Turkish text arrives at the receiving system as replacement characters. Second, Excel writes whichever separator your regional list setting specifies — a semicolon in much of Europe and Latin America — while nearly every import endpoint is written to expect commas. Converting rather than re-saving removes both variables: the output is UTF-8 with comma separators regardless of the machine it was produced on.
What a CSV cannot carry, and what that costs you
A CSV is one table of plain text. Everything else in the workbook is discarded, and it is worth knowing what goes: multiple sheets, formulas, cell formatting, colours, merged cells, charts, comments, frozen panes and column widths. None of that is a bug — the format has no place to store it. The practical consequence is that the CSV is a one-way export for feeding a system, not a working copy of your workbook. Keep the .xlsx as the file you edit and treat the CSV as output, or the first time you open the CSV in Excel and save, the formulas you spent an afternoon on are gone.
Numbers, dates and the formatting trap
A spreadsheet displays a formatted view of a stored value, and only one of those two can go into a CSV. A cell showing `1.240,50` stores the number 1240.5; a cell showing `15 Mar 2024` stores a date serial. When the export writes the displayed text, a receiving system gets a string with a thousands separator it cannot parse; when it writes the raw value, a date arrives as a five-digit number. Neither is universally right, which is why the fix belongs upstream: before converting, set the columns a system will read to plain formats — no thousands separators, and dates in ISO form as `2024-03-15`. That one change prevents most import failures.
Preparing a sheet that will import cleanly
Import endpoints expect a rectangle: one header row, then data, nothing else. Real workbooks rarely look like that. Merged title cells across the top become a first row full of empty fields; a blank spacer row makes many parsers stop reading; a totals row at the bottom arrives as a record with a name like "TOTAL" and no valid identifier. Trailing empty columns produce phantom fields. Before converting, delete decorative rows above the header, remove blank separator rows, cut the totals line, and make sure every header cell has a short unique name. Ten minutes there saves an hour of debugging a rejected upload.
When you want CSV and when you want something else
Choose CSV when the destination is a machine: a bulk import form, a script, a database load, a mail-merge source. Choose to stay in .xlsx when the destination is a colleague who will read and edit it — and if someone sends you a CSV that you need to work in, the reverse conversion is the tool for that. If the destination is an application or an API rather than a table-shaped importer, Excel to JSON usually fits better, because JSON carries typed values and nested structure that a flat CSV cannot express.
Why the conversion happening locally matters here
The workbooks people convert are payroll runs, customer databases, order books, membership lists, patient schedules. An .xlsx is often the most sensitive file on a small business's machine, and a hosted converter receives all of it. Because this tool runs entirely in the browser, the workbook is read from disk into the page and the CSV written back out with no network request carrying the data — verifiable in the Network tab of developer tools. For a file whose contents would be a serious incident if leaked, that is not a marketing distinction but the reason to use it.
Common mistakes to avoid
- Using the CSV as your working file. Everything except one sheet of values is discarded — formulas, formatting, other tabs. Keep the .xlsx as the file you edit and treat the CSV as a one-way export.
- Leaving thousands separators and locale date formats in place. A receiving system cannot parse `1.240,50` or guess whether `03/04` is March or April; set those columns to plain numbers and ISO dates before converting.
- Converting a sheet with merged title cells or a totals row. Importers expect one header row followed by data; decorative rows arrive as empty records and the totals line as a nonsense entry.
- Assuming Excel’s own Save as CSV gives you UTF-8. On Windows it has historically written the regional code page, which is why correct accented or Arabic text arrives at the destination as replacement characters.
- Exporting the wrong tab. A workbook has many sheets and a CSV holds one; pick the sheet deliberately instead of accepting whichever one was active when the file was saved.
How it compares
| Feature | This tool | Excel’s Save as CSV | Online converters |
|---|---|---|---|
| Data uploaded to a server | Never | No | Usually |
| UTF-8 guaranteed | Yes | Often not on Windows | Usually |
| Separator independent of your locale | Yes | No | Usually |
| Choose which sheet | Yes | Active sheet only | Sometimes |
| Account or sign-up | Not required | Licence required | Often required |
| Price | Free | Paid software | Free / paid tiers |
Features
xlsx and xls supported
Both the modern format and the older binary one that legacy systems still export.
Sheet selection
Convert the tab you actually need instead of whichever one happened to be open.
UTF-8 encoding
Accented Latin, Arabic, Turkish and other non-ASCII text survives the export intact.
Proper quoting
Values containing a comma, a quote or a line break are quoted and escaped so the row cannot split.
Formulas resolved to values
A cell showing `1,240` exports as `1240`, not as the formula behind it.
Large sheets supported
Tens of thousands of rows convert without an upload queue.
No installation
Nothing to download or install — it works on the web page.
Arabic & RTL friendly
Full interface in eight languages, including right-to-left Arabic.
Secure by default
Served over HTTPS, with no file tracking and no third-party upload.
Who uses it
Developers & data teams
Getting a clean UTF-8 CSV to load into a database without fighting Excel’s encoding.
Online sellers
Turning an inventory or price sheet into the CSV a marketplace bulk-upload form demands.
Marketing & CRM staff
Exporting a contact list in the format an email platform will actually accept.
Anyone handling personal data
Converting a member or payroll sheet without sending it to a third-party service.
Frequently Asked Questions
No. The conversion runs entirely in your browser — your data is never uploaded, stored, or shared.
Yes. Every row and column is converted faithfully; the structure is preserved.
Yes — completely free, with no account, no watermark, and no limit on how many files you convert.