Lorem Ipsum — Tips & Tricks

Back to the overview: Lorem Ipsum · Open the tool: www.jpkc.com/tools/lorem-ipsum/

The manual explains every setting, the examples show the workflows. This page is about what both assume but rarely state: which variant is right in which case, where a length figure can mislead, and how to pair the generator sensibly with other tools.

Choosing the right language

• Latin for page-filling, neutral amounts. Only the Latin variant is assembled word by word — it delivers any amount of text without visible repetition and distracts least while you lay things out, because the brain doesn't try to read real content. First choice for wireframes and large areas.
• German/English for a realistic look in short form. When your draft should read in a real language (word and sentence lengths, umlauts, the typical visual rhythm), use the matching variant. But it comes from 35 fixed sentences each — in Plain text nothing repeats up to the 35th sentence (in Markdown and HTML a quote can duplicate a sentence earlier), after that it does. Good for a few paragraphs, visibly repetitive at length.
• Rule of thumb: short, language-authentic placeholder → German/English. Lots of text without a repetition pattern → Latin.

Setting lengths wisely

• Pick the unit that matches the brief. All four units hit their target: Paragraphs for "exactly three blocks of text", Sentences for editorial sentence limits, Words (exact) for word budgets, Characters (max.) for hard character caps. The count below the field (N words · M characters) confirms the result.
• Characters are a ceiling, not a target. Testing fields with a length cap (meta description, teaser, tweet, DB column)? Use Characters (max.) — the tool stays at or under the limit, cuts at a word boundary, and adds a period. That's why it often lands a few characters short, in Markdown and HTML sometimes a few dozen. Blank lines between paragraphs count as two characters.
• Structure costs length. In Markdown and HTML, headings, list items, and quotes count towards words and characters — so 150 words of Markdown contain less running text than 150 words of plain text. The markup itself (##, <p>, …) never counts.
• Know the bounds. Paragraphs 1–50, sentences 1–500, words 1–5,000, characters 1–30,000. Type more and the tool sets the value to the upper limit. If you really need more, generate twice and join the results.

Using Markdown and HTML

• For testing templates, not just running text. Markdown mode sprinkles in headings (##/###), lists, quotes, and bold/italic/code words. Just right for checking whether your CSS renders the full range of formatted content cleanly — not just gray paragraphs.
• HTML when no Markdown parser is involved. For CMS source fields, static test pages, or stylesheet checks, pick HTML: the output field holds a fragment to paste, while Download .html delivers a complete document with <!DOCTYPE html>, UTF-8, and a matching lang attribute (la, en, or de).
• Every run differs. The formatting is placed at random; there's no seed. If you don't hit an element (no list in the result), just click New text again until the construct you want shows up. Very short texts sometimes contain no structure at all — headings, lists, and quotes only appear after the first paragraph.
• Download follows the format. The button shows the extension: Download .txt, Download .md, or Download .html. A glance at it is all you need before saving the file.

Pitfalls from practice

• "Start with Lorem ipsum…" applies to Latin only. The checkbox disappears the moment you switch to German or English — a Latin opening sentence in a foreign-language text would be pointless. Don't look for it there.
• German/English repeat. That's not a bug but a consequence of the fixed 35-sentence pool. If repetition shows up in your mockup: request less text or switch to Latin.
• No reproducible result. The generator has no seed, and the text isn't saved — only your settings are. If you need the same text more than once, copy or download it once and keep using that version rather than hoping for another identical run.
• Every setting regenerates. The output field is editable and handy for small fixes — but the tool works live: if you then change Text, Format, Length in, Amount, or the checkbox, or click New text, a new text replaces your manual edits. Settle all settings first, then edit, then copy.
• The count follows your edits. N words · M characters counts the current field content without markup and updates on every keystroke. When you trim text by hand, you see right away whether you're still within the limit.
• Very small character counts. If not even the first word plus a period fits under Characters (max.), you only get the first characters of a different sentence without a period, possibly cut mid-word — with German compounds like "Microservices-Architektur" that happens below 26 characters already. For ultra-short fields, use Latin with the checkbox on: from 6 characters you're guaranteed whole words with a period, at least "Lorem.".

Combining with other JPKCom tools

Lorem Ipsum provides the placeholder — these tools process or complement it:

• View and edit the Markdown: cross-check the Markdown output with a live preview in the Markdown Editor and polish it.
• Shape it into rich content: in the WYSIWYG Editor bring the placeholder text into a formatted HTML view — with Markdown import/export.
• Place it in a layout: in the Playground drop the filler text straight into HTML/CSS and see live how it reads in the draft.
• Matching placeholder graphics: for images and backgrounds in the same mockup, the Placeholder Service (placeholder images in any size), GeoPattern (geometric SVG patterns), Trianglify UI (low-poly backgrounds), and the Graphic Editor (crop and convert images) provide the visual placeholders to go with the text.

There's more context: the overview for the big picture, the manual for every setting, and the examples for the step-by-step workflows. You can try it all directly in the tool.