GUIDE - Updated 2026-06-25
Excel Character Encoding for CSV
Choose the right Excel CSV encoding by comparing UTF-8, UTF-8 BOM, Shift-JIS, CP949/EUC-KR, delimiters, and upload requirements.
Open CSV Encoding FixerQuick Answer
Excel CSV encoding problems happen when Excel guesses a character set, delimiter, or BOM behavior differently from the system that created the file. Use CSV Encoding Fixer to compare previews, then choose the output by destination instead of looking for one universal CSV.
Excel vs Upload Decision Table
| Situation | Best First Choice | Why |
|---|---|---|
| Excel must open the file by double-click | UTF-8 with BOM | Helps Excel recognize UTF-8 directly |
| A browser upload form receives the file | Plain UTF-8 | Some upload validators treat BOM as extra bytes |
| Japanese legacy export | Preview Shift-JIS / CP932-style input first | Prevents mojibake before converting |
| Korean legacy export | Compare CP949 / EUC-KR-style input first | Prevents broken Hangul before converting |
| Columns shift after opening | Check delimiter and quotes before encoding | Encoding and CSV structure are separate problems |
When UTF-8 BOM Helps
UTF-8 BOM can be useful when a human reviewer will double-click a CSV in Excel and expect it to open immediately with readable Korean or Japanese text. It is an Excel-sharing copy, not a guarantee that every upload system will accept the file.
When Plain UTF-8 Is Safer
Plain UTF-8 is usually safer for APIs, web uploads, databases, and automated jobs because the receiving system can parse the first header exactly. If the destination documentation mentions BOM handling, follow that requirement.
Practical Workflow
- Keep the original CSV untouched.
- Paste a small sample into CSV Encoding Fixer.
- Compare UTF-8, UTF-8 BOM, Shift-JIS-style, and CP949/EUC-KR-style signals.
- Confirm delimiters and quoted fields before exporting.
- Create separate files for Excel review and production upload when needed.
- Test the output in the real destination with a small row set first.
Practical FAQ
What encoding should Excel CSV use?
There is no single answer. Use UTF-8 with BOM when Excel must open the file directly, and plain UTF-8 when a web system or API expects a clean UTF-8 file.
Is a delimiter problem the same as an encoding problem?
No. Mojibake breaks characters; delimiter issues shift columns. Check both because they often appear together in messy CSV handoffs.
Why does a CSV look correct in Excel but fail upload?
Excel may tolerate or hide details that upload systems reject, including BOM, line endings, empty required columns, or inconsistent quotes.
Should I convert Shift-JIS to UTF-8 before uploading?
Usually yes for modern systems, but preview the original first. If the text is already garbled, conversion will preserve the wrong characters.
Can I use one CSV for every destination?
Sometimes, but separate Excel-review and upload-safe copies are less risky when business users and systems consume the same data.
Related Tool
Related Articles
Updated
Last reviewed: 2026-06-25.
Official references
These official references were used to verify the criteria discussed in this article.
- Import or export text (.txt or .csv) filesMicrosoft Support - Checked: 2026-06-25
- Encoding StandardWHATWG - Checked: 2026-06-25
- TextDecoderMDN Web Docs - Checked: 2026-06-25
- The Unicode StandardUnicode Consortium - Checked: 2026-06-25