Keep a Google Docs Table Row Together Across Pages

1. Set up a reproducible table

The practice text contains a table header and several fictional handoff records. Paste it into a safe Google Doc and turn the records into a table, or use your own table with one tall row. Add enough preceding content that the target row approaches a page boundary. The exact line break depends on your fonts and margins, so use the visible break as your starting state.

Checkpoint: Fictional records; Target row near page break; No private client data.

2. Check document format

Open File, Page setup, and confirm Pages is selected. Google's row overflow control is not available in Pageless format. If you switch formats, scroll through the table again, because pagination may change. The target row must be close to a page boundary for this exercise to show a before-and-after difference; otherwise you can still set the option, but the visual check is weaker.

Checkpoint: File > Page setup; Choose Pages; Recheck boundary.

3. Disable row overflow

Select the table row that splits. Use Format, Table, Table options, or right-click the table and choose Table options. Under Row, turn off Allow row to overflow across pages, then apply the change. The wording sounds backward: unchecking overflow is what keeps the row together. Select the whole affected row rather than clicking an unrelated row in the same table.

Checkpoint: Select affected row; Table options > Row; Uncheck Allow row to overflow.

4. Inspect the page boundary

Scroll to the page break. The selected row should begin on a page where its content can fit, rather than being cut in two. The preceding rows may leave some blank space at the bottom of the earlier page; that is a normal tradeoff of keeping this record together. If your target row still spills, confirm the selected row and that the document is in Pages format.

Checkpoint: Target row in one place; Blank space may remain; Check selection.

5. Know when the setting cannot help

A row taller than a full page cannot fit intact on a normal page. Shorten its notes, split the record deliberately, reduce unnecessary padding, or revise the page layout. Do not shrink the font until it is hard to read. This lesson solves the common near-boundary split, not an oversized record. Also distinguish row overflow from pinning header rows; the two controls serve different purposes.

Checkpoint: Oversized row needs redesign; Keep text readable; Not header pinning.

Check the finished result

Export or download a PDF and inspect the same fictional record, because that is what someone may actually receive. Its row label, owner, and notes should appear together on one PDF page. Compare the PDF with the Docs view and confirm the table header remains legible. If the PDF differs, revisit page setup and the row option before sharing the file.

Expected answer: After the Row setting is changed, the selected fictional handoff row should not be divided across a page break. Its label, owner, and notes remain within the same row on one page; a preceding row may end the previous page. Export a PDF and inspect that same row there. If the row is taller than an entire page, reduce its content or layout first. The control is available only in Pages format.

If it still fails

If the handoff row still splits, confirm the document is in Pages format and that you changed the affected row's Allow row to overflow setting. A row taller than a whole page needs shorter content or a different layout.

Official references

• Google Docs official help

Checked 16 October 2026. On-screen explanatory panels are labelled illustrative diagrams; any separately identified actual capture is a genuine English app view.