It's really easy to help Tails users downloading it over BitTorrent... especially if you are already a BitTorrent user.

1. Get the latest BitTorrent files

Here are the latest available BitTorrent files:

2. Share Tails images

Feed your preferred BitTorrent client with the .torrent files downloaded at the previous step. Make sure you open and/or forward the needed ports in your router and/or firewall configuration so that you are a real seed.

3. Stay tuned!

As a contributor to Tails availability over BitTorrent, it is very important you share the very latest published version, and only this one: users need to be able to quickly download it and upgrade when we release security fixes, and there is no need to help propagate outdated versions with security flaws.

New versions are announced on:

  • our news list

  • our RSS and Atom feeds that announce new available BitTorrent files.



In order to efficiently help users download Tails images and upgrades, you need:

  • a 1Gbps Internet uplink or faster

  • 80 GiB of disk space

  • sufficiently privileged access to a HTTPS web server

  • ability to also serve the content over Rsync

  • unfiltered access to your web server (no GeoIP blocking, no IP bans, no CAPTCHAs, etc.): we want people everywhere to be able to download Tails

  • either a system operated by a professional team with on-call people 24/7, or a high-availability setup

If you satisfy these practical requirements, please read on! Else, please consider seeding Tails images over BitTorrent instead.

The big picture

All downloads are currently served from a diverse pool of mirrors (see the design document for details).

Every HTTPS mirror makes our files available under a fixed URL (e.g. that contains per-version sub-directories (such as

Our automated server-side redirector periodically checks each mirrors' health (using Rsync) and is able to redirect users to the nearest mirror based on IP geolocation data.

Alongside our mirror pool redirecting to mirrors using their own domain, we maintain a DNS Round Robin pool for the hostname. This pool serves as a fallback, we add only a few fast and reliable mirrors to it.

We only accept mirrors that provide a SSL certificate deemed valid by Firefox for the exact hostname used.

Pick a hostname for your mirror

Your web server needs to answer HTTP and HTTPS requests sent to a dedicated hostname that is unique, within our mirror pool. Furthermore, your web server should answer requests sent to (your mirror could be added to our fallback mirror pool at any moment).

Use a hostname of your choice, under a domain you control. For example, if you control, you can call your Tails mirror

Manual set up

1. Set up your web server

Set up a virtual host for the hostname chosen at the previous step. The virtual host will need to have indexing enabled.

Files must be served over HTTP and HTTPS. To be helpful in our context, this requires a certificate that is considered valid by mainstream web browsers; you can get such a certificate free of charge, from Let's Encrypt for example.

Apache configuration example

<VirtualHost YOUR_WEBSERVER_IP:80>
   RewriteEngine On
   RewriteRule ^/?(.*) https://%{SERVER_NAME}/pub/$1 [R=permanent,L]

<VirtualHost YOUR_WEBSERVER_IP:443>
   ServerAdmin YOUR_EMAIL

   SSLEngine on
   SSLCertificateFile /etc/apache2/ssl/apache.crt
   SSLCertificateKeyFile /etc/apache2/ssl/apache.key

   DocumentRoot /var/www/YOUR_PATH/
   <Directory /var/www/YOUR_PATH/>
      Options Indexes
      AllowOverride None
      IndexIgnore README.html
      IndexOptions FancyIndexing FoldersFirst IgnoreCase NameWidth=50
      IndexOrderDefault Descending Date
You can harden this configuration using the Mozilla SSL Configuration Generator.

Lighttpd configuration example

$HTTP["host"] =~ "^(\d+\.)?dl\.amnesia\.boum\.org$" {
    server.document-root = "/var/www/YOUR_PATH/"
    server.dir-listing = "enable"

nginx configuration example

server {
    root /var/www/YOUR_PATH;
    location / {
        autoindex on;

2. Download the files

Download a snapshot of the current Tails files:

rsync -rt --delete \ /var/www/YOUR_PATH/

3. Schedule the pulling of the files

Your mirror should sync every hour + a random time (maximum 40 minutes). Use cron or equivalent to schedule the same rsync command as above. For example, you can create a file in /etc/cron.d/ with this content:

0 * * * * root sleep $(shuf --input-range=0-2400 --head-count=1) && flock -n /var/run/lock/tails-mirror-rsync rsync -rt --delete /var/www/YOUR_PATH/

4. Set up a read-only Rsync server

You must also provide the archive via Rsync, as this is needed for our setup to automatically determine the health of your mirror. Please take note of the Rsync URL and include it when you send your mirrors' information to us.

You can now ask for your mirror to be added to the pool.

Go wild: ask for your mirror to be added to the pool

As soon as your web and Rsync servers are ready, please email us the HTTP and Rsync URLs so that we can add your mirror to the pool.

We will publish your email address, associated with the URL of your mirror, in a file hosted on our website. If you are not comfortable with this, give us an email alias that we can publish without revealing additional information, such as

Talk to us

To get in touch with the sysadmins who manage our pool of mirror, write to (OpenPGP key).