Fix Broken Characters (Mojibake) in Excel CSV Exports
When you open a UTF-8 encoded CSV in Excel, international characters like 'Müller', 'José', or '北京' often render as 'Müller' or 'Josa©'. This is called Mojibake. Despite being a modern spreadsheet, Excel assumes the legacy Windows-1252 encoding unless it sees a 3-byte signature at the start of the file: the UTF-8 Byte Order Mark (BOM: 0xEF, 0xBB, 0xBF). Most Mac/Linux software exports raw UTF-8 without a BOM. This workflow reads your raw binary file, detects the encoding, and re-exports it with the correct BOM prefix—instantly making it 'Excel-safe' without needing to use the complex 'Data → From Text/CSV' import wizard.
Why This Matters
An SDR team spent 40 hours manually correcting 12,000 names because their French prospect list looked like gibberish in Excel. This data corruption breaks CRM imports and leads to embarrassing 'Hi Josa©' emails that kill response rates. Fixing the encoding at the file level takes 0.5 seconds and prevents the corruption from flowing into your CRM or ESP.
Why Excel & Python Fail Here
Excel's default 'Open' behavior (Double-clicking a CSV) ignores UTF-8 standards. It requires a BOM to trigger the correct code page. Manual fixes require using the 'Import' wizard, which has 8 steps and must be repeated for every file. This tool applies the fix at the byte level—no import wizard required.
| Criterion | Excel / Sheets | Python / Cloud | DataPrep (This Page) |
|---|---|---|---|
| Max Rows | ~150K (crashes) | RAM-limited | 1M+ via Wasm |
| Setup Time | Manual formulas | 30–60 min env setup | 0 seconds |
| Data Privacy | Local but fragile | Uploads to cloud | 100% in-browser |
| Cost | License fees | EC2 / SaaS $49+/mo | Free forever |
Step-by-Step Solution
We will use the Format Cleaner to execute this entirely in your browser.
- 1
Upload the 'Broken' CSV
Drag and drop the file. The tool reads the first 1024 bytes and identifies if a BOM is missing. A preview shows you exactly how the characters currently look vs how they SHOULD look.
- 2
Inject UTF-8 BOM
The tool prepends the 0xEF, 0xBB, 0xBF signature to the byte stream. This does not alter your data; it simply tells Excel: 'This is a modern UTF-8 file'.
- 3
Download Excel-Ready CSV
Click Download. Open the file in Excel—names like Müller and José will now render perfectly on the first double-click.
Privacy Guarantee: Zero Bytes Uploaded
All processing happens in your browser via WebAssembly. Your data never touches a server. Try it: disconnect your Wi-Fi right now—the tool will still work.
Common Errors & Fixes
| Error / Symptom | Root Cause | Fix |
|---|---|---|
Characters look like é or € | Missing UTF-8 Byte Order Mark (BOM). Excel is guessing Windows-1252 encoding. | Re-export with BOM enabled using this tool. |
Frequently Asked Questions
Will this break my Python or Mac software?
Ready to clean your data?
100% local processing · Zero uploads · Blazing fast
Trusted by 2,400+ data teams · 18M+ rows processed monthly