To split text into tweets, you need each post to fit X's 280-character count, where links cost 23 characters no matter how long they are, and emoji and CJK characters count as 2. Thread Splitter does that counting for you and breaks your draft into numbered posts as you type or paste it. There is no button to press and no file to add first: the text box sits beside the words 'Your posts appear here.' and the split happens live.
What the Thread Splitter actually does
Most online thread makers ask you to paste a draft and then click a button to see the result. This one works differently. The page opens on a large text box, and the moment your text is in it, the tool splits it into posts.
A post holds 280 characters, counted the way X counts them:
- Most letters, numbers and punctuation count as 1.
- Emoji and Chinese, Japanese or Korean characters count as 2.
- Every link counts as 23, however long the URL is.
When a post fills up, the split happens between sentences where it can, then between words. If you want to force a break, a line with just --- starts a new post.
Under the box you get a numbering list with three choices: 'No numbers', '1/5 at the end' (what it starts on) or '1/5 at the start'. There is also a tick box labelled 'Long posts (X Premium)', which lets a post run to 25,000 characters and marks roughly where X shows 'Show more'.
Each post appears as a card with its number and its count, plus a 'Copy' button. 'Copy all' copies the whole thread at once.
How to split text into tweets: step by step
- Open Thread Splitter. There is nothing to install and no account to make.
- Paste or type your draft into the big text box. The split into posts happens as you go, so you can watch the cards build up on the right.
- Read the counter on each card. It tells you the X character count for that post, not a raw character count, so a post with a link inside will show a higher number than a word processor would.
- Add a line with just
---anywhere you want a new post to start. Use this when you want a specific thought to open a post rather than land at the end of the previous one. - Choose your numbering from the list under the box. '1/5 at the end' is what it starts on and is the common style on X. Switch to '1/5 at the start' if you prefer the count up front, or 'No numbers' if the thread reads better without them.
- If you have X Premium and want one long post instead of a thread, tick 'Long posts (X Premium)'. A post can then run to 25,000 characters, and the tool marks about where X will show 'Show more'.
- Fix anything that split awkwardly. Move a word or add a
---line and the cards update instantly. - Press 'Copy' on a card to take that single post, or 'Copy all' to take the whole thread.
- Paste into X by hand. The tool does not post to X, does not connect to an X account, does not schedule posts and does not attach pictures. The posts are yours to paste in one at a time.
Why the count is the hard part
A thread that looks fine in a notes app can still fail on X, because X does not count characters the way a word processor does. A single link can push a post over the line even though the URL is short. A run of emoji eats twice the space you expect. If you are writing in Japanese, Chinese or Korean, every character costs 2.
That is why a tweet splitter that only counts raw characters is not much use. The count has to match X's own rules, and the split has to fall in sensible places. Breaking mid-sentence is what makes a thread read badly, which is why this tool tries sentences first and only falls back to word breaks when a single sentence is too long to fit.
Why local, in-browser processing beats upload-based tools
Thread Splitter runs the split on the page, in your browser. Nothing you type is sent anywhere. That matters more than it sounds for a tool like this, because drafts are often unpublished: a client announcement, a launch you have not made yet, a personal story you are still deciding whether to share.
With an upload-based online tool, the text leaves your machine and lands on someone else's server, where it may sit in a log or a queue. Here it does not leave the page. The draft is kept in this browser, so if you come back on the same device, your work is still there.
The other advantage is speed. There is no round trip to a server, no waiting for a result to come back, and no file-size cap on what you can paste in. A 6,000-word essay splits as fast as a two-line note. You also do not need an account, and this tool is not counted against the daily allowance that applies to the file-based tools on the site.
Common mistakes and pro tips
- Writing for the counter instead of the reader. The tool tells you where the breaks fall, but you decide whether the thread flows. Read the cards in order before you copy.
- Forgetting the 23-character link rule. A short link and a long one cost the same. Do not shorten a URL to save space; it will not help.
- Splitting a good sentence for no reason. Use
---deliberately. A thread where every post starts mid-thought reads like a machine made it. - Leaving numbering on when it hurts. A two-post thread rarely needs '1/2' at the end of the first post. Switch to 'No numbers' for short threads.
- Assuming the tool posts for you. It does not connect to X. You copy and paste each post yourself, which also means you can reorder or edit before anything goes live.
- Mixing platforms. The counts here are for X only. Threads, Bluesky, Mastodon and LinkedIn have their own limits, and this tool does not model them.
Where this fits in a publishing workflow
A thread is usually one piece of a larger push. If you are announcing something, the same session often needs a visual. Mockup Generator drops a screenshot into a phone, browser or laptop frame, or warps artwork onto a surface, which is handy for a header image that matches the thread. If you need the same design in every social size rather than one, Social Pack Exporter exports one design to a whole pack. And if the announcement is a podcast episode, Podcast Artwork Pack turns one square of cover art into every size Apple, Spotify and your host ask for.
None of that replaces the writing, though. The thread is still the part people read, and the split is what decides whether they keep reading past post one. Getting the count right and the breaks in the right places is most of the work, and it is the part a counter cannot do for you. Use the tool to handle the arithmetic, then read the thread as a reader would, in order, one post at a time, and fix the joins that feel wrong. That is the difference between a thread that reads like a thought and one that reads like a character limit.