What is lorem ipsum and why do designers use it?
Typesetters and UI designers use scrambled Latin placeholder text so stakeholders evaluate visual hierarchy, font weights, and grid spacing instead of editing unfinished copy. Because the word lengths and letter distribution resemble English prose, layouts stay realistic while real content is still being written.
During wireframe reviews, readable English drafts often distract reviewers into debating phrasing before the page structure is settled. Pairing realistic text blocks with W3C WCAG 2.1 Understanding Visual Presentation guidelines lets teams verify comfortable line widths (such as keeping columns under 80 characters) and clean vertical rhythm early.
Every block is generated 100% locally in your browser with zero server calls, so you can test 60 to 75 character column measures, card heights, and typography scales immediately. Once real copy replaces your placeholder blocks, you can check exact character counts and reading time with the Word counter.
| Design component | Recommended Unit | Typical How many count | HTML <p> tags |
|---|---|---|---|
| Hero subheading or card summary | Sentences | 1 to 2 sentences |
Not available |
| Navigation badge or button label | Words | 2 to 5 words |
Not available |
| Blog post or documentation body | Paragraphs | 3 to 6 paragraphs |
Optional (<p> for HTML) |
| Long-form scroll or pagination test | Paragraphs | 15 to 50 paragraphs |
Checked for CMS/HTML |
| Search index or stress test | Words | 1,000 to 10,000 words |
Not available |
Choosing paragraphs, sentences, or words for your mockup
Different UI slots fail in different ways when text is too short or too long. Switching between Paragraphs, Sentences, and Words lets you match the exact shape of headings, cards, and long articles without manually trimming pasted blocks.
Generator limits up to 200 paragraphs or 10,000 words
The How many input enforces safe browser limits of 200 paragraphs, 2,000 sentences, or 10,000 words, clamping out-of-range numbers on blur. Each generated sentence varies naturally from 6 to 15 words with commas added to longer clauses, while each paragraph groups 4 to 7 sentences.
Instead of relying on biased Math.random() loops, randomInt() draws 32-bit integers via rejection sampling over MDN Crypto.getRandomValues() Web API (well within its 64 KB per-call entropy cap) so every vocabulary word and sentence length is equally likely. If you already have Markdown drafts to test instead of Latin, you can strip Markdown syntax into clean plain text before pasting them into your layout.
Controlling the classic Lorem ipsum opening line
When Start with “Lorem ipsum…” is checked, the output begins with the familiar "Lorem ipsum dolor sit amet, consectetur adipiscing elit" phrase so clients recognize immediately that the text is intentional placeholder copy.
Unchecking it starts directly with randomized Latin words, which prevents repetitive cards when populating multi-column grids. In Words mode, choosing fewer than 8 words trims the opening cleanly to match your exact requested word count.
Adding HTML paragraph tags for web templates and CMS blocks
Copying raw multi-paragraph text into an HTML prototype often collapses blank lines into one giant wall of text. Wrapping each block in semantic paragraph tags saves manual markup editing when building static pages, email templates, or CMS seed files.
When the HTML <p> tags option appears
Selecting Paragraphs under Unit reveals the HTML <p> tags checkbox in the toolbar. When checked, every paragraph is wrapped in <p>...</p> tags following the MDN HTML Paragraph (<p>) Element Reference and separated by single newlines for clean source formatting.
Tip: Leave HTML
<p>tags unchecked when pasting into Figma, Sketch, Adobe XD, or Google Docs, and check it when pasting straight into HTML, JSX, or Astro templates.
Testing line length, card truncation, and responsive wrapping
Generating 3 to 5 varied paragraphs lets you inspect how CSS line-clamp, responsive breakpoints, and 16 px mobile body fonts behave under realistic copy lengths. Testing both short 1-sentence summaries and dense 15-word headlines exposes overflow bugs early.
When your team is ready to move from HTML mockups to formatted deliverables, you can also turn Markdown notes into editable Word documents for stakeholder review.
Moving from dummy copy to accessible production text
Placeholder text is a visual scaffolding tool rather than a substitute for real content design. Before shipping any prototype, replacing Latin blocks with real copy exposes edge cases that dummy words hide, such as long German compound nouns or multi-line legal disclaimers.
Checking reading time and word counts before launch
Real headlines, error messages, and form hints rarely match the exact length of Latin filler. Measuring final copy lengths against your UI containers ensures buttons do not wrap awkwardly and summary cards stay scannable on 360 px mobile screens.
Comparing your placeholder word count against actual draft copy also prevents last-minute layout shifts. Aim to keep card excerpts within 25 to 40 words so multi-column grids maintain even heights across desktop and tablet viewports.
Stress-testing multilingual and audio accessibility
Screen readers cannot pronounce scrambled Latin meaningfully, so accessibility audits should always run against real draft copy. Testing real language strings also reveals how accented characters, non-breaking spaces, and long compound words wrap inside narrow containers.
Once real text is in place, you can read text aloud with your device’s voices to hear how your page’s pacing and punctuation sound to listeners.