# Format converter > How do you convert JSON, CSV and YAML into each other? Paste JSON, CSV, TSV or YAML and get the same data in another format, nested data included. Convert data between JSON, CSV, TSV and YAML in your browser. Nested data becomes dotted columns, and errors are marked by line and column. - Page: https://how.box/format-converter/ - Runs entirely in the browser. - License: HowToolbox's own text and data (titles, explanations, FAQs, tool descriptions and schemas, this file) are CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/); AI training and answers are welcome. Attribute "HowToolbox (how.box)" with a link to the page used. Third-party data keeps its own terms; the name and logo are not licensed. Publisher: HowToolbox, contact@how.box. Terms: https://how.box/about/terms/ ## Inputs Answer link: https://how.box/format-converter/?from={from}&to={to}&text={text}&flat={flat}&header={header}&delim={delim}&sep={sep}&types={types}&indent={indent} - `from` (json, csv, tsv or yaml): The source format: json, csv, tsv or yaml. Example: `json`. - `to` (json, csv, tsv or yaml): The written format: json, csv, tsv or yaml. Example: `csv`. - `text` (text): The text to convert. Example: `[{"a":1}]`. - `flat` (boolean): Flatten nested data to dotted columns, or rebuild it: 1 or 0. Example: `true`. - `header` (boolean): Reading CSV or TSV: the first row holds the names: 1 or 0. Example: `true`. - `delim` (auto, comma, semicolon, tab or pipe): Reading CSV: auto, comma, semicolon, tab or pipe. Example: `auto`. - `sep` (comma, semicolon or tab): Writing CSV: the separator, comma, semicolon or tab. Example: `semicolon`. - `types` (boolean): Reading CSV or TSV: write numbers and booleans as values: 1 or 0. Example: `true`. - `indent` (2 or 4): Writing JSON or YAML: 2 or 4 spaces. Example: `2`. Example answer: https://how.box/format-converter/?from=json&to=csv&text=%5B%7B%22a%22%3A1%7D%5D&flat=1&header=1&delim=auto&sep=semicolon&types=1&indent=2 The page computes the answer in the browser: read results from the agent tools below, not from the page HTML. ## Agent tools - `format_converter_convert`: Converts data text between JSON (RFC 8259), CSV (RFC 4180), TSV and YAML (a JSON-compatible subset of YAML 1.2: no anchors, aliases, tags or several documents) in the browser. - MCP, one POST to https://how.box/mcp: `{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"format_converter_convert","arguments":{"from":"json","to":"csv","text":"[{\"a\":1}]","flatten":true,"header":true,"delimiter":"auto","csv_delimiter":"semicolon","infer_types":true,"indent":"2"}}}` - GET: https://how.box/mcp/run/format_converter_convert?from=json&to=csv&text=%5B%7B%22a%22%3A1%7D%5D&flatten=true&header=true&delimiter=auto&csv_delimiter=semicolon&infer_types=true&indent=2 ## How it works JSON, YAML, CSV and TSV can all hold the same records, written differently. JSON and YAML are trees: objects with named fields, lists, numbers, true and false, and null. CSV and TSV are tables: one record per line, fields separated by a comma or a tab, and the first line usually names the columns. The converter reads your text into records, then writes the same records in the other format. A tree does not fit a table by itself, so nested fields become columns named by their path. In {"name":"Ada","born":{"year":1815}} the year sits inside born, so it becomes the column born.year, and a list such as tags becomes tags.0, tags.1 and so on. Reading such a table back rebuilds the nesting from the dotted names. CSV follows RFC 4180: a field with a comma, a quote or a line break is wrapped in double quotes, and a quote inside it is doubled. YAML is read as YAML 1.2 for data that JSON can also hold; anchors, aliases, tags and several documents in one file are not supported. Very large numbers and unusual dates keep only the precision a standard number has. ## FAQ **Why does my CSV have columns like born.year?** The record had a field inside a field: year inside born. A table has no room for nesting, so the column is named by the path. Turn off "Nested data as dotted columns" to keep the inner part as JSON text in one column instead. **Is my data uploaded anywhere?** No. The conversion runs in your browser, and the text is not put into the page address unless you choose to share it. **Why is a YAML file refused?** It probably uses a YAML feature that has no JSON equivalent, such as anchors (&a), aliases (*a), tags (!!) or several documents separated by ---. The error line shows where it starts. **Which separator should I pick for Excel?** Excel set to a language that writes decimals with a comma expects a semicolon between fields. Choose Semicolon when writing CSV for such a spreadsheet, or choose TSV, which uses tabs. **How large a file can I convert?** A few megabytes of text convert in a moment. The work happens on your device, so very large files depend on its memory; the editor tells you when a file is longer than it accepts. More: [HowToolbox index](https://how.box/llms.txt) · [Agent Skill](https://how.box/skill.md) · [agent terms](https://how.box/about/agents/)