CSV UTF-8 BOM for Excel: When to Use It
CSV files do not always say what character encoding they use. Many modern tools export UTF-8, but some versions or configurations of Excel may open a CSV with the wrong encoding if there is no clear signal. A UTF-8 BOM is a small marker at the beginning of a file that can help Excel recognize UTF-8 text.
Symptoms of encoding problems
- Names with accents show strange characters.
- Currency symbols display as boxes or odd letter pairs.
- Non-English product titles look corrupted.
- Text looks fine in one app but broken in Excel.
When to enable UTF-8 BOM
| Situation | Recommendation |
|---|---|
| Opening the cleaned file directly in Excel | Enable UTF-8 BOM if text may contain accents or symbols. |
| Importing into a database or developer tool | Check the target first; many tools do not need BOM. |
| Sharing with mixed spreadsheet users | BOM can reduce Excel encoding surprises. |
| Plain ASCII data only | BOM usually does not matter. |
How the cleaner uses it
Universal CSV Cleaner includes an Excel UTF-8 BOM option. When enabled, the downloaded CSV starts with the UTF-8 marker. The cell values are still normal CSV text; the marker only helps spreadsheet software interpret the file encoding.
What BOM does not fix
BOM does not repair a file that was already saved with corrupted characters. It also does not choose a delimiter, infer missing columns, or translate text. If characters are already broken in the source export, go back to the original system and export again using UTF-8 if possible.
Quick test
If you are unsure, export two cleaned files: one with BOM and one without. Open both directly in Excel and compare names, accents, currency symbols, and product titles. Keep the version that opens cleanly in the tool your recipient will actually use.
Create an Excel-friendly CSV