To make a Twitter thread from long text, paste the whole draft into Thread Splitter and let it break the text into posts as you type. Each post is counted the way X counts it, so a 280-character post is really 280 by X's rules — not by your word processor's. You then copy the posts and paste them into X by hand.
That is the whole job. The rest of this guide is about getting the breaks in the right places, avoiding the counting traps that make a 'short' post fail on X, and keeping your draft private while you work on it.
What 'counted the way X counts it' actually means
Most people assume 280 characters means 280 keystrokes. X does not count that way, and this is the single biggest reason a thread that looked fine in a notes app gets rejected when pasted.
| What you type | What X counts |
|---|---|
| Ordinary Latin letters, digits, punctuation | 1 each |
| Emoji | 2 each |
| Chinese, Japanese or Korean characters | 2 each |
| Any link, however long | 23 |
That last row matters most for anyone writing a thread with sources in it. A 90-character URL with tracking parameters still costs you 23. A short link also costs 23. There is no advantage to shortening links for the character count, and no penalty for pasting the long one.
Thread Splitter applies these rules as you type, so the count on each post card is the count X will show you. If you write in Japanese or use a lot of emoji, a post that looks like 200 characters in a plain editor may already be over the limit — the tool will show you that before you paste.
How to make a Twitter thread from long text, step by step
1. Open the tool and start typing or pasting
Go to Thread Splitter. It opens on a large text box beside the words 'Your posts appear here.' There is no button to press and no file to add — the text is split into posts as it is typed or pasted.
Paste your full draft, essay, newsletter section or script. It does not need to be pre-formatted.
2. Let it split between sentences first, then between words
The tool breaks the text between sentences where it can, and only falls back to breaking between words when a single sentence is longer than a post. This matters: a thread that breaks mid-sentence reads badly, and readers scrolling X notice.
If you want a specific break, put a line containing just --- where the new post should start. That forces a new post at that point regardless of how much room is left in the previous one.
3. Choose your numbering
Under the box there is a numbering list with three options:
- No numbers — for threads where the numbering would clutter the text
- 1/5 at the end — what it starts on, and the most common convention on X
- 1/5 at the start — useful when the first post needs to signal immediately that there is more
Numbering is cosmetic on X, but it sets expectations. A reader who sees '1/7' knows to keep going; a reader who sees nothing may scroll past the first post assuming it is a standalone thought.
4. Decide about long posts
There is a tick box labelled 'Long posts (X Premium)'. Ticking it lets a post run to 25,000 characters and marks roughly where X shows a 'Show more' cut. Only use this if your account actually has X Premium — otherwise the post will not publish as written.
For most threads, leave it unticked and let the text split into 280-character posts. Threads made of several short posts tend to get more engagement than one long post with a fold in the middle, because each post is a fresh item in the timeline.
5. Review each post card
Every post appears as a card with its number and its character count, plus a 'Copy' button. Read through them in order. This is the moment to catch a post that ends awkwardly, a link that pushed a sentence into the next post, or an emoji that ate two characters and shifted a break.
6. Copy and paste into X by hand
Use 'Copy' on a single post, or 'Copy all' for the whole thread. The tool does not post to X, does not connect to an X account, does not schedule anything and does not attach pictures. You paste the posts into X yourself, in order.
That sounds like a limitation and is really the point: you keep control of images, alt text, tagging and timing, none of which a splitter can guess for you.
Why splitting in the browser beats upload-based thread tools
Most 'thread maker' sites ask you to paste text into a form and press a button that sends it to a server. Yours goes over the network, sits in a queue, comes back, and you have no idea what happened to it in between. For a rough draft that is tolerable. For an unpublished essay, a client's launch copy or anything under embargo, it is not.
Thread Splitter runs the split on the page. Nothing typed is sent anywhere, and the draft is kept in this browser, so you can close the tab and come back to it on the same machine. There is no account to create. It also does not count against the free daily allowance — the metering on Alvseike applies to exports and file processing, not to this.
Speed is the other half of it. There is no round trip, no waiting for a server to reply, no file-size cap. A 12,000-word draft splits as fast as a 200-word one because the work happens on your own machine.
Common mistakes and pro tips
Write the first post last. The opening post is the only one most people will see. Draft the thread, split it, then rewrite post one as a standalone hook that makes sense without the rest.
Do not number manually. If you type '1/' yourself and then also select a numbering option, you get '1/5 1/'. Pick one.
Watch the link budget. Three links in one post cost 69 characters before you have written a word. If a post is mostly links, it will split earlier than you expect.
Use --- for deliberate breaks. Automatic splitting is good at sentences, not at ideas. If a section should start fresh, mark it.
Check the last post. Automatic splitting often leaves a two-word final post. Either merge it by trimming earlier text or accept it as a sign-off line.
Keep emoji out of tight posts. At 2 characters each, a row of five emoji costs 10 — enough to push a link into the next post.
Do not assume other platforms. Thread Splitter counts for X only. Threads, Bluesky, Mastodon and LinkedIn all count differently and have different limits, so a thread built here is an X thread.
Where this fits in a publishing workflow
A thread rarely travels alone. If you are announcing something, the same copy usually needs a square image for the thread, a story-sized version, and a link preview. Once your thread text is settled, Mockup Generator is useful for putting a screenshot of the product into a phone or browser frame so the visual matches the post that describes it. If the thread is part of a wider launch, Social Pack Exporter turns one design into every size you need in a single pack rather than exporting each by hand. And if the thread is promoting an episode, Podcast Artwork Pack handles the cover art sizes Apple, Spotify and your host ask for.
None of that touches the text. The split stays where it is, in this browser, until you copy it out.
The habit worth building is simple: write long, paste once, and let the tool find the sentence breaks rather than breaking the draft by hand at 280 characters. Hand-splitting is where threads go wrong — a sentence cut in half, a link orphaned on its own line, a count that was right in your editor and wrong on X. Doing it in the browser, with X's own counting rules applied as you type, removes that whole category of error and leaves you with the only decision that actually matters: what the first post says.