Convert JSON to Text

It uses Unicode box-drawing characters from the U+25xx range: ├── (intermediate child), └── (last child), │ (continuation marker). The same characters terminals use for tree output. Result: hierarchical structure that’s visually obvious without needing JSON syntax knowledge.

Pretty JSON keeps the punctuation: { } [ ] , ". YAML-like strips the syntactic noise – no quotes around keys, no commas, no braces – just indentation and colons. YAML-like is more “human” but no longer machine-parseable as JSON.

For documents and slide decks that follow numbered hierarchy (e.g., legal/policy documents, training material, structured reports). Each line gets a unique reference like 1.2.3 that you can cite. Best for shallow-to-medium nesting (4-6 levels); very deep nesting produces unwieldy numbers like 1.1.1.1.1.1.1.

Three modes. Indexed paths: items.0: a, items.1: b (deterministic, machine-readable). Numbered: 1. a, 2. b (human-friendly). Comma-joined: items: a, b, c (only for arrays of primitives; arrays of objects fall back to indexed).

Adds a parenthetical type label to each leaf value: name: Ada (string), age: 30 (number), active: true (boolean), missing: null. Useful for documentation that explains a schema or when reviewing API responses where you need to call out the value types.

Default: no – strings appear bare for clean reading. Turn on if your text contains values that could be confused with other types – e.g., the string "42" vs the number 42, or "true" vs true. With quoting on, strings show as "value".

Three modes. Render: emit as the literal word null. Empty: emit just the key with no value (missing:). Skip: omit the entry entirely. Pick what matches your downstream consumer.

Yes. All Unicode characters in your JSON pass through unchanged: emoji 🚀, accented letters (café), CJK (中文), Arabic, anything. We don’t escape or transcode. The output textarea and download preserve UTF-8.

No. All parsing, walking, and rendering runs in your browser. Open DevTools → Network and watch zero requests fire after the page loads. Safe for API responses, internal data, or proprietary schemas.

Yes. Total bundle is under 20 KB. Once the page loads, disconnect and keep converting. Useful when documenting API responses or generating reports without internet.