The real origin of lorem ipsum
"Lorem ipsum dolor sit amet" is not nonsense. It's a scrambled excerpt from a real Latin text: Cicero's De Finibus Bonorum et Malorum ("On the Extremes of Good and Evil"), written in 45 BCE. The canonical starting words come from section 1.10.32, where Cicero is explaining that no one loves pain for its own sake — the line being garbled is "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet...".
An unknown typesetter in the 1500s scrambled that passage and used it as filler to show off a specimen book. The earliest documented modern use was on Letraset dry-transfer sheets in the 1960s, and when Aldus PageMaker shipped with lorem ipsum built in in 1985, it became the default placeholder for the desktop publishing era. Every design tool since has inherited it by convention.
Why Latin? Because it's familiar enough to feel like real text (so designers can judge how a paragraph will look) but strange enough that readers won't get distracted trying to read it. English placeholder pulls the eye toward the meaning; Latin lets the eye judge the shape.
When to use lorem ipsum — and when not to
Placeholder text is a tool, not a default. It fits some situations and hurts others:
- Use lorem ipsum when you're evaluating layout, typography, line length, and visual hierarchy. The goal is to see how a paragraph block looks, not how it reads.
- Use realistic content as soon as you're testing the actual product experience. A sign-up form with "Lorem ipsum dolor" as a field label looks fine to a designer and baffling to a user tester. Real copy surfaces real problems earlier.
- Never ship lorem ipsum to production. Every designer has a story about a site that went live with "Lorem ipsum" headings still in place. Run a string search for
lorembefore every deploy.
For anything content-strategic — hero headlines, CTA buttons, form labels, error messages — skip lorem ipsum entirely. Those micro-copy decisions are half the product, and placeholder text hides that work.
How much to generate
There are no absolute rules, but these defaults work for most design tasks:
- Headlines and CTA labels: 2–6 words. Generate a word count and pick what fits. Real marketing copy is almost always shorter than your lorem ipsum.
- Intro paragraphs and feature descriptions: 30–60 words (roughly 3–6 sentences). That's the length most people will actually read before skimming.
- Long-form content blocks (blog posts, docs): 3–8 paragraphs. More than that and you're stress-testing scroll behaviour rather than layout.
- Single-line placeholders (inputs, tooltips): 5–12 words. Enough to see typography, short enough to not overflow.
A quick trick: generate slightly more than you think you need, then trim in the design file. It's faster than generating twice.
Themed ipsum generators — when to skip them
A growing ecosystem of joke "ipsum" generators exists — Bacon Ipsum, Hipster Ipsum, Cupcake Ipsum, and dozens more. They're fun, but they're a different tool. The whole point of lorem ipsum is that readers don't try to read it. Themed ipsum is readable, which means your client will start focusing on the content instead of the design.
Two cases where themed ipsum does work:
- Internal design reviews where a joke ipsum will make the team smile without affecting how seriously the design gets critiqued.
- Marketing assets for light-hearted brands where themed filler hints at brand voice — food sites using Bacon Ipsum, for example.
For everything else, plain lorem ipsum is still the safest choice. Its strangeness is a feature.
Related text tools on CodeBoxTools
- Word & Character Counter — paste generated text back in to confirm the count matches what your CMS wants.
- Slug Generator — turn a working title into a URL-safe slug while you're prototyping.
- Case Converter — switch placeholder headings between Title Case, UPPERCASE, and sentence case in one click.
- Markdown Preview — drop lorem ipsum into a markdown block to see how formatting will render.