Skip to Content
RowSlice

Free CSV Tool

Fix CSV Encoding and Delimiter Problems

Repair garbled characters such as é and ’, save as UTF-8 that Excel reads correctly, and switch between comma, semicolon, tab and pipe delimiters.

  • No file size limit
  • Never uploaded
  • Free, no sign-up

How to Fix a CSV File's Encoding

  1. Choose or drag in the CSV file. Its encoding and delimiter are detected from the first part of the file.
  2. Look at the preview. If letters still look wrong, change the Encoding under Advanced Options until they look right.
  3. Pick the delimiter you want in the result and whether Excel will open it (keep the BOM ticked if so).
  4. Press Convert File and download the fixed CSV.

Which Garbled Characters Mean What

You seeShould beWhat happenedFix
CaféCaféUTF-8 file read as Windows-1252Convert with BOM ticked
don’tdon’tUTF-8 curly apostrophe read as Windows-1252Convert with BOM ticked
M�nchenMünchenWindows-1252 file read as UTF-8Convert (encoding detected automatically)
Everything in column ASeparate columnsDelimiter does not match Excel's regional settingChange the delimiter

If you see é and the file has already been saved again by another program, the damage may be written into the file itself, and converting will faithfully keep é. In that case go back to the original export if you can.

Why CSV Encoding Goes Wrong So Often

A CSV file is plain text and has no place to say which character encoding it uses. Most modern systems write UTF-8, which can store every language. Excel on Windows, when it opens a CSV by double-click, assumes the older encoding of your Windows region unless the file starts with a UTF-8 byte order mark. Many exports from web apps, databases and Google Sheets do not include one, so accented letters, curly quotes and currency symbols come out garbled.

Delimiters have a similar history. In regions where the decimal separator is a comma, spreadsheet programs save and expect semicolons, so a CSV from a US system opens as a single column in a German or French Excel, and a CSV from a European Excel confuses US software.

What This Converter Changes, and What It Doesn't

The result is always UTF-8. When you keep the same delimiter, each row's text is copied as it is, so quoting and values like 00742 do not change. When you change the delimiter, values are re-quoted only where needed. Line endings can be kept, or set to Windows (CRLF) or Mac and Linux (LF). The file is processed in small chunks on your own computer, so large files are converted without being uploaded.

Last updated .

FAQ

Frequently Asked Questions

Why does my CSV show characters like é, ’ or ü?

The file is UTF-8, but the program opening it read it as Windows-1252 (or another older encoding). In UTF-8, é is stored as two bytes, and read the old way those two bytes show up as é. Saving the file as UTF-8 with a BOM tells Excel which encoding to use, and the characters display correctly.

Why does my CSV show � or ? instead of letters?

That is the opposite problem: the file was saved in an older encoding such as Windows-1252, and it is being read as UTF-8. Choose the file above; the tool detects this, and you can pick a different encoding under Advanced Options until the preview looks right. The converted file is saved as UTF-8.

What is a BOM and should I add one?

A byte order mark is three invisible bytes (EF BB BF) at the start of a file that mark it as UTF-8. Excel on Windows relies on it: without a BOM, Excel opens UTF-8 CSV files with the wrong encoding. Keep the box ticked if the file will be opened in Excel. Untick it for programs and databases that treat the BOM as part of the first column name.

Why does Excel put all my data in column A?

The delimiter in the file does not match your computer's list separator. In countries that write decimals with a comma, such as Germany, France or Brazil, Excel expects semicolons; elsewhere it expects commas. Convert the file to the delimiter your Excel expects and it will open in columns.

Will converting to commas break values that contain commas?

No. Any value containing the new delimiter, a quote or a line break is wrapped in quotes, following the CSV standard (RFC 4180). A price like 1,50 in a semicolon file becomes "1,50" in the comma version.

Does converting the encoding change any of my values?

No. When you keep the same delimiter, each row is copied through as its own text, so quoting, leading zeros like 00742 and long ID numbers are untouched — only the bytes that encode the characters change. When you change the delimiter, values are re-quoted where the standard requires it. The conversion runs in your browser and nothing is uploaded, at any file size.

Guides

More Tools

More CSV Tools