Question 1

How do I convert CSV to JSON online?

Accepted Answer

Paste your CSV into the input editor and the converter instantly emits JSON in the right pane. The first row is treated as the header (object keys); subsequent rows become objects in a JSON array. Type inference promotes numbers and booleans automatically. Click Copy for clipboard or Download to save as a `.json` file. Conversion runs entirely in your browser — no upload, no server.

Question 2

What is the difference between CSV and JSON?

Accepted Answer

CSV (Comma-Separated Values) is a flat tabular format — each line is a row, fields separated by a delimiter (usually comma). It has no native types (everything is text), no nesting, and no metadata beyond an optional header row. JSON (JavaScript Object Notation) is a hierarchical format with explicit types (string/number/boolean/null), nested objects and arrays, and self-describing keys. CSV is great for spreadsheet exchange and bulk data; JSON is better for APIs, configs, and structured records.

Question 3

Is JSON better than CSV?

Accepted Answer

It depends. For machine-to-machine APIs, configs, and nested data — yes, JSON is better (explicit types, hierarchical, self-describing). For bulk tabular data exchange, spreadsheet edits, and analyst workflows — CSV is often better (smaller, every tool reads it, easier to scan in a text editor). Many data pipelines use CSV for ingestion and JSON for serving — convert at the boundary.

Question 4

Can I convert Excel CSV files to JSON?

Accepted Answer

Yes — Excel exports CSV by default with comma delimiters and quoted text fields. The parser handles Excel-specific quirks: UTF-8 BOM at the start of the file (stripped automatically), CRLF line endings (Windows), and Excel's quoting style (double-quote escape via `""`). For Excel files saved with non-comma delimiters (semicolons in EU locales), switch the delimiter setting before parsing.

Question 5

Can I convert large CSV files to JSON?

Accepted Answer

Yes — the converter handles CSV files up to tens of megabytes in modern browsers. Very large files (100MB+) may slow your browser; for those, use a streaming command-line tool like `csvkit` (`csvjson input.csv > output.json`), `jq` with `@csv` mode, or Papa Parse with worker chunks. For routine exports under 10MB, this in-browser tool is the fastest option.

Question 6

How does CSV parsing handle quoted fields and escaped quotes?

Accepted Answer

Per RFC 4180: fields containing the delimiter, a double quote, or a newline must be enclosed in double quotes. Inside a quoted field, a literal double quote is escaped by doubling it (`""` represents a single `"`). For example, the cell value `He said "hi"` is encoded as `"He said ""hi"""` in CSV. Our parser handles this correctly, preserving the original cell content exactly.

Question 7

What is type inference in CSV to JSON conversion?

Accepted Answer

Type inference promotes obvious numeric and boolean strings to JSON-native types: `42` → integer 42, `3.14` → number 3.14, `true`/`false` → booleans, empty cells → null. Strings that look like numbers but should stay strings (ZIP codes, phone numbers, account IDs) need to be quoted in the source CSV — quoted values always stay strings. Toggle type inference off entirely if your downstream consumer expects all-strings.

Question 8

What is RFC 4180 and why does it matter?

Accepted Answer

RFC 4180 (2005) is the IETF informational standard for CSV — defines comma as delimiter, CRLF as line terminator, double-quote as text qualifier, and `""` as the escape for embedded quotes. It's not strictly enforced (CSV existed long before the RFC), but most modern tools target RFC 4180 for compatibility. Common deviations: Unix LF instead of CRLF, semicolon instead of comma in EU locales, trailing newline at end of file. Our parser tolerates all three.

Question 9

How do I handle CSV files with semicolons or tabs as delimiters?

Accepted Answer

Switch the Delimiter setting from comma to semicolon, tab, or pipe before pasting. EU Excel exports often use semicolons (since comma is the decimal separator in many locales). Tab-delimited files (TSV) are common in scientific data and database exports. Pipe-delimited files appear in legacy mainframe exports. The conversion logic is identical — only the field separator changes.

Question 10

Can I convert CSV without a header row to JSON?

Accepted Answer

Yes — toggle 'Header Row' off and the output becomes an array of arrays instead of an array of objects. Each row is a sub-array of cell values. Useful when your CSV is purely positional data (no column names) or when you want to preserve the original tabular structure. Switch back to header mode if you later add column names.

Question 11

How do I avoid CSV injection vulnerabilities?

Accepted Answer

CSV injection happens when a CSV file containing formula prefixes (`=`, `+`, `-`, `@`) is opened in Excel or Google Sheets — the spreadsheet executes the formula automatically, potentially exfiltrating data or running macros. To mitigate when generating CSV: prefix any cell that starts with one of those characters with a single quote (`'=cmd|...`). Our converter is read-only (CSV → JSON), so it doesn't introduce injection risk, but always sanitize before exporting CSV from untrusted user input. OWASP has a full guide.

Question 12

Can I convert nested data from CSV to JSON?

Accepted Answer

Direct CSV → nested JSON is not possible since CSV is inherently flat. Three workarounds: (1) Encode nested values as JSON strings inside a CSV cell (`"{""city"":""NYC""}"`) — our parser keeps these as strings; you re-parse downstream. (2) Use dot notation in headers (`address.city`, `address.zip`) and post-process the JSON output to nest. (3) For complex hierarchies, switch to JSON or YAML as your source format. Pure flat objects (one level deep) round-trip cleanly through CSV.

Question 13

Why is my CSV failing to parse?

Accepted Answer

Most common causes: (1) Unclosed quote — a field starts with `"` but never has a matching closing `"` before the next delimiter. (2) Escaped quotes used incorrectly — use `""` to embed a literal quote, not `\"`. (3) Wrong delimiter — your file uses semicolons but the parser is set to commas. (4) Inconsistent column count (ragged rows) — some rows have fewer or more fields than the header. (5) BOM/encoding issues — ensure UTF-8 encoding. The error message shows the line and column where parsing failed.

Question 14

Can I use the JSON output directly in JavaScript?

Accepted Answer

Yes — the JSON output is standard ECMA-404 JSON, ready to feed `JSON.parse()`, `fetch()` POST bodies, React state initializers, Node.js APIs, or any JavaScript dataset library. For typed projects (TypeScript), the inferred types match: numeric cells become `number`, boolean cells become `boolean`, empty becomes `null`. If your project requires uniform types regardless of source, run a normalization pass (e.g., `Number(row.age) || 0`) after parsing.

Question 15

Is this CSV to JSON converter safe for sensitive data?

Accepted Answer

Yes — all conversion runs in your browser via JavaScript. No CSV is uploaded to a server, logged, or transmitted anywhere. Verify by opening DevTools → Network: no requests fire when you paste or convert. Safe for customer exports, payroll data, internal database dumps, and any other sensitive tabular data. The page works offline once loaded.

Question 16

How do I convert JSON back to CSV?

Accepted Answer

Use the JSON to CSV Converter (sister tool, coming soon) or export programmatically with `csvkit` (`in2csv input.json`), Papa Parse (`Papa.unparse(rows)`), or Python's `csv.DictWriter`. Round-tripping CSV → JSON → CSV preserves cell values exactly (modulo type promotion if you re-parse the JSON before exporting). Nested JSON requires flattening before CSV export — pick a strategy (dot notation for keys, JSON strings for cells, or first-level only).

Question 17

How does this compare to Papa Parse or csvkit?

Accepted Answer

Functionally similar for the common case. Papa Parse is the canonical JS CSV library — better for programmatic use, streaming, and worker-thread parsing. csvkit is the canonical Python CLI — better for shell pipelines and large files. Our online converter is a browser tool — no install, instant feedback, easy to share a URL with colleagues. All three target RFC 4180 strict mode and produce equivalent JSON for standard inputs.

Question 18

What encoding should my CSV use for best results?

Accepted Answer

UTF-8 (with or without BOM) — the universal default for modern CSV files. Excel for Windows often saves as UTF-8 BOM or Windows-1252 (Latin-1); Excel for Mac usually saves UTF-8. If your CSV contains non-ASCII characters (accents, emoji, CJK) and they appear garbled, the file is probably not UTF-8 — re-save as UTF-8 in your spreadsheet app. Our parser strips BOM automatically and treats input as UTF-8 by default.

CSV to JSON Converter

lightbulb Tips