The shutdown of Nitter following the cease and desist letters sent by X Corp on August 24, 2026, has reshuffled the deck for anyone viewing public profiles without an account. The GitHub repository was archived on August 25, 2026, and the majority of public instances followed suit in the days after. Finding a reliable alternative frontend now requires understanding the technical and legal constraints that weigh on each solution.
Scraping and undocumented APIs: the weakened technical foundation
Nitter operated by directly querying Twitter’s internal endpoints, bypassing the official paid API. This mechanism relied on reverse engineering the HTTP requests made by the web client. X Corp specifically cited this method in its cease and desist letters, labeling the process as unauthorized scraping in violation of the terms of service.
The issue is not limited to Nitter. Any third-party frontend that displays public tweets without OAuth authentication depends on unauthorized access to X’s servers. The official API v2, the only legal route, imposes fees that make a free and anonymous service economically unfeasible.
Every alternative still online either uses a cache of already collected data, relays through rotating authenticated accounts, or residual access that has not yet been blocked.
Several forks of Nitter’s source code remain technically functional. An inventory published in early September 2026 still listed a few active instances, often limited in request rates and accessible via .onion mirrors on the Tor network. Their lifespan is unpredictable: X Corp can cut access at any time by modifying its endpoints or blocking the relevant IP address ranges. We recommend considering the best alternatives to Nitter while keeping this structural instability in mind.
Functional alternatives to Nitter: what remains accessible in 2026
After the closure of Nitter, several independent tools are positioning themselves as viewers of X profiles without login. None are clones of Nitter: each adopts a different architecture to bypass restrictions.
- Bibliogram was initially designed for Instagram, but the project inspired forks adapted to X. These forks remain marginal and poorly maintained, with limited compatibility for text-only tweets (no threads, no embedded media).
- Some independent tools allow users to view public profiles and posts without authentication. They generally operate via a proxy that caches the displayed data, introducing a delay in updates ranging from a few minutes to several hours.
- Some users turn to browser extensions that inject a lightweight frontend over the x.com site, removing trackers and tracking scripts. These extensions do not eliminate the need for login but significantly reduce client-side data collection.
- The Tor network remains an option for accessing still-active .onion mirrors. Browsing is slower, and the reliability of instances varies from day to day.
None of these solutions guarantee sustainable access. The difference from the Nitter era is that the legal risk now weighs on the operators of instances, not just on end users.
Selection criteria for a viable alternative on mobile and desktop
The choice of a tool depends on the use case. A watcher aggregating tweets for reporting has different needs than an occasional user wanting to read a thread without creating an account.
Privacy and absence of trackers
Nitter did not load any third-party scripts, did not set any cookies, and did not transmit any data to X. This was its main appeal. Any credible alternative must at a minimum block X’s JavaScript trackers and not require authentication. On mobile (Android or iPhone), check if the tool works via the browser or if it imposes a dedicated app that could collect data on the device.
Compatibility with rich content
Tweets are no longer just blocks of text. Videos, audio spaces, polls, long threads with nested quotes: a viewer that displays only plain text loses a significant portion of the information. Most current alternatives do not support embedded videos, making them less useful for following visually-oriented accounts.
History and archiving
For professionals who used Nitter as a monitoring tool, the ability to consult a user’s publication history is crucial. The caches of existing alternatives generally do not go back more than a few days, whereas Nitter allowed users to scroll through a complete user’s feed.
Legal risk and sustainability of third-party frontends for X
The reasons cited by X Corp in its cease and desist letters are not limited to a simple violation of the terms of service. The platform notably cited the Texas Harmful Access by Computer Act and the Lanham Act, legal frameworks that cover unauthorized access to computer systems and trademark protection. This legal precedent changes the game for any open-source project that might want to take over.
Hosting a public viewer instance for X now exposes one to lawsuits. Unlike Invidious for YouTube, which benefits from a more ambiguous gray area, X frontends face active and documented legal action. The developers of still-active Nitter forks mostly operate anonymously, without an identifiable legal structure.
For users, the direct risk remains low: consulting a third-party instance does not constitute an offense in itself. However, the fragility of these services means that backup solutions must be planned. The RSS feeds generated by some instances, when they still function, offer a way to receive updates without relying on a specific web frontend, but their reliability declines as X tightens its restrictions.
The current situation resembles a game of cat and mouse where X Corp has vastly superior legal and technical resources. Relying on a single replacement tool would be a mistake: diversifying access methods (browser extensions, RSS, Tor mirrors, web caches) remains the most resilient strategy for continuing to view X content without an account or tracking.
