table_view CSV to Excel Converter (& Excel to CSV) star

How the Conversion Respects the Format

CSV → Excel: paste or choose a CSV (comma, semicolon or tab separated — detected automatically) and download a genuine .xlsx workbook, not a renamed text file. The parser follows RFC 4180, the actual CSV specification: fields are separated by commas, but any field that itself contains a comma, a double quote, or a line break must be wrapped in double quotes — "Smith, John" stays one field, not two, and a quoted multi-line value stays one cell instead of splitting the row. Numbers land in Excel as numbers, text as text, and Turkish/accented characters survive intact — the three things that break when someone just renames a .csv to .xlsx.

Excel → CSV: choose an .xlsx file, pick the sheet if there are several, preview the data, and download UTF-8 CSV with the delimiter you choose. Concrete example: a cell containing Ankara, Turkey is exported as "Ankara, Turkey" — quoted — precisely so a comma-delimited reader doesn't mistake it for two columns. A BOM is included so Excel reopens the CSV with correct accented characters.

The quoting rule cuts both ways, and understanding it explains most "why did my CSV break" moments. A field that contains a literal double quote has that quote doubled and the whole field wrapped in quotes — He said "hi" becomes "He said ""hi""" — which is exactly why hand-editing a CSV in a plain text editor is riskier than it looks: get the doubling wrong and every spreadsheet reader downstream will parse the row differently. Sticking to RFC 4180 in both directions is what lets this tool round-trip odd data — addresses with commas, notes with line breaks, quotes inside quotes — without silently shifting columns.

What's Worth Knowing

• Excel's own CSV dialect isn't universal. In many European and Turkish locales, Excel exports CSV with a semicolon delimiter instead of a comma — because the comma is already used as the decimal separator in those locales (1.234,56 instead of 1,234.56), so it can't double as a field separator without ambiguity. This is a frequent, genuine source of incompatibility when a CSV file crosses borders: a Turkish or French Excel export opened as comma-delimited elsewhere lands entirely in one column.
• Dates are stored as serial numbers. The "date-looking" display is a cell format layered on top of a plain number; converting only moves the underlying value faithfully.
• Formulas don't survive to CSV. CSV has no formula concept, so Excel → CSV exports each formula's last calculated result, not the formula itself.
• Nothing is uploaded. Both directions run in your browser with JavaScript; no row limit beyond your device's memory, and closing the tab clears everything.
• Sheet selection matters for multi-tab workbooks. Only the sheet you pick is converted; if your data is spread across several tabs, run the conversion once per sheet rather than expecting them merged into one CSV.