CSV ENCODING & EXCEL
CSV Encoding in Excel: How to Fix Garbled Text and Choose UTF-8
Names show up as José, punctuation turns into – or �, or the whole CSV lands in one column. This guide separates encoding problems from delimiter problems and shows the safest way to open and save a CSV in Excel.
UTF-8 or Windows-1252: which one should you choose?
The best encoding is the one the receiving system expects. When there is no specification, UTF-8 with BOM is the safest Excel-oriented choice because it keeps accents, symbols, Asian scripts, and emoji in one file.
| Encoding | Best for | Excel behavior | Watch out for |
|---|---|---|---|
| UTF-8 with BOM | Excel, email attachments, multilingual sharing | Usually opens correctly by double-click | Check whether an automated importer forbids a BOM |
| UTF-8 without BOM | Web apps, databases, UTF-8 APIs | Use Data > From Text/CSV for reliable import | Older Excel setups may guess another encoding |
| Windows-1252 | Older Western European accounting or CRM tools | Works for common Western European text | Cannot represent Asian scripts or emoji |
| ISO-8859-1 | Legacy systems that explicitly require Latin-1 | Select the file origin manually | Unlike Windows-1252, bytes 0x80–0x9F are controls |
| Shift_JIS / CP949 / Big5 / GB18030 | Specific Japanese, Korean, Taiwanese, or mainland Chinese systems | Select the matching file origin manually | Do not use without a requirement from the recipient |
UTF-8 with BOM
- Best for
- Excel, email attachments, multilingual sharing
- Excel behavior
- Usually opens correctly by double-click
- Watch out for
- Check whether an automated importer forbids a BOM
UTF-8 without BOM
- Best for
- Web apps, databases, UTF-8 APIs
- Excel behavior
- Use Data > From Text/CSV for reliable import
- Watch out for
- Older Excel setups may guess another encoding
Windows-1252
- Best for
- Older Western European accounting or CRM tools
- Excel behavior
- Works for common Western European text
- Watch out for
- Cannot represent Asian scripts or emoji
ISO-8859-1
- Best for
- Legacy systems that explicitly require Latin-1
- Excel behavior
- Select the file origin manually
- Watch out for
- Unlike Windows-1252, bytes 0x80–0x9F are controls
Shift_JIS / CP949 / Big5 / GB18030
- Best for
- Specific Japanese, Korean, Taiwanese, or mainland Chinese systems
- Excel behavior
- Select the matching file origin manually
- Watch out for
- Do not use without a requirement from the recipient
How to convert CSV encoding with LocaCSV
LocaCSV reads and converts the CSV inside your browser. The file body, file name, headers, and cell values are not uploaded. The Free version accepts one input file up to 50 MiB.
- Open Character encoding & format conversion and select the original CSV.
- Choose Auto, UTF-8, Windows-1252, or the appropriate regional source encoding, then check the preview.
- Confirm the input delimiter so the columns line up correctly.
- Choose UTF-8 with BOM for Excel, UTF-8 without BOM for a specified integration, or a legacy encoding only when required.
- Verify the preview and row counts, then save the converted CSV.
How to open a CSV in Excel without garbled characters
Do not save over a file while it is showing garbled text. Saving can replace the original bytes with the wrong characters. Keep a copy and import the original again with an explicit encoding and delimiter.
- Open a blank workbook in Excel and choose Data > Get Data > From File > From Text/CSV. Menu wording varies slightly by Excel version.
- Select the CSV, then change File Origin or encoding to UTF-8 (65001), Windows-1252, or the encoding supplied by the sender.
- Choose the actual delimiter: comma, semicolon, tab, or another character. A one-column CSV is usually a delimiter issue, not an encoding issue.
- Set IDs, ZIP codes, account numbers, and phone numbers to text when leading zeros must be preserved.
- Check names, punctuation, currency symbols, and column boundaries in the preview, then select Load.
How to save a CSV from Excel without losing text
After editing, choose File > Save As and select CSV UTF-8 (Comma delimited) (*.csv) when it is available. CSV stores plain values for one worksheet; it does not preserve workbook formatting, multiple sheets, charts, or most Excel-only features.
- Confirm that the active sheet is the one you intend to export
- Check dates, long numbers, and leading zeros before saving
- Use the delimiter required by the receiving application
- Reopen or preview the saved CSV and compare row counts
How to repair a CSV that already looks corrupted
Garbled text usually means the bytes were decoded with the wrong character set. Return to the untouched source file, try the likely encodings in a preview, and convert only after names and symbols look correct.
- José or España: UTF-8 bytes were probably read as Windows-1252
- – or ’: UTF-8 punctuation was probably read as a Western legacy encoding
- The replacement symbol �: invalid or incomplete bytes may already have been substituted
- Everything in one column: check comma versus semicolon before changing encoding
Encoding choices for English and Western European data
English-language files are not always ASCII-only. Customer names, place names, currencies, smart quotes, and imported data can contain characters from many writing systems, so UTF-8 remains the best general choice.
- Modern Excel and general sharing: UTF-8 with BOM
- A system that explicitly requires UTF-8: use BOM or no BOM exactly as specified
- Older Western European software: Windows-1252
- Mixed-language names or emoji: keep UTF-8 and avoid legacy conversion
Protect sensitive CSV data and watch for spreadsheet formulas
CSV files often contain customer names, email addresses, financial figures, or internal IDs. Before using an online converter, check whether it uploads the file. LocaCSV does not send CSV content or CSV-derived values to an external API.
A CSV opened in a spreadsheet can also contain formula-like cells beginning with =, +, -, or @. Treat files from unknown sources carefully, do not enable unexpected external content, and review formula warnings before downloading or opening the result.