JSON to Text Converter

Turn JSON into plain readable text, one path: value line per value. Runs in your browser.

Make JSON readable for anyone

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.

How to use it

  1. Paste JSON into Input: an object, an array, or a single value.
  2. Click Run. Each leaf value appears on its own line in Output, in the same order as the source.
  3. Click Copy and paste the text where you need it. If the input is not valid JSON, the parser message is shown instead.

Example 1: a customer record

{"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

Example 2: an API error for a support ticket

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)

Example 3: a table stored as nested arrays

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

Conversion rules

Why one line per value is useful

Because every line carries its full path, the output works well with ordinary text tools, not just human eyes:

Edge cases to know about

When to use a different format

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.

Frequently asked questions

Is my JSON uploaded?

No. The conversion runs in your browser and nothing is sent to a server.

What if my JSON is invalid?

The parser error is shown. Fix it with the JSON formatter, whose repair option handles trailing commas, single quotes and comments.

Can I convert the text back to JSON?

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.

How are null and empty values shown?

null becomes (none), an empty object becomes (empty) and an empty array becomes (empty list), so missing data is still visible in the text.

Does it keep the original key order?

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.