When a cell range is better than a full table capture
Use a range for a few columns from a wide comparison, a visible slice of a long report, or one block inside a table with several subheadings. It also helps when current records sit next to totals and archives.
Do not use a range to hide a structural mess. If columns already shifted, capture the useful area and fix it in the editor before export.
How to select the right cells
Keep the header row in the selection whenever the export will be filtered, shared, or imported. Missing headers is how “mystery column C” starts.
- Start cell range mode from the extension.
- Drag from the first required header cell to the last cell in the last required row.
- Check the highlighted rectangle before confirming.
- Open Table Studio and rename incomplete headers if the range started under a grouped title.
- Export the reviewed range to the format you need next.
Headers, totals, and frozen columns
A range that starts halfway through a grouped header loses context. Include the most specific header row, then rename columns if the page used a decorative title above the real labels.
Keep totals only when the next step needs them. Mixed into ordinary records, they double-count in pivots and imports. Delete them when the destination will calculate totals again.
Capture visible rows or the full dataset
Some sites only render the rows on screen. Others paginate or lazy-load while you scroll. A cell range can select what exists in the DOM. It cannot invent records the page never loaded.
For virtualized or paginated tables, load the rows you need first, or use scroll-assisted capture. Compare the final row count with the source before you download.