Fix Garbled Korean Text When Opening UTF-8 CSV in Excel
Use Excel's text and CSV import options to diagnose character-encoding problems without rewriting the original file.
What is the problem?
A CSV is a text file, and characters can appear corrupted when the reader chooses the wrong encoding. Before editing, distinguish a display or import problem from data that was already damaged during export.
Step-by-step solution
Keep a source copy and inspect the raw file
Duplicate the CSV before opening and saving it in a spreadsheet. Check whether a plain-text editor displays the Korean text correctly; an unwanted save operation may change encoding or data types.
Import through Excel's Text/CSV data menu
Microsoft documents using Get Data from Text/CSV or the text import wizard when a UTF-8 file has no byte order mark. Inspect the preview and choose the encoding that actually displays your source text correctly.
Verify identifiers and dates after import
Check that postal codes, employee IDs and phone numbers have not lost leading zeros. Inspect date columns and re-import with explicit text types where Excel converted values unexpectedly.
Alternative method
Ask the file provider for a UTF-8 CSV with a byte order mark if the receiving workflow supports it; first verify compatibility with downstream systems.
Known limitations
Encoding selection cannot restore text already corrupted in the source file. The import menus and conversion behavior depend on the Excel version and platform.
Frequently asked questions
No. It may only have been decoded using the wrong encoding. Check the untouched source in a text editor before deciding whether the original data was damaged.
Official primary sources
This article uses the official references below; consult them for the full guidance.
