Change Korean CSV encoding: CP949 input and UTF-8 output
For garbled Korean CSV, first determine which encoding should interpret the original bytes. Re-saving incorrectly decoded text in another encoding can preserve the garbled values rather than recover the intended characters.

How to use this tool
- Choose files in CSV, TXT format. Maximum files per batch: 1.
- Review Source encoding, Output encoding, then start processing.
- Download the CSV result and check its content and quality.
Choose the right settings
Choose UTF-8, an EUC-KR-compatible source or UTF-16LE as appropriate. Output choices are UTF-8, UTF-8 with BOM and UTF-16LE; there is no CP949 writing option.
- Supported input
- CSV, TXT
- Output
- CSV
- Available settings
- Source encoding
- Output encoding
Before you start
Establish the meaning of the input
Before converting or arranging data, identify what a row or value represents and keep a source copy. In tabular files, review headers, separators and text encoding; in structured files, inspect the required object or array shape. Identifiers, dates and amounts should not be interpreted solely from how a spreadsheet happens to display them.
Where the tool offers matching columns, type rules or output fields, choose them according to the destination’s requirements. Test a sample with a blank, a repeated value and a value containing punctuation. For labels, charts or personalized documents, check which column supplies each displayed value and whether the source units and wording are correct.
Define a few checks before processing: an identifier that must retain its spelling, a value with a known interpretation and an expected relationship between records. If the tool offers type conversion or matching rules, distinguish a source value from the program’s display of it. Test ambiguous dates or differently written keys before accepting a broad rule. Keep the chosen rules and destination requirements with the result; this makes a discrepancy traceable to input, interpretation or the requested transformation.
Verify values, structure and exceptions
Reopen or import the result using the destination’s settings. Compare headers, record counts and several values with the source, allowing for the operation you requested. A summary, split or duplicate-removal task can legitimately change the count; verify why it changed rather than expecting every transformation to keep identical rows.
Inspect any exception or validation report before continuing. If columns shift, characters are garbled or a key is not found, check delimiters, encoding and exact header spelling first. Encoding data does not encrypt it, and formatting a value does not confirm its meaning. For printed codes or labels, test the actual output before making the full set.
Example input and output
known source encoding → UTF-8/UTF-8 BOM/UTF-16 LE CSVExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Compare Korean names and symbols with their display in the source application. Re-import the saved file in its destination program and review column separation as well as characters.
If the result is different from what you expected
A wrong source encoding can produce an error or interpret characters incorrectly. If question marks or damaged characters are already stored in the source, changing encoding alone cannot reconstruct the lost text.
Limits to keep in mind
- The source encoding must be correct. This does not repair text that was already corrupted before upload.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.