Question 1

How do I convert CSV to JSON without writing code?

Accepted Answer

Paste your CSV (from Excel, Google Sheets or any export) into jslet's CSV to JSON tool. The first row becomes the JSON keys and each following row becomes an object. You can choose between 4 output shapes: array of objects ([{"name":"Alice"}]), array of arrays ([["name"],["Alice"]]), keyed by first column ({"Alice": {...}}) or column arrays ({"name":["Alice"]}). The parser follows RFC 4180: quoted fields with embedded commas or newlines are handled correctly, and a UTF-8 byte-order-mark (BOM) added by Excel is stripped automatically so your first column name never gets corrupted. Everything runs in your browser — no uploads, no server.

Question 2

Why does my CSV-to-JSON converter turn "00501" into 501?

Accepted Answer

That is type inference: a converter that 'helpfully' coerces every digit-only string into a JSON number will drop leading zeros, because JSON's number grammar has no concept of leading zeros. Zip codes, phone numbers and account IDs are the classic victims. This tool keeps type inference OFF by default and only applies it when you enable the 'Infer types' option — and even then you can disable it for a specific conversion. When type inference is on, "42" becomes the number 42, "true" becomes boolean true, and empty cells become null. When it is off, everything stays a string, which is the safe default for data you do not fully trust.

Question 3

Why does my first JSON key look corrupted after conversion?

Accepted Answer

That is almost always a UTF-8 byte-order-mark (BOM). When Excel exports 'CSV UTF-8', it writes three invisible bytes (EF BB BF) at the very start of the file. If the converter does not strip them, those bytes get glued onto your first header name, turning "id" into a key that looks right but fails strict matching in code. This tool strips a leading BOM automatically before parsing headers. If you paste data copied from a web page instead of a file export, BOMs can also sneak in — the stripping handles both cases.

Question 4

What happens when a CSV row has more or fewer columns than the header?

Accepted Answer

A short row (fewer fields than headers) produces objects with missing keys for the unfilled columns — the values do not shift into the wrong fields. A row with MORE fields than headers is almost always a malformed CSV, usually an unescaped delimiter or unbalanced quote inside a quoted field. This tool flags that mismatch with a warning instead of silently shifting every subsequent value one column over, which is the failure mode of naive converters that zip headers to values by position without checking lengths. Fix the source data rather than trusting a silently misaligned output.

Question 5

Is my CSV data uploaded to a server?

Accepted Answer

No. The conversion runs entirely in your browser via JavaScript — your CSV never leaves your device. This matters when your data contains customer PII, employee records or proprietary datasets. You can verify it yourself: open the browser Network tab (F12) before converting and you will see zero outbound requests. No account, no signup, no file-size limit beyond your browser's memory.

CSV →JSON Converter

🟢📖 The Four CSV Traps This Converter Handles