Generate Lorem Ipsum text
- Dashboard
- Documentation
- API
What is Lorem Ipsum?
Lorem Ipsum is a fake pseudo-Latin text used since the 16th century in printing to test layout without the meaning of the text distracting the reader. It is actually a distorted extract from Cicero's De Finibus Bonorum et Malorum (45 BC), first spotted in a typographic sample from the printer Letraset in the 20th century.
Today, the terms Lorem Ipsum, filler text, dummy text, placeholder text, fake text or test text are used interchangeably. They all designate the same objective: fill a visual area to evaluate a typography, a grid or a template.
Why use fake text?
The real content of a site is almost never available at design time. To avoid blocking production, you insert filler text that simulates the final volume while staying neutral. Its main uses:
- UI / UX mockups in Figma, Sketch, Adobe XD
- Web or mobile prototypes shown to the client
- Typography tests: kerning, justification, line height
- Validating CMS templates (WordPress, Drupal, Strapi)
- Sales demos or pitches before the real content is written
- Overflow tests (long sentences versus short titles)
How our generator works
Our generator produces Lorem Ipsum based on the canonical Latin corpus. You indicate the desired character count, the generator cuts or repeats the reference text to reach exactly this length. It systematically starts with Lorem ipsum dolor sit amet, consectetur adipiscing elit... in line with the typographic convention established since the 1960s. A language option also lets you generate random text in French or English instead of Latin.
How to use it
Three steps:
- Enter the character count in the "quantity" field
- Pick the language: Lorem Ipsum (Latin), random French or random English
- Click the "Generate" button, then copy the result with the dedicated button
Concrete use cases
A few typical contexts where this Lorem Ipsum generator is useful day to day:
- UI designer: fill cards, articles or descriptions before the copywriter delivers the content
- Front-end developer: test components with variable lengths (short title, medium paragraph, long block)
- Project manager: prepare annotated wireframes for a client review
- Copywriter: have a neutral canvas to calibrate a newsletter or an article
Lorem Ipsum examples
Lorem Ipsum of 100 characters:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labor
Lorem Ipsum of 500 characters:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Sed ut perspiciatis unde omnis iste natus error sit volupt
FAQ
Why does the text always start with "Lorem ipsum"?
By typographic convention. The "Lorem ipsum dolor sit amet" opening has become a universal signal for designers: it indicates at a glance that the text is not the final content.
Does Lorem Ipsum mean anything?
No, it is intentionally distorted Latin from a Cicero fragment but reworked to no longer form a coherent sentence. If you try to translate it, you only get disjointed scraps.
How many characters for my design?
A few practical benchmarks: 50 characters for a title, 150 for a hook sentence, 500 for a short paragraph, 2000 for a blog article. Adjust to your real need.
Can I generate random text in French?
Yes. Our generator offers a language option: pick "French (real text)" to get a French sample from a natural corpus, rather than fake Latin.
Does Lorem Ipsum affect SEO if I leave it in production?
Yes, negatively. Google detects this fake content and may consider the page as "thin content". Always replace with the real content before going live.
Frequently asked questions
Should I prefer classic Lorem Ipsum or custom text?
Classic lorem ipsum is neutral and clearly signals filler text, which avoids any confusion with the final content. Custom text in English may be preferable when you present the mockup to a non-technical client, so they are not thrown off by the Latin. For typographic tests, lorem ipsum remains the reference because its word-length distribution is representative.
Does the generator produce multilingual text?
Yes. You can pick classic Latin lorem ipsum, random French or random English text. These variants are useful when you test the rendering of a specific language: the average word length in German or Finnish is very different, which can break a mockup validated in lorem ipsum. For these languages, copy a real sample from an open source.
How much text should I request depending on the context?
A few practical benchmarks: 50 characters for a title, 150 for a standfirst, 300 for a product description, 500 to 800 for an article paragraph, 2000 to 3000 for a full blog article. For an overflow test, double the expected quantity: a template that supports 200% of the final content will not break in production when a writer produces slightly more.
When should fake text absolutely be avoided?
Three risky situations: presentations to an executive or a sponsor who may interpret the Latin as negligence, user tests where the content must be credible to assess comprehension, and any publicly accessible or indexable page. In these cases, prepare a real-content draft, even imperfect, or use the real-text option in your language.
Is the generated text computed client- or server-side?
Generation is done server-side in this implementation, then the result is returned in the page. No personal content is processed, the tool simply takes a character count as input and returns filler text. You can use it freely without fear of sending sensitive data: only the length parameter is transmitted.
How do I avoid leaving fake text in production?
Add an automated check in your pipeline: a simple grep -r "Lorem ipsum" on your templates or content folder before each deployment catches forgotten leftovers. Several content linters (textlint, vale) provide a dedicated rule. CMS-side, a convention is to use a "draft" status until the content is validated, which prevents accidental publication.
Example request
curl -X POST https://cdrn.fr/api/v1/tools/text-generator/execute \
-H "Content-Type: application/json" \
-d '{"language":"lorem","quantity":200}'
Input schema
| Field | Type | Required | Default |
|---|---|---|---|
language |
choice (lorem, fr, en) | ✓ | lorem |
quantity |
integer | ✓ | 200 |
Endpoints
GET https://cdrn.fr/api/v1/tools- lists every available toolGET https://cdrn.fr/api/v1/tools/text-generator- returns the schema for this toolPOST https://cdrn.fr/api/v1/tools/text-generator/execute- runs this tool with a JSON payload