How to see comments on X, even signed out

#How to see comments on an X post

Comments on X are called replies, and they live on the post's own page, which opens when you tap the post itself. The steps are the same in the X app for iPhone and Android and on x.com in a browser. The free Twitter Replies Viewer lists the public replies of any post from its link.

1. Open the post. Tap or click its text, the empty space around it or its timestamp. The speech-bubble icon only opens a box to write your own reply.

2. Scroll past the counts. The replies run down the page under the post, the reply count and the other buttons.

3. Choose the order. Above the first reply, a sort menu starts on Most relevant. Switch to Most recent for the newest replies or Most liked for the most popular; the app may call the default Trending replies. X added the menu in August 2024 (opens in a new tab).

4. Open a branch. Replies to a reply sit in their own branch. Tap the reply, and it opens as a page with its replies underneath.

5. Load the rest. At the end of a long conversation, tap Show probable spam to load the replies X filtered out of the list.

Anyone's replies, your own included, are also collected on their profile's Replies tab, newest first. That tab shows what one account said across X; the post's own page shows what everyone said under one post.

#What X's reply buttons mean

Each button around a conversation on X opens a different set of replies, and none of them deletes or changes anything. Only two of them, Show probable spam and the hidden-reply icon, open replies that X keeps out of the main list; the rest load, sort or expand what is already there.

• Speech bubble with a number

  What it does

  Opens a box to write your own reply; the number counts every reply

  Where you see it

  Under every post

• Most relevant, Most recent, Most liked

  What it does

  Sorts the replies: X's ranking, newest first or most liked first

  Where you see it

  Above the first reply

• A count under a reply, such as "View 2 replies" or "See 1 more reply"

  What it does

  Opens the branch of replies written to that reply

  Where you see it

  Under a reply that has replies

• Show more replies

  What it does

  Loads the next part of a long list; older guides use the name for the spam layer

  Where you see it

  End of the loaded replies

• Show probable spam

  What it does

  Loads the replies X rated as likely spam or lower quality

  Where you see it

  End of the conversation

• Hidden-reply icon

  What it does

  Opens the replies the post's author hid; anyone can open it

  Where you see it

  Bottom right of the original post

• "See all the replies" with Continue to X

  What it does

  The signed-out limit: log in to read past the first replies

  Where you see it

  x.com without an account

• This post is unavailable

  What it does

  Stands in for a reply you can't see, such as one from an account you muted

  Where you see it

  In place of a reply

X's help page on replies (opens in a new tab) explains the default order. Replies are not shown in time order: X ranks a reply higher when the post's author answered it, when you follow the person who wrote it, or when that person pays for Premium. Show probable spam holds replies X judges from the replier's past behavior and the reply's content.

#Why you can't see all the comments on X

The reply count on a post includes replies you can't see: X filters some, the author hides some, privacy keeps some, and very busy posts can't show them all. Five of the ten causes below take one tap or one setting to undo; the rest come from privacy or deletion, and no app or tool can show those replies.

• X filtered it as probable spam

  How to tell

  Show probable spam at the end of the conversation

  Can you still see it?

  Yes, tap the button

• The author hid it

  How to tell

  The hidden-reply icon on the original post

  Can you still see it?

  Yes, tap the icon

• It ranks low on a busy post

  How to tell

  The default Most relevant order

  Can you still see it?

  Yes, switch to Most recent

• You muted the account and don't follow it

  How to tell

  The account is in your Muted list

  Can you still see it?

  Yes, unmute it

• You muted a word it contains

  How to tell

  The word is in your Muted words

  Can you still see it?

  Yes, remove the word

• The replier's account is protected

  How to tell

  A lock on their profile

  Can you still see it?

  Only if they approve your follow

• The author limited who can reply

  How to tell

  A line under the post says who can reply

  Can you still see it?

  No, the reply was never possible

• The reply was deleted or its account suspended

  How to tell

  A lower count, or This post is unavailable

  Can you still see it?

  No

• The post has an overwhelming number of replies

  How to tell

  The list stops loading long before the count

  Can you still see it?

  Partly, with another sort or the API

• You're signed out

  How to tell

  The "See all the replies" panel

  Can you still see it?

  Sign in

The muting rows come from X's pages on muting accounts (opens in a new tab) and muted words (opens in a new tab): replies from muted accounts you don't follow disappear from conversations, and muted words remove matching replies too. The conversation settings (opens in a new tab) let an author allow replies only from accounts they follow, accounts they mention or verified accounts, and change that midway. For very busy posts, X's help with replies (opens in a new tab) says it "is unable to show all of these replies".

Being blocked is not on the list. X's blocking page (opens in a new tab) says accounts you block can still see your public posts, so a public account that blocked you can't hide its replies from you. If the missing replies are your own, that is a visibility question about your account: start with what a Twitter shadowban is.

#How to see hidden replies on X

Open the original post and tap the hidden-reply icon at its bottom right: it appears only when the author has hidden at least one reply, and anyone can open it.

1. Open the original post. Hidden replies belong to the post that received them, not to the timeline.

2. Find the hidden-reply icon. No icon means the author hid nothing.

3. Tap it. A page lists every reply the author hid, ready to read and answer.

Hiding moves a reply out of the conversation without deleting it, and the person who wrote it gets no notice. The author can unhide it at any time. Two kinds never reach that page: hidden replies from protected accounts, and hidden replies their writers later deleted. The feature works in the X apps and on x.com, not in X Pro. Replies behind Show probable spam are a separate group that X chose, not the author.

#How to read comments on X without an account

Without an account, x.com shows a post and only its first few replies, so a viewer that reads public replies is the reliable way to see the rest. We opened three public posts from X's own developer account, @XDevelopers, on x.com while signed out on Nov 2, 2026. Swapping x.com for xcancel.com in a post's link now opens a page saying the service is suspended.

To read the replies of any public X post without an account, use Sorsa API Replies Viewer, the free tool linked above: no X login, 20 replies a check, top, newest or most liked first. Paste the post's link and choose top, newest or most liked first: the viewer shows 20 replies a check, each with its author and their follower count. These are the same three orders as X's sort menu: Most relevant, Most recent and Most liked. Replies to a reply open the same way, and the list saves as a CSV file. To collect every reply of a long conversation, the API route below pages through them 20 at a time. Replies from protected accounts stay private everywhere.

#How to get every reply to a post with Sorsa API

To collect every reply of a post as data, page through Sorsa API's POST /comments (opens in a new tab), which returns up to 20 replies per request with the full author profile. Each response's next_cursor leads to the next 20 until none is left. Researchers, moderators, giveaway hosts and brand teams use it when reading a thread is not enough.

1. Get a key. Sign up and copy your API key from the dashboard. The first 100 requests are free, about 2,000 replies.

2. Request the first page. Send the post's link or ID as tweet_link, with order_by set to Relevance (the default), Recency or Likes.

   curl -X POST "https://api.sorsa.io/v3/comments" \
     -H "ApiKey: YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"tweet_link": "2115302847719350272", "order_by": "Recency"}'
   

   {
     "tweets": [
       {
         "id": "2115318840027283456",
         "full_text": "Caraway in the rye, please. Pick-up on Saturday?",
         "created_at": "2026-10-30T15:12:08Z",
         "likes_count": 41,
         "reply_count": 4,
         "is_reply": true,
         "in_reply_to_tweet_id": "2115302847719350272",
         "in_reply_to_username": "maple_street_bakes",
         "conversation_id_str": "2115302847719350272",
         "user": {
           "id": "1730446120995815424",
           "username": "rye_bread_regular",
           "display_name": "Dana R.",
           "followers_count": 1288,
           "verified": false
         }
       }
     ],
     "next_cursor": "DAACCgACG9Ew2xQAJxAKAAMb0TDbE__6sAgABAAAAAIAAA"
   }
   

   Show full response

3. Follow the cursor. Send next_cursor back in the body with the next request until a response comes without one.

4. Write the rows. Save each page as it arrives, so even a thread of 100K replies never sits in memory at once.

   import csv
   import requests
   
   URL = "https://api.sorsa.io/v3/comments"
   HEADERS = {"ApiKey": "YOUR_API_KEY"}
   POST = "https://x.com/maple_street_bakes/status/2115302847719350272"
   
   
   def export_replies(post_link, path="replies.csv"):
       body = {"tweet_link": post_link, "order_by": "Recency"}
       with open(path, "w", newline="", encoding="utf-8") as f:
           out = csv.writer(f)
           out.writerow(["id", "username", "created_at", "likes", "text"])
           while True:
               r = requests.post(URL, headers=HEADERS, json=body)
               r.raise_for_status()
               page = r.json()
               for t in page.get("tweets", []):
                   out.writerow([t["id"], t["user"]["username"],
                                 t["created_at"], t["likes_count"],
                                 t["full_text"]])
               cursor = page.get("next_cursor")
               if not cursor:
                   break
               body["next_cursor"] = cursor
   
   
   export_replies(POST)
   

   const URL = "https://api.sorsa.io/v3/comments";
   const headers = {
     ApiKey: "YOUR_API_KEY",
     "Content-Type": "application/json",
   };
   const body = { tweet_link: "2115302847719350272", order_by: "Recency" };
   
   const replies = [];
   do {
     const res = await fetch(URL, {
       method: "POST",
       headers,
       body: JSON.stringify(body),
     });
     const page = await res.json();
     replies.push(...(page.tweets ?? []));
     body.next_cursor = page.next_cursor;
   } while (body.next_cursor);
   
   console.log(`${replies.length} replies`);
   

A reply's own replies form a branch: when reply_count is above 0, send that reply's ID as tweet_link and page through it the same way. A 403 means the key is missing or out of requests, and a 429 means more than 20 requests in one second; failed requests are never charged. To check whether one account replied, for a giveaway or a campaign, GET /check-comment (opens in a new tab) answers in one request with the reply itself, as the Twitter verification API guide shows.

Good to know

The count under a post is not the list. It includes replies nobody can read, such as protected accounts' replies and deleted ones that stay counted for a while, so a full collection usually returns fewer replies than the count shows.

#What it costs to collect replies from X

Sorsa API collects replies from $0.07 per 1,000, with each author's profile in every reply. The official X API charges $5.00 per 1,000 replies today and $15.00 per 1,000 once it starts billing each reply's author on Nov 22, 2026.

The official X API has no endpoint for a post's replies. Its conversation ID guide (opens in a new tab) has you search for conversation_id: plus the post's ID, and its search endpoints (opens in a new tab) reach only the last 7 days unless you pay for full-archive search, read by read. Each post read costs $0.005 on its pricing page (opens in a new tab), and an Oct 23 notice (opens in a new tab) adds $0.010 for every author returned with a post from Nov 22. It also needs a developer account, OAuth and prepaid credits, and pay-per-use stops at 3M post reads a month.

For collecting replies, four things decide the choice: the price per 1,000, how far back it reaches, whether the author comes with each reply, and the setup. Sorsa API answers each one: from $0.07 per 1,000, any public post with no 7-day window, the author's profile in every reply, and one API key with no developer account. Every plan runs at 20 requests per second, and one call to any endpoint counts as one request.

#Start with the replies you need today

Open the post, pick the order and check the two buttons that hold the rest; without an account, paste the link into the free viewer. When you need every reply as data, use Sorsa API: POST /comments returns 20 replies per request with their authors, from $0.07 per 1,000. The 100 free requests read your first 2,000 replies.

#FAQ