Long-form X posts: when to use 25,000 chars vs 280

Three formats, three trade-offs:

• 280-char post (free or Premium): standard tweet. Fully visible in the timeline. Most reach per character. The default.
• Thread (280 × N posts): chain of standalone 280-char posts. Compounding reach since each post can surface in feeds independently. Free.
• Long-form X Premium post (up to 25,000 chars): single post body up to ~4,900 words. Timeline truncates at ~280 with a "Show more" link. Requires Premium.

The cap was 4,000 characters from February 2023 to late 2023 when X raised it to 25,000 — most older articles still cite 4,000. The ceiling is 25,000 today. For the full character-limit reference, see every X character limit and the deeper Premium discussion in X Premium character limit explained.

Every long-form post on X gets truncated at roughly 280 characters in the timeline, followed by a "Show more" link. The reader has to click to see the rest. In practice, most readers do not click. The timeline-truncation effect is the single most important factor when deciding between long-form and a thread.

In contrast, every individual post in a thread is fully visible in the feed. A 6-tweet thread gives readers six chances to surface in the algorithm, six fully-read posts before any click is required. The first tweet acts as a hook, but readers see the substance of every subsequent post inline as they expand the thread.

This is why threads usually outperform long-form for distribution goals, even when the underlying content is identical. Long-form posts are optimized for the post page (where the full body is always visible). Threads are optimized for the timeline (where most discovery happens).

Three legitimate use cases. Outside these, threading or staying inside 280 is usually the better call.

1. Technical reference content where readers need the full block.A deployment runbook, a long bug postmortem, a detailed product spec, a code-heavy answer. The reader who needs this will click "Show more" because the post has the answer to their question; the reader who does not need it will not click and that is fine. Long-form is right for documents.

2. Formal announcements where chunking feels evasive. Layoff announcements, public apologies, founder letters explaining a strategic shift, security incident disclosures. Threading these reads as defensive — "this is going to be a thread, brace yourself" is the wrong tone for a sober statement. A single long-form post telegraphs gravity and confidence.

3. Permanent reference posts you expect to be read on the post page.When the share happens via DM, newsletter link, or support docs (rather than via feed scroll), the timeline truncation does not matter — readers always land on the post page where the full body is visible. The post becomes a mini-article hosted on X.

Most of the time. Specifically:

1. When you have multiple distinct points. A thread of six points, one per post, lets each point breathe. A 25,000-character post burying six points in a single block forces the reader to do the structuring work. Threads make every point a separate hook.

2. When you want quote-tweet engagement. Quote-tweets cite a specific post, not a passage. People quote individual tweets in a thread to react, correct, or build on a specific claim. They cannot quote a passage from a long-form post — they can only quote the whole post, which is a much higher commitment for the quoter.

3. When you want compounding feed reach. Every individual tweet in a thread has its own chance to surface in someone's feed. A thread that gets a second wind two days after posting (because one tweet starts circulating) is a common pattern. Long-form posts get one feed slot, one chance.

ReplySocial's free X post formatter splits long drafts into clean threads at sentence boundaries with optional "(n/m)" numbering. Paste any draft, switch to standard mode, click split.

The default for everything else. A sharp 280-character post is the highest-leverage format on X — fully visible in feeds, easy to quote-tweet, easy to skim, easy to save. Most posts that get threaded would have hit harder as a single 250-char post with the right edit pass.

Stay inside 280 when:

• The draft is naturally a single point with a single payoff
• The audience is going to skim — most do
• You want maximum reach per unit of writing effort
• The content is a take, observation, or reaction (not reference material)

For editing moves that pull most drafts under 280 without losing the message, see how to write tweets that fit.

Even when long-form is the right format, the first ~280 characters do all the work. That is what readers see in the timeline. That is what decides whether they click "Show more". That is what gets quoted and screenshotted. Treat the opening of a long-form post like ad copy: hook, specificity, a reason to expand.

Common hook patterns that work for long-form openings:

• The lead with the conclusion. "We are sunsetting feature X. Here is exactly what changes, why, and what we are replacing it with." Tells the reader what they get if they click.
• The setup-then-promise. "Three weeks ago we shipped a thing that broke. Here is the postmortem, including the parts we got wrong." Promises specificity.
• The hot take. "Most people misunderstand how social listening works. Long version below." Promises a contrarian payoff.

Fail the first 280 and the rest of the 25,000 are wasted. Win them and you earn the click.

When you have a draft over 280 characters, run it through this:

1. Can edits pull it under 280 without flattening the message? Yes → stay 280. See the editing guide. No → continue.
2. Does the draft have multiple distinct points? Yes → thread. ReplySocial's formatter splits at sentence boundaries. No → continue.
3. Is the content technical reference, formal announcement, or a permanent referenceable post? Yes → long-form Premium. No → thread.
4. Is your goal feed reach? Always thread. Long-form trades reach for cohesion.

For the broader monitoring + reply context that makes character planning matter at scale, see our pillar guide: social media monitoring: the complete 2026 guide.