Backups & maintenance · Explainer
Are Your Host's Backups Enough?
Short answer
No, not on their own for most sites. Host backups give you a handy restore point, yet they are often kept for only 7 to 30 days, stored on the host's own systems, and lost if the account closes. Add your own off-site copy on a schedule, keep several recent copies, and check that a restore works before you need one.
Key takeaways
- Host backups are a safety net, not a full backup plan for most sites.
- Retention is often 7 to 30 days, so an old problem can age out of reach.
- A backup stored only on your host can fail with the host itself.
- Keep your own off-site copy, plus the host copy, in different places.
- A backup you have never restored is only a hope, so check it on staging.
- Take a fresh backup before every update, move or redesign.
Are your host's backups enough on their own?
No, host backups alone are not enough for most sites, because they are a short-term safety net rather than a full backup plan.
Most hosts take a daily copy of your site, and that copy can save you after a bad update or a deleted file. The WordPress handbook warns that hosts back up the whole server, yet getting a copy back can take time, so recovery needs your own plan too (Backups).
The gaps are retention, location and control. A host decides how long copies live, where they sit and what is left out, and those choices may not match what your site needs.
Start by reading what your own host promises. Our guide to whether Kinsta includes backups shows one host's limits, and the same check applies to any host you use.
What does a host backup actually include?
A host backup usually holds your site files and your database, which together form the full site.
WordPress stores content in two parts. The developer handbook explains that files live in your WordPress folder while the database sits in MySQL or MariaDB, and you need both to rebuild a typical site (Backups).
WP Engine lists what its checkpoints hold: WordPress core files, themes, plugins and the database. It also lists what it leaves out, such as cache files, logs and old backup files (Backup and Restore).
Some hosts leave out email or staging copies, so read your host's list. If a part of your site is not in the backup, a restore will not bring it back.
How long do hosts keep backups?
Most hosts keep daily backups for 7 to 30 days, and the exact limit depends on your host and plan as of November 2026.
| Host | How often | How long it is kept | Can you download it? |
|---|---|---|---|
| SiteGround | Daily | Up to 30 daily copies on shared hosting | Only with Premium Backup |
| WP Engine | Daily | 30 days | Yes, as a ZIP, for 7 days |
| Kinsta | Daily | 14 days, or 30 on larger plans | One download per week |
| Hostinger | Weekly, daily on higher plans | Weekly 6 weeks, daily 7 days | Yes, files and database |
| Bluehost | Weekly, daily on higher tiers | Varies by plan | Through CodeGuard |
SiteGround keeps up to 30 daily copies on shared hosting, and its knowledge base says downloads need the Premium Backup service. Its prepared download links stay live for 24 hours, so fetch the file at once (How to download a full backup).
WP Engine keeps 30 days of backups and stores them off site on Amazon S3, with ZIP downloads open for 7 days. That off-site storage helps, yet the 30-day limit still applies (Backup and Restore).
Kinsta takes a daily backup and keeps it for 14 days on entry plans, or longer on larger plans. You can make one downloadable backup per week, and the file stays open for 48 hours (How to Restore WordPress from a Backup).
Hostinger keeps weekly backups for 6 weeks and daily backups for 7 days on plans that include them. After that, older copies are removed for good, and an expired plan gives you 30 days to download the latest copy (How to download backups at Hostinger).
Our guide to whether WP Engine includes backups lists its limits in more detail.
Our guide to whether SiteGround includes backups covers its daily copies and Premium Backup service.
What can go wrong with host-only backups?
A host-only backup can fail, expire, miss files, or vanish with the account, so one copy in one place is a weak plan.
- A hack found late. Malware can sit in a site for weeks, so every copy in a 14-day window may hold the same bad code.
- An account that ends. If you cancel or miss a payment, the host may delete the site and its backups, so your only copy goes with it.
- A restore that wipes new work. WP Engine warns that a restore is destructive, so files not in the chosen backup are removed when you roll back (Backup and Restore).
- A backup that misses parts. Cache and log files are often left out, and some hosts leave out email, so check the list of what is covered.
- A backup you cannot reach. Some hosts charge for downloads or limit them to one per week, which slows you down in a crisis.
Backups can also fail without warning. A full disk, a lost cloud link or a plugin clash can stop the run, and the next copy never arrives. Check the backup log or the cloud folder each month, so a failed run does not sit unnoticed.
Our guide to whether Hostinger includes backups shows how one budget host limits retention and downloads.
What is an off-site backup, and why does it matter?
An off-site backup is a copy kept away from your host, so a host failure cannot take both your site and its backup.
Jetpack notes that host backups often run only once a day, stay on the same setup as your site, and can be hard to restore. Its VaultPress Backup stores each change in the Jetpack Cloud, away from the host (VaultPress Backup).
The WordPress handbook gives the same idea in plain terms: keep at least 3 to 5 recent backups in different places, such as the host, cloud storage and your own computer. If one copy fails, another can still work (Backups).
Off-site does not mean far away in miles only. A second account, a different cloud service or a drive you hold all count, as long as a host problem cannot reach them.
Bluehost states the same idea as the 3-2-1 rule: keep three copies of your data, on two storage types, with one stored off site. Our guide to whether Bluehost includes backups covers its CodeGuard backup setup.
How do you add your own backup layer?
Add a backup plugin that runs on a schedule and sends each copy to cloud storage you control.
- Pick a backup plugin, such as UpdraftPlus, and install it from the WordPress plugin directory.
- Set a files schedule and a database schedule, such as daily for a busy site.
- Connect a remote store, such as Google Drive or Dropbox, and run a manual backup to check the link works.
- Download one copy to your own computer each month, and keep the newest few copies.
UpdraftPlus lists more than 4 million active installs on WordPress.org as of November 2026, and its free version can run on a schedule from every 2 hours to monthly. It can send copies to Dropbox, Google Drive, Amazon S3, FTP or email (UpdraftPlus).
If a backup run fails, see our guide to fixing UpdraftPlus backup failures before the next scheduled run.
Keep the host copy too. Two layers beat one, and the host copy is often the fastest way back after a small mistake.
How do you check that your host backups work?
Check your backups by restoring a copy to a staging site, then opening pages and forms to confirm the copy works.
A backup file that exists is not proof that it restores. Kinsta makes a fresh backup before each restore, so you can undo a restore that goes wrong, and restoring to staging leaves the live site alone (How to Restore WordPress from a Backup).
Pick a recent backup, restore it to staging, and check the home page, a post, a form and the admin area. If a page is blank or a form fails, fix the backup plan before the live site needs it.
Repeat the check after big changes, such as a new plugin or a theme switch. A backup plan that worked last year may not cover what your site holds now.
Write down where each copy lives and how old it is. A short note with the host, the plugin, the cloud folder and the date of the newest copy makes the next crisis faster, because you will not hunt for a backup while the site is down.
What mistakes should you avoid?
Avoid trusting one copy, skipping the restore check, and letting old backups age out before you notice a problem.
- Relying on the host alone, with no copy of your own.
- Keeping backups only on the same server as the site.
- Never opening a backup to check that the files and database match.
- Restoring to live without a fresh backup of the current site first.
- Forgetting email, uploads or custom tables that the backup may leave out.
- Assuming a backup from last month is still there after a short retention window ends.
Frequently asked questions
Do all hosts back up WordPress sites automatically?
Most managed and shared hosts take automatic backups, yet the schedule and retention differ by host and plan. Bluehost lists weekly backups on lower tiers and daily backups on higher tiers, while SiteGround, WP Engine and Kinsta take daily copies. Check your plan page and your host panel, and do not guess from the plan name alone.
Can I download my host's backups?
It depends on the host. WP Engine lets you prepare a ZIP of a backup point, and Hostinger lets you download files and databases from its Backups page. SiteGround needs its Premium Backup service for one-click downloads, and Kinsta allows one downloadable backup per week. If downloads are blocked, a backup plugin can send copies to your own cloud storage.
What happens to host backups if I cancel hosting?
They can go with the account, so never treat them as long-term storage. Hostinger gives you 30 days after a plan expires to download the latest backup. Download a full copy before you cancel, and keep it somewhere outside the host, such as cloud storage or your own computer.
Is a backup plugin still needed with managed hosting?
Yes, for most sites. A plugin adds a copy you control, stored off site, on a schedule you set. It also lets you keep copies after the host retention window ends. The host copy stays useful for quick restores, and the plugin copy covers the cases the host copy cannot.
How often should host backups run?
Daily suits most sites that change often, while a site that rarely changes can live with weekly copies. Add a manual backup before any update, theme change, move or redesign. If your site takes orders or bookings each day, look at hourly or real-time backups instead of daily ones.
Sources
- Backups — Advanced Administration Handbook WordPress Developer Resources
- Backup and Restore WP Engine Support
- How to download a full backup of my website? SiteGround Knowledge Base
- How to Restore WordPress from a Backup Kinsta
- How to download backups at Hostinger Hostinger Support
- VaultPress Backup: Real-Time WordPress Backups Jetpack
- UpdraftPlus: WP Backup & Migration Plugin WordPress.org
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.
Thanks — we review requests within 3 business days.
