CSV to Excel

Excel opens CSV by itself — badly. It guesses the separator from your regional settings, so in half of Europe a comma-separated file lands in a single column. It reads a file without a BOM as the local encoding, so Cyrillic turns into rubbish. And it quietly mangles long numbers: article codes lose their leading zeros, sixteen-digit card numbers become exponents. Here the file is read properly and you see the result before you press the button.

The file is read in your browser and the workbook is written there too — nothing is uploaded. The encoding is detected as well: a CSV saved in Windows-1251 does not have to turn into gibberish.

Nearby: CSV to JSON · Excel to PDF · PDF to Excel · JSON Formatter and Validator

How to use

  1. Choose the CSV file, or paste the table into the box.
  2. Look at the preview: if the columns are wrong, pick another separator.
  3. Press the button and download the XLSX.

Good to know

Where a plain CSV goes wrong

Three things break it, and all three are invisible until the file is already open. The separator: Excel takes it from the system list separator, not from the file. The encoding: without a BOM it assumes the local one, and a UTF-8 export shows as mojibake. And the values: anything that looks like a number becomes a number, so «007» turns into 7 and a long code turns into 1.23E+15. This page detects the first two and writes the third as text.

Rows are squared off

Exports often stop writing trailing empty cells, so the rows are ragged: the header has nine columns, some rows have seven. A spreadsheet expects a rectangle, so short rows are padded with empty cells — otherwise a formula over the last column silently reads different fields on different rows.

Frequently asked questions

Is my file uploaded?

No. It is read in your browser and the workbook is written there too.

What if the columns come out wrong?

The separator was guessed wrong — pick it by hand in the list. The preview updates at once, so you see the correct answer before converting.

Will leading zeros survive?

Yes. Values go into the cells as text, so «007» stays «007» and a long code does not become an exponent.

And Cyrillic from an old export?

The encoding is detected: a file saved in Windows-1251 is read as such instead of turning into gibberish.

Related tools