What Are the Text, Tree, and Table Modes in JSON Editor Online?

JSON Editor Online offers three editing views—text, tree, and table—and you can switch between them without losing your undo/redo history. Use text mode for raw JSON editing, tree mode for navigating deeply nested structures, and table mode for a tabular view of array-based data. The right choice depends on whether you need precise syntax control, structural navigation, or a spreadsheet-like overview.

Text Mode: Raw JSON Editing

Text mode shows your JSON as plain text in an editor. This is the view to use when you need full control over syntax—writing new JSON from scratch, pasting in a payload from an API response, or fixing a formatting problem character by character.

• Best for: authoring JSON, pasting raw data, precise edits to keys, values, and punctuation.
• What you see: the literal JSON document, including braces, brackets, commas, and quotes.
• Practical tip: text mode now includes Expand All and Collapse All buttons (added September 2025), so you can collapse the whole document and then expand only the nodes you care about—useful for large, deeply nested files.

Because text mode exposes the raw syntax, it is also where formatting and beautifying actions make the most visible difference: you can take minified JSON and reformat it into readable, indented output.

Tree Mode: Navigating Nested Structures

Tree mode renders JSON as a collapsible tree of nodes. Instead of scanning lines of text, you expand and collapse objects and arrays to drill into the parts you need.

• Best for: exploring large or deeply nested documents, understanding structure before editing, and making targeted changes without touching surrounding syntax.
• What you see: a hierarchical view where each key and value is a node you can expand or collapse.
• Why it helps: in a deeply nested document, collapsing everything and expanding only the relevant branch is far faster than scrolling through raw text. The search box can locate the part you are looking for and navigate you to it.

Tree mode is generally the safer place to make structural edits, since you are working with nodes rather than hand-editing punctuation.

Table Mode: Tabular Viewing

Table mode presents JSON data in a table layout, which suits documents whose structure maps naturally to rows and columns—typically arrays of objects with consistent fields.

• Best for: scanning many records at once, spotting patterns or outliers across entries, and getting a spreadsheet-like overview of array data.
• What you see: your data arranged in rows and columns rather than as nested text or a node tree.
• When it fits less well: heavily nested or irregular JSON does not flatten neatly into a table, so text or tree mode will usually be more informative there.

Switching Modes Without Losing History

A key behavior to know: when you switch between text, tree, and table modes, the editor no longer resets the undo/redo history (changed November 2024). Previously, switching views could wipe your history; now you can switch to another view just to inspect something and switch back without worrying about losing your undo stack.

This matters in practice. A common workflow is to edit in tree mode, switch to text mode to check the exact serialized output, then switch back—and with history preserved, that inspection step costs you nothing.

Choosing a Mode: A Quick Comparison

Practical Notes

• You can combine modes. Edit in one view, verify in another; history is preserved across switches.
• Large documents benefit from collapsing. Use Expand All / Collapse All in either text or tree mode to reduce visual noise before navigating.
• Table mode is not a universal view. If your JSON is irregular or deeply nested, expect text or tree mode to serve you better.
• The tool covers more than viewing. Beyond these three modes, JSON Editor Online also formats, repairs, compares, queries, transforms, and validates JSON, and converts between JSON and CSV.

If you are unsure where to start, open your document in tree mode to understand its shape, switch to text mode when you need to change exact syntax, and use table mode when your data is a list of similar records you want to scan side by side.