Thread Unroller Not Working? 7 Fixes to Try

If your thread unroller is not working, the problem is usually not mysterious. In most cases, one of a few simple issues is responsible: the wrong tweet URL, a private or deleted post, a partial thread, or a temporary network or rate-limit problem.

This guide walks through the fastest fixes for the curl-x Thread Unroller, but the same logic applies to most thread-reading tools.

Fix 1: Paste the last tweet, not the first one

This is the most important fix.

If you paste the first tweet in a thread, the tool may only show that single tweet. If you paste a middle tweet, the tool may only reconstruct part of the chain. For the best chance of getting the complete thread, copy the last tweet in the thread and paste that URL into the unroller.

If your result says only one tweet was found or looks incomplete, retry with the last tweet's link first.

Fix 2: Make sure you are using a real tweet URL

A thread unroller needs a direct tweet link with a status ID.

These usually work:

• https://x.com/username/status/1234567890
• https://twitter.com/username/status/1234567890
• common alternate tweet-link formats such as fxtwitter.com, vxtwitter.com, and fixupx.com
• shortened t.co links that resolve to a tweet

These usually do not work:

• profile URLs
• search result URLs
• screenshots of tweets
• copied text without a direct link

If in doubt, open the specific tweet and copy its direct link again.

Fix 3: Check whether the tweet is public

No thread unroller can reliably load a tweet that is:

• from a private account
• deleted
• suspended
• otherwise unavailable

If the source tweet is not publicly accessible, the thread cannot be rebuilt. Open the tweet in a private browser window or logged-out browser profile to confirm it is public.

Fix 4: Retry with a different tweet from the same thread

Sometimes the problem is not the thread - it is the anchor tweet you chose.

If a thread has 15 tweets and you paste tweet 4, you may only see the portion that can be reconstructed from that point. The easiest workaround is to find the final tweet in the chain and use that URL instead.

This is especially useful when the tool shows a partial thread notice or fewer tweets than you expected.

Fix 5: Wait and retry if you hit a rate limit

Public tweet services can occasionally rate limit repeated requests. When that happens, the best fix is usually to wait briefly and retry.

Try this:

1. wait a few seconds
2. paste the same URL again
3. if needed, refresh the page and try once more

If you were testing many threads in a row, give it a little more time before retrying.

Fix 6: Check your connection if the request fails outright

If the page shows a network-style failure, the issue may be temporary rather than thread-specific.

Quick checks:

• refresh the page
• confirm your internet connection is stable
• open the tweet directly on X to confirm it still loads
• try again after a short pause

If the tweet opens on X but the unroller still fails, retry with the last tweet URL to rule out a partial-thread issue at the same time.

Fix 7: Confirm you are looking at a self-reply thread

A thread unroller is best at rebuilding an author's own self-reply chain. It is not the same as a full conversation viewer for every branching reply in a busy discussion.

If several people are replying to one another, the page may not behave like a "conversation unroller" because that is a different problem. Choose a true single-author thread when testing.

What it means when only one tweet appears

Seeing one tweet does not always mean the tool is broken.

Usually it means one of the following:

• the tweet is standalone
• you pasted the first tweet in the thread
• the pasted tweet is not part of a same-author self-reply chain
• the better entry point is the last tweet, not the one you used

The fix is usually simple: go back to X, copy the last tweet, and try again.

What to do when the thread loads but looks incomplete

An incomplete result usually points to the starting URL rather than a total failure.

Try this order:

1. use the last tweet in the thread
2. confirm the thread belongs to one author replying to themselves
3. make sure none of the relevant tweets were deleted or hidden
4. retry after a short pause if the service was rate limited

That sequence solves most partial-thread cases.

Extra tip: use the output clues on the page

When the thread loads, the page itself gives you useful hints:

• if you only got one tweet, the starting tweet may be standalone or the start of a thread
• if the result looks partial, you likely need the last tweet URL
• if media appears, the tool has at least detected part of the thread successfully

Those clues can save time during troubleshooting.

FAQ

Why does the thread unroller say only one tweet was found?

Usually because the tweet is standalone, you pasted the first tweet in the thread, or the best URL to use is the final tweet in the chain.

Why does a thread work for some tweets but not others?

Different threads have different structures. Public single-author self-reply threads are the easiest to reconstruct. Deleted, protected, or branching conversations are harder or impossible.

Can a thread unroller open private tweets?

No. If the tweet is not public, the thread cannot be loaded.

What should I do first when a thread fails?

Copy the last tweet in the thread and retry. That is the highest-signal fix.

Wrapping up

If a thread unroller is not working, start with the basics: use a direct public tweet URL, prefer the last tweet in the chain, and retry if the request was temporarily limited. Most failures come down to those three checks.

If you want the full workflow after the fix, read Twitter Thread Unroller: How to Unroll X Threads in 2026 or go straight to Thread Unroller and test the thread again.