Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/chrisbenincasa/tunarr/llms.txt

Use this file to discover all available pages before exploring further.

Tunarr 1.0 is a major release that includes significant changes to the database schema and internal architecture compared to the pre-1.0 (0.22.x) series. If you have been running an earlier version of Tunarr, you can upgrade directly to the 1.x line, but there are important things to know before you do.
There are many breaking changes between 0.22.x and 1.x. Once you upgrade to 1.0, rolling back to a previous version is not supported. Take a full backup of your Tunarr data directory before proceeding.

​
Before You Upgrade

Downgrading is not supported. If you upgrade to 1.x and encounter an issue, the only recovery path is restoring from a backup taken on the previous version. There is no in-place downgrade procedure.
Always back up your data before a major version upgrade. The steps below walk you through taking a complete backup.

​
Migration Steps

1

Note your current Tunarr version

Before making any changes, record the exact version of Tunarr you are currently running. You will need this information if you ever need to restore the backup and return to the previous version.In the Tunarr web UI, navigate to the System page. Your current version is displayed there.
2

Locate your data directory

On the System page, note the path shown for the Data Directory.
  • If you are running Tunarr in Docker, the UI will show /config/tunarr. The actual data lives in the host directory that you mapped to that container path (the left-hand side of your volume bind mount, e.g. /path/to/tunarr/data).
  • If you are running the standalone binary, the data directory is the path shown directly in the UI.
3

Shut down Tunarr

Stop the Tunarr process or container before creating the backup. This ensures the database is not written to while you are archiving it.Docker Compose:
docker compose down
Docker CLI:
docker stop tunarr
systemd (Linux):
sudo systemctl stop tunarr
4

Create a full backup of the data directory

Archive the entire data directory. Both of the examples below produce a single compressed archive you can store safely.Linux / macOS (tar):
tar -czf tunarr-backup-0.22.x.tar.gz /path/to/tunarr/data
Windows (PowerShell):
Compress-Archive -Path "C:\path\to\tunarr\data" -DestinationPath "tunarr-backup-0.22.x.zip"
Store the resulting archive somewhere outside of the Tunarr data directory.
5

Upgrade to Tunarr 1.x

Update your Docker image tag to latest (or a specific 1.x.x version) and restart the container. Tunarr will automatically run any required database migrations on first launch.Docker Compose — update the image tag:
image: chrisbenincasa/tunarr:latest
Then apply the change:
docker compose pull
docker compose up -d
For standalone binary users, download the 1.x binary from the releases page, replace the existing binary, and start Tunarr.

​
Restoring a Backup

If something goes wrong after upgrading and you need to return to your previous version, follow these steps:
1

Stop Tunarr

docker compose down
# or
sudo systemctl stop tunarr
2

Remove or rename the current data directory

mv /path/to/tunarr/data /path/to/tunarr/data.broken
3

Restore the backup archive

tar -xzf tunarr-backup-0.22.x.tar.gz -C /
Adjust the destination path to match your original data directory location.
4

Start the previous version of Tunarr

Downgrade your Docker image tag back to the version you noted in Step 1 of the migration, then start Tunarr:
docker compose up -d
You must start the exact version of Tunarr that created the backup. Starting a 1.x binary against a 0.22.x database is not supported.

Build docs developers (and LLMs) love

Get started for freeTalk to us