Long Paragraphs Go Unread: Is Font Size Really to Blame?

Long paragraphs often go unread not because of font size, but because line height, line length, and contrast fail to support the reading rhythm. In typical UI deliveries around 2026, adjusting line height to 1.5-1.8 times the font size, limiting line width to roughly 45-75 characters, and then checking whether the body text color is too light will solve the problem more effectively than simply increasing font size. Font size affects "legibility," but line height and line length determine whether readers are willing to continue.

Users Skip Body Text: Why Can't It Be Blamed Solely on Font Size?

"Font too small" is the most common guess during UI reviews, but often even increasing the font from 14px to 16px doesn't stop users from scrolling past. The reason is that during reading, the eyes continuously move from the end of one line to the beginning of the next; if line height is tight and lines are too long, the eyes easily lose their place. Font size is just one layer of perception, not the entire burden of continuous reading.

• Line height determines the vertical space between lines; too tight causes line confusion, too loose makes paragraphs seem scattered.
• Line length determines the sweep distance; too wide makes returning to the next line difficult, too narrow breaks the text into fragments.
• Contrast between body text and background affects eye fatigue; light gray text makes the whole paragraph seem "dimmed."
• Paragraph spacing provides pause points; without any spacing, long text on the first screen looks like a solid gray block.

Experience Range for Body Text Readability and Comparative Approaches

I do not treat the following values as fixed rules but as a typical range for starting adjustments. Mobile body text commonly uses 14-16px with line height about 1.5-1.7 times the font size; desktop body text commonly uses 15-16px with line height about 1.6-1.8 times. On desktop, the content column should also be width-limited so that each line contains roughly 45-75 characters, which for Chinese interfaces corresponds to about 25-40 Chinese characters.

If you compare two adjustment strategies, the cost difference often shows up in subsequent reviews:

• Option A: Increase font size first. It's quick to change and can be done in about half an hour, but it alters line breaks and may create new line-length issues; later you often need to adjust line height again, requiring at least one additional round of visual confirmation.
• Option B: Check in order of line height, line length, contrast, then paragraph spacing. Initial troubleshooting may take about an hour, but once parameters are stabilized, they can be documented for specs, keeping development implementation on track and usually reducing visual review rounds by one or two.

The above are experience ranges. For multilingual interfaces, text may lengthen in other languages, so constraining "characters per line" rather than pixel width is even more critical. This prevents regression when switching languages.

Four-Step Troubleshooting: Structure First, Then Color

To avoid trial-and-error based on subjective feeling, follow these four steps in order. The order matters: if structural issues are unresolved, adjusting color and weight only makes misaligned paragraphs more noticeable.

1. Measure line height: Select the body text and ensure line height is at least 1.5 times the font size; if it's below 1.4, first bring it back into the typical range.
2. Set line length: On desktop, narrow the content column to roughly 45-75 characters per line; if you are already in a narrow container, check for excessive orphaned lines.
3. Check contrast: Do not use light gray for long body text. Compare dark gray or near-black with the background, ensuring information hierarchy is not dulled by poor legibility.
4. Add paragraph spacing: Use at least half a line height between paragraphs to ensure each break is recognizable.

This sequence fits long-text scenarios such as content pages, detail pages, and help centers. If the page body text is only one or two sentences, you can skip it.

Practical Delivery: Writing Text Parameters into Specs Saves More Than Repeated Screenshots

During a corporate website redesign in the first half of 2026, the client wanted to emphasize a "lightweight feel," so the news article text was designed in light gray with line height left at the editor's default. During internal evaluation before launch, many long articles were quickly skimmed, and everyone's first reaction was "the font is too small."

I did not increase font size first. Instead, I changed the body text to near-black, raised the line height to 1.6 times, added half a line height between paragraphs, and narrowed the content column to about 30 Chinese characters per line. After producing that version, I prepared an alternative with "larger font but everything else unchanged." When the client tested on their own phones, almost all chose the version with adjusted line height and line length. That wasn't because my instincts were sharper, but because that version gave enough margin for line breaks, return sweeps, and paragraph pauses. Afterward, I recorded font size, line height, paragraph spacing, and color values in the design specs. The developer implemented according to parameters, and visual review required one less round of rework. Based on similar tasks, the extra half hour or so spent on parameter organization usually saves at least one round of rework cost.

This is what I often call the typical range: readability rework for content-heavy pages usually falls within one to two rounds; documenting structured parameters clearly often eliminates one of those rounds.

Applicability and Boundaries: First Identify Which Text Deserves This Treatment

Body text readability is not something every page needs to optimize specifically. Only when text is the primary vehicle for users completing a task do line height and line length merit detailed attention. UI labels, button names, and short tooltips should focus more on clarity and action feedback than on reading continuity.

• Suitable for: news detail pages, help centers, product descriptions, long tooltips beside forms, and long descriptions in order or billing details; run the three checks of line height, line length, and contrast first.
• Not suitable for: short text scenarios like buttons, icon labels, navigation, and one-line welcome messages; forcing long-text rules here can make the UI feel loose.
• Even with perfect typography, if the content itself is verbose and lacks subheadings or key terms, readers will still scroll away. Typography can increase the probability of "readability," but it cannot replace content editing.

Additionally, some designers might set line height above 2 times to create a "breathing feel," but for continuous body text this causes the eyes to wander vertically too long. Line height typically need not exceed 1.8 times; only verify special cases individually.

FAQ

What line height works best when body text is being skipped?

A common typical range is 1.5 to 1.8 times the font size. For continuous long-form text, aim closer to 1.6 to 1.8; if below 1.4, bring it back before checking other parameters.

Why do users still not read even with a larger font?

Because font size improves "whether it's legible," while line height and line length improve "how tiring it is to jump between lines." If the latter remains unsolved, a larger font increases visual weight, making the reading burden of a whole block even more obvious.

What is a good maximum line length?

For desktop, a stable target is about 45-75 characters per line, which corresponds roughly to 25-40 Chinese characters per line. If you exceed that, narrow the content column first.

Can light gray be used to downplay long body text?

Not recommended. Light gray lowers contrast, causing users to subconsciously shorten reading time. Gray suits secondary labels or auxiliary notes, while body text is safer in near-black or dark gray.

So, when long paragraphs go unread, don't rush to increase the font size. First measure line height, narrow line length, and check body text color and paragraph spacing; these usually get closer to the root cause than directly changing font size. The boundary of this approach is clear: it fits content-driven interfaces that require continuous reading, not short text with only a few words. If you have a long paragraph that just doesn't look right no matter what, try setting line height and line length as fixed variables first, then judge whether the font size is truly insufficient.