How to Read Twitter (X) Replies Without Logging In (2026)

Updated 2026-08-27

The problem

Logged out, X shows you a single post and then blurs or collapses the conversation under it into a sign-up prompt. The replies are public content — X just uses them as a login incentive. Threads ("🧵 1/12") are hit hardest, since parts 2–12 are technically replies.

Method 1: the viewer thread page

On nitter.app, a status URL renders as a conversation page: the post, the thread above it, and replies below, no login asked. URL recipe:

x.com/karpathy/status/1234567890 → nitter.app/karpathy/status/1234567890

Honest limits: reply depth for logged-out access is not what a logged-in client gets — very long threads may show the first layers rather than every branch, and X sometimes withholds reply pages for accounts it flags as sensitive.

Method 2: the "Tweets & Replies" tab

To read what a specific person has been replying to others — often more informative than their main feed — a profile's replies tab exists as a plain URL: nitter.app/<username>/with_replies. X's own logged-out view doesn't offer this tab at all.

Method 3: search-engine fallback

When a viewer can't render a thread, the text often survives in indexes: search a distinct phrase from the post in quotes, or site:x.com "<phrase>". Thread-archiving services' pages (from the rolled-up-thread era) also rank well for older viral threads.

Why some threads still won't open

Three real cases: the author is protected (nothing public exists); the author blocks logged-out access via sensitive-content flags (X withholds the data itself); or the thread is brand-new and no cache has it yet — a retry after the live fetch completes usually works.

Frequently asked questions

Why does X hide replies from logged-out visitors?

Sign-up pressure. Replies are among the most-clicked elements, so gating them converts readers into accounts. The content itself is public.

Can I read quote-tweets of a post without an account?

Partially. Quote-tweets are surfaced by X's search, which is login-walled; a viewer shows quotes inline where the data allows, and search engines catch popular ones.

Do 'thread reader' style services still work?

The category shrank after API prices killed most bots, but archived thread pages still exist and rank in Google for older threads — worth a search before giving up.

Why does a thread show only some replies on nitter.app?

Logged-out access returns the top layers of a conversation, not every nested branch. It is a data limit on X's side, not a rendering choice.