Bulleted and Numbered Lorem Ipsum – deskrush Ipsum Lists Explained starts with a simple distinction: bullets suggest a set, numbers suggest a sequence. Choosing the wrong one sends a quiet signal that the layout does not intend, even when every word inside the list is placeholder text.
TL;DR: Bulleted lists fit unordered groups, numbered lists fit steps. Set the item count, choose a type, and enable HTML output if you need list tags.
Two List Styles, One Purpose
A bulleted list signals items of equal weight. The reader is meant to scan them in any order, the way someone reads a feature grid or a packing list. A numbered list signals order: first this, then that, and the sequence carries meaning that the individual items do not.
Both styles do the same structural job. They break a dense block into shorter lines, create a strong left edge, and give the eye resting points. The difference is the promise each one makes about how the content should be read.
The filler inside each item should be short. A bullet that runs four lines stops behaving like a bullet and starts behaving like a paragraph with a dot beside it. If an item needs that much text, the list is probably the wrong structure.
When Bullets Are the Right Choice
Use bullets when the items are peers. Features, benefits, ingredients, supported formats and checklist entries all belong in an unordered group. The reader can jump in anywhere, and nothing is lost by reading the last item first.
- Feature summaries on a product page
- Benefits beside a signup form
- Included items in a package
- Short specifications in a sidebar
- Reasons listed in a comparison section
Bullets also work well in narrow columns because each item can wrap independently without implying a broken sequence. A wrapped bullet looks like a continuation. A wrapped number can look like a new step, which confuses scanning.
When Numbers Carry Meaning
Use numbers when order matters. Setup instructions, ranked results, process steps and anything the reader must follow in sequence need explicit ordering. Removing the numbers would change the meaning, not just the look.
- Prepare the environment.
- Install the dependency.
- Run the first check.
- Review the output.
- Repeat with the final settings.
There is a middle case: a list that is technically unordered but benefits from counting, such as five reasons or seven tips. Numbers there are stylistic. They help the reader track progress without promising a strict sequence.
Setting Item Counts
Item counts run from one to one hundred, with the same slider and number field used for other units. Most real lists hold three to seven items. Below three, a list is usually unnecessary. Above ten, the reader starts skimming and the structure loses its edge.
Generate a few more items than you need, then delete the weakest. This is faster than regenerating because the first item was too long or too short. The extra items also let you compare lengths and pick a set that looks even.
If the design has a fixed row height, keep item text to one line. That constraint is worth testing early, because a single long item can push the whole list out of alignment and make a tidy component look broken.
HTML Output for Lists
When HTML output is enabled, bulleted lists are wrapped in an unordered list element with list item tags, and numbered lists use an ordered list element. Paragraphs, if any, keep their own paragraph tags. The result can be pasted into a template that expects real markup.
Without that option, the download is plain text. The line breaks survive, but the list structure does not, so a content system may treat every item as an ordinary line. If the destination styles lists automatically, enable HTML before downloading.
Check the generated markup before publishing. Filler that includes list tags is still filler, and it should be removed from a live page along with everything else. The tags make the mockup accurate; they do not make the content appropriate.
Checking the Result
Look at the list at the width it will actually use. A five-item list that fits a desktop sidebar may wrap awkwardly on a phone, especially with numbers, where the marker takes horizontal space. Narrow previews catch that early.
Also check the gap between the marker and the text. Placeholder items of very different lengths expose spacing rules that look fine with uniform sample content. That is one of the useful side effects of filler that varies naturally.
If the list still looks uneven, the markers may be the cause rather than the item text. Switch the list type once and compare the two results before changing the copy.
Can I switch a list from bullets to numbers after generating?
Yes, if you regenerate with the other type selected. The text changes too, so the items will not match word for word. For a quick visual check, that is fine. For a controlled comparison, note the item count and length before switching.
How many items should a feature list have?
Three to six is the usual range. Fewer looks like an afterthought, and more turns into a wall that readers skip. If the product genuinely has more features, split them into groups with short subheadings instead of one long list.
Does the list output include punctuation?
Items are drawn from the same sentence pool, so punctuation follows the source text rather than a list-specific rule. Some items end with periods and some do not. For a mockup that is acceptable. For a style guide test, edit the endings by hand.
Final Thoughts
Lists are structural choices, not decoration. Pick bullets for peer items and numbers for sequence, keep the count small, and enable HTML when the destination needs markup. Test at the final width, then replace every item with real content before launch.
-
Tags:
