Lorem Ipsum Generator
Generate lorem ipsum online by paragraph, sentence, or word target with tone, case, wrap, seed, metrics, and chart exports for repeatable layout testing.Lorem Ipsum Summary
| # | Preview | Sentences | Words | Chars | Copy |
|---|---|---|---|---|---|
| {{ p.index }} | {{ p.preview }} | {{ p.sentenceCount }} | {{ p.wordCount }} | {{ p.charCount }} |
| Word | Count | Share | Copy |
|---|---|---|---|
| {{ row.word }} | {{ row.count }} | {{ row.share }} |
Introduction:
Lorem ipsum is pseudo-Latin placeholder text used when a layout needs realistic text shape before final copy is ready. Its value is visual and practical: paragraph weight, word length, line breaks, and block rhythm can be tested without asking reviewers to debate unfinished wording.
The familiar opening comes from an altered tradition tied to Cicero's De finibus bonorum et malorum, but modern lorem ipsum is not meant to be read as classical Latin. Words are changed, shortened, repeated, and mixed so the text looks language-like while staying mostly meaningless. That makes it useful for mockups, typesetting, component states, CMS fixtures, documentation shells, and slide layouts where text mass matters more than message.
Good placeholder text should be obvious enough to prevent accidental publishing and neutral enough to keep attention on structure. It helps a team see whether a card can hold a paragraph, whether a table cell wraps too soon, whether a content block needs a shorter heading, or whether repeated samples make a page look artificially tidy.
Real copy should replace filler as soon as the content task becomes clear. Placeholder text cannot test tone, legal meaning, accessibility wording, search intent, product promises, or the way a reader responds to actual instructions. It is a layout aid, not a substitute for content design.
Technical Details:
Placeholder generation is a controlled sampling process. A length target decides when generation stops, sentence and word ranges shape rhythm, and weighted word pools decide which terms appear most often. The same paragraph count can therefore feel compact, airy, classic, or product-like depending on the ranges and vocabulary weights.
The page supports three stop rules. Paragraph mode creates the requested number of paragraphs. Sentence mode keeps adding paragraph groups until the requested sentence total is reached. Word mode treats the amount as a word budget after each generated sentence, so a final sentence may shrink to land on the remaining count. One exception is the classic opener: when it is enabled, the first sentence is the familiar eight-word opener, even if a very small word target was entered.
Generated wording is intentionally mechanical. The text is useful because it has line length, punctuation, repeated terms, case, and markup shape, not because it carries meaning. A seed changes the random source from fresh randomness to a repeatable sequence, which makes the same settings recreate the same sample for screenshots, QA notes, or design review files.
Generation Rule Core:
| Mode or rule | How it behaves | Important boundary |
|---|---|---|
| Paragraph target | Builds the requested number of paragraph blocks. | Each paragraph uses the active sentence and word ranges. |
| Sentence target | Builds paragraphs until the total sentence count is reached. | The last paragraph can contain fewer sentences than the maximum range. |
| Word target | Uses the requested amount as a remaining word budget. | The classic opener can exceed tiny word budgets because it is fixed at eight words. |
| Sentence range | Accepts whole-number minimum and maximum sentence counts per paragraph. | Values above 24 sentences per paragraph trigger an error until corrected. |
| Word range | Accepts whole-number minimum and maximum words per generated sentence. | Values above 36 words per sentence trigger an error until corrected. |
The word picker uses weighted bands. Topic words, custom vocabulary, tone words, and the Latin or English fallback lists do not have equal influence. The first matching band wins, so the same custom word list can feel stronger when no topic hints are present.
| Word source | Selection behavior | Practical effect |
|---|---|---|
| Topic focus | Can take the first 30 percent of random picks when topic terms exist. | Lightly steers text toward a subject such as onboarding or API docs. |
| Custom vocabulary | Can take picks below 55 percent when custom words exist and topic did not already win. | Gives user-provided words a visible presence in mockup copy. |
| Tone words | Can take picks below 70 percent after topic and custom bands are checked. | Adds classic, friendly, playful, or technical flavor without creating real prose. |
| Latin blend | Chooses between the Latin-style fallback list and the modern English fallback list. | Moves the remaining text toward a traditional or contemporary placeholder feel. |
| Randomness | Changes comma placement and sentence-ending variety. | Raises or lowers punctuation texture while keeping the main length rule intact. |
Case is applied after words are chosen, and wrap style is applied after paragraphs are built. HTML paragraph output escapes generated text before adding paragraph tags, so topic terms and custom vocabulary are treated as text rather than executable markup.
Everyday Use & Decision Guide:
Begin with the constraint you need to test. Use paragraph focus when a page needs a fixed number of content blocks. Use sentence focus when the pacing across cards, callouts, or article sections matters. Use word focus when a component has a tight copy budget and overflow is the risk you are checking.
For early wireframes, leave the classic opener enabled and use a higher Latin blend so reviewers see unmistakable placeholder text. For product screens or documentation shells, lower the Latin blend and add a few topic or custom words. That gives the copy enough subject shape to test labels and spacing without pretending the draft is final.
- Use narrow sentence and word ranges for clean grid checks, table cells, and repeatable component states.
- Use wider ranges when you want a layout to face uneven paragraph rhythm.
- Use sentence case for normal body text, title case for heading tests, and uppercase only when the target surface really uses all caps.
- Use a seed before taking screenshots or sharing QA notes so the same text can be recreated later.
The most common misread is treating styled filler as content quality. A technical tone with API-related vocabulary can make a documentation mockup look convincing, but the output still has no factual argument, task flow, or editorial intent. Once a page needs wording decisions, replace filler with real copy and rerun the layout check with actual sentences.
Before copying a result, check the summary badges and the paragraph metrics. The badges confirm total paragraphs, sentences, words, reading-time estimate, case, and wrap style. The table shows whether one paragraph is longer than the rest, which is often the part that breaks a card, column, or fixed-height preview.
Step-by-Step Guide:
Use the controls in this order when you need a predictable placeholder sample.
- Choose
Output focusasParagraphs,Sentences, orWord count, then setAmount. The summary headline should reflect that target after generation refreshes. - Set
Sentences per paragraphandWords per sentence. If an error appears for the 24-sentence or 36-word cap, lower the maximum value before trusting the preview. - Pick
Tone,Case style, andWrap style. Use theText Previewtab to confirm the rendered shape and theMarkuptab to inspect the copy-ready text. - Open
Advancedwhen the default sample is too generic. AddTopic focusterms, add shortCustom vocabulary, tuneRandomness, and adjustLatin blend. - Turn
Start with classicon when the sample must begin with the recognizable opener. Turn it off for tiny word budgets or when you want all sentences to follow the requested word range. - Enter a
Seedbefore sharing the result. Matching settings and seed should recreate the same paragraph, vocabulary, and sentence-length pattern. - Review
Paragraph Metrics,Vocabulary,Sentence Lengths, andJSONif the sample is going into QA notes, a fixture file, or a repeatable design handoff.
Interpreting Results:
The generated text is successful when the shape matches the test, not when the words sound polished. Paragraph count, sentence count, word count, character count, and sentence lengths tell you whether the sample stresses the same spaces your real content will occupy.
| Result area | What to check | What not to overread |
|---|---|---|
| Summary badges | Total paragraphs, sentences, words, read estimate, case, and wrap style. | The read estimate is pacing only, not a readability score. |
| Paragraph Metrics | Paragraph-level sentence, word, and character counts. | A balanced sample does not prove final content will stay balanced. |
| Vocabulary | Top words, counts, and percentage share across the generated text. | Frequent topic terms are weighting evidence, not editorial quality. |
| Sentence Lengths | Words per sentence as a bar chart and CSV rows. | A varied chart shows rhythm, not meaning or clarity. |
| JSON | Inputs, summary values, and paragraph objects for repeatable notes. | It records the sample settings; it does not validate the future copy. |
If the output looks too convincing, make the placeholder cue stronger by raising Latin blend, enabling the classic opener, or avoiding real product claims in custom vocabulary. If it looks too artificial for a realistic layout test, lower Latin blend, add a seed, and use topic terms that match the screen without becoming final messaging.
Worked Examples:
Dashboard card review
A designer needs three blocks for a dashboard review. They set Output focus to Paragraphs, Amount to 3, sentence range to 2 to 3, word range to 6 to 10, and keep sentence case. The summary should show three paragraphs, while Paragraph Metrics reveals whether any card receives a much longer paragraph than the others.
Documentation shell with repeatable wording
A technical writer is building a documentation page before the real tutorial is approved. They choose sentence focus with Amount set to 10, select Technical tone, add topic terms such as schema, release, and latency, then enter the seed docs-alpha. The Vocabulary tab should show those terms or related technical words often enough to make the mockup resemble a docs page, and the seed lets the writer recreate the same result after a design revision.
Small word budget edge case
A component has room for only 6 words. With Word count selected and Start with classic enabled, the first generated sentence can still be the eight-word classic opener, so the summary may exceed the requested budget. Turning the classic opener off lets word mode use the remaining budget directly and makes the summary easier to compare against the component limit.
Validation recovery
A tester enters 40 as the maximum words per sentence and the result clears with an error. Reducing Words per sentence maximum to 36 or lower restores generation. After the preview returns, the Sentence Lengths chart and chart CSV can confirm that generated sentence sizes stay within the corrected range.
FAQ:
Is the generated text real Latin?
No. The opener is recognizable, and the fallback pool includes Latin-style words, but the output is mixed filler text rather than a reliable Latin passage or translation.
Why did word count mode exceed my amount?
The classic opener is fixed at eight words. If Start with classic is on and the requested word amount is smaller than that, the opener can exceed the target. Turn the switch off for very small budgets.
What does the seed control?
The seed makes the random sequence repeatable. Keep the same seed and settings when you need the same paragraphs, word counts, vocabulary mix, and chart pattern later.
Can custom vocabulary add HTML to the output?
No. HTML paragraph wrap escapes generated text before adding paragraph tags, so custom terms are treated as visible text instead of markup.
Why did the result disappear after I changed a range?
The generator clears output when validation errors are present. Keep sentences per paragraph at 24 or lower, words per sentence at 36 or lower, and amount at 1 or higher.
Are topic terms and custom words sent to a text service?
The generation itself runs in the browser, and there is no tool-specific upload step for topic or custom vocabulary. You choose what to copy, download, or include in exported result files.
Glossary:
- Placeholder text
- Temporary copy used to test layout, spacing, and content structure before final wording is ready.
- Pseudo-Latin
- Text that resembles Latin visually but is not meant to be read as a correct Latin passage.
- Latin blend
- The setting that shifts fallback word choices toward Latin-style terms or modern English filler words.
- Seed
- A repeatable starting value that recreates the same random sequence when other settings match.
- Wrap style
- The output format used for the generated text, such as plain paragraphs, HTML paragraphs, Markdown paragraphs, or list items.
- Vocabulary share
- The percentage of generated words represented by a single word in the vocabulary table.
References:
- Microsoft Word sample-text article, Microsoft Support.
- Figma lorem ipsum generator, Figma.
- Wireframing with real content article, Adobe, January 27, 2022.
- Lorem ipsum overview, Wikipedia.