To keep a Word table row from splitting across two PDF pages, change that row's pagination setting in the DOCX, export a new PDF, and inspect the boundary again. Do not add blank paragraphs to push the row down, and do not expect a PDF preview tool to repair the Word table.
Change the affected row in desktop Word
Select the row that must stay together, open Table Properties > Row, and clear Allow row to break across pages. Make the change in a saved working copy of the DOCX so the original layout remains available if pagination shifts elsewhere.
Microsoft's current Table Properties guidance says to click in or select the row, right-click the table, choose Table Properties, and use the Row tab for page-breaking options. Its current version list covers Word for Microsoft 365, Word 2021, Word 2019, and Word 2016.
For example, consider a two-page event schedule. Most rows contain a time, speaker, and room, but one session has a long accessibility note. In the exported PDF, the session title remains at the bottom of page 1 while the note continues on page 2. Select that complete session row, clear the break-across-pages option, and leave the neighboring short rows unchanged.
Remove an exact-height conflict before judging the result
A row set to an exact height may clip or conceal growing content, so review its height setting at the same time. If Specify height is enabled, choose At least when the content needs room to expand, or clear the fixed height when the design does not require one.
Microsoft's row-height instructions document Table Properties > Row and explain that an exact height prevents cells from expanding with their contents. That page currently lists Word for Microsoft 365, Word 2024, Word 2021, Word 2019, and Word 2016.
No setting can make a row taller than the usable page area fit intact on one page. If the schedule note, nested table, or large image makes one row exceed a page, shorten the content, reduce legitimate spacing, resize the image, or split the material into two meaningful rows. Repeated blank paragraphs are not a stable fix because edits to margins, fonts, or preceding content will move the break again.
State the version and interface limit explicitly
The exact break-across-pages workflow is verified here for the desktop editions named on Microsoft's current Table Properties page: Word for Microsoft 365, Word 2021, Word 2019, and Word 2016. That page does not list Word 2024 or Word for the web, although a separate Microsoft row-height page lists Word 2024 and uses the same Table Properties route.
In Word 2024, confirm that the installed build exposes the same checkbox before using it. If the control is absent, search Word Help or use an edition covered by the support page. Open a web document in the desktop app when the browser editor lacks the row property; Mac, localized, and managed installations may also use different labels.
Export a new PDF from the corrected DOCX
Save the working DOCX, then export a new PDF with a filename that distinguishes it from the previous attempt. Microsoft's current PDF export guidance documents File > Save As or Save a Copy, selecting PDF, and using More Options > Options when additional controls are needed.
That PDF page currently lists Word for Microsoft 365, Word 2021, Word 2019, and Word 2016. It describes Word for the web as producing a basic PDF and points users to the desktop app for more control.
For the schedule example, save event-schedule-row-fix.docx, export event-schedule-row-fix.pdf, and open the new PDF independently. The long session row should begin on page 2 as a complete unit. A larger blank area at the end of page 1 is not automatically an error; compare it with the requirement that one record remain readable as a whole.
Do not overwrite the previous PDF until the new one passes. If the row still splits, return to Word and check the row selection, page-break checkbox, and height setting. Editing PDF pages would hide the symptom without correcting the reusable DOCX source.
Use page images only as a visual inspection aid
The PDF to Image converter can render the affected PDF pages as PNG or JPG for side-by-side visual review. It reads selected pages in the browser, offers 72, 150, or 300 DPI, and creates separate images; it does not change the PDF, open the DOCX, or alter table properties.
Choose a custom range containing the pages around the break, such as 1-2. PNG at 150 DPI is a practical first visual check for text and rules. Confirm that the session title, note, border, and following row appear on the expected pages.
Raster output does not preserve selectable text, links, bookmarks, form fields, tags, or Word's table structure. After checking the images, return to the actual PDF and test page count, text selection, links, headers, footers, and the table boundary at normal reading zoom.
PDF Page Manager is not a substitute for this fix. It can rebuild a separate PDF from selected pages, but it cannot move part of a table row within a page or repair the Word source. When the DOCX is available, correct its pagination and export again.
Verify nearby content before delivery
A successful fix keeps the affected row intact without damaging neighboring content. Review the page before the moved row, the complete row, the row after it, and any repeated header at the new page boundary.
Use a short acceptance check:
- The title, all cells, notes, and bottom border of the affected row appear on one page.
- No text is clipped by an exact row height, image, or nested table.
- The preceding page has no unintended blank paragraph or manual page break.
- Repeated header rows, page numbers, footnotes, and section-specific headers still appear correctly.
- The PDF page count and table order match the reviewed DOCX.
- Text remains selectable in the actual PDF when that is part of the delivery requirement.
If the table is part of a signed, accessible, regulated, or records-controlled document, use the document owner's approved review process. A clean visual boundary is useful evidence, but it is not the only requirement such a document may have.
Common questions
Why does clearing Allow row to break across pages leave a large gap?
Word moves the complete row to the next page when it cannot fit in the remaining space. Check whether the row truly belongs together before trying to remove the gap.
Why is text still clipped after the row moves?
The row may have an exact height. In Table Properties > Row, change the height rule to At least or remove it when the layout permits, then export and inspect again.
What if one row is taller than a whole page?
It cannot remain intact within that page area. Shorten or restructure the content, resize legitimate large objects, or divide the material into meaningful rows instead of adding blank paragraphs.
Does this exact path apply to Word 2024 or Word for the web?
Microsoft's current page for row-breaking options lists Microsoft 365, Word 2021, Word 2019, and Word 2016, not Word 2024 or the web editor. Confirm the control in your installed build or use a covered desktop edition rather than assuming identical behavior.
Can ToolboxHub keep the row together for me?
No. ToolboxHub's PDF to Image tool only creates page images for visual review, and PDF Page Manager only rebuilds whole PDF pages. Neither tool opens or edits the DOCX, changes a table row, or writes corrections into the exported PDF.
Is checking the PNG pages enough before sending the PDF?
No. Page images help you inspect the visual break, but they cannot verify selectable text, links, bookmarks, tags, forms, or accessibility. Open and test the actual exported PDF after the image review.