When CSV Exports Open as One Column in Excel

Double-click a marketplace or SaaS CSV and Excel sometimes parks the entire row in column A. Delimiter and encoding guesses fail more often than people admit.

Fast fix

Upload the file to /tool/csv-to-excel and open the .xlsx. Columns come back as columns.

Going the other way

Legacy importers that only accept CSV: /tool/excel-to-csv. Engineering fixtures: /tool/excel-to-json, then tidy with /tool/json-formatter if needed.

Prevention tip

Ask vendors for UTF-8 CSV with a clear delimiter — but when you only have the broken file, conversion beats fighting the import wizard.

Why Excel piles everything into column A

Excel guesses the separator from the first lines. A European export that uses semicolons, or a file that uses tabs, often fails that guess and the whole row stays in A. Encoding does the same when names contain accents and the file is not UTF-8: characters turn into junk and the delimiter can be misread with them. Opening the file by double-click uses those guesses. Converting to a workbook writes real cells, so the delimiter question is already answered. After you have columns, scan the header row. A blank first column or a title sitting above the headers means the table starts on the wrong row — fix that in Excel before you convert onward to JSON. If a field itself contains commas, a good conversion keeps it as one cell. If it split, the source quoting was broken and you may need the vendor’s file again rather than another pass on the damaged CSV.