What's the difference between NDJSON and regular JSON?+
Regular JSON wraps your rows in a single array: [ {...}, {...} ]. NDJSON puts one complete JSON object on each line with no enclosing array and no commas between objects. That makes it streamable — tools can read it line by line instead of parsing one huge document. NDJSON, JSON Lines (.jsonl) and JSONL all refer to the same format.
Are the values typed, or strings?+
Typed. We infer each column's type from its data: numbers come out unquoted, booleans as true/false, empty cells as null. Everything else stays a JSON string. Most free converters quote every value, which is valid JSON but useless when your code expects a real number.
Is there a trailing newline?+
No. Lines are joined with a single newline between objects and there's no extra newline at the end, so the file is exactly N lines for N rows. If a specific tool requires a trailing newline, add one when you save.
Are dates converted automatically?+
No, by default — we keep detected dates as their original strings so ambiguous formats like 03/04/2025 aren't silently mis-parsed. Toggle 'Normalize dates to ISO 8601' to emit them as YYYY-MM-DD instead.
How are quotes, commas and newlines inside cells handled?+
Each line is produced with JSON serialization, so quotes, backslashes, embedded newlines and control characters are all escaped correctly. A newline inside a cell becomes \n within that line's JSON string — it never splits a record across two lines.