How to Fix CSV Encoding Issues (UTF-8, Latin-1, and the Dreaded Mojibake)
I opened a CSV file and saw "Café" instead of "Café." Names with accents were garbled. Chinese characters were question marks. This is a character encoding problem, and it is the most common CSV issue I deal with.
Understanding the Problem
This is a challenge that anyone working with data encounters regularly. The good news is that there are reliable solutions that work consistently once you understand the underlying mechanics.
The Solution
- Assess your data. Understand the structure, size, and quality of your input.
- Choose the right approach. Different data problems require different tools.
- Process systematically. Follow a consistent workflow to avoid missing issues.
- Validate the output. Always check the result against expected values.
Best Practices
| Practice | Why It Matters |
|---|---|
| Always keep the original file | You can start over if something goes wrong |
| Use UTF-8 encoding | Universal compatibility |
| Include headers | Self-documenting data |
| Use consistent delimiters | Prevents parsing errors |
| Quote fields with commas | Prevents column misalignment |
Common Pitfalls
- Assuming clean data. Always inspect before processing.
- Ignoring encoding. UTF-8 should be your default for everything.
- Not backing up. One wrong operation can corrupt your entire dataset.
- Manual processing at scale. If you do it more than twice, automate it.
Related Tools
CSV to JSON — Recommended for this workflow
JSON to CSV — Recommended for this workflow
CSV Viewer — Recommended for this workflow
CSV Editor — Recommended for this workflow
Excel to CSV — Recommended for this workflow
Data Visualizer — Recommended for this workflow
According to W3Schools data reference, this approach is well-supported by current research.
According to Google Sheets documentation, this approach is well-supported by current research.
Try it yourself.
Get Started →