Formatting, design & craft
Widows, Orphans, and Rags: Fixing Common Typesetting Problems
What widows, orphans, rags, rivers, and bad line breaks are in typesetting — how to spot them in your book interior and fix them before going to print.
Widows and orphans are two of the most discussed problems in professional typesetting, and also two of the most commonly confused. They're both cases where a single line of a paragraph ends up visually isolated — stranded on a page or at the bottom of a column — but they happen in different positions and are solved in slightly different ways.
Beyond widows and orphans, professional typesetting involves a set of related problems: rags (the uneven right edge of left-aligned text), rivers (vertical channels of white space running through justified paragraphs), stacked hyphens, and bad word breaks. These issues are what separate a book that was formatted from one that was typeset — that has been attended to at the level of individual lines rather than just paragraphs and pages.
Most self-published books don't address these issues because formatting tools don't fix them automatically. But the difference between a book with and without resolved typesetting problems is visible — readers feel it, even if they can't name it.
Why typesetting details matter
Readers process text largely unconsciously. When text is well-set, their eyes move smoothly through the page and they experience only the story or the argument. When text has typesetting problems — a dangling widow, a jarring river of white space — something snags their attention at the level of the page layout rather than the content.
Professionally published books are typeset with attention to these issues because publishers understand that the physical reading experience is part of the product. Self-published books that have been formatted but not typeset often have an indefinable quality that makes them feel slightly off even when the words themselves are excellent. Resolving typesetting problems is part of what distinguishes a book that competes with traditional publishing from one that doesn't.
See print proofing checklist for the full workflow for reviewing a print interior before publication — typesetting problems should be on your review list alongside margins, bleeds, and font embedding.
Widows
A widow is the last line of a paragraph that appears alone at the top of a new page or column, separated from the rest of its paragraph which ended on the previous page.
The name comes from the image of isolation: the last line of the paragraph has been left behind, stranded at the top of the new page with nothing above it except white space. Widows are considered one of the most distracting typesetting problems because the eye lands on a new page expecting to begin something, but instead finds a sentence fragment completing a thought that was on the previous page.
A widow line is especially problematic when it's short — a single word, or two or three short words. A widow that's a near-full line is less visually disruptive but still a problem by strict typesetting standards.
How to fix widows
The toolkit for widow elimination:
- Edit the paragraph. Adding or removing a word or two in the paragraph often causes it to reflow, resolving the widow naturally. This is the cleanest solution because it doesn't alter the visual texture of the surrounding text.
- Adjust tracking. Slightly loosening or tightening the letter-spacing (tracking) in the paragraph can pull the widow back or push more text to the following page. Changes should be imperceptible — typically fractions of a point.
- Adjust where the page break falls. In some cases, pulling the page break one line earlier — pushing more text to the next page — resolves a widow cleanly, though this can create an orphan problem elsewhere.
- Rewrite. If all else fails, a sentence-level rewrite in the affected paragraph that shortens or lengthens it resolves the reflow.
Orphans
An orphan is the first line of a paragraph that appears alone at the bottom of a page, with the rest of the paragraph continuing on the next page.
The widow/orphan distinction trips up many people. A useful mnemonic: a widow is at the top of a page (the last line of a paragraph, left alone); an orphan is at the bottom of a page (the first line of a paragraph, left alone). Both represent visual isolation, but in opposite positions.
Orphans are considered somewhat less disruptive than widows because the reader at least begins the paragraph in its correct location on the page. But a single orphan line at the bottom of a page — especially a short first line like "He waited." or "The answer was no." — still signals poor typesetting care.
How to fix orphans
The same toolkit applies: edit the text to cause a reflow, adjust tracking, or adjust where the page break falls. For orphans specifically, one additional option is to tighten the previous page — by tightening tracking or making a small edit that removes a line from the preceding page, you can move the orphaned first line back to join the rest of its paragraph on the previous page.
Short last lines (runts)
A runt (sometimes called a widow at the paragraph level) is the last line of a paragraph that contains only one short word or a very short fragment — ending a paragraph on a single word like "me." or a two-letter word like "it." This is technically a widow at the paragraph level rather than the page level, but it's treated as a distinct problem in typesetting.
Runts are common in justified text because the typesetter (or auto-layout engine) distributes words across lines without considering what remains. A paragraph that ends on "And then everything changed for her." may be fine; a paragraph that ends on "her." is a runt.
The fix is almost always an edit — adding or removing a word somewhere in the paragraph to cause the final line to be longer. Tracking adjustments can sometimes help but are less reliable for runts than for page-level widows and orphans.
Rags
A rag refers to the uneven right edge of text set in left-aligned (ragged right) alignment. In left-aligned text, the left edge is straight and the right edge varies in length from line to line — that variation is the rag.
Some variation is normal and desirable. Left-aligned text should have a natural, varied right edge — this is one reason editors and typographers often prefer it over fully justified text for certain formats. But bad rags occur when the variation is extreme or irregular in a way that draws the eye:
- A very short line followed by a very long line, then a medium line — the irregular step pattern is distracting
- A staircase pattern where each successive line is shorter than the previous
- A line so short it leaves a large void of white space in the middle of a paragraph
Good rags vs. bad rags
Good rags are characterized by gentle, irregular variation — no dramatic jumps in line length. The right edge has texture but not chaos. Bad rags have lines that are wildly unequal, especially consecutive short lines that create a staircase or triangular effect.
Hyphenation settings directly affect rag quality. With no hyphenation, long words either fit on a line or force the entire word to the next line, creating large gaps and dramatic length variation. With moderate hyphenation, long words can be split, producing more even line endings.
How to fix bad rags
- Adjust hyphenation settings. Allowing more hyphenation smooths the rag by distributing word breaks more evenly.
- Edit the text. Adding a word to a short line or removing a word from a long line can smooth out a dramatic step in the rag.
- Adjust tracking. Slightly loosening or tightening tracking in the affected paragraph changes how words distribute across lines.
Rivers
A river is a visual phenomenon in fully justified text where gaps between words accidentally align vertically through several consecutive lines, creating an irregular vertical channel of white space that the eye can trace through the paragraph.
Rivers happen because justified text must distribute spacing across lines to make every line the same width. When the algorithm that does this creates similar amounts of word-space in similar positions on consecutive lines, the coincidental alignment creates a visible river.
How rivers form
Rivers are most common in:
- Narrow columns — less horizontal space means less flexibility in word distribution, so gaps are forced to align more often
- Justified text with aggressive word spacing — when the typesetter allows large gaps between words to make justification work, rivers are more likely
- Long words — a long word that forces large gaps on one line tends to create a visual cascade on adjacent lines
How to fix rivers
- Loosen or tighten word spacing settings. Adjusting the minimum, optimum, and maximum word spacing parameters changes how aggressively the justification algorithm distributes gaps.
- Edit the affected paragraph. Adding or removing a word at a key position changes the word distribution and breaks up the aligned gaps.
- Add a discretionary line break. Forcing a line break at a strategic point within a problem paragraph redistributes the remaining words across lines differently.
- Enable better hyphenation. Allowing hyphenation gives the justification algorithm more options for line breaks, reducing the need for large word gaps.
Hyphenation settings and typesetting problems
Hyphenation is the primary lever for managing rags, rivers, and line length variation. The settings that matter:
- Hyphenation on/off. Some authors prefer no hyphenation. This is typographically defensible in left-aligned text but will worsen rags in many paragraphs.
- Consecutive hyphenated lines limit. Set a maximum of 2–3 consecutive lines ending in hyphens. More than 3 is considered poor typography.
- Minimum letters before/after break. Setting a minimum of 3 letters before the hyphen and 3 after prevents awkward breaks like "the-" or "-ing."
- Hyphenation zone. The distance from the right margin within which hyphenation is allowed. A larger zone means more hyphenation; a smaller zone means fewer breaks.
Stacked hyphens
Stacked hyphens occur when three or more consecutive lines end in a hyphenated word break. This creates a column of hyphens on the right margin that draws the eye and looks amateurish.
Traditional typesetting allows a maximum of two consecutive lines ending in hyphens. Some style guides say three is acceptable in rare cases; more than three is never acceptable in professional typesetting.
Fix stacked hyphens by adjusting hyphenation settings, editing the paragraph, or adjusting tracking to change which words land at the end of lines.
Bad word breaks
Hyphenation algorithms don't always break words at acceptable points. Common problems:
- Proper nouns broken mid-word: "Mc-Carthy" at a line break is technically a valid syllable break but looks strange
- Words broken to leave only 2 letters: "co-" or "-ly" at a line end reads awkwardly
- Words broken so the break changes the meaning or looks like another word: "the-rapist" for "therapist" is a classic example
- Numbers and abbreviations broken: "15,-000" or breaking "$12" across a line
Most hyphenation dictionaries handle standard word breaks correctly, but they don't know about proper nouns in your manuscript or context-specific break problems. A line-by-line review will catch these.
Typesetting review workflow
The table below summarizes the key typesetting issues, what to look for, and how to fix them.
| Issue | What to look for | Primary fix | Priority |
|---|---|---|---|
| Widow | Last line of paragraph alone at top of page | Edit paragraph; adjust tracking | High |
| Orphan | First line of paragraph alone at bottom of page | Edit paragraph; tighten previous page | High |
| Runt | Final line of paragraph = 1 short word | Edit paragraph to lengthen final line | Medium |
| Bad rag | Dramatic irregular right edge in left-aligned text | Adjust hyphenation; edit text | Medium |
| River | Vertical white-space channel in justified text | Adjust word spacing; edit paragraph | Medium |
| Stacked hyphens | 3+ consecutive lines ending in hyphen | Adjust hyphenation settings; edit | Medium |
| Bad word break | Awkward or meaning-altering hyphen placement | Add discretionary break or no-break | Low–Medium |
Work through a book systematically from page one, preferably from a printed proof — some of these issues are easier to spot on paper than on screen.
Physical proof as the final check
Screen review catches most typesetting problems but not all. Line spacing, rag quality, and rivers in particular can look different on screen versus printed paper — both in the way your eye processes them and in the way the final printed reproduction renders fine spacing details.
Ordering a physical proof from your print-on-demand provider before approving a final version is the professional standard. See print proofing checklist for a complete guide to what to review when your proof arrives.
Frequently asked questions
How many widows and orphans are acceptable in a finished book? Professionally typeset books aim for zero. In practice, eliminating every single widow and orphan requires edits that some authors aren't willing to make, and very near-full-line widows may be left if they would require significant text changes to fix. For a self-published book, resolving all obvious widows (especially short ones) and all orphans is the right standard.
Do ebooks have these problems? Reflowable ebooks don't, because the text reflows based on the reader's device and settings. A widow in your print layout doesn't exist in the ebook — it would be on a completely different "page" on every device. Typesetting attention for widows, orphans, and rivers applies only to fixed layouts: print books and fixed-layout ebooks.
Is it worth the time to fix every single widow? For short lines — a single word or two words stranded at the top of a page — yes, absolutely. These are visually disruptive and edits to fix them are usually small. For near-full-line widows that are 4–5 words long, the visual disruption is modest and whether to fix them is a judgment call about how much you want to alter the text.
What's the difference between a widow and an orphan again? A widow is the last line of a paragraph left alone at the top of a page. An orphan is the first line of a paragraph left alone at the bottom of a page. Remember: widows are the ones left at the top because the rest of the paragraph has gone ahead to the next page.
Can formatting software fix these automatically? Some layout software (like InDesign) has widow and orphan control settings that prevent obvious cases by automatically adjusting page breaks. However, automatic controls can solve one problem while creating another, and they have no way to fix rags, rivers, or runts. Human review and targeted edits remain the definitive solution.
The bottom line
Widows, orphans, rags, rivers, and stacked hyphens are the visible signs of a book that was formatted but not typeset. None of them are catastrophic on their own, but collectively they give a book the slightly rough quality that distinguishes self-published from traditionally published interiors.
The good news is that these problems are fixable. Most require only a word-level edit or a small tracking adjustment. Building a systematic typesetting review into your pre-publication workflow — ideally on a physical proof — is what takes a formatted manuscript to a genuinely professional book.
LiberScript formats your manuscript with typesetting quality built in, handling hyphenation, line spacing, and text flow to minimize these issues from the start. Get started to format your book or see pricing for available pass options.
Related guides
Ready to put this into practice?
LiberScript brings writing, critique, design, and export into one workspace, with no subscription.