How to Split a Long Post Into a Tweet Thread

Start from the whole text, not from the composer

Write the full piece first — in a document, a notes app, anywhere you can see all of it at once. Threads go wrong when they are written one post at a time inside the composer, because each part gets shaped by the box it is typed into instead of by the argument you are making. A finished draft lets you find the natural chapters: the setup, the evidence, the turn, the conclusion.

Read the draft once and mark every place a reader could pause without losing the thread of the argument. Those pauses are your split points. A good thread part usually carries one idea — a claim, an example, a step — and ends where the next idea deserves its own screen.

Split at sentence seams, then check the real count

Never split mid-sentence if you can avoid it, and never split a link, a handle, or a number away from the words that explain it. X does not count characters the simple way: every URL counts as 23 characters whatever its length, and many emoji and non-Latin characters count double. A part that looks like 260 characters can weigh far more.

That counting is exactly what AutoTweet's free character counter is for. Paste each part in and read the weighted count X will actually use, with the splitter view showing the whole chain at once. Keep parts comfortably under 280 — a part at 279 leaves no room for the numbering you are about to add, and tight parts are the ones that break when you edit later.

• One idea per part; split where a reader could pause
• Check the weighted count, not the raw character count — URLs weigh 23
• Leave headroom in every part for numbering and small edits
• Keep links with the sentence that gives them context

Number the parts and protect the first one

Numbering (1/, 2/, or a simple 1/7 style) is a courtesy that measurably changes reading: it tells the reader the chain has a shape and an end, so they invest in finishing it. Put the total in the first part when you know it. If you later add or remove a part, fix the numbers before scheduling — a chain that skips from 3/ to 5/ reads as careless even when the content is strong.

The first part does double duty: it is both the opening of the thread and a standalone post in every feed and search result. Write it to survive alone — the claim or the hook, stated plainly — and only then let it hand off to part two. If the first part is throat-clearing ('A thread on…'), the chain loses most readers before the good material arrives.

Schedule the chain as one unit, in order

A thread must post as one chain, in order, seconds apart — not as separate posts scattered across a day. In AutoTweet the split parts schedule as a single thread item, so the order you arranged is the order that publishes, and the whole chain stays editable until its slot arrives. Threads count toward your plan's daily thread rail: 1 a day on Pro at $29/mo, 2 a day on Creator at $49/mo, with every segment also counting toward the daily post total.

Pick the slot the way you would pick it for your best single post, because the first part carries the chain. If your account has a proven strong hour, give the thread that hour instead of spending it on a routine update.

A pre-post pass over the split

Before the chain goes out, read it once at phone width, top to bottom, as a stranger. Check three things: that no part leans on a word that ended up in the previous part, that the numbering is unbroken, and that the last part actually lands — a call to action, a summary, or the payoff the first part promised. Threads most often fail at the joins, not in the middle of parts.

Keep the original long draft. A thread that performs is a blog post, a newsletter section, and a follow-up thread wearing different clothes — and the next time you write long, the split gets faster because you start hearing the seams while you draft.

Worked example: one long post, split live

Take a real long post: 'Most people price freelance work wrong. They start from what they need to earn, pick a number, and hope. The clients who pay well are not buying your hours; they are buying the risk you remove. So price the outcome: what does the finished thing make possible, what does failure cost them, and where does your work sit between those two numbers? That is the whole negotiation, and it fits on an index card.' Count the joints: the hook stands alone ('Most people price freelance work wrong'). The diagnosis becomes post two. The reframe — clients buy risk removal — is post three and the thread's most quotable line, correctly given its own frame. The method ('price the outcome') is post four, the index-card line closes as post five.

Five posts, none padded, each survivable alone — and notice the split changed nothing about the argument. It changed the reading: five doorways into one idea instead of one wall the scroller had to climb. That, in one example, is the entire skill this page teaches.