Updated 2026-08-27
All 'Twitter viewer' sites do the same core job — show public X profiles without login. Differences that matter: real linkable URLs (nitter.app/nasa vs a search box), thread/reply pages, RSS, and whether the operator is honest about cache age and limits. Judge any viewer by those four.
Three families exist. Classic public Nitter instances — the open-source project's survivors; most died when X killed guest accounts in 2024, a handful run on borrowed time. Commercial viewer sites (twitterwebviewer.com, tweetviewer.com and similar) — closed tools with a search box and often a paid tier. This site — a maintained Nitter fork with its own fetching infrastructure, free cached pages, and paid extras for live data.
| nitter.app | typical viewer site | surviving Nitter instances | |
|---|---|---|---|
| Profile URL you can link/bookmark | ✅ /<username> |
⚠️ often ?user= behind a search box | ✅ |
| Single posts + threads | ✅ swap domain in any status URL | ⚠️ varies | ✅ when up |
Replies tab (/with_replies) | ✅ | ❌ rare | ✅ |
| Works without JavaScript | ✅ cached pages | ❌ usually app-shell sites | ✅ |
| RSS | ✅ via rss.gurify.com | ❌ | ⚠️ sometimes, rate-limited |
| Live up-to-the-minute timeline | 💲 Fresh ($0.99 day) | 💲 varies | ⚠️ when their account pool lives |
| Email alerts on new posts | 💲 $5/mo | ❌ | ❌ |
| Keyword search | ❌ (honest: login-walled by X) | ⚠️ often advertised, often broken | ⚠️ comes and goes |
1. Linkable URLs. If profiles live behind a search box with query-string URLs, you can't bookmark, share, or find pages in search results. 2. Honesty about freshness. Every free viewer serves cached data — the question is whether the site says so. Ours: cached pages can be up to a day old; the live option is the paid one, because live fetches cost money per request. 3. A thread story. Viewing one post without its conversation is half the product — check the replies handling before trusting a viewer. 4. What they claim about search and private accounts. Full free search and any private-account access are both impossible; a site claiming either is lying about something.
Self-hosting: the open-source project with your own account pool gives you features no public site can safely offer, on your own hardware. That's the power-user path — for everyone else, instance-hunting in 2026 mostly teaches you which instances are dead.
It runs a maintained fork of the open-source Nitter codebase with its own fetching infrastructure on top. The original public flagship instance shut down in 2024; this is an independent deployment.
Each live fetch costs real money (metered API access). Cached pages amortize one fetch across every reader for a day, so they can be free; on-demand freshness can't be.
None — RSS is. A feed per account in any RSS reader beats bookmarking pages on any viewer, ours included. rss.gurify.com converts any public account to a feed.
Mostly no — they show public data like everyone else. Distrust specifically any claim of private-profile access or 'see who viewed you', which no legitimate tool can deliver.