Why this extension exists
Copying a table looks like a solved problem until the page uses merged headers, DIV grids, links, form controls, virtualized rows, or a PDF that stores every word as positioned text. The result may look acceptable for the first few rows and fail quietly further down.
The extension was built around a simple idea: extraction and export should be separate steps. First capture the structure. Then inspect and repair it. Only then create the Excel, CSV, Markdown, PNG, PDF, or clipboard output.
Correct data before convenient export
File formats are useful only when the underlying rows and columns are correct. That is why the free product includes Capture Score, structural diagnostics, cell range selection, intelligent column types, and Table Studio.
Capture Score does not pretend that every page can be parsed perfectly. It highlights missing headers, uneven rows, type mismatches, and other signals worth checking. Table Studio then gives you direct control over the result instead of hiding the raw capture behind a download button.
Local first by design
Page content, local PDF files, table editing, and file generation are processed in the browser. The extension does not require an account to capture or export a table. It makes a network request only when the user explicitly asks it to load a PDF from a URL.
This design keeps the basic product useful without a server dependency. It also makes the privacy boundary easier to understand: the data belongs to the browser session and local extension storage, not to an unseen processing queue.
What comes next
The planned Pro version adds repeatable workflows rather than charging for basic correctness. The roadmap includes capture history, comparison between two captures, JSON and HTML exports, and destinations such as Notion, Airtable, and webhooks.
Those features require separate work on retention, credentials, permissions, and delivery logs. They will not be described as available until they are implemented.
Read the product FAQ