Skip to content
Toolew.com

Tweet Thread Splitter

Break long-form text into word-boundary-safe, automatically numbered X (Twitter) thread posts.

Runs in your browser. Your data is not uploaded.
Loading tool…

This guide is not yet available in your language and is shown in English.

Tool guide

What this tool does

Tweet Thread Splitter divides a long piece of writing into individually copyable posts, each within your chosen character limit, splitting only on word boundaries and automatically adding a "1/n" style counter to every post once the thread length is known.

Turning a long piece of writing into an X/Twitter thread means manually finding good break points under the character limit, over and over, for every single post, tedious to do by hand for anything longer than a few hundred words.

This tool handles that splitting automatically: it packs your text into chunks that never exceed your chosen character limit, always breaking between whole words, never mid-word, and adds an auto-numbered "1/n" suffix to every post once the total thread length is known.

How to use Tweet Thread Splitter

  1. Paste your full long-form text.
  2. Set your character limit per post (280 for standard X accounts).
  3. Review each generated post in the list.
  4. Copy each post individually and paste it into your thread, in order.

Tips for better results

  • This performs a plain character count per post, not X’s real weighted count (which treats links and CJK/emoji differently); if your text contains links or non-Latin characters, use the Character Counter tool to double-check, or lower your per-post limit slightly for headroom.
  • The "i/n" suffix length is automatically reserved for in each post’s length budget, so a post never actually exceeds your set limit once the counter is added.
  • A lower character limit (like 250 instead of 280) leaves room to add a tiny flourish, like an emoji, after pasting each post, if you want one.
  • Reviewing each post’s content (not just the count) matters, splitting is purely mechanical and doesn’t understand sentence meaning, so occasionally manually adjusting a break point for readability is worth doing.

Common use cases

  • Converting a blog post or long explanation into a ready-to-post X thread.
  • Breaking up a long announcement or story into digestible numbered posts.
  • Preparing a long-form idea for a platform with a strict per-post character limit.
  • Quickly estimating how many posts a piece of writing will take as a thread before committing to write it that way.

Common mistakes to avoid

  • Not leaving extra headroom for links or emoji, which count differently (and often higher) under X’s real weighted counting rules than this tool’s plain character count.
  • Pasting the generated posts out of order; always post sequentially from post 1 onward so the thread reads correctly and the auto-numbering makes sense to readers.
  • Setting an unnecessarily low character limit, producing far more, choppier posts than needed; 280 (the standard limit) is usually the right default unless you have a specific reason to go lower.

Frequently asked questions

Does this account for X’s weighted link/emoji counting?

No, it uses a plain character count per post; for text containing links, emoji or CJK characters, cross-check with the Character Counter tool or lower your per-post limit for safety margin.

Will a word ever get cut in half across two posts?

No, splitting always happens on whole-word boundaries, a word is never divided between two consecutive posts.

How is the "1/n" numbering calculated?

The text is split once to determine the total number of posts, then re-split reserving exact room for that final "i/n" suffix in every post’s character budget, so no post exceeds your limit after numbering is added.

Is my text uploaded anywhere?

No, splitting happens entirely in your browser using plain string operations; nothing is transmitted anywhere.

Feedback & suggestions

Help us improve Tweet Thread Splitter. We read every message.

Rating (optional)
Necessary
Required for security, language and theme preferences. Always on.