Flush left gives a stable starting edge
Aliases: ragged right · left aligned · start aligned
What it is
In a flush-left (ragged-right) paragraph every line leaves from the same vertical. The returning eye does not have to re-estimate “where does this line begin”; it has a fixed address. That is not the same as lining up buttons, cards, and icons on a grid — that is alignment of layout objects. This is about whether the line start inside a paragraph is treated as the origin of reading.
In a left-to-right UI, left is the starting edge. In right-to-left writing the stable edge is the right. Horizontal Chinese also enters from the left. The name “left” refers to the starting datum, not a decorative preference.
Why it happens
The line start is the target of the return sweep. If that target sits at the same x on every line, aiming can become a habitual short hop rather than a search. The right edge keeps the rag, so the engine does not have to haul on word spaces: each word’s own gap remains, letters are not stretched, the grey texture of the paragraph stays even. The rag is also a fingerprint of “which line I am on” — one line ends on the, the next on from — so a skip is easier to catch.
Flush left dumps all the unevenness at the line end. The end is where reading of that line is already finished, so rag there costs less than rag at a start that has not begun. Centering splits the unevenness across both ends, so the start moves every line. Justification swallows the unevenness between words: the start is neat, the texture is full of holes. Flush left is the only of the three that keeps both a fixed origin and unmolested word spacing.
Chinese has no compressible word space of the Latin kind, so flush left is the default of horizontal body, not a borrowed style. Even so the start line still matters: if indent, bullets, and quote bars take a different bite each row, the datum is gone the same way.
Studying it
When comparing flush left with justified and centered, measure two things separately: whether the return hits the correct start, and whether word spacing stays even. Eye tracking gives horizontal error at line start; a greyscale of the type only shows whether “rivers” open in the texture. In Tinker’s print-reading tradition, alignment sits with measure and leading as a page variable, not a taste item. Dependents: skip rate, speed, rated “neat / easy to read” (these two often fight: justified is rated neater, flush left easier).
The copy has to be a multi-line paragraph. A one-line label has no return, so it cannot show the value of a starting datum.
Where it stops holding
Column headers, figures, and money compare digits, not a reading start; they want right or decimal alignment. Titles, verse, and signatures need not share the body’s origin. A short column makes an ugly rag under flush left — that is an overshort measure, not a reason to justify in order to “fill.” Formal print that wants two neat edges (book interiors, newspapers) can, in a wide column with hyphenation, trade a little spacing stability for a double edge; interface columns are usually neither wide enough nor well hyphenated, so the trade is a bad one. Alignment of objects on a grid still belongs to the layout system. “Paragraphs should be flush left” is not a reason to glue an icon to the left of a card — object alignment is a different job.
Applying it
- Default continuous-reading paragraphs to flush start. Do not justify them so the card edge “looks fuller.”
- Give the line start a real vertical: same indent on sibling paragraphs, same slot for list marks, quote bars that do not appear and vanish.
- For right-to-left languages put the same rule on the starting edge; do not copy an LTR
leftvalue across. - While reading, run a pen down the line starts. If the line wobbles, the datum is gone — check indents and list slots first, then whether centering or justification walked it off.