Lorem Ipsum Generator

How it works

The generator draws from the 63-word vocabulary of the traditional passage using a small deterministic random-number generator (mulberry32). The seed starts at one and the Regenerate button increments it, which is the entire trick behind reproducibility: the "randomness" is a fixed function of the seed, so variation N is the same text on every machine, every visit.

Sentences are built six to fourteen words long, with no word repeated back-to-back. Sentences of nine words or more receive a comma clause at a varying position — a small detail that does outsized work, because commas are what give prose its visual rhythm and their absence is what makes cheap filler look like a ransom note. Paragraphs collect four to seven sentences. The first sentence is swapped for the canonical opening when the classic switch is on.

Word mode bypasses sentence construction entirely and emits bare lowercase words, exactly as many as requested.

The counts are exact, not approximate

Asking for 40 words gets you 40 words, not "about a paragraph". This matters more than it seems: character and word limits are real constraints in the layouts being mocked — a card that must survive a 40-word description should be tested with exactly 40 words, and a headline slot with twelve. Pair this generator with the word counter to verify what a layout actually receives.

When you'd use this

Filling a page mockup before the copy exists. Stress-testing a component with one paragraph, then seven. Populating a staging CMS with body text that nobody will mistake for publishable. Supplying printable filler for a typography specimen. Any moment a layout needs words whose only job is to occupy space convincingly.

When Latin filler tests the wrong thing

Lorem ipsum is good at one job — occupying space without being read — and there are layouts where that is exactly the wrong property.

The word-length distribution is not English. Latin runs long and even, so a column of lorem sets into tidy blocks with few awkward gaps. Real English is lumpier: short function words, the occasional very long noun, and the ragged edges those produce. A justified column that looks immaculate in Latin can open rivers of white space once actual copy arrives.

It also has no capitals mid-sentence, no numerals, no currency symbols, no URLs and no email addresses — all the things that break line-wrapping in practice. A card component tested only with lorem has never seen a forty-character unbroken string, which is the input that actually overflows it.

And it is Latin script only. If the interface will ever carry German compounds, Arabic or Hebrew right-to-left text, or the taller line boxes that Devanagari and Thai need, lorem ipsum will not reveal a single one of those problems. Test those with text in those languages, early, because the fixes are structural.

Use lorem where the point is to judge rhythm and density without being distracted by meaning — that is a real benefit, and it is why designers still reach for it. Switch to realistic copy before deciding anything is finished.

Never let it reach production

Placeholder text escaping into a live product is common enough to be a genre. It has appeared in shipped apps, printed annual reports, hotel signage and at least one national newspaper, and the reason is always the same: it looks plausible enough that nobody reads it during review.

Two habits prevent it. Make the filler findable — a grep for lorem across the repository before any release costs nothing and catches every instance. And keep placeholder copy out of anything a build can consume, so it lives in a mock file or a fixture rather than a template that might ship with a default.

The higher-risk places are the ones nobody looks at: meta descriptions, alt text, empty-state messages, transactional email templates, error pages and the seed data behind a demo account. All of them are rendered by machines or seen rarely, and all of them are read by somebody eventually.

The deterministic seeding here helps with the opposite problem — a screenshot test that must produce identical output on every run — but it offers no protection against shipping. That part is a checklist item, not a feature.