How to use
- Drop a
.csv,.tsv,.txtor.xlsxfile, or paste cells copied from Excel. This page opens with the Convert (export settings) step ready. - For CSV, check the encoding (auto-detected) and delimiter; for xlsx, check the sheet and whether the first row is a header.
- Under Export, choose xlsx, csv or json and set the options.
- Download. The file name looks like
original_cleaned.xlsx.
Directions and options
| You want to | Setting |
|---|---|
| CSV → XLSX | Export format xlsx |
| XLSX → CSV | Format csv. One sheet is converted at a time |
| Change the delimiter (comma, tab, semicolon, pipe) | Set the delimiter used to read (auto or manual) and the one used to write separately |
| Excel → JSON | Format json: an array of objects (headers as keys) or an array of arrays |
| Change the encoding | csv encoding: UTF-8 (BOM, default) / UTF-8 / CP949 |
For CSV you can also pick the line ending (CRLF default, or LF), quote every value, and formula-injection protection.
Converting delimiters
The same table is saved with a different delimiter. Take a table Name, Note, Amount with rows Kim, =SUM(A1), -12.5, Lee Younghee (with a comma in the name), a note containing a line break, 1234.5 and Park, (empty), 00123. Saved with semicolons, the first line is Name;Note;Amount, and a name containing a comma is written as-is because the comma is no longer the delimiter. If a value contains the delimiter or a line break it is wrapped in "…" automatically, like the note with the line break above. Saved with tabs, the first row reads Kim[tab]'=SUM(A1)[tab]-12.5.
Many European versions of Excel use a semicolon as the CSV delimiter instead of a comma, so if all columns appear squeezed into one, change the delimiter first.
Leading zeros and CSV formula protection
- CSV values are read as text exactly as written, so
00123stays00123. Saving as xlsx keeps them as text cells, so the leading zero survives. Even with the “save as numbers” option on, values with a leading zero are left alone. - When exporting CSV, a text cell starting with
=,+,-or@could be run as a formula by Excel, so a'is put in front (on by default).=SUM(A1)becomes'=SUM(A1), while the number-12.5stays as it is. JSON export does not apply this and writes the value as is.
Encodings
- UTF-8 (BOM): the default that keeps Korean and other non-ASCII text intact in Excel. A 3-byte BOM is added at the start.
- UTF-8: no BOM, better for developer and data tools.
- CP949: for old Korean software. Hangul takes 2 bytes, so
가나다plus a CRLF line break is 8 bytes, and characters CP949 lacks (such as emoji) become?. The number of replaced characters is shown on the export panel. - When reading, UTF-8 and CP949 are detected automatically and you can choose manually. If you only need to change the encoding, there is also the Text Encoding Converter.
Formats that are not supported
| Format | Support | Alternative |
|---|---|---|
| .xlsx | Read and write | - |
| .csv · .tsv · .txt | Read and write | - |
| .xls (Excel 97–2003) | Not supported | In Excel use “Save As → .xlsx”, then convert |
| .ods, password-protected files | Not supported | Remove the password and save as .xlsx |
An .xls file is an old binary format whose first bytes are D0 CF 11 E0; it cannot be opened and a notice is shown instead. Renaming the extension to .xlsx does not convert it. Formula cells are read as their last calculated values, so only values are saved.
Related tools
- Clean up before converting: Excel & CSV Workbench
- JSON and CSV conversion: JSON CSV Converter
- Changing only the encoding: Text Encoding Converter
- Sorting and filtering: Sort & Filter Spreadsheet
Your file is processed only in your browser and is never sent to a server.