Following legal advice, the Nitter project will continue

A free and open source alternative Twitter front-end focused on privacy and

performance.

Inspired by the Invidious project.

No JavaScript required

All requests go through the backend, client never talks to Twitter

Prevents Twitter from tracking your IP or JavaScript fingerprint

Uses Twitter's unofficial API (no developer account required)

Lightweight (for @nim_lang, 60KB vs 784KB from )

RSS feeds (instance-specific, often disabled due to abuse)

Mobile support (responsive design)

AGPLv3 licensed, no proprietary instances permitted

Embeds (see

Account system with timeline support

Archiving tweets/profiles

BTC: bc1qpqpzjkcpgluhzf7x9yqe7jfe8gpfm5v08mdr55

ETH: 0x24a0DB59A923B588c7A5EBd0dBDFDD1bCe9c4460

XMR: 42hKayRoEAw4D6G6t8mQHPJHQcXqofjFuVfavqKeNMNUZfeJLJAcNU19i1bGdDvcdN6romiSscWGWJCczFLe9RFhM3d1zpL

SOL: FF5bheiD5AqPEdc3eyjymJ8AoMRF1hS78Ht6FiSZZF1t

$Nitter: 4fSxCKc91ELQYVdv3tmHW8R15KoALPwEngyoQe1Xpump

ZEC: u1vndfqtzyy6qkzhkapxelel7ams38wmfeccu3fdpy2wkuc4erxyjm8ncjhnyg747x6t0kf0faqhh2hxyplgaum08d2wnj4n7cyu9s6zhxkqw2aef4hgd4s6vh5hpqvfken98rg80kgtgn64ff70djy7s8f839z00hwhuzlcggvefhdlyszkvwy3c7yw623vw3rvar6q6evd3xcvveypt

The wiki contains

a list of instances and

browser extensions

maintained by the community.

It's impossible to use Twitter without JavaScript enabled, and as of 2024 you

need to sign up. For privacy-minded folks, preventing JavaScript analytics and

IP-based tracking is important, but apart from using a VPN and uBlock/uMatrix,

it's impossible. Despite being behind a VPN and using heavy-duty adblockers,

you can get accurately tracked with your browser's

fingerprint, no

JavaScript required. This all became

particularly important after Twitter removed the

for users to control whether their data gets sent to advertisers.

Using an instance of Nitter (hosted on a VPS for example), you can browse

Twitter without JavaScript while retaining your privacy. In addition to

respecting your privacy, Nitter is on average around 15 times lighter than

Twitter, and in most cases serves pages faster (eg. timelines load 2-4x faster).

In the future a simple account system will be added that lets you follow Twitter

users, allowing you to have a clean chronological timeline without needing a

Twitter account.

redis/valkey

To compile Nitter you need a Nim installation, see

for details. It is possible

to install it system-wide or in the user directory you create below.

To compile the scss files, you need to install libsass. On Ubuntu and Debian,

you can use libsass-dev.

Redis is required for caching and in the future for account info. As of 2024

Redis is no longer open source, so using the fork Valkey is recommended. It

should be available on most distros as redis or redis-server

(Ubuntu/Debian), or valkey/valkey-server. Running it with the default

config is fine, Nitter's default config is set to use the default port and

Here's how to create a nitter user, clone the repo, and build the project

along with the scss and md files.

Set your hostname, port, HMAC key, https (must be correct for cookies), and

Redis info in . To run Redis, either run

redis-server --daemonize yes, or systemctl enable --now redis (or

redis-server depending on the distro). Run Nitter by executing ./nitter or

using the systemd service below. You should run Nitter behind a reverse proxy

such as Nginx or

Apache for security and

performance reasons.

Page for the Docker image:

To run Nitter with Docker, you'll need to install and run Redis separately

before you can run the container. See below for how to also run Redis using

First create your config file. The Docker commands mount it into the container,

so it has to exist on the host beforehand. If you've cloned the repo:

If you're using the prebuilt image without a local clone, download

and save it as instead.

To build and run Nitter in Docker:

A prebuilt Docker image is provided as well:

Using docker-compose to run both Nitter and Redis as different containers:

Change redisHost from localhost to nitter-redis in , then run:

Note the Docker commands mount (and for

docker-compose) from the directory you run them in. If a mounted file doesn't

exist, Docker silently creates a directory in its place and the container fails

with not a directory: Are you trying to mount a directory onto a file. Remove

that directory and create the file as shown above.

To run Nitter via systemd you can use this service file:

Then enable and run the service:

systemctl enable --now

Nitter currently prints some errors to stdout, and there is no real logging

implemented. If you're running Nitter with systemd, you can check stdout like

this: journalctl -u (add --follow to see just the last 15

lines). If you're running the Docker image, you can do this:

docker logs --follow *nitter container id*

Feel free to join our Matrix channel.

You can email me at zedeus@ if you wish to contact me personally.

For legal inquiries and DMCA requests, contact legal@