Lorem ipsum, and why realistic placeholder text is a UX trap

It's real Latin, just rearranged

The standard lorem ipsum text is not gibberish — it's a scrambled, incomplete excerpt from Cicero's De Finibus Bonorum et Malorum, written in 45 BC. The familiar opening, "Lorem ipsum dolor sit amet, consectetur adipiscing elit," is a mangled fragment of a real sentence from that text; words are dropped, reordered, and run together in a way that destroys the Latin grammar while keeping letter frequencies and word lengths that read as plausible language.

The colourful "a printer scrambled a tray of type in the 1500s" origin story is largely folklore. What's actually documented: classicist Richard McClintock traced the standard passage back to sections 1.10.32–33 of Cicero's text in the 1980s, after noticing the word "consectetur" in a specimen and looking for its source. Specimen books using this exact scrambled text are known from at least the 20th century, popularised industry-wide once Letraset dry-transfer sheets and, later, desktop publishing software shipped it as a default filler.

"Greeking," and why it works

The typesetting term for this is greeking: text whose job is to have the right visual density, word-length distribution and letter shapes to read as a text block from a glance, without being legible enough to actually read. The point isn't obfuscation for its own sake — it's that a human brain automatically reads legible text, and once it starts reading, it starts evaluating the words instead of the layout.

That's the concrete failure mode realistic-sounding filler text causes: hand a stakeholder a mockup with real-sounding English sentences instead of lorem ipsum, and the feedback that comes back is "can we change this headline" or "I don't like this wording" — about content nobody was supposed to be evaluating yet — instead of "the spacing here looks off" or "this column is too narrow," which is what the review was actually for. Lorem ipsum's illegibility-while-still-looking-like-text is doing real work, not just being quaint.

The real limitation: uniform word length hides layout bugs

Lorem ipsum's weakness isn't that it's Latin — it's that its word and sentence lengths are far more uniform than real content ever is. Real copy contains a stray 20-character word that doesn't wrap cleanly, a headline that runs twice as long as the one you designed against, a label translated into a language with a very different average word length. A layout that has only ever been tested against lorem ipsum's gentle, consistent rhythm can look completely solid right up until it meets real content, and then overflow, truncate, or wrap in a way nobody caught in review.

This is a genuine, well-known critique of relying on it exclusively — not a reason to abandon greeking, but a reason to deliberately stress-test past its comfortable middle. Generating an unusually short heading and an unusually long one, on purpose, and checking both against the same layout catches exactly the class of bug that generating only "reasonable-looking" filler text never will. A word-count or paragraph-count generator like this one is well suited to that: push the count to the extremes deliberately, not just to a number that looks about right.

The wider family, and the non-Latin gap

Themed variants — Hipster Ipsum, Bacon Ipsum, and others — serve the identical greeking purpose with a novelty vocabulary substituted in; the mechanism is the same, only the flavour changes. More substantively, greeking generators exist for non-Latin scripts too, and that matters for a reason lorem ipsum specifically can't address: a design meant to ship in Japanese, Arabic, or Korean needs to be checked against that script's own typical character density and line-breaking behaviour, which a Latin-alphabet filler text can never reveal no matter how long or short you generate it. If a layout has to work in more than one script, testing it with only Latin greeking text is its own version of the uniform-word-length blind spot above.

The one place greeking backfires: a screen reader

Lorem ipsum reads as plausible text to the eye precisely because it has real Latin letter frequencies and word shapes — which means a screen reader has no way to know it isn't meaningful content, and will dutifully pronounce it, phonetically, as though it were English or an attempt at Latin. To a sighted reviewer it registers as "text-shaped and not worth reading." To someone listening, it's just confusing noise read aloud in full. If placeholder text will ever be exposed to assistive technology — a live staging environment a screen-reader user might reasonably encounter, not just a static image of a mockup — marking the container aria-hidden, or swapping in real content before that environment is reachable, avoids handing them gibberish with no indication it's a placeholder.

A practical rule of thumb

• Early layout and structural review, before content exists — lorem ipsum or an equivalent, specifically because it stops reviewers from commenting on wording.
• As soon as content or copy itself needs feedback — switch to real or realistically-varied text; continuing with greeked text past this point actively gets in the way.
• Before shipping any layout — generate at least one deliberately short and one deliberately long version of the filler and check both, rather than only ever previewing a comfortable middle length.
• Anything shipping in more than one language or script — check against real or greeked text in the target script too, not only the one the design was drafted in.

Last updated 21 August 2026