A widow or an orphan is a line of text left on its own, cut off from the paragraph it belongs to by a page or column break. They're small. They're also the first thing a trained eye lands on, and one of the few typographic mistakes that make a layout look unfinished to people who couldn't name what's wrong with it.
This page covers what each term means, why so many sources define them the opposite way round, how to fix them in the tools you actually use, and when it's worth the effort.
Widows vs. Orphans: What's the Difference?
Both are single lines separated from their paragraph. The difference is which end of the paragraph got stranded, and where it landed.
Understanding Widow Typography
A widow is the last line of a paragraph pushed onto the top of the next page or column. The paragraph ends, but it ends somewhere else. The reader turns the page and finds a sentence fragment sitting alone above the next paragraph, with nothing to connect it to.
Understanding Orphan Typography
An orphan is the first line of a paragraph left alone at the bottom of a page or column. The paragraph starts, then the page runs out. One line sits under a block of unrelated text, and the rest of its paragraph is somewhere the reader hasn't got to yet.
The old typesetters' mnemonic is that an orphan has no past and a widow has no future. An orphan is a beginning with nothing before it. A widow is an ending with nothing after it.
Why the Definitions Get Swapped
Search the two terms and you'll find them defined both ways round, often with equal confidence. That isn't carelessness. There are three overlapping conventions in use, and most sources pick one without saying so.
Traditional typesetting. A widow is the last line of a paragraph, alone at the top of a page or column; an orphan is the first line of a paragraph, alone at the bottom. This is the convention behind Microsoft Word's Widow/Orphan control, the CSS widows and orphans properties, and most print manuals.
Reversed usage. A widow is the first line alone at the bottom; an orphan is the last line alone at the top. Common in design blogs and some foundry glossaries.
Loose usage. A widow is any very short last line of a paragraph, often a single word, and orphan is rarely used at all. This is everyday designer shorthand, where "widow" means any stranded word.
The traditional convention is the one worth learning, because it's the one your software uses. When Word's settings say "Widow/Orphan control" and CSS has widows and orphans properties, they follow the first of those conventions. If a colleague uses the terms the other way, you're both right and you're describing the same two problems. Just agree which end of the paragraph you mean.
The loose usage causes the most confusion. A single word left on the last line of a paragraph isn't a widow or an orphan in the strict sense, because it hasn't crossed a page break. It has its own name, a runt, covered further down. Most designers call it a widow anyway.
The Impact of Widows and Orphans on Typography
Reading is rhythmic. The eye moves across a line, drops to the next, and expects the paragraph to hold together as a block. A stranded line breaks that rhythm twice: once when the reader hits an unexpected gap, and again when they reach the fragment and have to work out what it belongs to.
The damage is proportional to how much the reader is supposed to trust the layout. In a novel, a widow at the top of a page costs a moment's attention. In an annual report, a pitch deck, or a print ad, the same widow reads as nobody having checked. Professional publishing treats them as errors for that reason, not because they're hard to read but because they're easy to see.
They also waste space. An orphan leaves a block of white at the bottom of one column and steals a line from the top of the next, so the two columns no longer align. On a two-column page the difference is visible from across the room.
How to Fix Widows and Orphans, Tool by Tool
Most tools that paginate text have an automatic control. Tools that don't paginate, like slides and design canvases, leave it to you. Here's where the control lives, and what to do when there isn't one.
Adobe InDesign. Paragraph panel menu, Keep Options, Keep Lines Together, where you set the minimum lines at the start and end of each paragraph. It won't fix short last lines.
Microsoft Word. On by default, in the Paragraph dialog under the Line and Page Breaks tab. It only acts at page breaks, not within a page.
Google Docs. Format, Line & paragraph spacing, Prevent single lines. Same limit as Word.
Google Slides and PowerPoint. Nothing automatic. Fix by editing the copy or adding a manual line break.
Figma. Nothing automatic. Fix by adjusting the text box or breaking the line by hand.
CSS. Set orphans: 2; widows: 2; on the text block, and text-wrap: pretty for short last lines. The orphans and widows properties only apply where text fragments across pages or columns, not to ordinary web flow.
Where there's no automatic control, or where the control has done what it can and a stranded line is still there, four manual fixes cover nearly every case.
Edit the copy. The fastest fix is the text itself. Cutting or adding one word changes where every line after it breaks, and pulls the stranded line back into its paragraph. It's the only fix that leaves no trace.
Adjust the tracking, slightly. Tightening a paragraph's letter spacing by a fraction pulls a short last line up into the one before. This is tracking, not kerning: it moves every letter by the same amount rather than adjusting one pair. Keep it small enough that the paragraph doesn't read as denser than its neighbors. Our guide to kerning vs letter spacing covers the difference.
Force the break. A soft return before the last two words keeps them together, so the final line has two words instead of one. A non-breaking space does the same job without a line break: Option+Space on a Mac, Ctrl+Shift+Space in Word, in HTML.
Change the container. Widen the column by a few points, deepen the text box, or move an image. Where the text can't change, the space around it can. In a deck, make the change in the slide master so it holds across every slide rather than being fixed one at a time.
In tools with no paragraph controls at all, editing copy and manual breaks are the whole toolkit. Our guide to kerning in Google Slides covers the same kind of workaround for spacing.
Runts and Rivers: The Neighbors
Two related problems get discussed alongside widows and orphans, and one of them is what most people mean when they say "widow".
A runt is a very short last line of a paragraph, a single word or a hyphenated fragment, sitting alone at the bottom of the paragraph without crossing a page break. It leaves a ragged gap and draws the eye. The fixes are the same as for a widow: edit the copy, tighten the tracking, or bind the last two words with a non-breaking space. In browsers that support it, text-wrap: pretty handles runts automatically by rebalancing the last few lines of a paragraph.
A river is a chain of word spaces that line up vertically across several lines, so a pale channel runs down through the paragraph. Rivers appear in justified text, where the spaces stretch to fill the measure. The fix is to set the text ragged right, narrow the column, or loosen the hyphenation so the spaces vary less.
When It Matters and When It Doesn't
Not every widow needs fixing. Four questions decide how much effort it's worth.
Will it be read on paper? Print is where widows and orphans cost most, because the page is fixed and the break is permanent. Books, reports, packaging copy, and printed ads should be clean.
Is the layout fixed? Slides, PDFs, and designed documents are fixed too, even on a screen. If every viewer sees the same break, fix it, and fix it in the template where there is one, so it stays fixed.
Does the text reflow? On a responsive web page the line breaks change with the viewport, so there's no single widow to fix. Set orphans, widows, and text-wrap: pretty in CSS and let the browser handle it. Chasing individual breaks by hand is wasted effort.
Is the reader judging you? Body copy in a long article can carry the odd runt. A headline, a pull quote, a cover, or the opening paragraph of a proposal can't. Fix the lines people look at hardest.
Frequently Asked Questions
Which one is the widow and which is the orphan?
In the convention your software uses, a widow is the last line of a paragraph alone at the top of a page or column, and an orphan is the first line alone at the bottom. Plenty of sources reverse them. The mnemonic is that an orphan has no past and a widow has no future.
Is a single word at the end of a paragraph a widow?
Strictly it's a runt, because it hasn't crossed a page break. Most designers call it a widow anyway, and the fixes are the same.
Does Word fix widows and orphans automatically?
Yes. Widow/Orphan control is on by default in Word, under Line and Page Breaks in the Paragraph dialog. It stops single lines being stranded at page breaks. It does nothing about short last lines within a page.
Do widows and orphans matter on the web?
Less than in print, because text reflows with the viewport. Set orphans and widows in CSS for anything paginated or in columns, and use text-wrap: pretty to avoid short last lines. Fixing individual breaks by hand doesn't survive the next screen size.
What is a river in typography?
A vertical channel of white space formed when word spaces on consecutive lines line up. It appears in justified text. Setting ragged right, narrowing the column, or allowing more hyphenation breaks it up.
Conclusion
Widows and orphans are easy to fix once you can see them. Seeing them is the part that takes practice. Learn the convention your tools use, switch on the automatic controls where they exist, and save the manual fixes for the lines people look at hardest.
Related reading
- The Importance of Typography in Branding — Explore the pivotal role of typography in branding, understanding how font choices can shape perceptions, evoke emotions, and reinforce brand identity.
- Understanding X-Height in Typography: Definition, Importance, and Applications — Explore the concept of X-height in typography, its significance, and practical applications.
- Font Psychology: The Emotional Impact of Typography — Delve into the world of font psychology and discover how typefaces influence our perceptions and emotions.