Guides

Why Designers Use Nonsense Text Instead of Real Words

By the Laborilo team. Last updated August 20, 2026.

Sending a client a mockup full of "Lorem ipsum dolor sit amet" can feel like handing over unfinished work, or like you're dodging the question of what the copy will actually say. Neither is true. Filling a mockup with gibberish Latin looks like a shortcut. It's actually a deliberate design choice, grounded in research on how people read, that real, meaningful words would quietly sabotage.

The practice has its own name: "greeking" text

Designers call deliberately illegible or nonsensical placeholder text "greeking". A term rooted in the old idiom for something unintelligible ("it's Greek to me"). The point isn't laziness; it's isolating one variable. A layout review is supposed to evaluate spacing, line length, font pairing, and visual hierarchy, and real, meaningful sentences actively work against that by pulling a reviewer's attention toward what the text says instead of how it looks.

That's also why it doesn't read as unfinished or evasive to the people who are supposed to look at it. A client scanning a wireframe generally knows the convention already, and a one-line note ("placeholder text, final copy TBD") removes any doubt for the people who don't. What would actually look less polished is a mockup full of real, half-written sentences that reviewers start editing instead of evaluating the layout.

What reading research actually shows

Eye-tracking studies on how people scan web and app content. Most famously the F-shaped reading pattern research from Jakob Nielsen's Nielsen Norman Group. Demonstrate that readers process real text very differently from how they visually scan a layout for structure. Meaningful copy hijacks attention toward comprehension; a designer trying to judge whether a heading is the right size doesn't want the reviewer's brain switching into "reading mode" instead of "looking mode."

Why some designers have started pushing back on it

There's a real, ongoing debate in the design world against lorem ipsum specifically because meaningless text can hide genuine content problems until it's too late. Text that turns out to be too long for a button, an awkward line break, a translation that runs much longer than the English original. A growing number of designers prefer contextual or realistic placeholder content (sometimes even AI-generated to match the eventual real copy's length and tone) specifically to surface those problems earlier, at the cost of losing lorem ipsum's clean neutrality.

What to actually do about it

If your goal is an early-stage layout review, stick with classic lorem ipsum: pure visual neutrality is the point, and generating clean, unreadable text at the exact length you need is what a lorem ipsum generator is for. If your goal is a client-facing mockup that reads as finished work, lorem ipsum is still fine, just add a short caption naming it as placeholder text so nobody mistakes intentional nonsense for a missing deliverable. And if your goal is catching content-fit problems, a heading that wraps awkwardly, a button label that's too long, switch to realistic or length-matched placeholder copy instead, since lorem ipsum's neutrality works directly against you there.

Generate your own placeholder text by word, sentence, or paragraph with the lorem ipsum generator.