Data & conversion tools
Move data between JSON, CSV, YAML, XML and back.
Data arrives in whichever format the system that produced it preferred, and it is almost never the format you need next. A colleague sends a spreadsheet export when your importer wants JSON; an API returns nested JSON when you need flat rows for a pivot table; a config comes as YAML when the tool reads TOML. These converters, validators, viewers and diff tools translate between those shapes and tell you clearly when the input is malformed.
Tools in this category
80About these tools
Flat and nested do not map cleanly
CSV is a rectangle: rows and columns, one value per cell. JSON is a tree, with objects inside arrays inside objects. Converting a tree to a rectangle always requires a decision about what to do with the nesting — flatten it into dotted column names, or serialise the branch into a single cell. Being aware that the choice exists is what stops a conversion from quietly losing half your data.
Validate before you blame the parser
Most "the import is broken" reports are malformed input: a trailing comma, an unquoted field containing a delimiter, a tab where a space belonged, or a byte-order mark at the start of the file that makes the first column name look wrong. A validator points at the offending line and column, which turns half an hour of squinting into a five-second fix.
Big files, one browser tab
Everything here runs client-side, so the practical limit is your own memory rather than an upload cap or a paid tier. A multi-megabyte export processes locally in seconds and never leaves the machine — which also means you can run a real customer export through a converter without it becoming a data-transfer question for someone else to answer.