DevKitBase
ToolsAboutPrivacy

CSV to JSON when the spreadsheet has to become an API body

First row = keys; each following row = object. Handles quoted commas; call out delimiter options (comma/semicolon/tab) if exposed.

chars: 16
Input
Output

When to use

Prototyping fixtures from a sheet export, or migrating a small CSV into JSON config.

Examples

Input
id,name
1,Ada
2,Lin
Output
[
  {"id":"1","name":"Ada"},
  {"id":"2","name":"Lin"}
]

How it works

Quote-aware row parse → map headers → array of objects → optional pretty JSON. Types stay strings unless a coerce toggle exists.

Common pitfalls

  • Numbers stay strings unless you coerce.
  • Mismatched column counts produce sparse/odd objects.
  • Excel locale separators (; vs ,) break naive parsers.

How this differs

Inverse of JSON→CSV. For YAML configs, convert JSON onward with JSON→YAML.

FAQ

Are numbers auto-typed?
Default strings unless you enable coercion; document the choice.
Empty fields?
Empty string or null — say which.
Huge files?
Browser memory limits; keep it interactive-sized.
Reverse?
JSON to CSV.

Related tools

Runs in your browser. Nothing is uploaded. Not a security product —hashes and JWT decode are for debugging, not password storage or auth advice.