How X Ranks Replies (and How to See Past It)

X does not show you replies in the order people posted them. By default it shows you replies in the order its ranking system thinks you want them, and that order is built from engagement and account signals, not from who arrived first or who said something most accurate. Once you know what feeds the ranking, the "best" order stops looking arbitrary and starts looking like what it is: a popularity-weighted guess.

What signals feed the ranking

X has never published the exact formula, but the visible behavior points to a consistent set of inputs:

• Engagement velocity — replies that collect likes, reposts, and further replies quickly get pushed up faster than ones that gain traction slowly.
• Account signals — verification status, your history of interacting with the replier, and whether the account looks established all weigh in.
• Relevance to you — X leans on your follow graph and past behavior, so two people can open the same thread and see a different "best" order.
• Recency, as a tiebreaker — among replies with similar engagement, newer ones get a slight edge, which is why a good reply posted late can still surface.
• Quality and spam filtering — replies flagged as low-effort, duplicate, or bot-like get demoted before ranking even applies, a separate step from why some replies look hidden or collapsed.

None of these are visible to you as a reader. You just see the result: one ranked list that feels authoritative but is really a blend of five or six weighted guesses.

Ranking is not the same thing as hiding

It's worth separating two mechanisms that get lumped together as "X buried my reply." Ranking reorders replies that are still fully visible — they exist in the thread, just further down the list. Hiding and collapsing is a different, earlier step: a quality filter, a mute, a block, or plain pagination that can keep a reply out of the visible count entirely, before ranking ever touches it. A reply can rank poorly and still be one tap away. A reply that's been filtered or paginated is a separate problem, and switching sort order will not fix it. Knowing which situation you're in saves you from assuming a low-ranked reply has vanished when it's really just sitting a few rows down.

Why the top reply isn't always the truest one

Ranking rewards what spreads, not what's correct. A reply that lands a joke or states something confidently tends to collect likes within minutes, long before a more careful correction has a chance to catch up. By the time the accurate reply exists, the ranked view has already decided what "best" means for that thread, and the correction often sits several rows down, buried under replies that arrived faster and hit harder.

This is a known shape of ranked systems generally, not something unique to X, but it matters for how you read threads. If you are looking for the most-liked take, the default order works fine. If you are looking for the most accurate one, the default order is optimizing for a different thing entirely, and you have to go looking for it yourself.

The gap is widest on threads that move fast — a launch announcement, a breaking story, a dunk that takes off. The first reply to land tends to set the tone, and every reply after it is competing against a head start rather than against the original point. A well-reasoned reply posted twenty minutes in is starting from zero likes while the early, punchier reply has already been ranked into the top slots. Nothing about that ordering says which reply is right; it only says which one arrived first and landed hardest.

Reading past the ranked order

You cannot see X's actual scores or turn ranking off entirely, but you have two honest ways to read past it:

1. Switch to newest. This shows replies in the order they were actually posted, with no scoring applied. It's the closest thing to seeing the raw conversation, and it's especially useful on fast-moving or breaking threads where order matters more than popularity.
2. Read more of the list, not just the top few. Because ranking is a blend of signals and not a certainty, the third or fourth reply is often just as relevant as the first — it just arrived a little later or came from a less-established account. Scrolling past the top three changes what you find on most threads.

Neither of these beats the algorithm; they just let you see more of what's actually there instead of accepting the first few rows as the whole conversation.

There's a third habit worth building, which is treating the reply count itself as a signal. If a thread shows forty replies but the ranked view only feels worth reading for the first ten, that's usually a sign the tail is genuinely lower-signal — but not always. On threads about anything contested, the correction or the dissenting view often sits exactly where engagement hasn't caught up to it yet: past the point most readers stop scrolling. The habit of reading one or two rows past where you'd naturally stop is a small tax that pays off disproportionately on the threads that actually matter.

The SkimFast way

Switching sort order on X's own page works, but every switch reloads the view and can drop your scroll position, so checking both "best" and "newest" on a long thread means repeating that round-trip more than once. SkimFast opens the full reply thread in a popover right in your timeline, sortable in place, so flipping between ranked and chronological order doesn't cost you a new tab or your place in the feed.

A quick routine

• Catching up on a cooled-off thread → leave it on best, but scroll past the top three replies before deciding you've seen the highlights.
• Following something live → switch to newest so order beats popularity.
• Suspect the top reply is confident rather than correct → check newest for a later correction that hasn't caught up in likes yet.
• Reading a thread that matters enough to get right → check both orders once, rather than trusting whichever one X shows first.

X's ranking is a reasonable default for casual scrolling, but it is still a ranking, not a neutral record of what was said. Treating the top reply as a starting point instead of the final word is a small habit that changes what you actually notice on a busy thread. And when checking both orders by hand gets tedious, SkimFast keeps the whole thread — ranked or chronological — in one place so you can compare them without losing your spot.