YAML Table Viewer

About Table Viewer

Shows the records inside a document as a table, which is how most people want to read data that happens to be stored as JSON, XML or YAML. Each record becomes a row and each field a column, so a list of orders, users or measurements can be scanned, compared and checked at a glance.

The list is found for you: a document that is an array is tabulated directly, and one that wraps its records — {"items": [...]} or <orders><order/></orders> — is unwrapped. When a document holds more than one list, a path says which one to show: $.items for JSON and YAML, //item for XML.

Nested fields are flattened into dotted column names, so {"user": {"name": "Ada"}} becomes a user.name column rather than an unreadable blob. Records that carry different fields are still tabulated: every column that appears anywhere becomes a column, and rows that lack it are simply empty there.

Where it helps

• Turns any of the formats into rows and columns without converting the file first.
• Finds the list of records on its own, and takes a path when the document holds several.
• Flattens nested fields into dotted columns instead of hiding them.
• Runs entirely in your browser, so production data never leaves the machine.

Limits

• It reads: there is no sorting by column, filtering or editing.
• A document with no repeating records has nothing to tabulate — a path is needed, or the document is simply not tabular.
• Deeply nested arrays inside a record are shown as their JSON text rather than as nested tables.
• Very wide records make for a very wide table; the panel scrolls, but a hundred columns is still a hundred columns.

Frequently asked questions

It says there is no list of records — what now?

The document holds no repeating structure at the top level. Point at the list with a path, such as $.results or //row, or use the Tree Viewer to see what the shape actually is.

It says the document holds several lists — which do I pick?

It names them, as paths you can paste straight into the path field. Nothing is guessed, because picking the wrong list silently would be worse than asking.

Why are some cells empty?

Because those records do not carry that field. Every field seen anywhere becomes a column, so the gaps show you exactly which records are missing what.

How are XML attributes shown?

As columns named after the attribute, alongside the child elements, so <item sku="TU-1"><price/></item> gives a sku column and a price column.

Can I get the table out as a file?

Use the Structure Converter with CSV as the target: it finds the records the same way and writes them as a spreadsheet-ready file.

Related tools

• Structure Converter — Convert between JSON, XML, YAML, TOML, TOON, HCL and CSV
• Tree Viewer — Explore JSON, XML, YAML, TOML, TOON or HCL as a collapsible tree
• Path Finder — Select nodes with JSONPath or XPath
• Expression Evaluator — Reduce a JSONPath or XPath match to a single answer
• String Escaper — Escape a JSON, XML, YAML, TOML or TOON document for embedding, or read one back
• Structure Formatter — Pretty-print JSON, XML, YAML, TOML, TOON or HCL with a chosen indent

More Structured Formats tools

• Structure Converter — Convert between JSON, XML, YAML, TOML, TOON, HCL and CSV
• String Escaper — Escape a JSON, XML, YAML, TOML or TOON document for embedding, or read one back
• Structure Formatter — Pretty-print JSON, XML, YAML, TOML, TOON or HCL with a chosen indent
• Structure Validator — Check JSON, XML, YAML, TOML, TOON or HCL and report structural problems
• Tree Viewer — Explore JSON, XML, YAML, TOML, TOON or HCL as a collapsible tree
• Code Generator — Turn a JSON, YAML, XML or other document into TypeScript, Go, C#, Python, Rust and more
• Schema Generator — Write a JSON Schema, XSD, Avro schema or .proto from a document you already have
• Schema Validator — Check a document against a JSON Schema, .proto, Avro schema, XSD or RELAX NG
• Table Viewer — Show the records in a JSON, XML, YAML, TOML or TOON document as a table
• Structure Compare — Diff two JSON, XML, YAML, TOML, TOON or HCL documents by path
• Structure Repair — Fix broken JSON, YAML, XML, TOML, TOON, INI, .env, .properties and HCL, listing every repair
• Structure Minifier — Strip formatting from JSON, XML, YAML, TOML or TOON
• Path Finder — Select nodes with JSONPath or XPath
• Protobuf & Avro Decoder — Read protobuf wire bytes and Avro container files without their schema
• Expression Evaluator — Reduce a JSONPath or XPath match to a single answer