Your export saved 40 rows. The table had 12,480.

Modern dashboards only build the rows on screen, so ordinary exporters save what is visible and say nothing about the rest. GridScoop spots it, scrolls, and saves every row.

Catches virtualized grids300 rows a day, free100% local · no account · no telemetry
One page. One grid. Two exports.
An ordinary exporter40
rows in the file
GridScoop12,480
rows in the file

The 12,440 rows in between were never on screen, so they were never in the file.

How the other 12,440 rows get out

No copy-paste, no truncated exports, no "select all" that grabs half the page. Click the icon, pick a table, done.

🔍

It warns you before you export

GridScoop spots that the grid is virtualized and says so before you export — so you find out that the rows on screen are not the whole grid before the report goes out, not after someone asks.

🧲

It scrolls so you don't have to

One click auto-scrolls the grid and stitches every batch into one table. Paginated reports merge too, up to 50 pages, without you touching Next.

📤

It lands in your spreadsheet, clean

Excel with real numbers, CSV and JSON as files; TSV and Markdown to the clipboard, for Sheets and for docs. Every table on the page — up to 50 — can go into one workbook.

The same grid, measured three ways

Nothing below is a benchmark. Open a dashboard you already use, export it twice, and compare the two files.

On the pageAn ordinary exporterGridScoop
Rows the grid holds12,48012,48012,480
Rows built in the page right now404040
Rows in the file you get4012,480
Warning that rows are missingnone“This grid is virtualized”
Pages merged into that file1up to 50
Tables on the page in one workbook1up to 50
Where the data was processedyour browser

This is not a difference you would notice in a menu. It is the difference between a report and a wrong report.

And where it still can't help youGrids rendered inside a shadow root — many web-component UIs — are not scanned in 1.0. Page merging needs in-place (AJAX) pagination — pages that fully reload stop the merge at what has been captured. Markdown treats row 1 as the header. Plain extraction caps at 20,000 rows. Full-grid capture walks up to 400 screens of the grid or 90 seconds, whichever comes first — in practice several thousand rows, depending on row height — and it tells you when it stopped early rather than handing you a short file quietly. Grids that virtualize columns as well as rows export only the rendered columns; when such a grid publishes its column count, a full-grid capture tells you columns are missing.

Every feature is free. So are 300 rows a day

Nothing is crippled and there is no trial clock: detection, full-grid capture, page merging and every export format are in the free plan. What the free plan counts is rows — 300 of them a day. That is one everyday table, or one grid of any size: a 12,480-row capture still goes through in full, and spends the day in a single click. So the free plan covers the occasional lookup, and you pay the moment exporting is part of your actual work.

A 300-row table100%
of today's free rows — one table is the day
One 12,480-row dashboard grid100%
also one day — it still exports in full, every row
The second export of the dayover the line
Pro removes the ceiling — or it resets tomorrow
PRO · NO DAILY CEILING
$15/year
that's $1.25 a month · 14-day refund, no questions
  • No daily row allowance — a whole dashboard in an afternoon, not one grid a day
  • Same features as Free — you are lifting a ceiling, not unlocking a product
  • No counter running — stop checking what you have left
  • Cancel anytime — you drop back to the free plan, nothing you exported is touched
Pro checkout opens with the launch. Get notified →
FREE · FOREVER
$0
no account, no trial clock
  • 300 rows a day — one ordinary table, or one big grid
  • Every feature, every format — capture, merging, Excel, CSV, TSV, Markdown, JSON, Sheets
  • Virtualized grids flagged — you always know what a plain export would miss
  • 100% local — no account, no telemetry
Get notified at launch

Questions

Why did my last export only save part of the table?

Because the page never had the rest of it. Modern dashboards are virtualized: to stay fast, they build only the forty or so rows on screen and throw away the ones you scroll past. Any tool that reads the page reads those forty and calls it done. GridScoop detects a virtualized grid, tells you what it found, then scrolls the grid itself and stitches every batch into one complete table.

What am I actually paying for?

Rows, not features. Every feature is free, in every format, with no trial: detection and warnings, full-grid capture, page merging, whole-page workbooks. The free plan includes 300 exported rows a day. Pro removes that ceiling for $15 a year.

Is 300 rows a day enough for me, and what happens when I run out?

For the occasional lookup, yes — 300 rows is one everyday table, and tiny tables give you two or three. Past that it is deliberately tight: that is where the paid plan starts. The generous part is the clamp — any single grid is one free export a day whatever its size, so a 12,480-row capture still goes through in full. Nothing is ever truncated, and the allowance resets the next day. GridScoop counts the rows before it exports, so you always know where you stand, and if you do reach the ceiling nothing breaks and nothing is lost — the allowance simply resets the next day. If large grids are your normal Tuesday, Pro works out at $1.25 a month.

Why is Pro a subscription?

Because grids keep changing. Sites update their grid engines constantly, and keeping capture working against them is ongoing work, not a one-time build. $15 covers a year of that upkeep — it's $1.25 a month, you can cancel anytime, and there's a 14-day no-questions refund. Nothing you exported ever locks.

Where does my data go?

Nowhere. Extraction and conversion happen entirely inside your browser — the free features make no network requests at all. If you buy Pro, the extension periodically validates your license key (the key plus the extension's ID and version — never your data) with our license server. No account, no analytics, no tracking.

What are the honest limits?

Markdown export treats the first row as the header. Grids rendered inside a shadow root — many web-component UIs — are not scanned in 1.0. "Merge pages" works with in-place (AJAX) pagination — pages that fully reload stop the merge at what's been captured. Plain exports cap at 20,000 rows and the popup lists the 50 largest tables on a page; "Capture full grid" walks up to 400 screens of the grid or 90 seconds, whichever comes first, and says so when it stops early. The caps keep your browser responsive. Grids that also virtualize columns export only the rendered columns; GridScoop warns you when it detects that.

How do refunds work?

Purchases are handled by Paddle, our reseller (Merchant of Record). You can request a refund within 14 days of purchase, for any reason — email info@bilingoplus.com or use the links in your Paddle receipt.