XLSX to CSV UTF-8 that keeps every accent and script
Upload the XLSX workbook, keep the encoding set to UTF-8 (or UTF-8 with BOM if a person will open the file in Excel), pick the sheet and delimiter, then convert and download the CSV.

Most garbled CSV files are not damaged at all. They are written in one character encoding and read in another, so José turns into José and a Greek product name becomes a row of question marks. UTF-8 is the encoding every database, scripting language and cloud import expects, and it covers every alphabet in a single file.
This converter starts with UTF-8 already selected, so you only decide whether the file needs a byte order mark. For the general options of the same conversion see XLSX to CSV, and if your importer wants semicolons instead of commas, look at XLS to CSV with semicolons.
How to convert XLSX to CSV UTF-8 in three steps
- 1Upload the .xlsx file that contains accented or non Latin text.
- 2Keep UTF-8, or switch to UTF-8 with BOM for Excel users, and choose the sheet.
- 3Convert and download the CSV, then import it without encoding errors.
When a byte order mark helps and when it breaks an import
A byte order mark is three invisible bytes (EF BB BF) at the very start of the file. Excel on Windows looks for them before deciding how to decode a CSV. Without them it falls back to the local code page, which is why a perfectly valid UTF-8 file shows mojibake when a colleague opens it. If the CSV is meant for people who live in Excel, choose UTF-8 with BOM.
The same three bytes cause trouble for machines. A script that reads the header row may see the first column as \ufeffemail instead of email, and a strict importer then reports a missing required column. Some older PHP and shell tools also print the marker as visible junk. For anything that goes into code, an API or a database, choose plain UTF-8 and let the reader assume Unicode.
XLSX itself stores text as Unicode, so the source is never the problem. Characters only disappear when an export squeezes them into a narrow code page such as Windows-1252, which has no room for Polish, Czech, Cyrillic, Chinese or emoji. If you need typed values rather than text, Excel to JSON writes UTF-8 by definition, and CSV to XLSX turns a UTF-8 CSV back into a workbook without guesswork.
XLSX to CSV UTF-8 questions
How do I save an Excel file as CSV UTF-8?
Upload the XLSX file here with UTF-8 selected and download the CSV. Every character from the workbook is written as Unicode, whatever language it is in.
Should my UTF-8 CSV have a BOM?
Add a BOM if people will open the file in Excel on Windows. Leave it out if the file goes to a database, a script or an API, because some of them read the BOM as part of the first header.
Why do accented letters look wrong after I export CSV from Excel?
The file was saved in one encoding and opened in another. Exporting as UTF-8, with a BOM for Excel, keeps names like Müller, Łukasz and São Paulo readable.
Does UTF-8 CSV support Chinese, Arabic and Cyrillic text?
Yes. UTF-8 covers every Unicode script, so mixed language sheets convert into one CSV without losing characters.
Can I test the UTF-8 export before buying a plan?
Yes, the one-time demo converts up to 100 rows once per account and IP. Full files need a paid plan, from 24 USD per month billed yearly.
Related converters
Convert full files and batches
Pro starts at $24 per month billed yearly. Cancel any time.