How to Fix Garbled Text and UTF-8 Encoding Issues in CSV Files
A CSV encoding error means the file’s characters were saved in one encoding and read in another. Most import tools expect UTF-8, so a file saved in an older encoding either gets rejected or arrives with garbled text, such as “é” turning into “é.” The fix is to save or reopen the file as UTF-8, starting from an undamaged copy.
The tricky part is that opening and saving a CSV in the wrong program can cause the problem in the first place. Knowing which symptom you’re seeing tells you whether the text can still be recovered or needs to come from the original export.
What a CSV Encoding Error Looks Like
Encoding errors show up in a few recognizable ways. Match your symptom to the table below before changing anything, because the right fix depends on what went wrong.
| What you see | What it usually means |
|---|---|
| “é” shows as “é” or “ö” as “ö” | A UTF-8 file was opened as an older encoding. The data is usually still recoverable. |
| Question marks or boxes in place of letters or symbols | The characters were already lost when the file was saved. Go back to the original file. |
| An upload error such as “Invalid encoding” or “CSV files must use UTF-8 encoding” | The file isn’t UTF-8, or it contains characters the tool doesn’t accept. |
| All data in one column | Usually a delimiter mismatch, though the wrong encoding can cause it too. |
These problems happen because a CSV file can’t declare its own encoding. Any program that opens it has to guess, and if it guesses an older encoding for a UTF-8 file, accented letters, currency symbols and other special characters come out wrong.
A few encodings account for most CSV files. UTF-8 is the modern default and the format most import tools expect. Windows-1252 and ISO-8859-1 are common in older exports, especially from Microsoft software and Western European systems, and UTF-8 with a byte order mark (BOM) is a UTF-8 variant that helps Excel recognize the encoding.
How to Fix a CSV Encoding Error
The goal is a file saved as UTF-8 with every character intact. Work through these steps in order, starting with the cleanest copy of the data you have.
Start from the original file
Before converting anything, find the cleanest version of the file. If the CSV came from another system, such as a store export or a supplier feed, download it again rather than working on a copy you’ve already opened and saved.
This matters most when characters have turned into question marks. That damage happens at save time, so no encoding change can restore the missing letters. Garbled sequences such as “é” are different, because the original bytes are usually still there and reopening the file with the right encoding fixes them.
Save the file as CSV UTF-8 in Excel
Excel offers more than one CSV format, and only one is reliably UTF-8. Go to File > Save As and choose CSV UTF-8 (Comma delimited) as the file type. The plain CSV (Comma delimited) option can use a different encoding, which is a common cause of garbled characters after import.
Check a few rows after saving, especially names, addresses, currency symbols and headers. If they look right and the destination accepts UTF-8, the file is ready to upload.
Open a UTF-8 CSV in Excel without garbling it
If a UTF-8 file looks garbled as soon as you open it, the file may be fine and Excel may simply be guessing wrong. A UTF-8 CSV saved with a byte order mark opens normally when you double-click it, but one saved without it can display incorrectly.
To open it correctly, start from a blank workbook and import the file instead:
- Go to Data > Get Data > From File > From Text/CSV.
- Select the CSV file and click Import.
- In the preview, set File Origin to 65001: Unicode (UTF-8) and confirm the characters look right.
- Check that the Delimiter matches the file, then click Load.
- When you’ve finished editing, save with CSV UTF-8 (Comma delimited) so the file stays UTF-8 for its next stop.
Use Google Sheets as a cleaner
Google Sheets often reads UTF-8 files correctly where Excel doesn’t, and it saves CSV files as UTF-8 by default. That makes it a simple way to repair a file without changing any settings.
In Google Sheets, open a blank spreadsheet and use File > Import to upload the CSV. If the text displays correctly, download a clean copy with File > Download > Comma-separated values (.csv) and upload that file to your destination.
Convert the file in a text editor
A text editor changes the encoding without touching the data’s structure, which makes it a good final step. In Windows Notepad, choose File > Save As and pick UTF-8 from the Encoding list. In Sublime Text, use File > Save with Encoding > UTF-8, and in Visual Studio Code, click the encoding shown in the status bar and choose Save with Encoding.
If the text looks garbled in the editor before you convert it, reopen the file with its original encoding first. In Visual Studio Code, that’s Reopen with Encoding, after which you can save it as UTF-8.
Converting can drop characters the target encoding or tool doesn’t support. After saving, scan the file for missing symbols before you upload it.
Fix Delimiter and Quote Problems That Look Like Encoding Errors
Not every broken CSV is an encoding problem. If all your data lands in a single column, the file most likely uses a different separator than the tool expects, such as semicolons instead of commas. Some computers’ regional settings make Excel save CSV files with semicolons, which then confuses tools expecting commas.
To fix this, choose the matching delimiter in the import options, or re-export the file with commas. When opening the file in Excel through From Text/CSV, check the Delimiter setting in the preview.
Curly quotes and apostrophes cause another lookalike problem. Text copied from documents often contains curly punctuation, which some importers reject with errors such as “illegal quoting.” Replace curly quotes with straight ones using Find and Replace, then save the file as UTF-8.
How to Prevent CSV Encoding Errors
Most encoding errors can be avoided with a few habits. Export as UTF-8 whenever the source system offers a choice, especially if your data includes accents, symbols or non-English names.
Avoid opening and re-saving a CSV in Excel just to look at it before uploading. Opening the file isn’t the problem on its own, but saving it in the wrong CSV format can change the encoding. If you only need to check the contents, close the file without saving, or preview it in Google Sheets or a text editor.
Finally, check before you import. Look at a handful of rows with special characters, keep the original export as a backup, and test-import a few rows when the destination allows it. Catching a garbled name in a sample is far easier than fixing it across thousands of records.
Conclusion
A CSV encoding error is almost always a mismatch between how a file was saved and how it’s being read. Starting from a clean original, saving as CSV UTF-8 and checking special characters before upload resolves most cases in a few minutes. We hope this guide helps you fix your CSV encoding error and import your data cleanly. If CSV imports and exports are a regular part of managing your store, you can explore Bulkflow.
