Why UTF-8 Matters for Excel CSV Exports
CSV is a byte stream plus an encoding agreement. UTF-8 is the modern default that handles English, accents, currency symbols, and non-Latin scripts equally well.
When Excel saves a plain "CSV" without choosing UTF-8, older Windows exports may use a legacy code page and downstream systems display mojibake like café or ?? in place of names.
Save Options in Excel Compared
Excel offers several CSV variants. Pick UTF-8 when the audience is international, is on another OS, or uses non-English text.
| Format | Encoding | When to use |
|---|---|---|
| CSV UTF-8 (Comma delimited) | UTF-8 (typically with BOM) | Default choice for cross-platform, multilingual data |
| CSV (Comma delimited) | System default (often Windows code page) | Legacy Windows workflows without special characters |
| CSV (Macintosh) | Mac-specific line endings | Legacy Mac workflows |
| CSV (MS-DOS) | DOS-specific | Legacy DOS pipelines |
Step-by-Step: Save Excel as UTF-8 CSV
Activate the correct sheet first. CSV saves only the active sheet.
- Open the workbook and select the sheet that contains the data.
- Choose File > Save As (or Save a Copy).
- In the file type dropdown, pick CSV UTF-8 (Comma delimited) if available.
- Save with a clear filename and .csv extension.
- Reopen the CSV in a plain text editor or the Online CSV Editor to verify accents and symbols.
- If characters look wrong, re-check the format choice and try again.
If the UTF-8 CSV option is missing
Older Excel versions may lack the UTF-8 option. Two safe workarounds: (1) copy the sheet into an Excel version that supports it, or (2) use a browser-based workflow—open the workbook in the Online XLSX Editor, export CSV, and verify in the Online CSV Editor. Convert CSV Online works on Windows, macOS, and Linux browsers.
About the BOM (Byte Order Mark)
UTF-8 CSV files saved from Excel often begin with a BOM. That mark helps some tools recognize UTF-8, especially on Windows.
A few parsers dislike the BOM and treat it as an extra character on the first header. If the destination importer shows a strange character before your first column name, strip the BOM by re-saving from a BOM-free tool or a script.
- Excel on Windows tends to detect UTF-8 more reliably with a BOM.
- Some Linux tools and CSV libraries do not need the BOM.
- Test both when you can, and document your choice for consumers.
Verify After Saving
Do not trust that Save As worked. Confirm with fresh eyes.
- Open the CSV in a text editor and inspect a row that contains accents or currency.
- Preview in the Online CSV Editor and check international columns.
- Try re-importing into Excel with Data > From Text/CSV and confirm the same characters.
- If the destination system supports it, test-load a small sample.
Real-World Examples
UTF-8 discipline is what separates working exports from urgent tickets.
Global customer list
A CRM export contains names from Québec, France, Vietnam, and Japan. Saving as CSV UTF-8 preserves every character; the plain CSV option would corrupt many.
UK finance report
£ symbols travel intact when saved as UTF-8 and are less likely to appear as ? on Linux servers.
Bilingual education dataset
A class dataset with English and Bangla text stays readable end-to-end after UTF-8 export and preview.
Common Mistakes
Small choices in the Save dialog create big downstream problems.
- Picking plain CSV when the data has non-English text.
- Ignoring the BOM effect on strict parsers.
- Saving multiple sheets in one file (only the active sheet is written).
- Not verifying after saving.
- Overwriting the workbook after a bad round trip.
Best Practices
Standardize on UTF-8 whenever you can.
- Prefer CSV UTF-8 in Excel for interchange.
- Keep the .xlsx as the working file.
- Document delimiter and encoding for recurring feeds.
- Verify special characters after every export.
- Use the Online CSV Editor for a quick verification loop.
Why Use Convert CSV Online?
When Excel’s Save As is limited, Convert CSV Online provides a free, browser-based alternative for cleaning and exporting CSV without installing anything. It requires no account for everyday conversions and processes these workflows client-side across Windows, macOS, and Linux browsers.
Ship UTF-8 CSV confidently
Export from Excel, verify in the Online CSV Editor, and hand off a file your international audience can actually read.
Conclusion
Saving Excel as UTF-8 CSV is a two-second choice with outsized impact. Pick UTF-8, verify special characters, and standardize the workflow for teams that share data globally.
FAQ
How do I save Excel as UTF-8 CSV?
Use File > Save As and choose CSV UTF-8 (Comma delimited) when available. Verify special characters afterward.
Why is my Excel CSV showing broken characters?
The file was probably saved with a legacy encoding, or the reader assumed a different one. Save as UTF-8 CSV and reopen with UTF-8.
What is a BOM and do I need it?
A byte order mark is an optional signature at the start of a UTF-8 file. It helps some Windows apps detect UTF-8 but can appear as a stray character in strict parsers.
Does Excel export UTF-8 by default?
Not always. Older versions and some regions default to a legacy code page. Explicitly choose CSV UTF-8 when it exists.
Can I convert my existing CSV to UTF-8?
Yes. Preview and re-save with UTF-8 encoding using a CSV-aware editor or script. Keep the original as backup.
What if my Excel version has no UTF-8 CSV option?
Use a newer Excel version, or export via a browser-based workflow that supports UTF-8 explicitly.
References
Convert your CSV in the browser
Preview, clean, and convert CSV files free with Convert CSV Online—no installation and no account required for everyday conversions.