Nitter

Nitter is a free, open-source self-hosted Twitter front-end that routes every request through a backend, giving privacy-focused users an ad-free,…

  • Cloud
  • Communication
  • Media Applications
  • Other
  • Productivity
  • Tools & Utilities
Nitter is a free, open-source self-hosted Twitter front-end that routes every request through a backend, giving privacy-focused users an ad-free, JavaScript-free feed. Its upstream repository has been archived after X Corp. cease-and-desist letters in 2026, but the Docker images still work and the author is seeking legal help to keep it running.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
0GitHub repository is archived
Popular
8314,456 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM
Security check
55no serious findings, 6 minor, CI, tests, OpenSSF Scorecard 3.2/10

Availability: platform listings confirmed today, links checked 14 days ago

GitHub stars
14,456
Open issues
153
Last commit
2026-10-09
License
AGPL-3.0
Activity
stale

Checked 12 days ago - source: GitHub (zedeus/nitter)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 2 CPU core(s), 500 MB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set up nitter.conf before starting Copy `nitter.example.conf` to `nitter.conf`, then set your domain, port, a random HMAC secret, HTTPS, and Redis details. Without a valid config, Nitter won't start properly and its links may not work. source
  • Start Redis and point Nitter to it Redis is the simple cache Nitter relies on, so start it (for example `redis-server --daemonize yes`) and make sure `nitter.conf` points to the same host and port. If Redis is not running, Nitter can fail with cache/connection errors. source
  • Let Nitter start automatically Copy the provided `nitter.service` file to `/etc/systemd/system`, then run `systemctl enable --now nitter.service` so Linux starts Nitter automatically on boot. Without this, the app stops after a reboot and you must start it manually each time. source
  • Legal status X Corp. demanded takedown in August 2026; verify current availability before deploying. source
  • Legal and project status (2026) On 24 August 2026, X Corp sent cease-and-desist letters demanding a permanent takedown of all Nitter instances and the project's repository, which is now archived. The author is seeking funding and legal help (update 10 October 2026, details on nitter.net). source
  • Repository and legal status The zedeus/nitter repository is currently archived. The maintainer reports X Corp. legal takedown demands dated 24 August 2026 and said on 10 October 2026 that they are seeking funding and legal help. source

Fetched 14 days ago - each note links to its source

Alternatives (3)

  • Nitterify - Nitterify is a Web Extension redirecting X links to Nitter, an alternative, privacy-friendly, interface.
  • Squawker - Squawker is an open-source anonymous X (Twitter) client.
  • piko

Checked 51 days ago - source: AlternativeTo

Common questions

What must I change in Nitter's config before first start?

Copy nitter.example.conf to nitter.conf and set your domain, port, a random HMAC secret, HTTPS, and Redis details. Without a valid config, Nitter may not start properly and its links may not work.

Why do I get Redis cache or connection errors?

Start Redis and make sure nitter.conf points to the same Redis host and port. If Redis is not running, Nitter can fail with cache or connection errors.

How do I make Nitter start automatically after reboot?

Copy the provided nitter.service file to /etc/systemd/system and run systemctl enable --now nitter.service. Without this, Nitter stops after a reboot and must be started manually.

Why do some Twitter accounts or links error on a Nitter instance?

Some instances or links may error for certain Twitter accounts due to account-specific reliability. This can be a normal reliability limitation rather than a local configuration issue.

Answers sourced from context7.com, github.com, www.reddit.com

Community

Collected 54 days ago - public community threads