The word list lives in this file, not on a Lorem CDN
Half the “Lorem Ipsum generator” results on the web fetch paragraphs from a public API so they can count you as a visit. Some inject ads into the textarea. This page does not. lorem-ipsum.js keeps a Cicero-flavoured Latin list (the usual lorem ipsum dolor sit amet… bag) and builds sentences by picking those tokens. Count is 1–50. Units are paragraphs, sentences, or words. Copy stays in this tab. If you need real copy, write it, or paste a draft into the word counter. Filler is a layout tool. It is not a content strategy, and it is not “AI-written placeholder” with a model hop I would have to disclose.
The start-with-Lorem checkbox prepends the classic first sentence and strips a duplicate if the random draw already began that way. Designers argue about this because a block that starts “Lorem ipsum” is obviously fake in a stakeholder review, which is the feature, until a client leaves it in production. Uncheck it when you are testing whether a reviewer actually reads.
Worked example: three paragraphs for a hero mock
Leave unit on paragraphs, count 3, start-with checked. You get a first line everyone recognizes and two more Latin-ish blocks. Drop them into the layout. Measure overflow. If the typeface at 48 px only fits eight words, you needed the words unit, not a novel. Hit copy, paste, do not “regenerate until it feels like English.” It will not feel like English. That is the point.
Worked example: twelve words for a button label
Set unit to words, count 12. Word mode is not a random bag in this script: it walks the list in order and wraps with modulo. You will see the same sequence starting at lorem ipsum dolor… more often than a “creative” generator. I left it that way so a screenshot of the mock is reproducible-ish. If you wanted shuffle, use sentences (those pick random indices). A 12-word button is also a reminder that real UI copy is three words; if Lorem looks fine at twelve, your button is too wide.
Worked example: the client thought Lorem was the product
Uncheck start-with. Generate two sentences. Put them in a pricing card. If nobody on the review call notices, you have a reading problem, not a generator problem. Replace with actual benefits before launch. I will not add an “English placeholder” mode that hallucinates features. For casing experiments on real strings, use the case converter.
Limits that are intentional
Fifty units max. No HTML output with <p> wrappers (you can split on blank lines yourself). No “lorem in the voice of a fintech hero.” No network. View source and you should see the word array, not a fetch. If a browser extension injects a different generator into the textarea, that is the extension. Close it.
Cicero’s original de Finibus passage is a scrambled, truncated tradition. This list is the web’s usual bag, not a Latin lesson. Words like consectetur exist so body text has a similar shape to English: ascenders, a mix of lengths, punctuation at sentence ends that I add in code. It will not stress-test hyphenation dictionaries or CJK line breaking. For those, paste real target-language copy. For a favicon or a card layout with no text, you did not need Lorem at all; you needed empty boxes.
Does this call a Lorem API?
No. A word array lives in lorem-ipsum.js. Paragraphs are assembled in this tab. There is no lipsum.com hop.
Why start with “Lorem ipsum…”?
Designers fight about whether placeholder should be obviously fake. The checkbox prepends the classic sentence. Uncheck it when a client mistakes filler for copy.
Word mode looks repetitive.
Word mode walks the list in order and wraps (modulo the list length). It is not random. Use sentences or paragraphs when you need shuffle.
Cap?
Count is clamped 1–50. This is mockup filler, not a novel generator.
Is the text uploaded?
No. Generated strings never leave this tab. Still do not paste real product copy into a “lorem” box thinking it is a CMS.
Can I add my own dictionary?
Not in this UI. Fork the WORDS array in the script if you want Hindi or English boilerplate.