Does the validator change my file?
Only when you press a fix. The parser repairs problems while reading so no value is lost, and the validator lists every repair with its file line number.
Check a CSV for the problems that break imports: rows with the wrong number of fields, quotes that never close, empty or repeated header names, encoding trouble, and values that do not match the column. Every finding has a line or row number, and several common problems can be fixed with one click.
Loading the CSV tools.
You do not have to take our word for it. Browser developer tools list every request a page makes, so you can watch 2csv work and confirm that your data is never sent anywhere. The check takes about a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Your file is read into this tab's memory with the browser's own file reader, parsed and changed by code that is already on the page, and handed back to you as a download. It is never uploaded, never stored in the browser, and gone when you close the tab. The only other request the site can make is the feedback form, and only when you submit it.
The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so even a bug could not send your data elsewhere.
A CSV validator is a tool that reads a file and lists everything that could make another program reject it or misread it. The 2csv parser repairs problems instead of failing, and the validator shows each repair it made, with the line number in the original file, so nothing is changed silently.
A column rule says what every value in a column should look like. The validator then lists each value that breaks the rule, by row. Rules are Anything, Not empty, Whole number, Number, Date, True/false, Email address, and Unique values. Detect column types fills the rules in from the data, so you only adjust the ones it gets wrong.
Header problems and empty rows have one-click fixes. Empty and repeated header names get unique names such as column_4 or name_2, header names lose spaces at the ends, and rows with no values are removed. For other findings the validator links to the right tool, such as Trim whitespace or the column type converter.
Findings are grouped by severity. Problems are things that will likely break an import, such as a quote that never closes. Warnings are things worth checking, such as a padded row. Notes are information, such as a removed byte-order mark. Each finding gives the line or row number so you can find it in the grid.
You can download the findings as an issue report CSV, with one row per finding. That is useful when the file came from someone else and you need to send them a precise list of what to fix in their export, without sending the data itself.
All eighteen tools are on the 2csv home page, and once a file is open you can switch between them without reloading it. Part of the 2suite.io privacy-first ecosystem.
Only when you press a fix. The parser repairs problems while reading so no value is lost, and the validator lists every repair with its file line number.
The table widens with extra columns so no value is lost, and the validator reports the row and its line number.
Yes. Set the Email address rule on that column, and every value that does not look like an email address is listed by row.
Yes. Download the findings as an issue report CSV, with one row per finding, its severity, and its line or row number.