Skip to content

JSON ⇄ YAML ⇄ CSV Converter

Convert between JSON, YAML and CSV instantly, with validation and pretty-print.

From
To
Tip: press Tab to indent · Ctrl/⌘ + Enter to convert · or drop a .json / .yaml / .csv file here
Options
Try:

100% in your browser — nothing is uploaded. CSV uses the first row as headers and nested objects are flattened with dotted keys.

Why you’ll love JSON ⇄ YAML ⇄ CSV Converter

Instant & freeNo signup, no paywall, no limits — JSON ⇄ YAML ⇄ CSV Converter works the moment the page loads.
Completely privateEverything runs in your browser. Nothing you enter is ever uploaded or stored on a server.
Works on any deviceFully responsive and touch-friendly — use it on your phone, tablet or desktop.
Built by developersAccurate, fast and keyboard-friendly — the details developers care about.

How to use it

  1. 01

    Open it

    No download and no login — the tool is ready right at the top of this page.

  2. 02

    Use it

    Enter your details or start interacting. Everything updates live as you go.

  3. 03

    Get your result

    Copy, download or share your result in a single tap. That’s it.

About JSON ⇄ YAML ⇄ CSV Converter

This converter moves data between JSON, YAML and CSV in any direction — JSON to CSV, CSV to JSON, YAML to JSON and back — entirely in your browser. Nothing is uploaded to a server, which makes it safe for API responses, config files with secrets, or production database exports. You can paste text, or drop a .json, .yaml or .csv file up to 5 MB straight onto the input pane.

Each format gets proper treatment rather than a naive string swap. JSON is strictly parsed and pretty-printed with your choice of 2-space, 4-space or tab indentation, with optional recursive key sorting. YAML goes through a full parser, so quoting, multi-line values and nested lists behave correctly. CSV parsing is RFC-4180 aware — quoted fields, embedded delimiters and newlines inside quotes all work — and you can switch the delimiter between comma, semicolon, tab and pipe, with optional type inference that turns "42", "true" and "null" into real numbers, booleans and nulls.

The tricky part of any JSON-to-CSV conversion is nesting, and this tool handles it losslessly: nested objects are flattened into dotted column names (address.city), arrays of scalars are joined into one cell, and arrays of objects are stored as JSON strings. Going the other way, dotted CSV headers rebuild the original nested structure. The swap button feeds valid output back in as input, so you can round-trip data through formats without re-pasting.

Popular uses

  • ✦ Turn an API's JSON response into a CSV you can open in Excel or Google Sheets
  • ✦ Convert a docker-compose or CI pipeline YAML file to JSON to inspect or query it
  • ✦ Rebuild nested JSON from a spreadsheet export using dotted column headers
  • ✦ Switch a config file between JSON and YAML when moving between tools
  • ✦ Pretty-print and key-sort minified JSON before a code review or diff

Frequently asked questions

How does the converter turn nested JSON into flat CSV columns?
Nested objects are flattened using dotted keys, so { "address": { "city": "Toronto" } } becomes a column called address.city. Arrays of plain values are joined into a single cell, while arrays of objects are written as JSON strings so no data is thrown away. When you convert that CSV back to JSON or YAML, the dotted headers are unflattened and the original nesting is rebuilt.
Why are my CSV numbers coming out as strings (or my ZIP codes losing zeros)?
CSV has no data types — every cell is text until something decides otherwise. The "Infer numbers/booleans" option converts cells that look like numbers, true/false or null into real typed values in the JSON or YAML output. If that mangles identifiers like ZIP codes, phone numbers or order IDs with leading zeros, switch the option off and every cell stays a string exactly as written.
Can it read CSV files that use semicolons or tabs instead of commas?
Yes. The CSV delimiter option supports comma, semicolon, tab and pipe. This matters in practice because Excel in many European locales exports semicolon-separated files, log pipelines often use tabs, and pipe-delimited dumps are common from older databases. Pick the matching delimiter before converting and the parser handles the rest, including quoted fields that contain the delimiter itself.
Is my data uploaded anywhere when I convert it?
No. Parsing, conversion and file reading all happen in JavaScript on your own device — there is no server round-trip, no logging and no storage beyond your browser's local settings. That makes it reasonable to convert real API payloads, config files containing keys, or customer exports that you would not paste into a random online service.
Is JSON ⇄ YAML ⇄ CSV Converter free to use?
JSON ⇄ YAML ⇄ CSV Converter is 100% free — no signup, no watermarks and no usage limits. It’s one of 200+ free tools we build and give away.
Is my code or data sent anywhere?
Never. Everything is processed locally in your browser — safe for secrets, tokens and proprietary code.

We built this. We can build yours.

JSON ⇄ YAML ⇄ CSV Converter is one of our free tools. Need a website, app, AI agent or automation? Fixed price — and you own the code.