Nitter and XCancel Shut Down 2026: X Kills Anonymous Tweet Viewers

September 2, 2026 · ThreadGrab

On August 24, 2026, X Corp sent cease-and-desist letters to both Nitter (the open-source anonymous X viewer) and XCancel (the largest public Nitter instance). By August 28, nitter.net was offline and xcancel.com was displaying the operator's verbatim "service stopped until further notice" notice. The move ended an eight-year run of third-party frontends that let anyone read public X posts without logging in, without ads, and without JavaScript tracking.

This is not a rate-limit or an API tweak. This is a legal shutdown — the first time X Corp has used C&D letters (rather than purely technical blocks) against the third-party viewer ecosystem. For anyone whose workflow depended on Nitter instances for reading or archiving public threads, the question is no longer "which instance should I use?" but "what should I replace Nitter with, and how do I capture a thread today before the next project is C&D'd too?"

What happened on August 24, 2026

Two near-simultaneous notices, one legal strategy. According to TechCrunch's Aug 25 report by Sarah Perez, X Corp sent cease-and-desist letters to:

• Zedeus (Nitter's anonymous maintainer) on August 24, 2026, demanding permanent takedown of Nitter instances and the project repository. Nitter's homepage now reads verbatim: "On 24 August 2026 cease and desist letters have been sent by X Corp. demanding a permanent takedown of Nitter instances and the project's repository. nitter.net is offline and development has stopped for the time being."
• XCancel operators on Monday August 24 at 8 PM EST, demanding the service cease. XCancel's homepage now reads verbatim: "On Monday 24th August at 8PM EST, we received at letter from X Corp. asking to cease and desist the service XCancel. The service XCancel is stopped until further notice."

TechCrunch reports it has viewed the letter, and notes Zedeus confirmed by email that other Nitter instances — not just nitter.net — also received C&D notices. The cease-and-desist demand was for a permanent takedown of both instances and the code repo, not a temporary halt.

The Nitter project, in plain language

Nitter is a self-hosted X frontend that fetches public posts and re-renders them without ads, tracking cookies, or any client-side JavaScript. Open source since 2018, written in Nim by a developer using the handle Zedeus. It existed because some readers did not want to open x.com to see a public thread — useful for journalists researching sources, academics archiving datasets, OSINT investigators, and anyone concerned about the tracking embedded in x.com.

Nitter's flagship instance nitter.net went dark temporarily in 2024 after X rolled out API restrictions, then came back online once instance operators adapted. The August 2026 letter is different: it is the first legal shutdown of the project, not a technical block.

The XCancel project, in plain language

XCancel was a large public Nitter instance operated independently of the Nitter project itself. By August 2024 it had become one of the most-trafficked anonymous-X viewers on the public web. Like Nitter, it stripped ads and JavaScript; unlike Nitter.net, it positioned itself as a standalone consumer product with its own domain and brand.

The XCancel operators received their C&D on Monday August 24 at 8 PM EST — approximately the same time window as Nitter's, suggesting a coordinated letter campaign from X Corp's legal team rather than two independent notices. The XCancel operators state verbatim: "We are seeking legal advice and won't share more details for now. Thank you for the trust you have put in these two years of XCancel."

Why X Corp made this move now

Two structural changes in X's platform posture line up with the timing:

1. Sign-in walls on public pages rolled out across X in late 2024 and tightened throughout 2025. Each tightening pushed more users toward third-party viewers to read the same public posts without an account. The audience for Nitter + XCancel grew as X's UX got more aggressive.
2. Read-side paywalls on Premium-only posts (X Pro tiers) gave X a fresh legal argument: even public-looking posts may be hosted under a paid gate, and a third-party viewer that fetches and re-renders them competes with the paywall — a stronger case than "scraping public data" alone.

Taken together, these moves mean a 2026 letter from X Corp can argue both (a) scraping violates the 2023 developer terms, and (b) the scraped posts may include paywalled content the viewer has no right to redistribute. That is a stronger combined posture than the rate-limit-only argument X used in 2024.

The 4-step pattern X has used against third-party viewers

Nitter and XCancel are not the first third-party X tools to be shut down. They are the latest in a sequence that maps cleanly to four escalation steps:

Each new third-party viewer that launches in 2026 inherits a legal landscape where step 4 is on the table from day one. The HN thread on the C&D reached 1,211 points and 1,348 comments within 48 hours — the audience for a successor project is large; the runway is short.

What still works (and doesn't) for reading X without an account

As of September 2, 2026, the public-tools landscape is significantly thinner:

• nitter.net — offline (C&D notice).
• xcancel.com — offline (C&D notice).
• Community-operated Nitter instances — a handful remain, but Zedeus's email to TechCrunch confirms other operators have also received C&D notices; expect further attrition.
• Direct x.com — still works but requires an account, serves ads, runs JS trackers, and increasingly requires sign-in for public-looking pages.
• X API — official, requires a developer account, paywalled tiers, and ToS prohibits bulk archival use cases.

For ad-hoc one-off reads, a logged-in x.com session remains the path. For durable access to a specific public thread — the kind of access you can show to a colleague six months from now — the path is to capture the thread today, in a stable format, and store it somewhere outside x.com.

How archive workflows change in 2026

The shutdown of Nitter and XCancel shifts the third-party-viewer ecosystem from "always-on infrastructure" to "per-thread capture at the moment you need it." Three operational patterns now make sense:

1. Capture-when-you-need-it

For a specific public thread you want to keep, capture it now as Markdown. The sooner you capture, the more durable the result — x.com edits, deletes, and sign-in-wall changes can erode a thread's public surface within days.

# Capture a public X thread as Markdown via the ThreadGrab public API
curl -sL "https://threadgrab.com/api/profile/USERNAME" \
     -H "Accept: application/json" \
     | jq '.threads[] | select(.id == "THREAD_ID")' \
     > thread.md

2. Self-host your own Nitter fork

For organizations that need an internal anonymous-X viewer (research labs, journalism outlets), running a Nitter fork is still technically possible — but the legal exposure is now explicit. If you self-host, you accept that an X Corp letter may follow. Treat the archive you build as your data, not as a public service.

3. Move capture upstream

Tools that capture X content at the moment a post is published — before any sign-in wall, paywall, or takedown notice — have a structural advantage over tools that fetch later. This is the wedge ThreadGrab has been pushing on since 2025: capture the public thread as Markdown at the moment the post is created, not hours later when x.com may have already changed the page.

A practical paired-capture recipe for the post-Nitter world:

# 1. Markdown capture via ThreadGrab public API
curl -sL "https://threadgrab.com/api/profile/USERNAME" \
     -H "Accept: application/json" \
     -o thread.json

# 2. Screenshot of the public x.com page at the same moment
#    (manual or via headless browser)
chromium --headless --screenshot=thread.png \
  "https://x.com/USERNAME/status/THREAD_ID"

# 3. Pair them in a single archive folder
mkdir -p archive/USERNAME/THREAD_ID
mv thread.json    archive/USERNAME/THREAD_ID/thread.json
mv thread.png     archive/USERNAME/THREAD_ID/thread.png

# Result: a stable Markdown + a visual proof that the post
# was public at capture time, both outside x.com

What ThreadGrab captures and what it doesn't

For full transparency, here is the line ThreadGrab sits on in the post-Nitter landscape:

• ThreadGrab captures public X posts from public profiles via the public API. Each capture stores the post text, media references, timestamps, and reply chain as Markdown.
• ThreadGrab does not bypass sign-in walls. If a post is hidden behind a login, we cannot capture it.
• ThreadGrab does not scrape at scale. We do not host a public mirror of x.com. We do not replace a Nitter instance.
• ThreadGrab does preserve the public thread you captured on a specific date, in the format you captured it, against later takedowns, edits, or paywall additions.

The point of an archive is not to defeat a platform's terms of service. The point is to keep a copy of the public thing you saw when you saw it, so that future-you can show it to future-them. That is a service any durable archive tool provides. The X Corp C&D letters of August 24, 2026 do not change that — they just make the case for capturing sooner, not later.

What this means if you were a Nitter user

If your workflow relied on Nitter or XCancel for reading public X posts, here is the practical pivot:

1. For reading one post today: a logged-in x.com session works. If you don't have an account, ask someone who does to share the canonical URL.
2. For keeping a copy of a thread: capture it as Markdown via the ThreadGrab API or any equivalent tool, and store the file outside x.com.
3. For ongoing archival of a public profile: use a tool that captures on publication, not on demand. ThreadGrab's profile endpoint can be polled; a Nitter fork cannot be relied on to stay online.
4. For research-grade evidence preservation: combine a Markdown capture with a screenshot of the public x.com page at the same moment, and store both. The Markdown gives you the text; the screenshot gives you the visual proof that the text was public at that moment.

The Nitter shutdown is a moment, not a permanent state. Someone will fork the project under a new name; X Corp will send another letter; the project will move again. That is the cycle. The way to be unaffected by the cycle is to capture the public thing you need into a stable format today, before the next round of letters goes out.

FAQ

Last verified: September 2, 2026 · Sources: TechCrunch (Sarah Perez, Aug 25 2026), Techdirt (Sep 2 2026), HN Algolia search for "Nitter XCancel cease desist," xcancel.com C&D notice, nitter.net homepage C&D notice, HN thread (Banditoz, 1,211 points, 1,348 comments).