Lorem ipsum is filler text used in design mockups when the actual copy isn’t ready. It’s pseudo-Latin: real words from Cicero’s De finibus bonorum et malorum (45 BC), shuffled and corrupted so the result is legible-looking but semantically empty. The tool above generates lorem ipsum in your browser; nothing leaves your machine.
What the text actually is
The first line of every lorem ipsum block is recognizable:
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
tempor incididunt ut labore et dolore magna aliqua.
This is a partial corruption of a sentence from Cicero’s section 1.10.32:
Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit…
(“Nor is there anyone who loves pain itself, who seeks after it and wants to have it, simply because it is pain…”)
A 16th-century typesetter — the popular but unconfirmed origin story — scrambled the passage to produce a Latin-looking specimen that wouldn’t distract from the typesetting itself. The opening words dolorem ipsum got cut to lorem ipsum, the first word lost its do- prefix, and the result has been used in printer-and-designer practice ever since.
Why filler text exists
The point of filler text is to let a designer evaluate the layout — typography, spacing, line length, paragraph rhythm — without the reader’s eye getting hooked on meaning. Real copy makes you read; pseudo-Latin lets you see the shape. This is the only legitimate use of lorem ipsum.
Why filler text hurts design
- It hides content problems. A heading that doesn’t fit the column. A “card title” that wraps to three lines. A button with copy that’s longer than the design accounted for. Lorem ipsum’s word lengths and sentence rhythms are not your product’s; the layout will need rework when real copy lands.
- It hides UX problems. Empty states, error messages, button labels — these have to read as English to be evaluated. “Lorem ipsum” in an error toast looks fine; “Your payment couldn’t be processed because the card on file is expired” might not fit.
- It hides hierarchy problems. When all the text is meaningless, every block feels equally important. Real copy reveals which sections need to be smaller, denser, or removed.
The professional advice from content-design folks: replace lorem ipsum with real content (or realistic placeholder content that resembles the actual product) as early as possible in the design process. Use lorem ipsum for the typography phase, not the product-design phase.
Variants you’ll see
| Variant | Source / character |
|---|---|
| Lorem ipsum (classic) | Scrambled Cicero. The default. |
| Cupcake ipsum | Bakery-themed nonsense. “Tiramisu lemon drops gummies sweet roll.” |
| Hipster ipsum | Williamsburg parody. “Locavore artisan pour-over kombucha.” |
| Bacon ipsum | ”Bacon ipsum dolor amet ribeye chuck pork belly.” |
| Corporate ipsum | Buzzword soup. “Synergize cross-functional deliverables.” |
| Lorem pixelsum / image placeholders | Not text — the equivalent for images. Tools like placehold.co serve gray rectangles. |
The themed variants are funny once and dilute the “neutral filler” purpose. Stick to classic lorem ipsum unless there’s a reason.
What “ipsum” generators control
Most generators expose:
- Quantity. Words, sentences, or paragraphs. The tool above counts in sentences (3, 5, 10 or 20) and returns them as one paragraph.
- Start with
Lorem ipsum. A toggle. Some designers want the recognizable opening; some want every paragraph to feel mid-stream. - Average sentence and paragraph length. Tighter for body copy; looser for long-form layouts.
- HTML-wrapped output. Optional
<p>tags around each paragraph for paste-into-content-fields use.
The text doesn’t mean anything, so the controls are about shape, not substance.
Common pitfalls
- Shipping lorem ipsum to production. It happens. Search the codebase for
lorembefore deploys. Add a CI check if it keeps slipping through. - Translating lorem ipsum. It’s not Latin, not really. Translating it produces nonsense in the target language. For locale layout testing, use a string of the target language’s average word length and character set, not translated lorem ipsum.
- Using lorem ipsum for accessibility testing. Screen readers will pronounce it (badly), which doesn’t reveal anything useful about how real content sounds. Use real copy or realistic placeholder copy when testing assistive tech.
- Treating word count as semantically meaningful. “I need ~50 words of body copy” is the right framing. “I need a paragraph that’s exactly 287 characters” is over-specifying — design for content ranges, not exact lengths.
For other text-shaping tools, see word counter and character counter.