Convert JSON to an HTML table

Shape the report before export

HTML table export works from an array. Each item becomes a row, and the exporter builds columns from the observed row shape. If the source contains too many fields, use a query first so the saved report tells one clear story.

HTML mapping has its own behavior. It is related to CSV and Markdown table export, but not identical in every internal display path. Verify the saved artifact separately from the workspace preview.

Escaped HTML output example

This example starts from a root object and selects .report.rows before export. Markup-like text should appear as text in cells, not become active markup. In the example below, <Ann> is shown as escaped text and A&B keeps the ampersand as text. The excerpt is intentionally compact so you can see the table structure without reading the full saved page shell.

{
  "report": {
    "rows": [
      {"name":"<Ann>","score":2},
      {"name":"Bob","note":"A&B"}
    ]
  }
}

.report.rows

[
  {"name":"<Ann>","score":2},
  {"name":"Bob","note":"A&B"}
]

<table class="json-html-table__document">
<thead><tr><th scope="col">#</th><th scope="col">name</th><th scope="col">score</th><th scope="col">note</th></tr></thead>
<tbody>
<tr><th scope="row">1</th><td>&lt;Ann&gt;</td><td>2</td><td></td></tr>
<tr><th scope="row">2</th><td>Bob</td><td></td><td>A&amp;B</td></tr>
</tbody>
</table>

Create the HTML table

1. Open the JSON source or shaped array result.
2. Review the table columns and remove unrelated fields before export if needed.
3. Choose Export, then HTML table.
4. Open the downloaded HTML file separately from the workspace.
5. Check row count, column names, escaped markup-like strings, and any display options you used.

Preview and saved file are different checks

The workspace can help you inspect and sort data before export. The saved HTML artifact is what you send to someone else, so check the downloaded file separately from the preview.

For a report that will be emailed or archived, open the downloaded file in a clean browser window. Check the first row, last row, sorted column if used, and any markup-like text against the data you selected.

Be precise about links and resources

Link detection, image handling, date markers, and security markers are display features with their own boundaries. For an ordinary text table, focus on what you can verify directly: the saved file contains readable rows and escaped text cells for the chosen data.

If you need a table for documentation source, use Markdown table export. If you need a spreadsheet import, use CSV or TSV.

If the data contains URLs or image-like strings, review that option set directly. A plain text fixture does not prove how every link or image-like value should behave in a saved report.

• Convert JSON to a Markdown table
• Convert nested JSON to CSV
• Compare all export formats