Paste a blog post, draft, or essay — we split it into ready-to-post tweets at word boundaries with thread numbering.
Long article text… → 1/4 First tweet…
2/4 Next tweet…
Twitter / X threads convert long-form content into a sequence of 280-character tweets. The hard part is splitting cleanly: at word boundaries (never mid-word), counting the "1/9 " prefix against your character budget, and producing chunks short enough to leave room for hashtags or polls.
This tool handles all of that. Paste your blog post, essay, or draft; the output is a clean numbered thread you can copy tweet-by-tweet into the X composer.
X engagement on threads of 8–12 tweets often beats blog-post link CTRs by 3–5×. Convert your latest post into a thread, post the thread first, drop the link in the final tweet.
Substack/Beehiiv writers thread the highlights of each new issue. The thread drives the subscribe.
Just gave a talk? Thread the script while the room is still excited. Far better reach than a recording link no one clicks.
Sports, finance, politics — analysts who thread their hot take get more reach than analysts who link to a Medium post.
Sometimes a single tweet isn't enough. Quote-tweet your own first chunk and reply to it with the next, and so on.
The tool processes input text by splitting it into chunks of up to 280 characters, respecting word boundaries to avoid mid-word breaks. It first calculates the required number of tweets based on total character count, then assigns a prefix "1/N" to each chunk. The prefix length (e.g., "1/9 " = 5 characters) is subtracted from the 280-character budget. The algorithm uses a greedy approach: it reads words (delimited by whitespace) from the input, accumulating them until adding the next word would exceed the budget (after accounting for the prefix and a space separator). It then finalizes that tweet, increments the counter, and repeats. The output includes a trailing newline between tweets for easy copying. Unicode characters are counted as single codepoints (Twitter’s counting method), but multi-byte characters like emoji may count as 2 characters in some contexts; the tool assumes codepoint-based counting to align with typical API behavior.
Compared to manual splitting or scripting, this tool automates prefix management and word-boundary handling.
| This tool | Manual text editor split | Python textwrap script | |
|---|---|---|---|
| Word boundary handling | Automatic; never splits words | Requires manual checking or regex | Must implement custom word-wrap logic |
| Prefix management | Automatically adds '1/N ' and increments | Manual typing of prefixes is error-prone | Requires custom prefix loop |
| Batch processing | Instant split of entire input | Tedious for long texts | Fast but requires coding skills |
| Character counting | Accounts for prefix in budget | Must count characters manually | Can be scripted to include prefix |
The 280-character tweet limit, introduced by Twitter in November 2017 (increased from 140), prompted users to create 'threads'—a series of connected tweets. Splitting long text into tweet-sized chunks became a common need, leading to tools like this that automate the process while respecting word boundaries and prefix numbering.
The numbering prefix "NN/NN " can take up to 7 characters; the trailing space is the 8th. The tool slightly under-budgets so the prefix never accidentally pushes content over 280 in real-world use.
It splits at word boundaries (whitespace), not sentence boundaries. If you want strict sentence-boundary splits, add line breaks at sentence ends in your input.
Yes — change the per-tweet limit to 500 or 300. The tool accepts limits from 50 to 500 characters.
It treats them as regular characters. X's actual URL counting (every URL = 23 chars) is more nuanced — leave 30 characters of headroom if you'll add a URL.