HTML Table to JSON Converter

What Is HTML Table to JSON Conversion?

HTML Table to JSON conversion parses HTML markup and represents table data as JSON. The usual result is an array of objects: each table row becomes one object, and each column becomes a property.

This is different from representing a whole document as a JSON DOM tree with tags, attributes, text, and children. This page extracts tables only; it does not serialize an entire page.

How to Convert an HTML Table to JSON

1. Enter HTML: paste markup containing a table, or open a local .html or .htm file.
2. Pick the table: when several tables are present, select the one you need.
3. Detect headers: use th cells, force the first row, or generate column names.
4. Configure values: trim text, infer basic types, or turn empty cells into null.
5. Review warnings: check spans, renamed headers, and uneven rows.
6. Convert: generate a JSON array of objects.
7. Copy or download: save the result as a .json file.

Example HTML Table

Input:

<table>
  <thead>
    <tr><th>Name</th><th>Age</th></tr>
  </thead>
  <tbody>
    <tr><td>Alice</td><td>30</td></tr>
  </tbody>
</table>

Output with the default options:

[
  {"Name":"Alice","Age":"30"}
]

Age stays the string "30" because type inference is off by default. Turn it on to get the number 30.

Header Handling

Column names can come from an explicit thead section, from a leading row of th cells, or from generated names. When a header cell is empty it becomes column_N for that position, and a repeated name gets a numeric suffix such as Name_2, so no column is silently dropped. Both cases are reported as a warning.

If a table has more than one header row, this page uses the first one and warns you, because grouped or stacked headings cannot be flattened unambiguously.

Why colspan and rowspan Matter

A cell with colspan="2" occupies two logical positions, and rowspan spans several rows. Correctly expanding them requires building a grid and filling every position a spanning cell covers. This version does not do that: it reads each row as written and warns when a span is present, so the column alignment can be checked by hand instead of being silently wrong.

Text Content, Not HTML

Values are read from cell text content. Tags inside a cell contribute their text, so <td><strong>Alice</strong></td> yields Alice. Markup and attributes such as href or src are not extracted. That keeps the output plain data, and it also means links and images inside a table are not part of the result.

Type Inference Can Change Values

Table cells are text, and text has no type. With inference enabled, lowercase true and false become booleans and plain integers or decimals become numbers. Values such as 00123, SKU-001, 1e5, and TRUE are never converted, so identifiers, postal codes, and formatted amounts stay intact. Keep the option off unless numeric types are what you need.

HTML to JSON Is Not Scraping

This tool parses HTML that you paste or open locally. It does not fetch URLs, run JavaScript, follow pagination, or evaluate access policies. For repeated extraction from live sites, a local scraper or a build-time step is the right tool; the browser converter is for saved markup, copied fragments, and one-off extraction.

Privacy and Browser-Based Processing

Parsing and conversion happen in the browser, so the HTML you paste stays on your device. That suits saved pages and exported markup, but it is not a secret-management system. Avoid pasting authenticated page content, credentials, or confidential customer data into any online tool.

When to Use a Local Parser

For many files, repeated jobs, very large documents, or confidential content, use a local HTML parser and keep the conversion in your own pipeline. Browser conversion is best for quick extraction, inspection, and small-to-medium tables.