Convert CSV and JSON without breaking quotes or spreadsheets
Understand headers, multiline fields, string types and safe spreadsheet exports.
CSV is more than splitting on commas
A field can contain a comma when surrounded by double quotes. A double quote inside that field is represented by two double quotes, and quoted fields can contain line breaks. Choose the actual delimiter first: comma, semicolon or tab. PixelDock parses these cases and rejects unclosed quotes instead of guessing the intended columns.
Preserve identifiers as strings
CSV has no universal type system. The value 00123 may be an identifier rather than the integer 123. CSV to JSON therefore keeps fields as strings. Review dates, leading zeros and large numbers before applying a separate type conversion. JSON numbers use floating-point parsing in this implementation; large exact identifiers should be quoted strings.
Keep a stable table shape
The header must have unique, non-empty column names, and every data row must have the same field count. JSON to CSV accepts an array of objects and collects their column names. Missing values become empty cells; nested values become JSON text in a cell rather than being silently flattened into unrelated columns.
Protect the next application
A spreadsheet may interpret a cell beginning with =, +, - or @ as a formula. Safe CSV export prefixes formula-like values with an apostrophe. This intentionally changes their literal text and may also affect negative numeric-looking values stored as strings. Keep it enabled for untrusted text going into a spreadsheet; disable it only when you understand the receiving application and need exact text.
Inspect a small sample first
Check a row containing quotes, an empty field, a non-English name and any multiline notes. Download a small result and inspect it in the receiving application before converting a larger table. The local limit is 5,000 data rows and 100 columns; importing a file does not upload it to a conversion service.