My CSV looks garbled in Excel. Why?
Excel reads CSV in the system encoding, so UTF-8 or GBK files come out garbled when they don't match. The encoding is detected automatically and the file converted to xlsx, or kept as a UTF-8 CSV with a BOM that Excel opens correctly.
IDs turn into 1.23E+17. How do I stop that?
Numbers longer than 15 digits, codes with leading zeros and scientific-looking values are kept as text during conversion.
Which formats are supported?
CSV / TXT / TSV, plus old .xls, binary .xlsb and OpenDocument .ods (to .xlsx).
Are formulas and formatting kept when converting xls to xlsx?
Yes. Old formats are converted with LibreOffice, keeping formulas, formatting and all sheets; some complex formatting may differ slightly, so open the result to check. .xlsx can't hold macros, so macros in an .xls are lost.
The last digits of my IDs turned into 000. Can I get them back?
Excel keeps only 15 significant digits, so once saved the extra digits are gone; convert again from the original CSV. This tool keeps numbers longer than 15 digits as text, so no digits are lost.
Are semicolon or tab separated files detected?
Yes. Comma, tab, semicolon and pipe separators are detected automatically.
Can it fix garbled Traditional Chinese (Big5) CSV?
Yes. Encodings are tried in order: UTF-8, GBK (GB18030), Big5.