📊 JSON ↔ CSV

Round-trip JSON and CSV with sensible defaults — RFC 4180-compliant, type-inferring, configurable.

About JSON ↔ CSV

Convert between JSON and CSV without leaving the browser. The CSV side is RFC 4180-compliant — quoted fields, embedded delimiters, doubled quotes, and BOM-prefixed input all round-trip cleanly. Type inference, delimiter auto-detection, and configurable nested-object handling cover the cases that usually trip plain copy-paste tools.

How to use

  1. Pick a direction: JSON → CSV or CSV → JSON. Switching clears both panels so the next input starts fresh in the right format.
  2. Paste your data into the left panel; the converted result appears live on the right.
  3. For CSV → JSON output, switch between Tree and Raw view to either explore the structure interactively or copy the plain JSON text.
  4. Tweak the options bar — delimiter, header row, nested handling, type inference — until the output looks right.

Common use cases

  • Turning an API response into a spreadsheet row dump.
  • Pulling a CSV export from a database dashboard into JSON for a script.
  • Auditing or sorting data in a spreadsheet, then converting back to JSON.
  • Quickly reshaping nested JSON for a flat reporting tool.

Tips

  • Auto-detect picks among , ; \t | by looking at the first ~10 rows.
  • Nested objects flatten to dot-paths by default — switch to JSON-literal mode if you'd rather keep them whole in one cell.
  • Type inference treats empty cells as null; turn it off to keep everything as strings.

FAQ

How are nested JSON objects handled?
Flattened to dot-path columns by default (so address.city becomes its own column). Switch to underscore or JSON-literal modes if you'd rather keep them whole.
How are arrays inside objects handled?
Joined with commas by default — for example ["red","blue"] becomes "red,blue" — or kept as JSON literals via the option toggle.
Why are numbers in my CSV becoming strings?
Type inference is on by default. Make sure the value isn't surrounded by extra whitespace or quoted twice. Switch to off if you want exact CSV → JSON.string round-trip.
Does it auto-detect the delimiter?
Yes for CSV → JSON. The detector samples the first ~10 lines and picks whichever of comma, semicolon, tab, or pipe produces the most consistent column count.
Will the CSV preserve quotes and commas in cell values?
Yes. RFC 4180 quoting is applied automatically: cells with the delimiter, a double-quote, or a newline get quoted, and any internal double-quote is doubled.

More tools

JSON

🗂️ JSON Formatter 🔷 JSON to TypeScript 🔍 JSON Diff 🔤 JSON Sort 📝 JSON ↔ YAML 🛡️ JSON to Validator Schema

Code

🧪 Regex Tester ⚛️ SVG to JSX 📷 SVG to Raster ⏱️ Cron Decoder 📸 Code Snippet to Image 📄 Text Diff 📝 Markdown Preview 🏷️ SemVer Checker 🔑 JWT Decoder

Ornaments

🎨 Gradients 🫧 Blob Generator 〰️ Wave Generator

Image

🗜️ Image Compressor 📐 Image Resizer ✂️ Image Cropper 🖼️ Image Format Converter 🔏 Image Watermark

Web / SEO

🔍 Meta Tag Preview 🕵️ User Agent Parser 🖼️ OG Image Builder

Generators

📱 QR Code Generator 📜 Lorem Ipsum Generator 👤 Avatar Generator ⭐ Favicon Generator 🪪 UUID Generator

PDF

📄 PDF Merger 📑 Image to PDF 🤏 PDF Compressor ✂️ PDF Splitter 🗂️ PDF Page Manager