CSV to Excel converter

What your spreadsheet needs first

Preparation here is about the table rather than the map, because this conversion asks for no coordinates anywhere in the file. A tidy CSV becomes a tidy workbook, and a few minutes spent on the text file spare whoever opens the result from repairing it later.

Three things to check before converting

• One header row at the very top, since the first line of the file becomes the column titles of the worksheet and a report banner above it would arrive as a data row.
• The same number of fields on every line, which means a description containing a comma must sit inside double quotes or that row splits into an extra column and drifts out of alignment.
• Plain values in number columns, with currency symbols and thousands separators stripped out, so the workbook can store the figures as true numbers rather than as text.

Columns of latitudes and longitudes are welcome and entirely optional, and they cross over as ordinary numbers like every other field. A table that should end up on a map rather than in a workbook belongs with the spreadsheet to map converters, which do read coordinate columns.

Why convert CSV to Excel?

Excel's double-click CSV import is notorious for quiet damage: leading zeros stripped from codes, identifiers rewritten as dates, long decimals rounded without a word. Writing the table as a native .xlsx sidesteps that import entirely, because a workbook stores numbers as numbers and dates as dates rather than the undifferentiated text a CSV holds. Coordinate columns, when the table has them, arrive as true numeric cells that Excel will not reformat on opening, and the same protection covers every other column in the sheet.

Coordinate system handling

No coordinate system is read, guessed or applied on this trip, because the converter carries every column across as plain values without looking for a location in any of them.

A workbook cell cannot hold a CRS tag, so a sheet of projected eastings and northings should name its system and units where a colleague will find them, in a header or a notes column. Writing EPSG:32643 beside UTM values costs one cell and settles every later question about what the numbers mean.

What to check when converting CSV to Excel

One CSV becomes one worksheet, so a set of related files needs converting one at a time before being combined into tabs. Give the result a short inspection as well: scan a few rows of long coordinate values and any code column that should start with zero, because a plain text source carries no hint that 0730 was a label rather than the number 730.

Troubleshooting CSV to Excel

• A code column lost its leading zeros. A CSV hands the converter plain digits, so a code arrives as the number it spells. Format the column as text in the workbook and restore the zeros there, or pad the codes in the system that exported the CSV and convert again.
• Accented characters came through garbled. The source file was saved in an older regional encoding rather than UTF-8, so the bytes no longer spell the intended characters. Export the CSV again as UTF-8 from the program that produced it and convert the fresh copy.
• Long coordinates look rounded in the cells. Excel often shows a shortened display while the cell still holds the full value. Widen the column or raise the displayed decimal places before concluding that precision was lost.
• Every value landed in a single column. Excel installations across much of Europe export CSV with semicolons between the fields, and a short or irregular header line can defeat the automatic delimiter detection. Re-export the table with comma separators, or swap the semicolons in a text editor outside any quoted values, and the columns come apart cleanly.
• The workbook stops at 1,048,576 rows. That figure is the hard worksheet ceiling of the .xlsx format rather than a fault in the conversion. Split a larger CSV into parts before converting, or keep an export of that size in a database format with no row limit, and bring Excel only the slice it actually needs.

About the formats

A CSV travels well between databases, scripts and converters precisely because it is nothing but delimited text, and that same bareness makes it fragile in front of a spreadsheet program. The Excel workbook is the opposite trade: a packaged file with typed cells that a colleague can sort, filter, chart and format without disturbing the underlying values. No coordinate columns are required at any point, since this is a table-to-table conversion; a price list converts exactly as happily as a survey of points.

Related converters