The short version: there's no neat "replies" tab on someone's profile anymore, so you have to use X's advanced search with the "from:" and "filter:replies" operators to pull up every reply a specific account has posted. It takes about 30 seconds once you know the exact search string, and I'll give you the worked example below.
Why X hides this in plain sight
When you land on someone's profile, you get Posts, Replies, Highlights, Articles and Media as tabs. The Replies tab exists, but here's the catch nobody mentions: it only shows replies where the person's original post or thread continuation is visible to you, and X's own filtering decides what counts as "worth showing." If the account is private, if you've muted them without realising it, or if their reply is to someone who's blocked you, that reply simply won't appear in the tab even though it exists.
So the Replies tab is a filtered version of reality, not the full record. That's the uncomfortable bit most how-to posts skip over because it makes the feature sound less useful than it's marketed to be.
Method 1: the profile Replies tab (the basic route)
- Go to the person's profile
- Tap the second tab along the top, usually labelled "Replies"
- Scroll. X loads these in batches of roughly 20 to 40 at a time, and older replies take several scrolls to surface
This works fine for casual browsing but it's slow and incomplete, especially on busy accounts that reply dozens of times a day.
Method 2: advanced search (the one that works)
This is the method I'd use if I needed to find a specific reply someone made, say, to check what a supplier promised a customer in public before a dispute kicked off. Type this into the X search bar:
from:username filter:replies
Say you run a small e-commerce brand and a customer claims your supplier, let's call them "NorthernCraftCo" for this example, promised a refund in a public reply three weeks ago. You'd search:
from:NorthernCraftCo filter:replies
That pulls every reply from that account, newest first, with no profile-tab filtering getting in the way. You can narrow it further by adding a date range:
from:NorthernCraftCo filter:replies since:2026-01-01 until:2026-01-21
That's the exact string format X's search operators expect: YYYY-MM-DD, no slashes.
Method 3: search a reply to a specific post
If you want to see whether someone replied to one particular post rather than scanning everything, combine operators:
from:username to:otherusername
This shows every reply from "username" directed at "otherusername," which is handy if you're trying to trace a conversation thread that's since been buried under hundreds of newer replies. This pairs well with knowing how to see comments on a specific post, since replies and comments on X are technically the same thing wearing different labels depending on where you're viewing them from.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
What stops you seeing someone's replies
- They've blocked you. You won't see their replies at all, anywhere, even through search, while logged into the account they've blocked.
- Their account is private (protected). Only approved followers see anything they post, replies included.
- You've muted them. Their content still exists, you've just told X you don't want it surfaced. Check your mute list if replies have mysteriously vanished.
- The reply is to a protected account. Even if the replier is public, if they're responding to someone private, you can't see that specific exchange unless you also follow and are approved by the protected account.
- Deleted replies. Obviously gone, though if you're fast, screenshots and the Wayback Machine sometimes catch public posts before deletion, worth knowing if you're doing anything resembling due diligence.
A worked example from start to finish
Say you run a small marketing consultancy and a prospective client asks you to check whether a competitor, call them "BrightPixelAgency," has been publicly promising results they can't deliver, because this prospect got burned before and wants reassurance before signing with anyone.
- Go to search and type
from:BrightPixelAgency filter:replies - Scroll through, looking for replies to prospective clients rather than peers (these read differently, more sales-pitch, less banter)
- Narrow by date if you know roughly when the prospect first contacted them, using
since:anduntil: - Cross-reference anything suspicious against their main Posts tab to see if the same claim appears there too
Total time: usually under five minutes, which is faster than scrolling a profile tab for twenty.
Why businesses need this (not just curiosity)
I get why this sounds like it's for snooping, but there's a real business use case. If you're running social media for a brand, checking a competitor's replies tells you exactly how they handle public complaints, what tone they use, and whether they're over-promising. That's free competitive intelligence most people don't bother collecting because they assume it's hidden. It isn't. It's one search operator away.
If you're trying to build out real tracking of this kind of thing over time rather than doing one-off searches, it's worth pairing it with X's free analytics tools so you're not relying on memory for what a competitor said three months ago.
A quick note on accuracy
One thing that trips people up: if someone edited a reply, you're only seeing the current version unless you caught the original within the edit window. Worth knowing how long the edit window is before you quote a reply as evidence of anything, because what you're reading now might not be what they first posted.
If you're doing anything with legal or reputational weight riding on it, screenshot with a visible timestamp the moment you find it. Don't rely on the tab still showing the same content tomorrow.
When this whole thing just won't work
If the account you're trying to check has been deactivated rather than deleted, their replies vanish from view entirely until, and unless, they come back. That's different from being blocked, and it's worth knowing the difference if you're wondering why a trail's gone cold; there's a separate process for reactivating a deactivated account that explains what happens to old content when someone returns.
And if you're trying to see replies sent to you as DMs rather than public replies, that's a different system altogether, closer to message requests than public search.
Frequently asked questions
Can I see someone's replies if they've blocked me?
No. Blocking hides everything, including replies, from your view while you're logged into the blocked account. Logging out or using a different account that isn't blocked will show them again, though that's worth doing only for legitimate reasons, not harassment.
Why does the Replies tab show fewer results than search?
The profile tab applies its own filtering based on your relationship with the account (muted, blocked, following status) and sometimes just lags behind in loading. The search method with "from:username filter:replies" pulls a more complete record because it queries X's index directly rather than relying on the tab's cached view.
Can someone tell if I've searched their replies?
No. Viewing public replies through search or the profile tab leaves no notification or trace, same as viewing any public post.
Is there a way to see deleted replies?
Not through X itself. Once deleted, they're gone from the platform. Third-party archive tools occasionally catch public content before deletion, but there's no guarantee and no official way to recover it.
