Data format converters

Convert between JSON, YAML, CSV, XML, TOML, Markdown, .env and more — free, instant and private: your data never leaves your browser.

• JSON to YAML — Ready for Your Config File Convert JSON to YAML. Indentation you choose, ambiguous values quoted, and a result that pastes straight into a Compose or CI file.
• YAML to JSON — Long IDs Kept Exact Convert YAML to JSON. Large integers keep every digit and several documents become an array, ready to feed to an API or a script.
• JSON to CSV — Open It in a Spreadsheet Turn a JSON array of objects into a spreadsheet. The keys become the header row, ready to open in Excel, Numbers or Google Sheets.
• CSV to JSON — Numbers Arrive as Numbers Turn a CSV table into an array of JSON objects keyed by the header row. Numbers and booleans come out typed, ready to sum or compare in code.
• JSON to XML — Valid XML, Ready to Paste Convert JSON to XML. One root element, tag names made legal and indentation you choose — ready for a SOAP body or a config file.
• XML to JSON — Attributes Included Convert XML to JSON. Attributes, repeated elements and text all land somewhere you can reach with a dot or a bracket in your code.
• JSON to TOML — Config You Can Read Convert JSON to TOML. Tables, dotted keys and arrays of tables come out as a configuration a person can read and edit by hand.
• TOML to JSON — Long IDs Survive Exactly Convert TOML to JSON. Large integers keep every digit and dates keep their offset, so the config reaches your code as it was written.
• CSV to YAML — A List You Can Read Turn a CSV table into a YAML list of mappings. Each row becomes a block you can read at a glance and drop into a config or a fixture file.
• YAML to CSV — A Spreadsheet From a List Turn a YAML list into a spreadsheet. Each mapping becomes a row and its keys become the header, ready for Excel or Google Sheets.
• YAML to TOML — Config Files, Converted Convert a YAML config to TOML. Nested mappings become tables, ready for Cargo, pyproject or anything else that reads TOML.
• TOML to YAML — Config Both Readers Agree On Convert a TOML config to YAML. Ambiguous scalars come out quoted, so an old PyYAML reader and a modern one give your app the same values.
• XML to YAML — Readable in One Step Convert XML to YAML. The tree becomes indentation instead of tags, which is usually the reason you wanted it out of XML to begin with.
• YAML to XML — Element Names That Work Convert YAML to XML. Keys that cannot be element names are repaired and collisions get a suffix, so the document parses on the first try.
• CSV to XML — A Document That Parses Convert a CSV table to XML, one element per column. Header names are repaired into legal tag names, so the document opens in any XML tool.
• XML to CSV — One Row per Element Turn repeated XML elements into rows. The child names become the columns, ready to open in a spreadsheet or feed to a script.
• Markdown to HTML — Paste It Into a Template Turn Markdown into HTML: GFM tables, task lists, strikethrough and footnotes, ready to drop into a page, an email template or a CMS field.
• HTML to Markdown — Turn a Page Into Notes Paste HTML and get Markdown: headings, lists, links, fenced code and tables that stay tables, ready for a README, a wiki or your notes.
• CSV to Markdown — A Table for Your README Turn a CSV table into a Markdown pipe table. Paste it into a README, an issue or a pull request and it renders as a table on GitHub.
• Markdown Table to CSV — Into a Spreadsheet Pull the first GFM table out of a Markdown document as CSV. What was a table in a README opens in Excel or Google Sheets, sortable.
• CSV to TSV — Commas Stop Splitting Columns Convert a CSV table to tab-separated values. Commas inside your data stop being separators, so the columns land where you expect them.
• TSV to CSV — Opens Where TSV Does Not Convert tab-separated values to CSV, quoting only the fields RFC 4180 requires. The result opens in the many tools that expect a comma.
• JSON to TSV — Tabs Instead of Commas Convert JSON to tab-separated values. Tabs stay out of the way of the commas in your data, and the result pastes straight into a spreadsheet.
• TSV to JSON — Ready for Your Script Turn a tab-separated table into an array of JSON objects. Field boundaries are never in doubt, so the result is ready to feed to a script or an API.
• JSON to NDJSON — One Record per Line Turn a JSON array into newline-delimited JSON. One document per line, minified, ready for bq load, a log pipeline or a streaming API.
• NDJSON to JSON — One Array for jq Turn newline-delimited JSON into a single array. Blank lines are skipped and a bad line is named by its number, so you know where to look.
• Properties to YAML — Spring Boot Ready Turn a Java .properties file into YAML. Dotted keys nest and indexed keys become lists, giving you an application.yml you can commit as is.
• YAML to .properties — Java Reads It Back Flatten YAML into a Java .properties file. The escaping is done for you, so what Properties.load reads back is exactly what you put in.
• .env to JSON — Settings Your Code Can Read Turn a .env file into JSON. Quotes, comments and export are handled, so the settings arrive as an object your app or CI can read directly.
• JSON to .env — Ready for Docker and CI Convert a flat JSON object into a .env file. Names are checked and values quoted where a shell needs it, ready for Docker or your pipeline.