Common workflows
- Crisis monitoring — when a viral negative reply chain hits a brand tweet, export the full thread to your customer-success team in minutes.
- Social listening — pull replies under your CEO's tweets to gauge audience sentiment.
- Competitor analysis — export replies to a competitor's launch tweet to see who's engaging and what they're saying.
- Influencer discovery — replies under a major industry tweet often contain the next-tier creators in the same niche; the verified accounts are usually worth following up.
- Sentiment analysis — pipe the CSV into ChatGPT or Anthropic Claude with a "score 1-5 for positive sentiment" prompt.
- Lead generation — replies with bio links pointing at .com domains are often potential customers; the export gives you their @-handle for outreach.
About X's "view rate-limited" behavior
X (Twitter) aggressively rate-limits anonymous reads of replies — large viral tweets often hit the cap and only show ~half the reply tree to any given viewer. The exporter respects this: if X starts limiting the public reply view on the tweet, the export tells you exactly how many replies it could see. For complete coverage of very large reply trees, authenticated mode uses your own X session.
X / Twitter URL formats
All of these work: twitter.com/user/status/..., x.com/user/status/..., www.twitter.com/..., mobile.twitter.com/.... The exporter normalises them all server-side.
Plan limits
Per-tweet size scales with your plan. Free (no signup): up to 100 results per tweet. Personal: 5,000. Premium: 50,000. Business: 250,000 — see pricing for the full feature comparison and API tiers for the API-specific limits.