Is my file uploaded?
No. Files are read and converted in your browser; large files are converted in a background Web Worker on your device. Nothing is sent to a server. If you press Share, the link itself carries a readable copy of your input, so don't share links that contain secrets.
Why did my ZIP codes or phone numbers lose their leading zeros?
Because a converter turned "02134" into the number 2134. This tool keeps every value as a string by default. With "Detect numbers & booleans" on, a column only becomes numbers when every value converts without changing — so a ZIP column with 02134 stays text, and so do +44 phone numbers and IDs longer than 15 digits.
My CSV uses semicolons. Will it work?
Yes. Excel in many European locales saves "CSV" with semicolons because the comma is the decimal separator. The delimiter is detected automatically (comma, semicolon, tab or pipe), and you can override it.
What is CSV injection?
A cell that starts with =, +, - or @ can be run as a formula when the CSV is opened in Excel or Google Sheets — for example =HYPERLINK(...) pointing to a malicious site. When exporting JSON to CSV, the tool counts such cells and can prefix them with an apostrophe, the OWASP-recommended mitigation. Plain negative numbers like -5 are not flagged.
Why does Excel show 1.23E+15 instead of my ID?
Excel converts long numbers to floating point when it opens a CSV and only keeps 15 significant digits, so long IDs and card-like numbers are displayed in scientific notation and can lose digits. The CSV itself is fine. Import the file with Data → From Text/CSV and set that column to Text, or keep such values quoted and prefixed. The "For Excel" option also adds a UTF-8 BOM so accented characters display correctly.
What happens with rows that have a different number of fields?
Nothing is dropped. Missing fields are empty and extra fields are kept under _extra1, _extra2… The tool lists each ragged row with its line number, which usually points to an unquoted comma or a stray quote.