pterodactylstorages3r2

Cloud Storage Options for Pterodactyl Panel Backups

4 min read

The default: backups live on the same machine

Out of the box, Pterodactyl stores backups on the Wings node. The same physical (or virtual) machine running your game server also holds your backup files. This is like keeping your house insurance documents inside the house. Technically organized, practically useless if things go sideways.

If the node's disk fills up, your backups might get corrupted or deleted. If the node goes offline, your server and your backups disappear at the same time. If the hosting company has a bad day, everything is gone together.

For a personal server you are just messing around with, this is probably fine. For anything you would be upset about losing, it is worth knowing where the exits are.

S3 storage via Wings .env

Pterodactyl supports S3-compatible object storage for backups. The configuration lives in the Wings .env file on the node. Here is what it looks like:

AWS_DEFAULT_REGION=us-east-1
AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
AWS_BACKUPS_BUCKET=my-pterodactyl-backups
AWS_ENDPOINT=https://s3.amazonaws.com

When configured, Wings sends backup archives to your S3 bucket instead of storing them locally. This is genuinely better than local storage. Your backups survive node failures, you get effectively unlimited storage, and you can access them from anywhere.

The catch: only the panel administrator can set this up. It requires SSH access to the Wings node to edit the .env file. If you are a client on a hosting provider, you do not have this access. Your host might offer it, or they might not. Many do not, because it means they need to manage S3 credentials and storage costs.

Even when it is configured, your backups still count against the per-server limit set by the host. So you might have fancy cloud storage that can only hold two backups at a time. Progress.

Your S3-compatible options

If you are the panel admin and want to set up cloud storage, here are the main providers:

Amazon S3

The original. Reliable, well-documented, available everywhere. Pricing is straightforward for storage (about $0.023/GB/month for standard tier), but data transfer out costs money. Restoring a large backup means paying egress fees. For a few game server backups this is pennies, but it adds up if you have many servers or large files.

Cloudflare R2

S3-compatible with one major difference: zero egress fees. You pay for storage ($0.015/GB/month) and operations, but downloading your data costs nothing. This matters for backups specifically because the whole point of a backup is downloading it when you need it. If restoring is free, you are less likely to hesitate when something goes wrong.

R2 also has no minimum storage duration charges, so deleting old backups does not incur penalties. You can point Wings at R2 using the S3-compatible endpoint.

Backblaze B2

Another S3-compatible option. Storage is cheap ($0.006/GB/month), and they have a partnership with Cloudflare that makes egress free if you route through Cloudflare. Setup is slightly more involved than R2 but well-documented.

MinIO (self-hosted)

If you want to keep your storage entirely under your control, MinIO is an open-source S3-compatible server you can run on your own hardware. This makes sense if you already have spare infrastructure. If you do not, you are just adding another thing to maintain.

The real-world problem

All of the above requires panel admin access. Here is the typical experience for someone running a game server on a hosting provider:

  1. You realize you should have better backups.
  2. You look up how to configure S3 in Pterodactyl.
  3. You learn it requires editing the Wings .env file.
  4. You submit a support ticket to your host asking them to set it up.
  5. Your host says no, or says "we will look into it" and never follows up.
  6. You give up and go back to manual SFTP downloads.
  7. Three months later you lose data and wish you had not given up.

This is not hypothetical. It is one of the most common support conversations in Pterodactyl communities.

Pink Narwhal + Cloudflare R2

Every Pink Narwhal plan stores backups in Cloudflare R2 by default. There is nothing to configure. You do not need panel admin access. You do not need to submit a support ticket. You do not need to set up an AWS account or manage credentials.

Each organization gets isolated storage in R2. Your backups are completely separate from other users and completely separate from the Wings node. R2's zero egress fees mean restoring a backup does not cost you anything extra, which removes the one hesitation people have about cloud-stored backups.

The storage is handled. You just pick which servers to back up, choose a schedule, and it runs.

The bottom line

If you are the panel admin with SSH access to your Wings nodes, configuring S3 (especially Cloudflare R2) is a solid move. It takes about five minutes and meaningfully improves your backup resilience.

If you are a client on shared hosting with no panel admin access, your options through Pterodactyl are limited to whatever your host decided to configure (usually nothing). In that case, a service like Pink Narwhal that handles storage independently is the path of least resistance.

Back to all posts