Bullet Points on X: How to Format Lists That Won't Break

The Problem with Native List Formatting

X (formerly Twitter) is a text-first platform that strangely refuses to offer basic text formatting. While LinkedIn and Facebook have incrementally added rich text options in certain contexts, X remains committed to the raw string. If you try to paste a list from Google Docs or Notion, the formatting usually collapses, leaving your carefully curated points as a dense, unreadable paragraph.

Because the platform relies on character count—and now ‘Long-form’ posts for Premium users—the way you structured your lists impacts both the algorithm's dwell time and whether a user actually clicks 'Show more.' To get bullet points twitter users can actually scan, you have to stop thinking like a writer and start thinking like a typesetter.

The reliable Unicode toolkit

Since you can’t highlight text and click a list icon, you need a library of ‘Safe Unicode’ symbols. Not all symbols are created equal. Some render as emojis (which can look unprofessional depending on your niche), and some disappear entirely on older Android builds or Windows desktop browsers.

For a standard, professional look, stick to these three:

1. The Standard Bullet (•): Unicode U+2022. This is the safest bet. It aligns perfectly with the center of the text height.
2. The Hollow Circle (◦): Unicode U+25E6. Best for sub-points or a lighter visual weight.
3. The Medium Square (▪): Unicode U+25AA. Excellent for technical or 'check-list' style posts.

Common Mistake: Avoid using the hyphen (-) as a bullet. On X, a single hyphen and a space often look like a mistake or part of a broken sentence. If you want a dash, use the Em Dash (—) which provides more visual separation.

Leading and Line Breaks: The 2-1 Rule

Whitespace is more important than the symbol itself. On a mobile device, X’s interface is crowded by profile pictures, engagement icons, and the infinite scroll.

If you have a list of five items, do not simply put them on five consecutive lines. This creates a 'block' effect that is repellent to the eye. Instead, use the 2-1 Rule: two line breaks between the introductory sentence and the first bullet, and one line break between each list item.

However, there is a catch. X frequently collapses multiple line breaks into a single break if it detects 'excessive' whitespace. To bypass this, ensure there is at least one character—even an invisible one or a period—if you are trying to create massive gaps, though for standard lists, a simple single return between items usually holds.

Handling the Truncation Trap

X truncates posts at different points depending on whether they are 'short' posts (280 characters) or 'Long-form' posts.

• For 280-character posts: You have no room to waste. Use a single bullet symbol followed by one space. Do not indent with spaces; X will strip leading whitespace in many viewports, making your list look jagged.
• For Long-form posts: Your list will likely be cut off after the first 2-3 items by the 'Show more' prompt. Always put your most impactful three bullets above the fold. If your fourth bullet is the 'hidden gem,' 80% of your audience will never see it.

A Case Study in List Conversion

Let’s look at a typical 'Before and After' based on a real marketing thread we edited at BoldlyType.

The 'Before' (Standard Copy-Paste): Developing a content strategy requires three things: 1. Goal setting 2. Audience research 3. Distribution planning. You also need to track your KPIs weekly.

The 'After' (Optimized for X): Developing a content strategy requires three non-negotiables:

• Goal setting (What does 1% growth look like?) • Audience research (Where do they hang out?) • Distribution (How do we repurpose this?)

You also need to track your KPIs weekly.

Why the 'After' works: The 'After' uses the U+2022 bullet, leading whitespace, and parentheses for secondary information. When formatted this way, the eye naturally jumps to the bullet points, increasing the 'scanning' speed of the reader. On the X mobile app, this takes up about 40% of the vertical screen, forcing the user to focus on your value proposition.

Accessibility and Screen Readers

This is where many 'Twitter Growth Hackers' fail. You may have seen lists that use 'fancy' fonts—the ones that look like 𝐛𝐨𝐥𝐝 or 𝘪𝘵𝘢𝘭𝘪𝘤. These are not actually fonts; they are mathematical alphanumeric symbols.

When a screen reader (used by those with visual impairments) hits these symbols, it doesn't read the word. It reads each individual character's Unicode name: "Mathematical Bold Capital B, Mathematical Bold Small o..." This makes your content completely inaccessible.

Stick to standard system text and the basic Unicode bullets mentioned above. If you need to emphasize a bulleted item, use standard caps sparingly or use an emoji that relates to the topic (e.g., a 📈 for a growth point), but never replace text with pseudo-fonts.

The 'Thread' Strategy for Lists

If your list is longer than 7 items, it shouldn’t be a single post. It should be a thread. The best way to format a list-based thread is to use the '1/n' convention.

• Tweet 1: The Hook + the first 2 bullet points.
• Tweet 2-4: Expansion on each point.
• Tweet 5: A summary list of all points for those who want to bookmark it.

For that summary list, you can use our Twitter text formatter to preview exactly how the line breaks will appear on various screen widths. This prevents the awkward 'wrapped' bullet where the second line of a list item starts at the far left margin, breaking the vertical line of the list.

Technical Constraints to Remember

• Character Count: Each Unicode bullet counts as 1 character. Most emojis count as 2.
• The 'Blue Check' Advantage: If you are a Premium subscriber, you have more leeway with 'Long-form' notes, but the desktop web version still displays a fixed-width container. Your bullets should not exceed 60-70 characters per line to avoid 'ugly wrapping.'
• Copy-Pasting: If you are drafting in Notion or Obsidian, use a plain text editor as a 'cleaner' before pasting into X. This removes unintended code that can cause X's composer to glitch or show weird spacing.

By treating your lists as visual elements rather than just text, you increase engagement and make your insights significantly more digestible for the 'scroll-fast' audience on X.