Tweet Engine

Guide 7 · 4 minute read

How to Number a Thread on X: 1/, 1/n or None?

Numbers tell readers where they are in a thread. Here are the formats people use, what they cost and when to skip them.

By the Tweet Engine Team · Updated

Short answer

Use "1/7" style numbers when you know the final count and the thread is a list or a set of steps, use "1/" when the count may change, and leave numbers out of short threads and stories where they add nothing.

Key takeaways

  • X connects thread posts on its own, so numbers are for readers, not for the thread to work.
  • "1/7" tells readers the total up front, but it breaks if you add or cut a post before posting.
  • "1/" or "1/n" keeps the order visible without promising a count.
  • Numbers cost 3 to 6 characters per post, which matters in posts close to 280.
  • Put the number in the same place in every post, at the start or at the end.

Numbering a thread is a small decision that people argue about more than it deserves. X doesn't need the numbers: it connects the posts on its own. The question is whether numbers help your readers, and which format costs the least.

Do you need to number a thread at all?

No: X joins thread posts automatically, so numbers are only there to help readers know where they are.

When you build a thread in X's composer, each post is attached to the one before it. The thread works the same with or without numbers. So the real question is what the numbers do for someone reading.

They help most in three cases:

  • In lists and steps, "Step 4" is easier to follow, and to refer to, when it's labeled 4.
  • In long threads of 10 or more posts, numbers show progress and tell readers how much is left.
  • When someone quotes post 6 on its own, a "6/" tells new readers it belongs to something larger.

They help least in short threads of two or three posts and in stories, where a number in every post reads like a page counter in a novel.

Which numbering formats do people use?

The common formats are "1/7", "1/", "1/n", "(1)", emoji digits and a thread emoji on the first post only.

Format Example What it tells readers Watch out for
Count and total 1/7 Where they are and how long it is Wrong total after edits
Count only 1/ Order, no promise on length Nothing much
Open total 1/n It's a thread, length not stated Looks unfinished to some
Brackets (1) Order, quietly Slightly more characters
Emoji digits 1️⃣ Order, with color Costs more characters, hard to read past 10
Thread marker 🧵 on post 1 "This is a thread" No order after post 1

None of these is the right one. "1/7" and "1/" are the most widely used and the easiest to read. Emoji digits look friendly in short lists but stop working past 10 and cost more in the weighted count.

How many characters does numbering cost?

Plain numbers cost 3 to 6 characters per post, while emoji numbers cost more because X counts most emoji as 2 or more.

X counts characters with a weighted method described in its developer documentation. Latin letters, digits and a slash count as 1 each. So:

  • "1/ " costs 3 characters.
  • "1/7 " costs 4.
  • "12/15 " costs 6.
  • A keycap emoji such as 1️⃣ is several code points and counts as more than a plain digit.

In most posts that's nothing. In a post that sits at 278 characters, it's the difference between fitting and not. If you number, write your posts with the number included and check the count afterwards. The Tweet Engine thread splitter counts by X's weighted rules, so you can see which posts are close to the limit once numbers are in.

When should you use 1/7 instead of 1/?

Use the full "1/7" only once the thread is final, because a wrong total looks careless and confuses readers.

The total is useful information. A reader who sees "1/5" knows the thread is short and is more likely to read on. A reader who sees "1/25" knows what they are signing up for.

The risk is editing. If you cut post 4 after numbering, every post after it is wrong, and the total is wrong in all of them. Two habits avoid this:

  1. Write and edit the whole thread without numbers.
  2. Add the numbers as the very last step, after the final read.

If you plan to add posts after publishing, for live updates or a running story, use "1/" or no numbers, since you don't know the final count.

Where should the number go in each post?

Pick one position, start or end, and use it in every post of the thread.

A number at the start makes the order easy to scan. A number at the end keeps the first words of each post for the content, which matters most for the opening post, since that's what people see in their timeline.

A common compromise: no number on the first post, or a thread marker at its end, then numbers at the start of every post after it. The opening post stays clean, and the rest are easy to follow.

What about numbering a thread that you add to later?

Use an open format like "1/" or none, because a fixed total will be wrong as soon as you add a post.

X lets the author add posts to a published thread from the thread view. If the thread is likely to grow, a total can't be right for long. Count-only numbering keeps the order clear without a promise you'll have to break. If you are still deciding between a growing thread and one long post, the guide on threads vs long posts compares the two.

Which numbering style should you pick?

Match the style to the thread: none for short threads and stories, 1/7 for finished lists, and 1/ for threads that will grow.

  • Two or three posts: no numbers.
  • A story: no numbers, or "1/" on the first post only.
  • A list, a how-to or a roundup: "1/7" style, added after the last edit.
  • A thread you'll add to later: "1/" style or none.
  • Close to 280 characters in several posts: plain digits, never emoji.

Whatever you choose, keep it the same from the first post to the last. Readers notice inconsistency faster than they notice the format itself.

Questions

Do I have to number a thread on X?

No. X links the posts of a thread together whether or not they are numbered. Numbering is a reading aid. It helps in lists and step-by-step threads and is optional everywhere else.

What does 1/n mean in a thread?

It means "post 1 of a thread of unknown or unstated length". The n stands in for the total. Some writers use it when they don't want to commit to a number, others because they plan to add posts later.

Should the number go at the start or the end of a post?

Either works if you are consistent. A number at the start is easy to spot when scanning. A number at the end keeps the first words of each post for content, which matters most in the opening post.

Do emoji numbers count more characters?

Yes. X counts most emoji as 2 characters, and keycap digit emoji are built from more than one code point. Plain digits and a slash are the cheapest option.

Tweet Engine is independent and not affiliated with X Corp. X changes its features and limits from time to time; X's help center has the current rules.

Have a draft ready?

Split it into a thread