Why iframe tables disappear from basic capture tools
Content in an iframe is a separate document. A script that only walks the top page never sees those rows. Cross-origin frames add another limit: the parent page cannot read the child DOM directly.
That is why some tools show “no tables found” on a screen that clearly has one. The table is there. It is just not in the document they searched.
A practical iframe capture workflow
Use an extension that injects into frames and aggregates the results. In the popup you should see tables labeled from iframes alongside top-page tables.
- Open the page and wait until the iframe finishes loading its report.
- Open Table Capture & Extractor and refresh the scan if needed.
- Select the table marked as coming from an iframe.
- Preview it in Table Studio and confirm headers survived the nested layout.
- Export Excel, CSV, or copy for paste once the grid looks right.
Same-origin vs cross-origin frames
Same-origin iframes are easier because more of the DOM is reachable. Cross-origin iframes still work when the extension runs inside that frame and reports the extracted table back.
If a frame never loads extension scripts — for example certain restricted contexts — capture may still fail. In that case, open the frame URL directly when the product allows it, then capture from that tab.
Troubleshooting empty scans
Confirm the iframe has finished loading. Try advanced or scroll-assisted capture if the table lazy-loads. Check whether you are looking at a canvas or image pretending to be a table — those need a different approach.
When the table is real HTML or an ARIA grid inside the frame, a frame-aware scan is usually enough.