JSON to Text Converter
Turn JSON into plain readable text, one path: value line per value. Runs in your browser.
Turn JSON into plain readable text, one path: value line per value. Runs in your browser.
Developers can read JSON, but a support agent, a client or a ticket system usually cannot. This JSON to text converter rewrites a JSON document as plain lines of path: value, with no braces, quotes or commas, so it can go straight into an email, a Jira ticket, a chat message, a spreadsheet note or a log line. Every value keeps its full path, so nothing is ambiguous about where it came from.
{"userId":7,"name":"Ada","nick":null,"tags":["a"],
"address":{"city":"London"},
"orders":[{"sku":"A1","qty":2},{"sku":"B","price":3.5}]}
becomes
userId: 7
name: Ada
nick: (none)
tags[0]: a
address.city: London
orders[0].sku: A1
orders[0].qty: 2
orders[1].sku: B
orders[1].price: 3.5
A failed request logged as JSON:
{"ticket":4812,"customer":{"name":"Priya Shah","plan":"Pro"},
"error":{"code":"E_TIMEOUT","retryable":true},
"attempts":[{"at":"10:02","ms":30000},{"at":"10:05","ms":30000}],
"notes":[],"refund":null}
converts to text a non-developer can read and quote back:
ticket: 4812
customer.name: Priya Shah
customer.plan: Pro
error.code: E_TIMEOUT
error.retryable: true
attempts[0].at: 10:02
attempts[0].ms: 30000
attempts[1].at: 10:05
attempts[1].ms: 30000
notes: (empty list)
refund: (none)
When the top level is an array, paths start with the index:
[["x","y"],[1,2]]
[0][0]: x
[0][1]: y
[1][0]: 1
[1][1]: 2
[index], the notation JavaScript and JSONPath use, so a line can be traced back to the original document.null is written as (none); empty objects and arrays are shown as (empty) and (empty list) instead of disappearing. An empty document at the root prints (root): (empty).true and false, and numbers print the way JavaScript writes them.Because every line carries its full path, the output works well with ordinary text tools, not just human eyes:
grep '^orders\[.*\]\.sku' on the text lists every SKU, and searching for (none) finds every null field in one pass.error.code: E_TIMEOUT, and the reader still knows where each value lives.": " gives a two-column path and value list without any formulas.a.b prints as a.b: 1, exactly like a nested {"a":{"b":1}}. The text is for reading, so this is rarely a problem, but do not parse the output back into JSON.\n is printed with a real line break, so one value can span several output lines. Search for the next path: prefix to see where it ends.12345678901234567890 prints as 12345678901234567000. Keep long IDs as strings in the source JSON.Plain text is one-way: it is for people, not for machines. If you need a key/value structure you can convert back to JSON, use JSON flatten, which produces {"address.city": "London"}. If you want something still readable but also parseable, JSON to YAML keeps the structure without braces. For an array of similar records, a grid reads better: use JSON to table or JSON to CSV. To explore the structure interactively, open it in the JSON viewer, and for XML input there is a matching XML to text converter.
No. The conversion runs in your browser and nothing is sent to a server.
The parser error is shown. Fix it with the JSON formatter, whose repair option handles trailing commas, single quotes and comments.
Not reliably. Quotes and types are dropped, so "7" and 7 look the same. Use JSON flatten if you need a reversible path/value form.
null becomes (none), an empty object becomes (empty) and an empty array becomes (empty list), so missing data is still visible in the text.
Yes, keys are printed in the order the browser parses them, which is the document order except that integer-like keys such as "1" come first within an object.