# Lorem Ipsum — Tips & Tricks > Tricks for the Lorem Ipsum generator: which language fits when, pitfalls with lengths and repetition, and combining it with other JPKCom tools. Source: https://www.jpkc.com/db/en/tools/lorem-ipsum/tips/ Back to the overview: [Lorem Ipsum](https://www.jpkc.com/db/en/tools/lorem-ipsum/) · Open the tool: [www.jpkc.com/tools/lorem-ipsum/](https://www.jpkc.com/tools/lorem-ipsum/) The [manual](https://www.jpkc.com/db/en/tools/lorem-ipsum/manual/) explains every setting, the [examples](https://www.jpkc.com/db/en/tools/lorem-ipsum/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 deceives, 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, the typical visual rhythm), use the matching variant. But it comes from **35 fixed sentences** each — good for a paragraph or two, visibly repetitive at length. - **Rule of thumb:** short, language-authentic placeholder → German/English. Lots of text without a repetition pattern → Latin. ## Setting lengths wisely - **Paragraphs when structure matters.** `Paragraphs` is the only unit that hits **exactly**. For "I need exactly three blocks of text" it's the right choice. - **Words and characters are approximations.** Both units trim the last paragraph to fit, so they land very close to the number but not guaranteed to the exact word/character. Read the `X words / Y chars` count at the bottom right when the exact value really matters. - **Characters for hard limits.** Testing fields with a length cap (meta description, teaser, tweet, DB column)? Use `Characters` — the tool cuts cleanly at the last whole word. - **Know the bounds.** Paragraphs 1–20, words 10–2000, characters 50–10000. Need more? Generate twice and concatenate the results. ## Using Markdown mode - **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. - **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 **Generate** again until the construct you want shows up. - **Export follows the format.** In Markdown mode **Export** downloads a `.md` file automatically, in plain-text mode a `.txt`. So watch the `Output Format` before you export. ## 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. If you need the same text more than once, **copy or export** it once and keep using that saved version rather than hoping for another identical run. - **The output field is editable.** Handy for small fixes — but careful: if you click **Generate** again afterward, your manual edits are overwritten. Edit first, then copy. - **The count refers to the generated text.** `X words / Y chars` shows the originally produced result. If you edit in the field, the count doesn't update automatically with every keystroke. ## 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](https://www.jpkc.com/db/en/tools/md/)** and polish it. - **Shape it into rich content:** in the **[WYSIWYG Editor](https://www.jpkc.com/db/en/tools/wysiwyg/)** bring the placeholder text into a formatted HTML view — with Markdown import/export. - **Place it in a layout:** in the **[Playground](https://www.jpkc.com/db/en/tools/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, **[GeoPattern](https://www.jpkc.com/db/en/tools/geopattern/)** (geometric SVG patterns), **[Trianglify UI](https://www.jpkc.com/db/en/tools/trianglify/)** (low-poly backgrounds), and the **[Graphic Editor](https://www.jpkc.com/db/en/tools/graphic/)** (crop and convert images) provide the visual placeholders to go with the text. --- There's more context: the [overview](https://www.jpkc.com/db/en/tools/lorem-ipsum/) for the big picture, the [manual](https://www.jpkc.com/db/en/tools/lorem-ipsum/manual/) for every setting, and the [examples](https://www.jpkc.com/db/en/tools/lorem-ipsum/examples/) for the step-by-step workflows. You can try it all directly in the [tool](https://www.jpkc.com/tools/lorem-ipsum/).