Widows and Orphans in Book Formatting: How to Fix Them (2026)

Open any professionally published paperback and flip through it slowly. You will notice something your eyes accept without comment: every page looks full and balanced, and no single line ever sits stranded by itself at the top of a page. That invisible polish comes from two tiny typographic details called widows and orphans — and controlling them is one of the quiet skills that separates a polished book from one that looks self-published in the worst sense. It belongs with the font, margin, and layout choices covered in our guide to book typography, fonts, and margins.

In this 2026 guide, you will learn exactly what widows and orphans are (and which is which, because nearly everyone mixes them up), why they quietly erode reader trust, and how to eliminate them in Microsoft Word, Adobe InDesign, Vellum, Kindle Create, and Atticus — plus the honest truth about the one format where none of this matters.

What Widows and Orphans Actually Are

A widow is the final line of a paragraph that ends up alone at the top of a new page. Picture eight lines of a paragraph: seven sit at the bottom of page 42, and the eighth — perhaps just the words “the door behind him.” — sits alone at the top of page 43. That lonely eighth line is the widow.

An orphan is the mirror image: the first line of a paragraph left alone at the bottom of a page while the rest continues on the next. Three words sitting by themselves at the foot of page 42 while their paragraph resumes on page 43 — that is the orphan.

Think of the words literally: an orphan is a child left behind, alone at the bottom of the page. A widow begins a new page alone at the top.

One complication: some sources swap the two terms. The Chicago Manual of Style convention — widow at the top, orphan at the bottom — is what professionals use, and what this guide follows. The names matter less than the rule: never leave a single line of a paragraph alone on a page. Two lines is the minimum on either side of a page break.

Why Widows and Orphans Make a Book Look Amateur

Readers cannot name a widow, but they feel one. A stranded line creates a small jolt — white space where the eye expected text, a page that looks oddly short. Multiply that jolt across 300 pages and the whole layout feels restless and cheap, even if the reader never identifies why.

Books are judged by micro-details. Your reader unconsciously compares your paperback to every traditionally published book they have held. Trade publishers have controlled widows and orphans for centuries — the rules predate computers, going back to hand-set metal type. Ignore them and your book signals that no professional touched the interior. Poor formatting is among the most common complaints in one-star self-published reviews, and stranded lines are exactly the sloppiness that triggers it.

There is a readability argument too. An orphan forces the reader to hold one line in memory across a page turn; a widow makes them reconstruct which paragraph they are in. Both add friction — the enemy of the immersive reading that sells your next book. The good news: this is one of the cheapest problems in publishing to fix. It costs no money, only attention.

Runts, Bad Breaks, and Other Page-Break Problems

Widows and orphans have relatives worth knowing, because you will meet them during the same cleanup pass.

A runt is a short final line — typically a single word — trailing at a paragraph’s end. Not technically a widow, since nothing is stranded on its own page, but almost as untidy, especially a hyphenated fragment or a lonely “the.” Fix runts in the same pass by rewriting the sentence so the last line fills out.

Stacked hyphens — sometimes called ladders — are three or more consecutive lines ending in hyphens, a staircase of dashes down the right margin. Most style guides allow no more than two in a row.

Then there are bad breaks that are not widows or orphans at all: a chapter heading stranded at a page bottom while its text starts on the next, a page breaking mid-dialogue, or a chapter whose final page holds only two lines. All share one trait with widows and orphans: the reader notices the break instead of the story.

The principle behind all of them is the same: page breaks should be invisible. The moment a reader notices a lonely line, a dangling heading, or a staircase of hyphens, the formatting has failed at its one job — to disappear.

How to Fix Widows and Orphans in Microsoft Word

Word has built-in widow and orphan control, and it is the first thing to check. Select your manuscript text (Ctrl+A), right-click, choose Paragraph, and open the Line and Page Breaks tab. Make sure “Widow/Orphan control” is checked. In Word’s default template this is usually already on — but manuscripts pasted in from Google Docs, Scrivener, or older files often arrive with it switched off, so verify rather than assume. This step belongs to the full print-ready setup in our complete guide to formatting a book in Word for KDP.

Three sibling settings on the same tab do the rest. “Keep with next” glues a paragraph to the one following it — apply it to chapter titles and subheadings so a heading never sits alone at a page bottom. “Keep lines together” blocks page breaks inside selected paragraphs — useful for epigraphs, but dangerous on body text, where it forces ugly gaps. “Page break before” pushes a paragraph onto a new page — the correct way to start chapters, never a fistful of empty paragraphs.

Word’s control is good but not perfect. It prevents stranded lines by pushing lines to the next page, leaving pages that end at slightly uneven depths. Professionals accept tiny variations. But when the control produces a conspicuously short page, the fix is editorial: rewrite a sentence a few pages earlier to add or remove a line, and the downstream flow rebalances.

Never fix a widow with manual page breaks mid-paragraph, and never pad pages with empty paragraphs. Both corrupt your eBook export — empty paragraphs become blank gaps on Kindle, and manual breaks shatter reflow. Fix the text, not the break.

Widow and Orphan Control in InDesign

InDesign handles this through Keep Options. Open a paragraph style, go to Keep Options, and check “Keep Lines Together,” with “At Start of Paragraph” and “At End of Paragraph” both set to 2 lines — the typographic rule encoded as a setting. Set chapter titles to “Keep with Next” for two or three lines so a heading never dangles at a page foot.

The critical discipline: apply keeps through paragraph styles, never as local overrides. When every body-text paragraph shares one style with Keep Options baked in, one change fixes the whole book. Local overrides get wiped out by the next style update.

Two InDesign-specific notes. First, keep vertical justification off for book interiors; it stretches spacing to force identical page depth, which looks far worse than a page ending one line short. Second, watch Keep Options interact with hyphenation: InDesign will hyphenate its way into a two-line widow that technically passes your settings. Limit consecutive hyphens to two.

When you are done, proof the old-fashioned way: export the PDF and flip through at full-page view, watching only the tops and bottoms of pages.

How Vellum, Kindle Create, and Atticus Handle Bad Breaks

With a modern book-production tool, much of this work happens without you. Vellum, the Mac-based formatter used across indie publishing, applies widow and orphan control automatically to its print PDF output — the generated paperback interior arrives with stranded lines already eliminated. See our Vellum book formatting guide for its full print and eBook workflow.

Kindle Create, Amazon’s free formatting tool, is primarily an eBook tool — eBooks have no fixed pages, as explained below — but its paperback PDF export applies keep-together logic so headings and short paragraphs do not break badly. Atticus, the cross-platform Vellum alternative, handles keeps automatically in its print export and shows a true print preview so you can spot escapees before uploading. Our Kindle Create formatting guide walks through Amazon’s free tool step by step.

The pattern: these tools automate the common cases and give you a preview for the rest. Your job is a final visual pass over the print PDF:

Manual Fixes vs. Automatic Control

Automatic control comes first: it fixes the great majority of widows and orphans in seconds, across the whole book. Manual fixes are for the stubborn remainder. Work in this order.

First, try the editorial fix: rewrite a sentence near the trouble spot. Adding or cutting a few words changes where every downstream line falls, and one small edit often dissolves the widow entirely — the highest-leverage fix there is.

Second, adjust hyphenation. Turning hyphenation on for justified text, or tuning its zone, changes line lengths enough to pull a stranded line back where it belongs. If a widow ends in a hyphenated fragment, forcing a different break point can absorb it.

Third, use tracking — overall letter-spacing — in tiny doses. In InDesign, tightening or loosening tracking slightly can gain or lose a full line; in Word, the equivalent is character spacing on the Font dialog’s Advanced tab. Use it sparingly: visibly altered spacing looks worse than the widow did.

What never to do: no soft returns (Shift+Enter) to fake line breaks — they create false paragraphs that wreck eBook conversion. No manual page breaks to shove a widow over. No shrinking one paragraph’s font. If a widow resists every honest fix, rewrite the paragraph. There is always a rewrite.

Your pre-publish page-break audit

• Widow/orphan control ON for all body text (Word: Line and Page Breaks; InDesign: Keep Options 2/2)
• “Keep with next” applied to all chapter titles and subheadings
• Chapters start with “Page break before” — never empty paragraphs
• Hyphenation tuned: max two consecutive hyphens, no hyphenated fragment as a last word
• No manual page breaks inside paragraphs; no Shift+Enter soft returns anywhere
• Print PDF flipped through page by page, tops and bottoms checked
• Short chapter-ending pages reviewed for overall balance, not just stranded lines

Print vs. Reflowable eBooks: When This Stops Mattering

Here is the honest truth: in a reflowable eBook, widows and orphans cannot exist. An EPUB or reflowable Kindle eBook has no fixed pages — pagination is computed on the reader’s device and changes with every font-size adjustment. The widow in your preview vanishes the moment a reader bumps the text up one size. Chasing stranded lines in a reflowable file is chasing shadows.

That is why Vellum, Kindle Create, and Atticus apply widow/orphan logic only to print outputs. For eBooks, what matters is structural: genuine paragraph styles, clean chapter breaks, properly anchored images. Kindle’s enhanced typesetting handles hyphenation and spacing dynamically per device.

The exception is fixed-layout eBooks — children’s picture books, cookbooks, print-replica PDFs — where every page is a fixed image. There, pages are real, widows are real, and the print rules apply in full.

So budget your effort honestly. Run the full widow-and-orphan pass on your print PDF, where every copy is identical. For the reflowable eBook, verify clean styles and chapter breaks, then let it go — the reader’s font-size button has the final say.

Conclusion: Give Your Pages an Invisible Polish

Widows and orphans are tiny — a single line here, a single line there. But they are exactly the kind of tiny that readers feel without naming: the difference between a page that looks inevitable and one that looks accidental. Switch on automatic control in your tool, clean up the survivors with honest edits, proof the print PDF’s page tops and bottoms, and let reflowable eBooks be. Do that, and your interior carries the quiet polish that tells every reader a professional made this book.