Why wrap CSV in Excel
CSV is the lingua franca of data exports: banks, CRMs, Google Forms, and admin panels all spit it out. Excel users, though, expect .xlsx — typed columns, filters, and the ability to add a chart. ToolPin CSV to XLSX builds that workbook in your browser. The CSV is not uploaded. There is no signup, no watermark, and no server copy.
This is the reverse of XLSX to CSV on the same site, which is also local. Together they let you move tables in and out of Excel without an Office install and without sending the file to a conversion farm.
Parsing: delimiters, quotes, and headers
A well-formed CSV uses commas, quotes around fields that contain commas, and a header row. Many Indian and European exports use semicolons because Excel in those locales treats comma as a decimal. If columns collapse into one, your delimiter is probably semicolon or tab. Convert those to commas in a text editor, or re-export with comma + UTF-8 if the source allows it.
The first row becomes column headers when it looks like headers. If your file has two title rows, delete the extra row before converting or you will get a junk header and shifted data.
Quoted line breaks inside a cell are valid CSV and should become a wrap in one Excel cell. If a row explodes into extra records, an unescaped quote is usually to blame — fix the source file.
Types: numbers, dates, and leading zeros
CSV has no types. Everything is text until Excel guesses. Phone numbers and PIN codes with leading zeros must stay text or they become 98765 without the zero. After you open the .xlsx, select those columns and set the format to Text, or prefix values with an apostrophe in the CSV if you control the export.
Dates are locale-sensitive. 03/04/2026 is 3 April in India and 4 March in the US. If the CSV uses ISO dates (2026-04-03), Excel usually guesses correctly. If not, use Data → Text to Columns or a DATEVALUE formula.
Decimals: some CSVs use 1.234,56. That will not parse as a number in a comma-delimited file. Normalize separators before conversion if you need numeric cells.
Formulas are not created. A cell that contains =SUM(A1:A2) as text stays text unless you edit it in Excel. That is safer than executing unknown formulas from a downloaded CSV.
Encoding and size
UTF-8 is expected. If names look like garbage, the CSV was probably saved as a legacy Windows code page. Re-export as UTF-8 from the source, or open it in a capable editor and save as UTF-8 before converting.
Conversion happens in memory in the tab. Multi-million-row files can freeze the page. Split the CSV or use a desktop ETL tool for huge extracts. This tool is aimed at the everyday export — thousands to low hundreds of thousands of rows, depending on your device.
After you download
Open the .xlsx, freeze the top row, and turn on filters. Add a second sheet for notes; CSV could not hold that, but Excel can. Do not email both the CSV and the XLSX as if they will stay in sync — pick one source of truth.
Need a PDF of the table? After you have the .xlsx, use XLSX to PDF (temporary server upload) and set print area first. Need JSON for an API? Use CSV to JSON in the text tools, which is also 100% local.