Lorem Ipsum Generator

Where lorem ipsum actually comes from

"Lorem ipsum" is not a made-up language — it is a corrupted fragment of a real Latin text, Cicero's De Finibus Bonorum et Malorum ("On the Ends of Good and Evil"), written in 45 BC. Somewhere in the 1500s, a typesetter scrambled a passage from Section 1.10.32–33 of that text into filler copy for a type specimen book, and the garbled result — missing words, Latin grammar broken by the cuts — is the exact scrambled pool every "lorem ipsum" generator on the web still draws from five centuries later, including this one. The tradition got a second life in the 1960s when Letraset used it on dry-transfer sheets for graphic designers, and again in the 1980s when early desktop publishing software (including early versions of Aldus PageMaker) shipped it as default placeholder text. It has been the default answer to "what goes here before the real copy is written" ever since.

Why designers use Latin-looking nonsense instead of English

The whole point of placeholder text is that a reviewer's eye should judge the layout — column width, line height, font size, how a heading sits above a paragraph — without getting pulled into reading and judging the words themselves. English filler text ("your content goes here") reads as a sentence with meaning, so a reviewer's attention snags on it. Latin that almost nobody reads fluently does the opposite: it has the visual rhythm and letter distribution of real prose (word lengths, punctuation frequency, capital letters at sentence starts) without offering anything to comprehend, so the eye stays on the layout. There's a real accessibility argument against ever shipping it to production, though — a screen reader will read "lorem ipsum dolor sit amet" out loud exactly as if it were real content, and a sighted user who does read Latin, or just reads carefully, will notice nonsense where real copy should be. Placeholder text belongs in a design mockup, never in a live page a real visitor might reach.

Exact counts, not approximate ones

Most lorem generators produce "about" the amount you asked for — five paragraphs come out as five paragraphs of whatever length sentences happened to land at, and a word-count request gets rounded to the nearest sentence boundary. That is a real gap when you need a specific number: testing how a UI handles exactly 500 words, or filling a database column with text that has to land under an exact byte limit. This generator verifies its own output after generating it and shows the achieved figure next to the requested one for every unit at once — words, characters, sentences, paragraphs and bytes — so "500 words" is visibly 500 words, and you can also see how many characters and bytes that same text turned out to be.

Why "bytes" is the unit a developer actually wants

Filling a VARCHAR(255) column or checking against an API payload limit is really a question about bytes, not characters — and for anything outside plain ASCII, those two numbers disagree. "café".length is 4 in JavaScript because .length counts UTF-16 code units, but new TextEncoder().encode("café").length is 5, because é takes two bytes in UTF-8. Classic lorem text is pure ASCII, so the two numbers happen to coincide here, but this tool still computes the byte count the honest way — from TextEncoder, never from .length — so the number is correct by construction rather than correct by coincidence. When a byte cap can't land exactly on a sentence boundary, the achieved-count strip says which rule was applied: cut at the nearest sentence boundary within the limit, or cut exactly at the byte limit when no earlier boundary fit.

Reproducibility, not unpredictability

A placeholder generator has the opposite job to a password generator. A password's entire value comes from being unguessable, which is why the password generator deliberately uses cryptographically secure randomness that can never be replayed. Placeholder text needs the exact reverse property: a designer approves a specific paragraph in a mockup, and that same paragraph needs to come back after a page reload, after sharing a link with a teammate, or a week later when the mockup is revisited. Math.random() output is lost the moment the page reloads, so this generator uses a small, fast, deterministic PRNG (mulberry32) seeded by a number you can see, edit, reroll or share — the same seed always produces the same sequence of text, on any machine, forever. Using cryptographic randomness here would be theatre: nothing about placeholder text is a security boundary, and claiming otherwise would be the same kind of dishonesty as printing a privacy number nobody measured.

Output already wrapped, not a blob you wrap by hand

Most lorem generators hand back one block of text and leave you to wrap it in <p> tags, Markdown bullets or a JSON array yourself. This one emits all four directly: Plain (blank-line-separated paragraphs, or one paragraph per line in single-line mode), HTML (<p> tags, or a <ul> of <li> for the "list" unit), Markdown, and a JSON array of paragraph strings — the shape a mock API response or a fixture file actually wants. Each format has its own copy button so the paste lands ready to use.