CSV to XLSX Converter

Choose a CSV. The download is a one-sheet XLSX of those cells.

Use this tool

Drop a file here, or use the picker. The file type is checked from its contents.

Result

The result appears in this panel after you run the tool.

About this tool

Every cell is an inline string in Sheet1.

How to use it

  1. Choose a CSV file. Commas and quoted fields follow the usual CSV rules.
  2. Convert it. The sheet is named Sheet1.
  3. Download the XLSX. Open it in a spreadsheet program. Formulas are not created.

Limitations

CSV rows as inline strings

Reading the CSV

The file is decoded as UTF-8 and parsed with a comma delimiter and a double-quote quote character. A quoted field may contain a comma or a line break. Two quotes inside a quoted field are one quote. Rows can differ in length. An empty file, or a file with no rows, is rejected. The sheet name is Sheet1. There is no control to rename it on this page. If you need several named sheets, build the JSON shape and use JSON to XLSX.

Writing the package

The XLSX is a ZIP of the parts a spreadsheet needs to open: content types, the package relationship, a workbook with one sheet, the workbook relationships, and the worksheet XML. Each cell is an inline string. The characters are XML-escaped. A value that looked like a number is still a string in the file, so a spreadsheet may show it as text until you convert the column. Dates are not detected. Formulas are not invented from text that starts with an equals sign. That text is stored as the characters you had, which is safer than executing it. Column letters go A, B, and onward, including AA when a row is wide.

Round trip

XLSX to CSV on this output should return a comma file of the same strings, aside from quoting differences the CSV writer normalizes. Styles will not appear, because none were written. A second hop will not add types. If the original CSV was an export from a workbook that had formulas, those formulas were already gone before this page saw the file. This page cannot recover them. The cap for a produced file is the memory of the browser. The reader side of the other Office tools still refuses encoded inputs over 80 MB.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.