Convert CSV to JSON

By default, your CSV becomes an array of objects — the first row supplies the field names, each subsequent row becomes one object. A CSV with columns name/email/age and three data rows produces `[{name, email, age}, {...}, {...}]`. This is the typical 'load CSV into a JavaScript / Python / database script' shape.

Mostly — the converter tries to detect numeric columns and store them as JSON numbers (no quotes) rather than as strings. CSV lacks explicit type information so this is heuristic: values that look like numbers ('123', '4.5') get number type; values with leading zeros, plus signs, or currency symbols stay as strings. If you need guaranteed type handling, post-process the JSON in your downstream code.

Empty CSV cells typically become empty strings ('') or null in the JSON depending on convention. The converter follows the common 'empty value = null' convention, which makes the JSON cleanly typed for boolean-check code (`if (!row.field)`). If your CSV uses explicit 'N/A' or 'null' markers, those come through as strings unless you post-process.

Handled correctly when the CSV uses proper quoting (`"value, with comma"`). The converter parses RFC 4180-compliant CSVs reliably, including quoted fields, escaped quotes (`""`), and multi-line cells. Malformed CSVs from buggy exporters can produce surprising results; if conversion looks wrong, inspect the source CSV in a text editor.

Three common reasons: (a) loading the data into JavaScript / Python / API code that prefers JSON; (b) feeding into a NoSQL database or document store; (c) generating fixtures or seed data for testing. CSV is the universal data export; JSON is the format programs prefer to read. Converting bridges human-friendly tables to machine-friendly objects.