Lorem Ipsum History and Modern Use
Lipsum looks like Latin but is corrupted Cicero. Learn its history, why it helps focus on layout, and when real content should replace it.
Produces placeholder paragraphs, sentences, or exact word counts for layout mockups, all client-side.
generate lorem ipsum placeholder text →Where lorem ipsum came from
The source is real and it is Latin. Lorem ipsum derives from sections 1.10.32 and 1.10.33 of De finibus bonorum et malorum, a treatise on ethics that Cicero wrote in 45 BC. The passage begins Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, and the modern placeholder begins with a truncation of dolorem ipsum, dropping the initial do. That is the whole reason it sounds like nonsense: it starts in the middle of a word. The passage was identified by Richard McClintock, a Latin scholar, who traced the rare word consectetur through classical texts; he connected it to Cicero sometime before 1982 and published the finding in 1994, correcting an earlier claim that the text had no source. A common story attributes the scrambling to an anonymous printer in the 1500s making a type specimen, and McClintock himself wrote that way. Later work matched the Letraset text against a specific 1914 Loeb Classical Library edition, page 36 onward, moving the likely physical origin to the twentieth century.
Why designers still use it
The reason is attention. Readable text in a mockup pulls the review toward wording, tone and phrasing, and away from hierarchy, alignment and line length, which are what a layout review is for. Lorem ipsum has a roughly normal distribution of letter shapes, so it exercises ragging, word spacing and typographic texture the way real text would, without being interpretable. That makes it right for the early question of whether a composition works, and for visual regression tests in component libraries, where you want stable deterministic strings rather than seeded personal data. It also reveals problems that only appear under load: a widow on the last line, a heading that wraps to three lines at one breakpoint, a card whose body overflows its fixed height. Real prose sometimes hides these because its words happen to fall well, and lorem ipsum does not, since it is not shaped to your content. The generator here builds sentences of six to fourteen words from a fixed word list, so the texture stays even.
When placeholder text misleads
The failure mode is testing with the wrong length and discovering the problem in production. English averages roughly 4.7 characters per word, but translated text is frequently longer, and compound languages expand the most. A headline mocked with three words may be twelve words in the target language and wrap unexpectedly, pushing everything below it down a line and breaking a fixed-height hero. The same applies to content: a product name mocked as lorem ipsum has no digits, no units and no capitalisation pattern, so a card that looks balanced with placeholder text can overflow with a real long product name, and a price rendered in a different numeral system may not fit the column. Numbers, dates, currency symbols and proper nouns have a different visual rhythm from Latin filler, which is the most likely reason a component looks fine in review and misbehaves with real data. If you are testing a truncation rule, lorem ipsum will not tell you whether it cuts mid-word, because its word boundaries are arbitrary. Switch to representative real content before visual QA, and certainly before anything ships.
Better placeholder strategies
Four approaches cover most of what lorem ipsum is used for. One, a content matrix: take the real headings from the outline and pair each with an approximate length range, so the structure under test is real and only the wording is synthetic. Two, named slots, written as [Product name], [Price $19.99], [Call to action], which survive into the prototype and make it obvious at review time that a real string belongs there. Three, pseudo-localisation for anything shipping internationally. Replace characters with visually heavier equivalents, so š becomes s-with-caron and Ā becomes A-with-macron, which both expands the string and adds the visual weight a real accented script will have. Running that through your layout catches the overflow that clean ASCII hides. Four, stress testing with deliberately extreme values, a title at its maximum allowed length and a price with an unusually large number, because the boundary case is where a fixed-height component breaks and the happy path rarely is. Keep lorem ipsum for purely visual checks where readable content would be a distraction.
Generating and checking placeholder text
The generator here offers three units. By paragraphs builds four to seven sentences of six to fourteen words each; by sentences gives a count of sentences; by words gives an exact count, which is the most useful mode when matching a known budget. The count runs from 1 to 100, and the classic opening is prepended by default so the first paragraph starts with the familiar phrase. Set it to 5 paragraphs for a standard page mockup, or switch to words and ask for 40 to fill a single card body. Then verify rather than assume: the word counter gives you the real count, which is how you catch the case where you asked for 600 words and got 850, or where a character budget matters more than a word budget. For a table, generate varied name-like strings rather than repeating one, since repetition hides wrapping problems that distinct values expose. Combine it with the case converter to test a heading in sentence case, title case and uppercase, where truncation and letter-spacing regressions tend to appear. All of it runs in the browser, so a long generation works with the network off.
A short timeline
45 BC, Cicero writes De finibus bonorum et malorum, and the source passage exists in the sections later sampled. Somewhere before 1982, and probably in the twentieth century rather than the 1500s as often repeated, someone extracts the passage and scrambles it for a type specimen. The 1960s bring the popular version, when Letraset publishes transfer sheets carrying the text and James Mosley, librarian at the St Bride Printing Library, supplies the passage to them. The mid-1980s take it digital, as Aldus uses it in PageMaker templates, after which word processors and then web editors adopt it by default. The 1990s establish the provenance, with McClintock's identification of Cicero published in 1994. Since then it has been a default in layout tools and content systems, and the reason has not changed: it occupies space convincingly without being readable enough to distract from the layout being reviewed. Knowing the history is useful mainly because it defuses the romantic version. It is a twentieth-century typesetting artefact built from genuinely ancient words, and using it deliberately rather than by default is what keeps it useful.