Docuboxer
By ··Updated: ·13 min read

Why Excel Breaks Accents and Zeros in CSV Files

Fix garbled accents, vanished zeros and one-column chaos by converting your CSV to a clean XLSX, with a preview of what Excel will receive before you download anything.

To convert CSV to Excel without breaking anything, don't double-click the file: convert it to a real XLSX instead of letting Excel guess. The CSV to Excel converter detects the encoding and the delimiter, shows you the first rows as they will be read, and downloads an XLSX with your accents, leading zeros and long IDs intact. You can try it on your own file right now, and the file never uploads to a server: the parsing and the XLSX are both built in your browser.

Why does Excel mangle my CSV data?

A CSV file is just text. It carries no header declaring its encoding, no schema declaring column types, and no metadata naming its separator. Excel has to invent all three every time you double-click one, and it makes those guesses using your machine's regional settings rather than anything in the file. That is the whole bug: the CSV is fine, the guessing is the problem, and the guessing happens silently.

XLSX has none of these ambiguities: text is Unicode, every cell records its own type, and there is no delimiter to misread. Converting up front is not a workaround, it removes the entire class of failure. Here are the five ways the guesswork shows up, and what each one costs.

The five ways Excel breaks a CSV

1. Broken encoding: accents come out as é and ñ

Almost every modern export (a database dump, an API response, a Shopify or Stripe report) is UTF-8. Without a BOM, Excel's double-click path usually reads it with a legacy single-byte encoding such as Windows-1252, and single-byte decoders read multi-byte characters one byte at a time. In UTF-8, é is two bytes; decoded as Windows-1252 those bytes render as é. ñ becomes ñ, € becomes €, and a smart quote becomes ’.

Your data is not damaged: the bytes are correct and only the interpretation is wrong, so re-reading the file as UTF-8 restores everything. Avoid repairing it with find-and-replace: the mapping has dozens of variants, so hand-cleaning fixes what you noticed and leaves the rest to be saved back as genuinely unrecoverable text. According to Microsoft, a UTF-8 CSV opens normally if it was saved with a BOM (byte order mark); otherwise you have to import it with Get Data from Text/CSV.

The opposite failure exists too. Older desktop exports, including many saved from Excel in Spanish or other European locales, are Windows-1252 rather than UTF-8, and reading those as UTF-8 turns José into Jos�. A converter has to handle both directions, which is why this one checks the bytes instead of assuming.

2. Leading zeros vanish from ZIP codes, phone numbers and SKUs

Excel sees 01810, decides it is the number 1810, and stores it that way. A Massachusetts ZIP code loses its identity, a UK phone number loses its trunk 0, an internal SKU like 000457 collapses to 457, and a German postal code like 01067 becomes four digits. Every one of these is an identifier that merely looks numeric: you never add ZIP codes together, so nothing is gained by storing them as numbers.

The important detail is that this is not reversible by formatting. Re-formatting the column as text afterwards shows 1810 as text: the zeros were discarded during import and are simply gone. The only fix is to never let the coercion happen, which is what keeping the column as text at conversion time does.

3. Long numbers turn into scientific notation, or lose digits

Order IDs, credit-card-length numbers, EAN barcodes and Snowflake-style identifiers are long strings of digits. Excel treats them as numbers and displays them as 1.23457E+15. Widening the column does not help, because the display is a symptom rather than the problem.

The real damage is underneath. Microsoft states that Excel has a maximum precision of 15 digits, and its page on leading zeros and large numbers explains that for numbers of 16 digits or more, such as card numbers, you must use a text format. A 16-digit identifier does not just display badly, its 16th digit is replaced with a zero on import, permanently. This is why a batch of order references can come back from a spreadsheet round-trip with the same value repeated in rows that were originally distinct. An 18-digit ID loses three digits the same way. Any column of long identifiers must arrive in the spreadsheet as text, without exception.

4. Dates get reinterpreted into something you never wrote

Date coercion is the most locale-dependent trap of the five. 3/4/2026 is March 4th on a US machine and April 3rd on a European one, and the same file therefore means two different things on two colleagues' laptops. Excel will also invent dates out of values that were never dates. According to Microsoft, a number typed with a slash or a hyphen, or a fraction like 1/2, can be turned into a date, and there is no way to switch that off. A version string like 1.10 can also lose its trailing zero.

Worst of all, the original text is destroyed at the moment of import: what remains is a date serial number rendered through a format. If your CSV holds dates you actually want as dates, the safe route is to write them as ISO 2026-08-16 at the source and convert them in the spreadsheet deliberately, instead of letting an import path decide for you.

5. Every row lands in column A: the comma-versus-semicolon problem

The "C" in CSV is regional. Where the comma is the decimal separator, Excel writes and expects semicolon-separated files, because commas are already spoken for. The separator Excel uses on double-click comes from your operating system's list-separator setting and ignores the file, so a comma-separated export opens as one giant column A on a machine configured for semicolons, and a semicolon file does the same on a US machine. Per Microsoft, the list separator is changed in the Windows regional settings and affects every application.

Quoting is the related trap. A value containing the delimiter is wrapped in quotes, so "Main St, Apt 4" counts as one field. A parser that splits naively on every comma shifts every subsequent column for that row only, which is far worse than an obvious failure, because the file still looks broadly correct while a handful of rows are quietly scrambled. Any converter worth using honours quoting and escaped quotes inside fields.

How do I convert CSV to Excel, step by step?

  1. Open the tool: go to CSV to Excel.
  2. Add your data: drag in one or more CSV files, or paste rows straight into the text box if you only have a fragment. Parsing happens locally in your browser, so a customer list never touches a server.
  3. Read the preview: the first 20 rows appear exactly as they will be read, together with the detected encoding (UTF-8, UTF-8 with BOM or Windows-1252) and the detected delimiter. If accents look wrong or everything sits in one column, you see it here before anything is downloaded.
  4. Name the sheet and set the delimiter if needed: each file becomes a worksheet, named after the file by default. As Microsoft documents, a sheet name cannot exceed 31 characters or contain \ / * ? : [ ], so long or awkward names are trimmed automatically. Auto-detection is right for almost every file; if it isn't, override it with comma, semicolon or tab.
  5. Decide on type detection: the "Detect types" checkbox is on by default. Leave it on if you want plain numbers and ISO dates to become real numbers and dates, or untick it to keep every cell as text (see the next section).
  6. Convert and download: open the XLSX in Excel, Google Sheets or LibreOffice for the same clean result in all three.

What "Detect types" changes, exactly

A spreadsheet full of text cells is safe but awkward: you cannot sum a column of numbers stored as text. With Detect types on, the converter turns a cell into a real number or date only when that is unambiguous, and leaves everything else as text:

  • Becomes a number: plain integers and decimals with a dot, such as 42 or -3.75, up to 15 digits.
  • Becomes a date: valid ISO dates in the form 2026-08-16, written to the sheet as yyyy-mm-dd.
  • Stays text: anything with a leading zero (01810), anything longer than 15 digits, scientific notation, dates like 3/4/2026 whose meaning depends on the locale, and numbers that use a comma as the decimal separator.

A warning about numbers: converting a cell to a number drops trailing decimal zeros, so 1.10 arrives as 1.1. If those zeros matter (versions, codes), untick the box and the whole sheet arrives as text.

Merging several CSVs into one workbook

If you export one CSV per month, per region or per campaign, you can add all of them at once and each becomes its own worksheet inside a single XLSX, renamed to whatever you want before you convert. It is the difference between twelve loose files in a downloads folder and one workbook you can hand to someone. Duplicate sheet names are de-duplicated automatically rather than silently overwriting each other.

What this converter does not do

These are its limits:

  • It recognizes two encodings. It tries UTF-8 first and falls back to Windows-1252 when the bytes are not valid UTF-8, which covers nearly every CSV from modern systems and from Excel itself. Other encodings, such as UTF-16, are not detected, so re-export those as UTF-8 at the source.
  • Type detection is deliberately cautious. A column you want to do arithmetic on may arrive as text if its numbers use a comma decimal or carry a leading zero. If a total refuses to compute, convert that column to a number in Excel, where the choice is yours.
  • It is a conversion, not a rebuild. A CSV has no formulas, colors or column widths to preserve, so the XLSX arrives as clean unstyled data.
  • The whole file is parsed in memory. Large files are fine on a modern laptop; a several-gigabyte CSV is not, and no browser tool can honestly promise otherwise. An XLSX sheet stops at 1,048,576 rows and 16,384 columns, per Excel's specifications. Past that, a database or Power Query is the right destination.

One more thing worth checking before you share the file

If the CSV came from outside your organization, look at cells beginning with =, +, - or @. Spreadsheets read those as formulas, which is the basis of CSV injection: a hostile value in an exported field that executes when someone opens the workbook. It is a property of spreadsheets in general rather than of any converter, and scanning untrusted columns costs nothing.

When XLSX isn't the right destination

CSV is the universal bridge format for tabular data, and a spreadsheet is only one of the places it can land. If the destination is code rather than a person, JSON is usually the better target: the CSV to JSON converter turns rows into objects with named fields, and the JSON to CSV converter flattens API responses back into rows a spreadsheet can digest. If your data arrives as a feed or an export from an older enterprise system, it may be XML instead, and the XML formatter and validator will make it readable before you decide what to do with it.

Which direction to pick is a decision worth making on purpose. We work through it in CSV to JSON or JSON to CSV: when to use each format. And if you want the background on why converting between formats never changes the amount of data while encoding it as Base64 inflates it by a third, that's covered in what is Base64.

Is it safe to convert my CSV files online?

Only if the tool never uploads them. Think about what actually gets exported as CSV: customer databases, payroll runs, sales ledgers, support tickets. Sending one to a random "free converter" site hands a stranger the exact data your privacy policy promises to protect. This converter parses the CSV and generates the XLSX in your browser. You can check that for yourself by opening your browser's developer tools, watching the Network tab while you convert, and confirming that no request carries your data.

Frequently asked questions

Why does Excel change my CSV numbers?

Because CSV stores no types, so Excel infers one per column and rewrites the value to match. A 16-digit order ID becomes 1.23457E+15, an ID longer than 15 significant digits loses its trailing digits to zeros, 00123 becomes 123, and 3/4 becomes a date. Converting the CSV to XLSX with those values kept as text stops the inference before it starts, because XLSX records the type of every cell inside the file.

How do I open a CSV with the correct encoding?

Don't double-click it. Without a BOM, double-clicking usually hands the file to Excel's legacy import path, which reads it with a regional encoding such as Windows-1252 and turns UTF-8 accents into sequences like é or ñ. According to Microsoft, a UTF-8 CSV opens normally only if it was saved with a BOM. Otherwise import it through Data › Get Data › From Text/CSV, or convert the CSV to XLSX first: XLSX stores its text as Unicode, so the encoding question never comes up again.

Why did Excel delete the leading zeros in my CSV?

Excel guesses column types, decides 00123 is the number 123, and drops the zeros, which is ruinous for ZIP codes, phone numbers with a trunk 0 and product SKUs. Formatting the column as text afterwards does not bring the digits back, because the zeros were discarded at import. A converter that leaves those values as text preserves every digit exactly as the CSV had it.

My CSV uses semicolons instead of commas. Will it convert?

Yes. Semicolon-delimited files are common where the comma is the decimal separator. Docuboxer's converter detects the separator from the first rows and shows it in the preview, and you can override it per file with comma, semicolon or tab if the detection is wrong.

What's the difference between CSV and XLSX?

CSV is plain text: rows of values separated by a delimiter, no styling, no types, one sheet, no declared encoding. XLSX is Excel's real spreadsheet format: typed cells, multiple sheets, number formats, formulas and Unicode text. CSV is ideal for moving data between systems; XLSX is what people want to open and work in.

Can I convert a multi-gigabyte CSV in the browser?

No, and no browser tool should claim otherwise: the file is held in memory to be parsed, so very large CSVs will exhaust the tab long before they finish. An XLSX sheet also caps at 1,048,576 rows and 16,384 columns. For files at that scale, load the CSV straight into a database or use Excel's Power Query, and keep the browser converter for the files a person will actually read.

Is it safe to convert business data online?

Only with a tool that doesn't upload it. CSV exports are typically customer lists, payroll runs and financial records, exactly what shouldn't sit on a stranger's server. Docuboxer converts CSV to XLSX entirely in your browser; the data never leaves your machine.

Convert your CSV now

Clean XLSX with accents, zeros and dates intact. Free and private.

Convert CSV to Excel →

Related tools

You might also like: CSV to JSON or JSON to CSV, what is Base64 and when to use it and how XML structure and validation work.

Sources