CSV Encoding and UTF-8 Guide
Learn why CSV files display strange characters and how to convert them safely to UTF-8.
What character encoding means
Character encoding defines how letters, punctuation and symbols are represented as bytes. A CSV file may look correct in one program but break in another when the programs assume different encodings.
Why UTF-8 is usually the best choice
UTF-8 supports characters from many languages while remaining compatible with ordinary English text. It is widely supported by ecommerce platforms, databases, analytics software and web tools.
Common signs of an encoding problem
- Characters such as
éinstead of é. ’instead of a curly apostrophe.at the start of the first header.- Question marks or replacement symbols in product names.
- Import errors mentioning invalid UTF-8 sequences.
UTF-8 with and without BOM
A byte-order mark, commonly called a BOM, is an optional sequence at the beginning of a Unicode file. Some spreadsheet applications use it to identify UTF-8. Other importers may treat it as part of the first column name.
Windows-1252 and Latin-1
Older Windows exports often use Windows-1252. Some tools label similar files as Latin-1. Converting these files requires decoding them with the original encoding before saving the text as UTF-8.
Safe conversion steps
- Make a copy of the original CSV.
- Detect or identify the source encoding.
- Decode using that source encoding.
- Save the result as UTF-8.
- Reopen the file and inspect non-ASCII characters.
- Test the converted file with the destination platform.