How to Open a Windows-1252 CSV File

If a CSV contains names like Jose, Beyonce, or Francois and the accents turn into odd symbols, the data may not be corrupted. The file may simply be encoded as Windows-1252 and opened as something else.

Windows-1252 is common in older Windows software, legacy exports, and business systems that predate UTF-8 as the default.

What the problem looks like

Wrong encoding can produce:

• é instead of e with an accent
• curly quotes turning into odd symbols
• currency signs changing
• question mark boxes
• names and addresses that look partially garbled

The key point: encoding is a decoding choice. If the bytes are still present, opening the file with the right encoding can make the text readable again.

Do not keep saving guesses

Opening the file in the wrong app and saving it can bake the bad decoding into a new file. Before making edits, open the original export in a tool that can detect or choose the encoding.

CEESVEE detects Windows-1252 along with UTF-8 and UTF-16 variants. Once the file is readable, you can edit it and Save As with explicit encoding settings.

Convert only after verifying

If the receiving system expects UTF-8, convert intentionally:

1. Open the original file.
2. Confirm names, currency symbols, and punctuation display correctly.
3. Save As UTF-8.
4. Reopen the saved file to confirm the characters survived.

For more examples, see fixing garbled CSV characters.

The bottom line

Windows-1252 CSV files are still common in real business workflows. The fix is not to guess repeatedly; it is to decode the file correctly once, verify the text, and export deliberately.

Download CEESVEE for free and open Windows-1252 CSV files without garbling accented characters.