Drop your TXT file here
or click to choose a file — or paste your data below
What makes it a proper CSV
- The separator is detected. Tab, pipe, semicolon and comma exports are all recognised by which one gives a consistent column count, not by the file extension.
- Fields get quoted when required. A value containing the separator, a quote or a line break is quoted and escaped, which is what a naive find-and-replace gets wrong.
- Line endings are normalised. Windows CRLF, Unix LF and old Mac CR all read; the output uses CRLF, which is what Excel expects.
- A UTF-8 mark is written. Without it, Excel opens the file in a legacy encoding and accented characters come out wrong.
- Ragged rows are padded. Fixed-width exports that lose trailing empty fields still line up.
- Blank trailing lines are ignored. The empty line most exports end with does not become a row of empty cells.
Is my file uploaded anywhere?
No. This page has no server side: the file is read and written back by JavaScript running on your own machine. You can check it by opening the page, disconnecting from the network, and converting a file anyway.
Why renaming the file is not enough
Renaming data.txt to data.csv changes nothing about its contents: if the fields are tab-separated, Excel will still put every row into a single column, and if any field contains a comma, the columns will split in the wrong places.