Lorem Ipsum Generator

What lorem ipsum is

Lorem ipsum is deliberately meaningless text used to stand in for real copy while a design is being built. Its words are corrupted Latin, and they come from a real book: Cicero's De Finibus Bonorum et Malorum, "On the Ends of Good and Evil", written in 45 BC. The famous opening is a fragment of the phrase neque porro quisquam est qui dolorem ipsum quia dolor sit amet — "nor is there anyone who loves pain itself because it is pain" — with the first two syllables lopped off, which is why the passage begins mid-word at lorem.

The corruption was not an accident of the internet age. The text has been used by printers since at least the 1500s, when a compositor scrambled a page of Cicero to make a specimen sheet showing a typeface at length. It reached modern designers through Letraset dry-transfer lettering sheets in the 1960s and 70s, then through desktop publishing software, which shipped it as sample copy. By the time the web arrived it was already the default answer to "what do we put in the box for now?"

Its usefulness comes from one property: it reads like language without being language. The word lengths and sentence rhythms are close enough to English or another Latin-script language that a block of it produces a realistic texture on the page, but no one can read it, so no one starts editing it. That is exactly what you want when the question on the table is "does this column feel too wide?" and not "should this say customers or clients?"

What this generator gives you

• Three units. Paragraphs, sentences or words. Word mode is exact — ask for 250 words and you get 250 — which is what you need when you are filling a field with a documented character or word limit.
• Three filler styles. The classic Latin text, a plain-English filler built from ordinary short words, and an API-flavoured filler made of the vocabulary that actually appears in developer documentation.
• The traditional opening, on or off. Some teams want every mock to start with Lorem ipsum dolor sit amet because it is instantly recognisable as placeholder; others want it off so the text does not look copy-pasted.
• HTML output, wrapping each paragraph in <p> and </p> so you can paste straight into a template.
• Copy to clipboard, and a shuffle button for a different sample at the same settings.

Why designers and developers use placeholder text

The honest reason is scheduling. Copy is usually written late, by someone who is not in the room when the layout is made, and waiting for it would stop the work. But there are real craft reasons too, and they are worth separating from the excuse.

It isolates the visual problem. Typography is a set of relationships — line length, leading, size, contrast, rhythm — and you can only judge them at full length. A heading looks fine over two words and falls apart over twelve. A measure that feels generous at 45 characters becomes a chore at 90. Filler gives you the volume you need to see those relationships without any of the content becoming a topic of conversation.

It stops the wrong review. Show a stakeholder a layout with real draft copy and the feedback will be about the copy, every time. It is the most legible surface in the artefact, and people respond to what they can read. Lorem ipsum is a polite way of saying "this part is not what we are discussing today".

It exercises the system. Front-end work needs bulk text to check overflow, scroll behaviour, sticky headers, truncation and the way a component behaves when the content is longer than the designer imagined. Generating a hundred paragraphs takes a second and immediately shows whether a layout collapses under weight.

It fills fixtures. In API work, filler is how you build request bodies for load and validation testing: strings that are exactly at, just under and just over a documented field limit. Pair this generator with the API tester to see what your endpoint actually does when a description field receives 5,000 characters — the answer should be 422 Unprocessable Content or 413 Content Too Large with a helpful message, and it is surprisingly often a 500 instead.

The real argument against lorem ipsum

Now the other side, because it is stronger than most generator pages admit. Placeholder text hides content-fit problems. Every property that makes lorem ipsum good for judging typography also makes it dishonest about content.

Look at what filler never contains. No proper nouns, so you never discover that a customer's company name is 38 characters long and breaks the card. No numbers or currency, so you never see how a price sits next to a label. No hyperlinks in the middle of a sentence, so you never notice the colour clash. No short paragraphs, no single-line entries, no empty states, no error messages, no legal disclaimer nobody wants but everyone must ship. Word lengths are evenly distributed, so no line ever has to break awkwardly. Every paragraph is roughly the same size, so the page has a comfortable regular rhythm that real writing simply does not have.

The result is a design that looks resolved and then falls apart the day content arrives. Anyone who has shipped a marketing site knows the sequence: the hero looked perfect with two lines of Latin, and the real headline is either four words or twenty-six, and neither fits. This is the core of the content-first argument that has been made for years by content strategists and information architects: design is a container for meaning, and a container designed without knowing what goes in it is a guess.

So the practical position, and the one worth adopting, is this:

• Use filler for typographic exploration, early, when you genuinely are judging measure and rhythm and nothing else.
• Switch to realistic copy before anything gets approved. Realistic does not mean final — a rough draft written by whoever knows the subject is far more useful than perfect Latin.
• Test the extremes deliberately. The shortest plausible string, the longest, an empty value, and one containing an emoji, an accented character and a right-to-left script. Those four cases catch more layout bugs than a hundred paragraphs of even Latin.
• Never let it ship. Search your build output for ipsum before release. It escapes into production more often than anyone admits, and a page of Latin is worse than an empty page because it looks intentional.

That last point is also why this tool offers two non-Latin styles. Plain-English filler keeps the "do not read me" quality of lorem ipsum while producing word shapes and sentence lengths closer to what your real audience will read, which makes measure decisions more trustworthy. The API-flavoured style goes further and uses the actual vocabulary of developer documentation, so a mocked-up docs page or changelog looks approximately like the thing it will become.

Practical notes on units and HTML output

Word mode is exact. If you ask for 40 words you get 40 words, counted by whitespace. That matters when you are checking a field with a stated limit, or building a test that asserts truncation at a boundary. Punctuation attaches to words, so a trailing full stop does not change the count.

Sentence and paragraph modes vary deliberately. Each sentence gets between four and fourteen words and each paragraph between three and seven sentences, so a block of output has an uneven shape instead of a mechanical one. That puts a typical paragraph somewhere around 30 to 90 words. If you need a precise total, generate in word mode and split it yourself.

HTML mode wraps each paragraph in <p>…</p>, one per line, ready to paste into a template. It emits nothing else — no classes, no attributes, no wrapper div — because placeholder markup that carries someone else's class names is a small trap waiting to be forgotten in a commit. If you need the text inside a JSON fixture rather than a template, generate plain text and escape it with the JSON formatter, which will also tell you immediately if a stray quote has broken the document.

A note on encoding, since it catches people. Placeholder text is plain ASCII, which means it will never reveal a UTF-8 handling bug in your stack. Real copy has curly quotes, em dashes, accented names and emoji, all of which travel through a different code path. When you move from filler to real content, that is the moment character-set problems appear — a good reason to check your Content-Type header declares charset=utf-8, and to run a suspicious string through the URL encoder or the HTML encoder to see exactly which bytes you are dealing with.

Frequently asked questions

Related tools and reference