When you need CSV to Excel
A .csv arrives with garbled Chinese or broken columns when opened; or you need merge, dedup, or SQL export—those flows work better with xlsx. ComTools CSV to Excel (Tools/Excel/CsvToExcel) uploads CSV and returns a standard .xlsx workbook.
Conversion rules
| Item | Details |
|---|---|
| Input | .csv only |
| Encoding | Read as UTF-8 with BOM auto-detection |
| Delimiter | Comma , (simple parse; trim surrounding quotes) |
| Output | Single-sheet .xlsx (Sheet1) |
| Layout | CSV row 1 → Excel row 1 |
Steps
- Open CSV to Excel.
- Select a UTF-8 (or BOM)
.csvfile. - Click Convert.
- Download
.xlsxand verify columns and text in Excel.
Common scenarios
| Scenario | Next |
|---|---|
| Fix garbled view | Confirm encoding after xlsx export |
| Join merge | Convert to xlsx first |
| Dedup / format | Remove duplicates, format |
| Database | Excel to SQL or import guide |
| JSON | Excel to JSON |
Encoding troubleshooting
| Symptom | Fix |
|---|---|
| Still garbled | Source may be GBK—re-save as UTF-8 |
| Wrong columns | Unescaped commas—quote fields in source CSV |
| Odd first column | BOM handled; usually harmless |
See CSV import tips for more.
Notes
- CSV input only—use Excel tools directly for xlsx.
- One sheet per CSV—split multi-table data into files.
- Complex CSV (embedded newlines, custom delimiters) may need Excel “From Text” then save xlsx.
- Server-side conversion—mind data sensitivity.
Round trip with Excel to CSV
Excel → CSV → edit elsewhere → CSV to Excel → continue in ComTools
Workflow
UTF-8 CSV download → CSV to Excel → dedup → SQL INSERT → test DB
FAQ
GBK CSV?
Tool reads UTF-8; convert GBK to UTF-8 first.
Semicolon delimiter?
Comma parser only—import in Excel or use text format.
Multiple sheets?
One CSV → one sheet; use multiple files or merge.
vs Excel From Text?
Same goal—quick xlsx for the ComTools pipeline.