Buying guide

Understand Cloudways off-site backup charges

Last materially reviewed 2026-09-21

Quick answerBudget from stored backup data rather than assuming it equals the live website size.
Likely to work well when

✓ Small WordPress teams that retain application responsibility

✓ Client portfolios needing explicit ownership and exit plans

✓ Readers comparing complete configurations rather than promotional prices

Important limitations

— A promise of unlimited custom-code support

— Readers expecting guaranteed speed or search rankings

— A stable current arrangement without a demonstrated reason to move

What to know

Calculate the documented storage fee

Cloudways documents off-site backup storage at $0.033 per stored GB, with charges rounded in $0.50 increments. Check the current billing article before relying on that rate. The important word is stored: backup usage is not necessarily identical to the current live website size. Retention, changes and the services included in your particular arrangement can affect the amount that is held, so a single application-size number is an incomplete budget.

What to know

Separate the backup budget from recovery policy

Choosing a backup schedule is a business decision about acceptable data loss and restoration work. It should not be driven only by making a small bill look smaller. A brochure site updated monthly and a store receiving orders all day have different consequences when an older database is restored. First state the recovery requirement; then determine the documented configuration and stored volume needed to support it.

What to know

Check a simple calculation carefully

At the stated unit rate, a hypothetical 100 GB of stored backups produces a raw calculation of $3.30 before the documented billing rounding is applied. This is not a prediction that a 100 GB website will create that amount of storage or receive that invoice. Use actual reported backup usage and the current provider billing rules to reconcile the charge. Do not silently apply a live-disk figure as though it were a backup measurement.

What to know

Investigate before removing recovery data

If backup charges rise, compare the period, stored usage and recent application changes before altering retention. Large imports, media changes or a different operating pattern deserve investigation. Do not delete recovery material merely to make a budget worksheet match an earlier guess. Agree on the recovery consequence first, preserve any required records and document the new expectation so the next reviewer understands why the configuration changed.

Source boundary

The evidence behind this buying guidance

This guide draws on Cloudways off-site backup billing. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.

Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Cloudways off-site backup billing — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21