Cloud storage & costs
Egress fees for WordPress backups: what a restore really costs in 2026
We priced a 20 GB and an 80 GB WordPress Multisite backup at Amazon S3, Wasabi, Backblaze B2, Cloudflare R2 and Hetzner, and counted the requests our own backup plugin sends for each archive.
How much does it cost to restore a WordPress backup from cloud storage?
For most WordPress networks the download itself is free: Cloudflare R2 never charges egress, Backblaze B2 includes three times your stored data, Wasabi up to your stored volume, Hetzner 1 TB a month and Amazon S3 100 GB a month before it charges $0.09 per GB [7][6][5][8][1]. The real costs sit elsewhere: Wasabi bills deleted archives for 90 days, archive classes cannot be read directly, and a broken download is paid twice.
Prices on 10 November 2026: storage, egress and minimums
All prices come from each provider's own pricing page, read on 10 November 2026, without VAT. For AWS we used the Frankfurt region; the other providers publish one price for all regions.
Amazon S3 Standard costs $0.0245 per GB-month in Frankfurt, and data leaving AWS for the internet costs $0.09 per GB for the first 10 TB each month. The first 100 GB of internet egress per month are free, but that allowance is shared by all AWS services and regions in your account [1]. Requests cost $0.0054 per 1,000 PUT and $0.0043 per 10,000 GET requests in Frankfurt [1].
Wasabi charges $7.99 per TB-month and no fees for egress or requests; if you regularly download more per month than you store, Wasabi reserves the right to limit or suspend the service. Every account pays for at least 1 TB, and every object for at least 90 days [5]. Backblaze B2 costs $6.95 per TB-month, includes egress up to three times your average stored data and then charges $0.01 per GB; the usual API calls are free and there is no minimum duration [6]. Cloudflare R2 charges $0.015 per GB-month for Standard storage and nothing for egress [7]. Hetzner charges a base price of €6.49 a month that includes 1 TB of storage and 1 TB of egress; beyond that, storage costs €0.0087 per TB-hour and egress €1.00 per TB, while S3 operations are free [8][9].
| Provider | Storage | Egress included | Egress above that | Minimums |
|---|---|---|---|---|
| Amazon S3 Standard (Frankfurt) | $0.0245 per GB-month | 100 GB per month, shared across AWS | $0.09 per GB | None; archive classes 90 to 180 days |
| Wasabi (pay as you go) | $7.99 per TB-month | Up to your stored volume | No fee; regular overuse may be limited | 1 TB per account, 90 days per object |
| Backblaze B2 | $6.95 per TB-month | 3× average stored data | $0.01 per GB | None |
| Cloudflare R2 Standard | $0.015 per GB-month | Unlimited | Not applicable | None; Infrequent Access 30 days |
| Hetzner Object Storage | €6.49 base price incl. 1 TB | 1 TB per month | €1.00 per TB | Base price for every hour with a bucket |
How many requests a backup sends: our harness count
Request fees are the line most cost calculators leave out, so we counted them for our own plugin. We ran the S3 upload and download code of Multisite Migrate Plus/Pro 1.0.33 unchanged against a simulated bucket and logged every HTTP request. Archives up to 256 KiB go up in a single PUT. Larger archives use a multipart upload with 8 MiB parts: one request to start, one per part and one to finish. A restore reads the archive back in 8 MiB ranges, one GET each.
For a 20 GB archive that makes 2,387 write requests per backup. On S3 in Frankfurt that is about $0.013 per backup, or $0.39 for 30 daily backups [1]. On R2 the same month uses 71,610 Class A operations, well inside the free million [7]. B2, Wasabi and Hetzner do not charge for these requests at all [5][6][9]. Request fees exist, but for backup archives they are cents, not dollars.
| Archive size | Upload requests | Download requests (restore) |
|---|---|---|
| 200 KiB | 1 (single PUT) | 1 |
| 100 MB | 14 | 12 |
| 1 GB | 122 | 120 |
| 5 GB | 599 | 597 |
| 20 GB | 2,387 | 2,385 |
Two worked examples: 20 GB and 80 GB networks
Both examples assume one full network backup per day, 14 archives kept in the bucket, a 30-day month and one complete restore in that month. Prices are those from the first table, excluding VAT; dollar and euro amounts are not converted. Free tiers are applied where the provider grants them: 10 GB at B2 and R2, and the 100 GB egress allowance at AWS [1][6][7].
At 20 GB the cheapest option is B2 at $1.88, followed by R2 at $4.05. The restore costs nothing anywhere, because 20 GB fits into every egress allowance, including the 100 GB at AWS. Wasabi is the most expensive option despite its low price per TB, for reasons explained in the next section [5].
| Monthly cost (14 daily archives, 1 restore) | 20 GB archive | 80 GB archive |
|---|---|---|
| Amazon S3 Standard (Frankfurt) | $7.25 (+$1.80 once the AWS allowance is used up) | $28.99 (+$7.20 once the AWS allowance is used up) |
| Wasabi | $19.85 | $56.18 |
| Backblaze B2 | $1.88 | $7.71 |
| Cloudflare R2 | $4.05 | $16.65 |
| Hetzner | €6.49 | €7.24 |
Hetzner's base price makes it expensive for very small buckets and cheap once you approach 1 TB: the 80 GB case stores 1.12 TB and adds only €0.75 to the base price [8].
Why Wasabi bills 14 backups like 90
On pay as you go, Wasabi bills every object for at least 90 days. If you delete an archive earlier, the remaining days appear on the invoice as Timed Deleted Storage [5]. Backup tools with a retention limit delete old archives all the time, and that turns the rule into a multiplier. With daily backups and 14 kept archives, each archive is billed for 90 days instead of 14: at steady state you pay for 14 active and 76 deleted archives at once.
For the 20 GB network that is 280 GB of active storage, raised to the 1 TB minimum ($7.99), plus 1,520 GB of deleted storage ($11.86): $19.85 in total [5]. Keeping all 90 daily archives would cost $14.04, less than keeping 14, because the minimum charge only applies to active storage. The rule of thumb for Wasabi: backup interval times the number of kept archives should be at least 90 days, for example 13 weekly archives instead of 14 daily ones.
The same logic applies with other periods to S3 Standard-IA and R2 Infrequent Access (30 days) and to S3 Glacier Instant Retrieval and Flexible Retrieval (90 days) [1][7]. B2 and S3 Standard have no minimum duration, and Hetzner bills storage by the hour [6][9].
In Multisite Migrate the relevant setting is “Max backups per destination” under “Cloud retention”. It defaults to 10; after each cloud upload the plugin deletes the oldest remote copies above that number, and 0 keeps all of them. With daily backups to Wasabi, the default deletes each archive after about ten days, and Wasabi still bills it for 90.
Where a restore really costs money
Egress is rarely the expensive part of a single WordPress restore. The bill grows in these five situations:
- Restores above 100 GB from S3, or in a month in which other AWS services have already used the shared allowance: from then on every GB costs $0.09 [1].
- Archives in S3 Glacier Flexible Retrieval or Deep Archive: a normal GET returns the error InvalidObjectState until you restore a temporary copy, and you pay for the retrieval and for that copy [4][1].
- Broken downloads: AWS bills the data it has already sent, and it may send more than your server received before the connection closes [1]. If a restore download fails halfway and starts again, you pay for both attempts.
- Abandoned multipart uploads: uploaded parts stay billable until the upload is completed or stopped. A lifecycle rule with
AbortIncompleteMultipartUploadremoves them after a set number of days [2][3]. - Small buckets with a minimum charge: Wasabi bills at least 1 TB, and Hetzner charges its base price for every hour in which a bucket exists, even an empty one [5][9].
The reverse also holds: if WordPress runs close to the bucket, the restore can be free regardless of size. AWS does not charge for transfers from S3 to an EC2 server in the same region, and Hetzner does not charge for traffic inside its eu-central network zone [1][9].
What Multisite Migrate does with the archive during a restore
Cloud destinations, including any S3-compatible bucket, are part of Plus and Pro; Free keeps backups on your own server. The following details come from the Plus/Pro 1.0.33 source code. A restore always needs the complete archive on the server. If the archive is still in the local backup folder, the plugin uses it and nothing is downloaded from the bucket. If only the cloud copy exists, the plugin first downloads the whole archive, also when you restore a single subsite from a network backup.
A finished download stays in the backup folder and is reused if its size matches the recorded file size, so a second restore attempt does not download again. An interrupted S3 download, however, starts over from the first byte. The plugin does not stop unfinished multipart uploads on the bucket when a job is abandoned, so the lifecycle rule from the previous section is worth adding. Uploads carry no storage class, so on AWS the archives are stored as S3 Standard unless a lifecycle rule moves them [10].
The cheapest restore is the one that never touches the bucket: keep the newest archive on the server and use the bucket as the second, offsite copy.
Checklist before you choose a backup bucket
- Multiply your archive size by the number of archives you keep.
- If the result is far below 1 TB, avoid providers with a 1 TB minimum or a base price, or accept that cost knowingly.
- On Wasabi, make backup interval times kept archives at least 90 days.
- Keep the newest archives directly readable; move only old ones into archive classes.
- On S3, add a lifecycle rule that stops incomplete multipart uploads after a few days.
- Keep the newest archive on the server as well, so most restores download nothing.
- After one test restore, compare the egress line on the invoice with your estimate.
How we tested
Prices were read on 10 November 2026 from the pricing pages of AWS, Wasabi, Backblaze, Cloudflare and Hetzner and from Hetzner's documentation. AWS rates for Frankfurt (eu-central-1) come from AWS's machine-readable price list published on 9 November 2026. All amounts exclude VAT, and we kept each provider's own unit: AWS bills binary gigabytes, the others state TB or GB as published. The worked examples are calculations, not invoices: steady state, 30-day month, one full restore, free tiers applied, no currency conversion. For the request count we ran the S3 class of Multisite Migrate Plus/Pro 1.0.33 unchanged on PHP 8.3 against an in-memory imitation of the S3 API and counted every request and byte for archives of 200 KiB, 100 MB, 1 GB, 5 GB and 20 GB. We did not upload to a real provider, so network errors, retries and provider-specific behaviour are not part of the count. Plugin behaviour during restores is taken from the same source code.
Frequently asked questions
Is restoring a WordPress backup from Amazon S3 free?
Often, yes. AWS does not charge for the first 100 GB of internet egress per month, so a restore of up to 100 GB costs only cents in request fees. The allowance is shared with all other AWS services in your account; once it is used up, S3 in Frankfurt charges $0.09 per GB.
Why does Wasabi cost more than its price per TB suggests?
Two rules: every account pays for at least 1 TB, and every object is billed for at least 90 days. A backup tool that keeps 14 daily archives deletes each one after 14 days, so Wasabi keeps billing it as deleted storage for the remaining 76 days.
Does restoring one subsite download the whole network backup?
With Multisite Migrate, yes, if the archive only exists in the cloud. A restore needs the complete archive on the server, so the plugin downloads all of it first. If the newest archive is still on the server, nothing is downloaded.
Can I keep WordPress backups in S3 Glacier to save money?
For old archives, yes, but not for the ones you would restore in an emergency. Objects in Glacier Flexible Retrieval or Deep Archive cannot be downloaded until you restore a temporary copy, which takes time and costs retrieval fees. They are also billed for at least 90 or 180 days.
Sources
- AWS: Amazon S3 pricing
- AWS: Multipart upload overview (billing of parts)
- AWS: Lifecycle rule to delete incomplete multipart uploads
- AWS: GetObject API reference (archived objects)
- Wasabi: Pricing FAQs (pay as you go)
- Backblaze: B2 Cloud Storage pricing
- Cloudflare: R2 pricing
- Hetzner: Object Storage prices
- Hetzner Docs: Object Storage overview
- AWS: Amazon S3 storage classes
Related guides and comparisons
Make your first restorable network backup for free.