JSON Converter
The way structured data travels between programs and, increasingly, the way it is stored.
13 tools
Convert to JSON
Image MetadataSee the camera, the exposure, the date and the GPS location stored inside a photo. It is read in this tab, never uploaded.
Image to TextRead the printed text out of a photo, screenshot or scan and download it as a .txt file, or as JSON with the position and confidence of every block.
CSV to JSONTurn a spreadsheet export into JSON, NDJSON or plain arrays, with the delimiter and the character encoding worked out for you.
Excel to JSONTurn a spreadsheet into JSON your code can actually consume: array of objects, array of arrays, or one array per column.
XML to JSONTurn XML into JSON with attributes, CDATA and namespaces handled the way you choose, and syntax errors that name the exact line.
Color PickerType or pick a color, read it back in twelve notations, build a harmony scheme and a 50-900 scale, and check its WCAG contrast.Convert from JSON
JSON to CSVFlatten an API response or an NDJSON export into a spreadsheet table, with every field from every record kept as its own column.JSON to ExcelFlatten a JSON or NDJSON export into a spreadsheet. Nested objects become dot-named columns and every record contributes its keys.JSON to XMLBuild a valid XML document from JSON: you name the root and item tags, and keys XML cannot accept are repaired rather than dropped.
Find and ReplaceSwap words, phrases or regex matches, up to twenty rules in one pass, with whole-word matching that works in every alphabet.
Compare TextTwo columns, deletions in red and additions in green, with the changed words picked out inside each line.Other JSON operations
What JSON is for
JSON describes objects, arrays, numbers, strings and nothing else, which is exactly enough for most data and simple enough that every language reads it without a library argument. It is what APIs return, what configuration files are written in, and what ends up in a browser's local storage. Its strength over CSV is nesting: a customer with three addresses and a list of orders is natural in JSON and awkward in a table.
Formatting, minifying and why both exist
The same JSON can be one long line or an indented tree; machines prefer the first, people need the second. Minifying strips every space that is not inside a string and can halve the size of a payload, which matters over a network. Formatting adds the indentation back and is the difference between finding a missing comma in ten seconds and not finding it at all. Neither changes the data, and both are safe to apply as often as you like, unlike re-encoding an image.
Converting to and from tables
Flattening JSON into CSV or Excel works when the data is really a list of similar records; it does not work when objects nest deeply, because a table has no way to express a list inside a cell. The conversions here take the pragmatic route: nested paths become dotted column names, and the tool tells you when a structure cannot be flattened rather than silently dropping it. Going the other way, from a table to JSON, is always safe: every row becomes an object.
Converting JSON to CSV or Excel without losing the structure
A JSON export from an API is usually a list of records, and that is exactly what a table wants. The parts that do not fit are nested objects and arrays. JSON to CSV flattens nested paths into dotted column names (customer.address.city) and lets you decide what happens to an array: its values joined in one cell, one column per item, or the raw JSON kept in a single cell. Anything nested deeper than the depth you set stays in its cell as JSON text instead of being dropped. JSON to Excel does the same into a real workbook, which is the better choice when a person will read the result. When the records sit inside a wrapper object, give the path to them, such as data.items.
Frequently asked questions
How do I open a JSON file?
Any text editor shows the raw text, and JSON Formatter makes it readable by indenting it and pointing at the first syntax error. To see it as a table, convert it to CSV or Excel; to inspect it, formatting is enough.
Why is my JSON invalid?
Almost always a trailing comma, a single-quoted string or a comment, none of which JSON allows. JSON Formatter reports the line and column of the first error; its lenient mode also accepts comments and trailing commas and writes the result back as strict JSON.
Can I convert JSON to Excel with nested data?
Yes, as long as the data is a list of similar records. Nested objects become dotted columns, arrays become joined cells, separate columns or JSON text, and anything nested deeper than the limit you set is kept in its cell as JSON rather than silently lost.