Empty boxes start the wrong conversation
A blank card in a mockup looks unfinished. A card filled with “Welcome to our platform” looks like a slogan waiting for a rewrite. Stakeholders then argue about wording while line length, heading scale, and image crop go unreviewed.
Latin placeholder occupies the same space as a paragraph without handing anyone a sentence to edit. Eyes stay on the grid.
Set the unit on the left, set the count, pick an export. The batch builds in the browser. Nothing is uploaded to Toolexe.
The opening line you already know
Lorem ipsum dolor sit amet is a scrambled slice of Cicero’s De Finibus Bonorum et Malorum, written around 45 BC. Printers kept a jumbled version in type cases for centuries because the letter mix looks like European language. Readers stop hunting for meaning.
Toggle the classic opening on if you want reviewers to recognize the block as dummy copy at a glance. Turn the toggle off when you are testing whether a layout still reads as “content” without the famous first words.
Limit of this generator: output is pseudo-Latin from a word bank, not a reprint of the 1914 Loeb chunk. Sentence grammar wobbles. Do not send the result to a translator. Do not drop the result into a legal footer. Hire a writer for those jobs. For a homepage mockup due tonight, the trade is correct.
English dummy copy starts a review you did not ask for
Clients read English. They will. “Your team deserves better tools” in a wireframe becomes a copy session before anyone looks at spacing.
Latin skips the detour. Use English filler only when you need to test hyphenation, Flesch scores, or how a real sentence wraps in a narrow column. For readable English on purpose, use the random paragraph generator instead. Keep this page for silence.
Pick the hole, then the unit
Count without a unit is guesswork. A “5” of words is a chip label. A “5” of paragraphs is an article body.
- Paragraphs
- Article bodies, card stacks, CMS seeds. Each block is a few sentences with a blank line between them.
- Sentences
- Pull quotes, alerts, captions, testimonial slots. One thought per line of output.
- Words
- Tags, badges, nav labels, button text. Short strings, no punctuation beyond the bank.
- Lists
- Feature bullets without inventing product claims. HTML export wraps these in
<ul>.
| Layout job | Unit | Count |
|---|---|---|
| Marketing hero | Sentences | 1–2 |
| Blog card excerpt | Sentences | 2–3 |
| Blog post body | Paragraphs | 4–8 |
| Product feature list | Lists | 5–7 |
| Settings help slot | Sentences | 1 |
| Button or chip label | Words | 2–4 |
| CMS JSON seed | Paragraphs + JSON | 3–5 |
The first batch already looks too long for a card? Drop the count before you copy. Regenerating with a smaller number is faster than trimming in Figma.
What each export writes
Plain text is the default. Line breaks sit between paragraphs. Paste into any editor.
HTML wraps each paragraph in a <p> tag. List mode builds a <ul> with <li> items. Sentences and words stay unwrapped because no single tag fits every slot.
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit.</p><p>Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</p>JSON returns { "paragraphs": [...] } in paragraph mode, or { "text": "..." } for the other units. Useful for API fixtures. Not a schema you should ship as production content.
Reading time on dummy text is a fake signal
The stats row estimates minutes at 200 words per minute. Nobody reads Lorem. Treat the number as a length proxy for long-form templates, not a claim about user attention.
Need a real estimate on finished copy? Paste the draft into the reading time calculator. Chasing a character budget on the block you generated? Use the word counter.
The cap at 100 units
The slider stops at 100. Older phones slow down past a few dozen paragraphs because the whole batch lives in one textarea. For a book-length dummy, generate in batches and concatenate locally.
The mistake that ships
Lipsum left in production is a ranking problem and a trust problem. Search engines index whatever you publish. Users bounce. Before you ship, search the repo for Lorem ipsum. Replace every hit.
- Theme previews often keep filler in default widgets. Strip those before a store listing.
- Staging databases seed posts with Latin. Do not clone staging into production without a copy pass.
- HTML export adds tags. A later whitespace pass with remove extra spaces cleans awkward gaps.
Need title case on a word-mode label? Run the string through the case converter. Duplicate bullets after a few regenerations? The duplicate line remover collapses repeats before you paste into a CMS.
Nothing persists in the tab
Refresh and the last batch is gone unless you copied it. Fine for mockups. Wrong if you expected a shared seed file to survive a reload. Save the JSON export to disk when the fixture has to last.
