When a cell range is better than a full table capture
Use a range when you need a few columns from a wide comparison table, a visible set of rows from a report, or one section of a table that contains several subheadings. Selecting at the source is also useful when the page mixes current records with totals and archived values.
Do not use a range to hide a structural problem. If rows have shifted columns or inconsistent headers, capture the relevant area and repair it in the editor before export.
How to select the right cells
Keep the header row in the selection whenever the exported data will be filtered, shared, or imported elsewhere.
- Start cell range mode from the extension.
- Drag from the first required header cell to the final cell in the last required row.
- Check the highlighted rectangle before confirming the capture.
- Open the result in Table Studio and rename incomplete headers if the range started inside a grouped heading.
- Export the reviewed range to Excel, CSV, Markdown, the clipboard, PNG, or PDF.
Headers, totals, and frozen columns
A range that begins halfway through a grouped header may lose context. Include the most specific header row, then rename columns in the editor when the page uses a decorative title above the real labels.
Totals belong in the export only when they are part of the next calculation. A total row mixed with ordinary records can produce double counting in a pivot table or database import. Remove it when the destination will calculate totals again.
Capture visible rows or the full dataset
Some sites render only the rows currently visible on screen. Others paginate or load more records while you scroll. A cell range can select what exists in the DOM, but it cannot safely infer records the page has not loaded.
For virtualized or paginated tables, load the required rows first or use the extension's scroll-assisted and multi-page capture tools. Compare the final row count with the source before export.