Why Designers Still Use Lorem Ipsum in 2026

Every few years someone declares lorem ipsum dead, and every few years it turns up in a fresh Figma file. The reason is not laziness. Filler text does one job that real copy cannot: it keeps a design review on the layout. The trouble starts when it stays past that first review. This is what lorem ipsum is genuinely good at, and the exact point where it starts costing you.

#TL;DR

• Lorem ipsum keeps early reviews on layout instead of wording.
• Its word and sentence lengths approximate real prose, so blocks size realistically.
• Nielsen Norman Group limits placeholders to early low-fidelity wireframes only.
• Filler hides long headings, empty states, and copy nobody has written.
• Grep your build for lorem before shipping — it escapes more often than you think.

#Why do designers still use lorem ipsum?

The argument against filler text is loud and mostly correct. The argument for it is quieter and rarely written down, so here it is.

#Unreadable text keeps the review on the layout

Put real English into a wireframe and the first comment will be about the third sentence. Put Latin in and the first comment is about the column width. That is the entire trick. Lorem ipsum is deliberately semi-Latin nonsense — it reads as text-shaped without reading as text, which is why typesetters called the technique greeking long before the web existed.

For a 20-minute review whose only question is "does this grid hold up," that property is worth something. The moment the question becomes "does this page persuade anyone," it becomes a liability.

#It sizes blocks the way real prose does

Random characters would fill space too, but badly. Lorem ipsum's value is that its distribution of word lengths and sentence lengths sits in roughly the same range as English body copy, so a three-paragraph block occupies a believable amount of vertical space. Swap it for aaaa aaaa aaaa and the line-break behaviour stops telling you anything.

That makes it a reasonable instrument for one specific measurement: line length. WCAG 2.2's Level AAA criterion 1.4.8 Visual Presentation asks that a mechanism exist to keep blocks of text at no more than 80 characters or glyphs per line — 40 for CJK, because CJK characters render about twice as wide at equal readability. Filler text is fine for checking whether your measure lands in that range.

/* Measure and wrapping — testable with filler text */
.prose p {
  max-width: 68ch;      /* comfortably under the 80 */
  text-wrap: pretty;
}
.prose h2 {
  text-wrap: balance;   /* see MDN text-wrap */
}

text-wrap: balance evens out the lines of a short block such as a heading; MDN's text-wrap page covers the values and their limits. Balance behaviour depends on how many lines the text produces, so test it with a realistic heading length, not a Latin one — more on that below.

#It fills forty text layers in one keystroke

The practical reason filler persists is throughput. Emmet has shipped a lorem abbreviation for over a decade, and every major design tool has a generator plugin. Typing an abbreviation beats writing forty paragraphs of anything.

p*3>lorem24        →  three <p> of 24 words each
ul>li*5>lorem6     →  a five-item list, 6 words each
h2>lorem5          →  one five-word heading

If you are not in an editor, an in-browser generator does the same job — the iKit Lorem Ipsum Generator produces paragraph, sentence, word, or list output entirely client-side, so nothing about your unreleased layout leaves the machine.

#Is lorem ipsum bad for design?

Yes, past a certain point — and the point is earlier than most teams assume.

#What the research actually says

Nielsen Norman Group's position is narrow and worth quoting precisely: use placeholders only if you have to, and then only in the first stages of low-fidelity wireframe communication. Susan Farrell's article Which Comes First? Layout or Content? is blunter still — it lists "lorem ipsum must die" among the failures of a container-first process, alongside empty placeholder regions and headings that exist only because the template has a slot for them.

NN/g's follow-up video on fake copy in prototypes makes the mechanism explicit: placeholders are convenient early and cause problems later precisely when the real content has different characteristics from the filler. Different characteristics is the whole risk. Latin has no 34-character German compounds, no all-caps product SKUs, no empty fields.

#Copy written to fit the box

The subtler failure runs the other way. Kyle Fiedler's 2010 Smashing Magazine piece Lorem Ipsum is Killing Your Designs put it memorably:

"By adding Lorem Ipsum to the design you are essentially dressing your king before you know his size."

Once a mockup is approved with three 24-word paragraphs, those three paragraphs become a requirement. The writer inherits a shape and pads to fill it. A point that needed one sentence gets four, because the design has a hole that size and the design was signed off first.

#It ships

Filler escapes into production more often than anyone admits — footers, meta descriptions, empty states, the admin screen three people ever open. It survives because no one owns that copy, and no test asserts against it.

# Run before every release
grep -ri "lorem ipsum\|dolor sit amet" dist/ src/ \
  --include="*.html" --include="*.json" \
  --include="*.js" --include="*.vue"

Two seconds in CI, and it catches nearly every case.

#When to use lorem ipsum and when to use real content

Think in stages rather than absolutes. The question is never "filler or not" — it is "what am I trying to learn from this screen right now?"

#A stage-by-stage rule

The rows above are the practical reading of NN/g's guidance, not a quotation of it. The shape is what matters: filler is a tool for the first two rows and a liability in the last three.

#What filler can and cannot test

Some things filler measures honestly. Others it quietly lies about.

• Measures honestly: line length, paragraph rhythm, vertical spacing, the general height of a text block.
• Lies about: heading wrap, button label width, truncation points, empty states, localisation expansion, tone.
• Cannot touch at all: whether the page actually answers the reader's question.

Heading wrap deserves special mention because it is the most common regression. lorem5 gives you a tidy five-word heading with no long tokens; your real heading is "Enterprise Single Sign-On Configuration" and it breaks to three lines on a 390 px viewport. Any heading you intend to ship should be tested with its real string, or at minimum with a worst-case one.

#The cheapest upgrade: your own ugliest content

If draft copy does not exist yet, you do not have to choose between Latin and nothing. Borrow. NN/g's recommendation for greenfield projects is to assemble comparable media from other sources inside the wireframe — a competitor's longest product title, the most awkward paragraph from your current site, the support article nobody wants to look at.

That content is free, it is realistic, and it breaks layouts in exactly the way real content will.

#How to use lorem ipsum without fooling yourself

Three habits make filler safe enough to keep using.

#Generate three lengths, not one

The single most useful change: never fill a component with one length of filler. Generate a short, a medium, and a deliberately absurd version, and look at all three.

// Three probes per text slot
const probes = {
  short:  8,    // terse — does the box collapse?
  medium: 45,   // typical
  long:   220,  // does it overflow or truncate?
};

A card that looks perfect at 45 words and shatters at 220 is a card you have not designed yet. If you need to hit a specific length, paste the result into the iKit Word & Character Counter to confirm the count before you commit the component to the library.

#Keep headings real, fake the body

Headings, button labels, nav items, and form labels are short, high-variance, and the first things to break. Write those for real from the first wireframe — they take two minutes — and reserve filler for body copy, where length matters more than wording.

This also removes the failure mode Fiedler described: nobody writes a headline to fill a Latin-shaped hole if the headline was real from the start.

#Draft in Markdown, not in the canvas

Structure first, prose later. Writing the page as a heading outline in a Markdown editor before anyone opens a design tool forces the content hierarchy to exist independently of the layout — which is the actual content-first practice that the anti-lorem argument is asking for. Fill the body under each heading with generated filler if you must; the outline is the part that has to be true.

#References

• Which Comes First? Layout or Content? — Susan Farrell, NN/g, 2015; source for the "placeholders only in early low-fi wireframes" guidance and the container-first failure modes.
• A Downside of Fake Copy in UI Prototypes — NN/g video by Page Laubheimer; used for why placeholders break when real content has different characteristics.
• Lorem Ipsum is Killing Your Designs — Kyle Fiedler, Smashing Magazine, 2010; source of the quoted line and the copy-written-to-fit argument.
• Understanding Success Criterion 1.4.8: Visual Presentation — W3C WAI; the 80-character (40 CJK) line-width figure.
• text-wrap — CSS — MDN; balance and pretty behaviour referenced in the CSS sample.

#Related on iKit

• Start with the practical overview of filler text in modern workflows — the umbrella guide covering what lorem ipsum is, how much a mockup needs, and where it goes wrong.
• Read the case against filler, argued properly — the counterweight to this post: exactly what placeholder text conceals during a design review.
• Trace the Latin back to Cicero and a 1960s type catalogue — why the words are semi-Latin nonsense in the first place, with the real paper trail.
• See how the generator itself works — the word bank and sentence rules behind every "generate 5 paragraphs" button.
• Test your layout against German before you localise — the expansion problem Latin filler will never show you.
• Swap Latin for themed filler when word shape matters — when Bacon, Cat, or Hipster Ipsum beats the classic.
• Generate markup-ready filler for HTML prototypes — Emmet abbreviations, the right tag per block, and the lang trap.
• Fill a README or docs page without breaking the renderer — which Markdown blocks to fill and which characters quietly become syntax.