JSON WalletPrivacy-first JSON & API workspace

CSV to JSON

Paste CSV — a spreadsheet export, a database dump, an API report — and get a clean array of JSON objects. The first row is treated as the header, and every following row becomes one object. Runs entirely in your browser.

CSV
JSON

Turn CSV into JSON in the browser

CSV is how most spreadsheets, analytics exports and legacy databases hand you data, but almost every API, config file and JavaScript program wants JSON. This converter bridges the two: paste a comma-separated file and get back a JSON array you can drop straight into code, a request body or a test fixture. There is no upload step and no size cap beyond your browser's memory, so you can convert a quick three-row snippet or a multi-thousand-row export the same way.

How the conversion works

The parser reads the first line as a header and maps each remaining line onto those keys. It respects RFC-4180-style quoting, so a field like "Smith, John" stays a single value even though it contains a comma, and doubled quotes inside a quoted field are unescaped correctly. Type inference is deliberately conservative: only cells that unambiguously look like a number or a boolean are converted, which avoids the classic bug where a ZIP code or phone number loses its leading zero. Empty cells map to null rather than an empty string so downstream if (value) checks behave.

When you would use it

Loading a spreadsheet into a JavaScript app, seeding a database from an exported table, building a fixture for a unit test, or feeding a CSV report into a tool that only speaks JSON. Because the output is a plain array of flat objects, it pairs well with the JSON editor's tree and table views, the JSONPath tester for pulling out a column, and the CSV direction of this same tool when you need to round-trip back to a spreadsheet.

Privacy

Everything runs client-side. The converter is loaded once and then works offline; your CSV is never sent to a server, logged, or stored. That makes it safe for exports that contain customer records, internal metrics or anything else you would not paste into an upload-based site.

Frequently asked questions

How is the header row handled?

The first line is read as the column names. Each subsequent row becomes an object whose keys are those column names, so id,name followed by 1,John produces { "id": 1, "name": "John" }.

Are numbers and booleans detected?

Yes. Cells that look like numbers become numbers, true/false become booleans, and empty cells become null. Everything else stays a string. If you need every value as a string, wrap the cell in quotes.

Does it handle quoted fields with commas?

Yes. Fields wrapped in double quotes may contain commas, newlines and escaped quotes (""), following the common CSV convention used by Excel and Google Sheets.

Is my file uploaded anywhere?

No. Parsing happens locally in your browser using JavaScript — the CSV never leaves your device.

Press K for commands