Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Backups & maintenance · Explainer

Where to Store WordPress Backups

Short answer

Store WordPress backups off your server, in at least two places you control, such as cloud storage and a local copy. WordPress guidance advises keeping 3 to 5 recent backups in different locations, so one failure cannot take them all. Check that each copy restores on a staging site before you need it.

Key takeaways

  • Keep 3 to 5 recent WordPress backups in different places, not all on your hosting server.
  • Google Drive gives up to 15 GB free, shared with Gmail and Photos, while Dropbox Basic gives 2 GB.
  • UpdraftPlus sends free backups to Google Drive, Dropbox or Amazon S3, and Premium adds more destinations.
  • WP Engine keeps 30 days of backups offsite on Amazon S3, with downloads available for up to 7 days.
  • A backup only counts once you have restored it on a staging site and confirmed it works.
  • Check storage space often, because a full cloud account can stop new backups without a clear warning.

Where should you store WordPress backups?

Store WordPress backups off your server, in at least two places you control.

The WordPress Developer Resources handbook advises keeping 3 to 5 recent backups in different locations, such as the hosting server, cloud storage and a local computer.

Learn WordPress gives the same advice in its backup lesson: store a copy away from your web server, and name Dropbox and Google Drive as good options.

One copy is not a backup plan. If the only copy sits on the same server as the site, a server failure can take both at once.

A simple starting setup is one copy with your backup tool, one copy in cloud storage and one copy downloaded to your computer.

Our guide to restoring a backup with UpdraftPlus shows how to use a copy once you have one.

Why is storing backups on your server not enough?

Storing backups only on your server leaves them exposed to the same failure that takes down your site.

UpdraftPlus stores backups on your hosting server by default, in a folder called UpdraftPlus inside wp-content, and its docs strongly advise moving them to remote storage.

Its docs spell out the risk: a server crash or a loss of service at your host can leave you unable to reach the backup files.

Kinsta shows the same gap from the host side. Its docs say each backup is stored on the same host machine as your site, as a full snapshot of files, database, redirects, Nginx settings and MyKinsta settings.

WP Engine stores its backups offsite on Amazon S3 in the same region, encrypted in transit and at rest, which protects against a single server failure.

Jetpack stores its backups on WordPress.com servers, not on your host, which is one reason its copies survive a host failure.

Our review of Jetpack VaultPress Backup covers how its offsite storage and restore options work.

Even so, a host copy depends on your host account. If you lose access to that account, reaching the copy can be hard, so keep one copy you control outside the host.

What does a 3-2-1 storage plan look like for WordPress?

A 3-2-1 plan means three copies of your site, on two different kinds of storage, with one copy offsite.

WordPress guidance points to the same shape: keep at least 3 to 5 recent backups, and store them in different places, such as the server, cloud storage and a local computer. The WordPress Developer Resources handbook gives that advice.

For a small site, that can mean a weekly full backup from your plugin, a copy sent to Google Drive, and a monthly download to an external drive.

CopyWhere it livesWhat it protects against
1Backup tool or hostA bad update or a deleted file
2Cloud storage such as Google DriveA server failure at your host
3Local drive or second cloud accountLoss of access to the host or the first cloud account

The numbers are less important than the spread. Two copies in the same account or on the same server do not give you two independent chances to recover.

Which cloud storage options work best?

Google Drive suits most small sites, Dropbox suits small sets, and Amazon S3 suits large sites that need room to grow.

Google gives each account up to 15 GB of storage at no charge, shared across Drive, Gmail and Photos, and Google One plans start at 100 GB. Google Drive Help lists those limits.

Dropbox Basic gives 2 GB of free storage for one person, with up to 3 connected devices and 30 days of file recovery and version history.

That 2 GB limit matters. A site backup larger than 2 GB will not fit in a free Dropbox account, so check your backup size before you pick a destination.

Amazon S3 has no fixed free allowance like Drive or Dropbox. AWS docs describe S3 Standard as the default class, with Standard-IA for data you rarely read and Glacier classes for long-term archives.

OptionFree space as of November 2026Best forWatch out for
Google DriveUp to 15 GB, shared with Gmail and PhotosSmall and medium sitesThe 15 GB is shared, so Gmail and Photos eat into it
Dropbox Basic2 GBSmall sites and single backupsThe limit is small for media-heavy sites
Amazon S3No fixed free allowanceLarge sites and long retentionYou pay for storage and downloads, and setup takes more steps
UpdraftVault1 GB included with UpdraftPlus PremiumUpdraftPlus users who want one-click setupThe included 1 GB is small for large sites

UpdraftVault is built on Amazon S3 and comes with 1 GB included in every UpdraftPlus Premium purchase, with more storage available to buy.

What should you know about host backups?

Host backups help with quick rollbacks, but their retention is short and their copies stay tied to your host account.

Kinsta makes a daily automatic backup for every site, and it also creates system backups when you restore, push staging to live, run search and replace, update a theme or plugin, or reset a site.

WP Engine makes daily backup checkpoints automatically and keeps 30 days of backups, with manual checkpoints you can create before updates.

A prepared WP Engine backup ZIP stays available to download for up to 7 days, and WP Engine says there is no way to automatically export its backups to another service.

Kinsta also takes a snapshot of every machine every 8 hours and keeps it for 24 hours, but those snapshots are for disaster recovery only and cannot be requested for a normal site restore.

Our guide to Kinsta backups lists what Kinsta keeps and for how long.

Our guide to WP Engine backups lists the same details for WP Engine.

How do you send backups to Google Drive or Dropbox with UpdraftPlus?

In UpdraftPlus, you pick Google Drive or Dropbox under remote storage, save the settings, and approve access to that account.

Both options are in the free version of UpdraftPlus. Its docs list Google Drive, Dropbox, OpenStack Swift, Rackspace Cloud, Amazon S3 and DreamObjects as free remote storage choices. The UpdraftPlus docs name each one.

The setup runs from the Settings tab. Choose the service, save your changes, and follow the link to sign in and allow UpdraftPlus to reach that account.

UpdraftPlus Premium adds more destinations, including Microsoft OneDrive, SFTP, Microsoft Azure, Google Cloud, Backblaze B2, pCloud and WebDAV.

Premium also lets you send backups to more than one place at once, so one run can fill both your cloud copy and a second destination.

Email is listed as an option too, but it is a poor fit for full backups. UpdraftPlus docs warn that mail servers often cap messages at 10 to 20 MB, so anything larger is unlikely to arrive.

Is Amazon S3 a good place for WordPress backups?

Amazon S3 is a good fit for large sites and long retention, but it needs more setup than Google Drive or Dropbox.

AWS docs say S3 Standard is the default class for data you read often, while Standard-IA suits long-lived data you rarely read but still need fast when you do.

AWS lists storing backups as an example use for Standard-IA, and notes that the class suits objects larger than 128 KB that you plan to keep for at least 30 days.

For archives you almost never open, Glacier classes cost less to store but take longer to retrieve, and they carry minimum storage periods and retrieval fees.

S3 Intelligent-Tiering can move objects you have not touched for 30 days to a cheaper tier, and after 90 days to an archive tier, with no retrieval fee for the tiering itself.

How do you keep stored backups safe?

Keep stored backups safe by limiting who can reach them, turning on two-step sign-in, and keeping the backup account separate from your daily accounts.

A backup copy is only useful if you can still open it. Use a strong, unique password on the storage account and turn on two-step verification where the service offers it.

Dropbox protects files in transit and at rest, and offers two-step verification plus an account page that lists linked devices and active sessions.

Do not store backups in a public folder or a shared link anyone can open. Keep the folder private and share nothing from it unless you mean to.

WP Engine warns that third-party backups should never be stored on the same server as your website, because local storage is limited and excess storage can hurt performance.

Write down where each copy lives and who can reach it. If only one person knows the backup account, a lost password can lock you out of every copy at once.

How do you check that a stored backup will restore?

You check a stored backup by downloading it, restoring it on a staging site, and confirming the site works there.

Jetpack lets you download a backup as a .tar.gz file from WP Admin or Jetpack Cloud, and you can choose which items to include, such as themes, plugins, the database or media.

WP Engine lets you prepare a full or partial backup as a ZIP, then download it from the Backups page for up to 7 days.

When you restore the copy on staging, log in, open pages, check media and submit a form. If any step fails, the backup set is not ready to trust.

Repeat the check after you change storage settings. A new destination, a new password or a full storage account can break a schedule without an obvious warning.

  • Download the newest backup from each destination once a month
  • Confirm the file size looks right for your site
  • Restore it on staging and log in
  • Note the date you last confirmed a restore

What mistakes should you avoid?

The most common mistake is keeping every copy in one place, so one failure takes them all.

  • Storing the only copy on the same server as the site
  • Letting a free cloud account fill up, so new backups stop saving
  • Forgetting the database and backing up files only
  • Using an email account for backups larger than 20 MB
  • Never downloading a copy to check it opens

The WordPress Developer Resources handbook warns that a full restore needs both files and the database, and keeping 3 to 5 copies in different places guards against one copy failing.

A full Drive or Dropbox account can fail quietly. Check the free space in each account when you check your backup list, and clear old sets before the account fills.

If you move hosts, download a fresh copy before you cancel the old plan. Host backups stay tied to that account, so they may not follow you.

Our comparison of UpdraftPlus vs host backups explains why your own copy matters when you move.

Frequently asked questions

Is it safe to store WordPress backups in Google Drive?

Yes, for most small sites, as long as the account uses a strong password and two-step sign-in. Google gives each account up to 15 GB free, shared with Gmail and Photos, so check that your backup fits. Keep a second copy somewhere else, because one account is still one point of failure.

How many backup copies should you keep?

WordPress guidance says to keep at least 3 to 5 recent backups in different locations. That gives you room to restore an older copy if a problem goes unnoticed for days. A busy store may keep more, while a small blog can stay near the lower end.

Can you store backups on the same server if you also use a plugin?

A plugin copy on the server is useful for a quick rollback, but it does not protect you if the server fails. UpdraftPlus docs advise storing backups remotely for that reason. Send at least one copy to cloud storage or download it, so the backup survives a server problem.

What is the cheapest way to store WordPress backups offsite?

Start with the free space you already have. Google Drive gives up to 15 GB free, and UpdraftPlus can send backups there at no extra cost in its free version. If your backups outgrow that space, compare a paid Drive plan with S3, and check the price of downloads as well as storage.

Do host backups replace your own offsite copy?

No. Host backups help with quick rollbacks, but retention is short and the copies stay tied to your host account. WP Engine keeps 30 days and offers no automatic export, while Kinsta stores backups on the same host machine as the site. Keep your own copy outside the host.

Sources

  1. Backups WordPress Developer Resources
  2. Where UpdraftPlus backups are stored TeamUpdraft Documentation
  3. Buy more Google storage Google Drive Help
  4. Dropbox Basic (Free account) Dropbox
  5. Understanding and managing Amazon S3 storage classes Amazon Web Services
  6. Backups and Disaster Recovery Kinsta Docs
  7. Backup and Restore WP Engine Support

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test