HTML Table Extractor

Parse local HTML, inspect table dimensions and captions, then export a chosen table as CSV.

HTML source

Table number

Detected tables

ReadyCell text is exported to CSV; colspan/rowspan visual geometry is not expanded into repeated cells.

Source & result review

Inspect what the browser parsed and what the tool produced

DOMParser ≠ sanitizer

Ready to inspect source and result.

Review is local and detached: this panel never inserts pasted markup into the live page. A browser parser can normalize malformed HTML, but successful parsing does not make markup safe to inject. Scripts, inline event attributes and embedded browsing/plugin elements are reported as active-content signals, not executed.

Browser-local does not mean standards-complete

HTML parsing is error tolerant. Source diagnostics, sandboxed previews, and transformations do not replace full conformance, security, or production-browser testing.

Choose the parsed table deliberately

Confirm the document table count, selected table number and extracted rows/columns before handing the result to a spreadsheet or CSV workflow.

Parser and sanitizer boundary

HTML DOMParser creates a detached document and may repair or normalize markup. That is useful for inspection, but parsing alone does not sanitize untrusted HTML. Review scripts, inline event attributes, embedded content and application-specific URL/context rules before any live-DOM insertion.

Practical guide and verification

Use the tool first, then apply these checks to verify inputs, interpret the result, and hand it off without displacing the primary workflow.

Identify the table you actually need

A page can contain navigation, layout, hidden, nested, and data tables at the same time. Verify the selected table number against headers and representative cell values before exporting. A technically valid table extraction can still be the wrong dataset if the page contains multiple similar structures.

Inspect rowspan and colspan semantics

Merged cells describe relationships visually that a flat CSV may need to repeat or expand. Check whether the extractor preserves, expands, or omits values from rowspan and colspan cells, then normalize the result deliberately before analysis. Do not assume a rectangular CSV preserves every semantic relationship in the HTML table.

Treat displayed text and underlying data separately

Cells can contain links, icons, hidden labels, formatted numbers, dates, or nested markup. Decide whether you need visible text, href values, raw HTML, or machine-readable attributes. If the downstream task depends on identifiers or URLs, a text-only extraction may be incomplete even when the table looks correct.

Verify CSV quoting before import

Commas, quotation marks, line breaks, and formula-like values need correct CSV escaping. Open a small export in the intended spreadsheet or parser and compare row/column counts with the extracted preview. Keep the source HTML when the table is important enough to reproduce or audit later.