If you searched for bluehost backup, you want a straight answer. Does Bluehost back up your site? Can you count on it? The short version: yes, but only up to a point. And that point is smaller than most store owners and bloggers expect. According to Bluehost's own support documentation, the automatic "Basic Weekly Backup" only covers sites under 30GB. The company is unusually direct about what that promise does and doesn't cover.
What Bluehost actually includes, in its own words
Per the company's current help article on backup frequency, Bluehost runs a free, automatic weekly backup for shared-hosting accounts, but there's a catch worth knowing about upfront. It only applies to accounts opened after July 10, 2024, so if your plan predates that cutoff, the automatic job may not be running on your account at all. The only way to know for sure is to check the Backups tab in your dashboard directly, rather than assuming the feature is quietly working in the background.
This is exactly the trap that catches accounts opened before the rollout: a 2022-era account hits a plugin conflict that corrupts several database tables, and no weekly snapshot is waiting, because the automatic feature simply didn't exist yet when the account was first created.
Manual backups through cPanel are free regardless of signup date, which sounds like good news on paper, but a manual backup only helps if someone actually remembers to run it before disaster strikes. In practice, almost nobody does, and not because people are careless about their sites. A backup that needs a human to trigger it tends to get skipped during the exact week a plugin update breaks the site, or a hosting migration goes sideways without warning.
The 30GB ceiling, and what happens once you cross it
Here is the number that matters most for this keyword: Bluehost's automatic backups only cover sites under 30GB, and crossing that threshold stops the automatic job from protecting you at all. It happens faster than most people expect, because a WooCommerce store accumulates product images quickly and a media-heavy blog crosses that line after just a few hundred image-rich posts.
Bluehost doesn't send an alert when this happens. You find out during a restore attempt, not before, which is the worst possible time to learn your backup coverage quietly stopped months earlier without any warning email or dashboard notice.
Bluehost also states, in language we rarely see a host use this plainly, that its backups are not something customers should treat as a service-level promise. The company says directly it does not provide mirrored or redundant copies of customer data, and that phrasing is worth quoting rather than paraphrasing, because it tells you exactly how much weight the free tier deserves: a convenience feature, not a formal recovery commitment.
There's a related gap worth understanding before you assume you're covered. A backup can exist and still take hours to retrieve during a live outage, simply because it sits on the same shared infrastructure as the site it's supposed to be protecting. Existence and recoverability turn out to be two very different things in practice.
The paid add-on, and where it still falls short
If the free tier's 30GB cap is a problem, Bluehost's answer is the "Site Backup & Restore Tool." It's a paid add-on, sold separately, managed from the same Backups tab. It moves you from weekly to daily backups. That closes part of the gap.
It does not change where the backup lives, though. Even when the paid add-on's backup is intact after a server-side incident, it still lives on Bluehost's own infrastructure, tied to that specific account. Restoring it means staying inside Bluehost's own tools and timeline, start to finish.
That's a structural limit, not a complaint about execution. A backup stored by your host, for your host's account, isn't portable. Not if your host has an outage. Not if you want to migrate away. Not if your account gets suspended over a billing dispute. Any of those three scenarios can happen to any account, and in each case, the backup that actually matters is the one sitting somewhere else entirely.
How to check your own exposure in under five minutes
You don't need our tool for this part. Log into your Bluehost dashboard. Open the Backups tab. Check three things. First, does a "Basic Weekly Backup" job show a recent run date? Second, was your account opened before or after July 2024? Third, roughly how large is your site — files plus database combined?
If you're near or past 30GB, or the backup list is empty, treat that as your answer. The free tier either isn't covering you fully, or isn't covering you at all.
Typically, store owners discover the size problem first. Product images and order history grow a database fast. Bloggers tend to discover the signup-date problem first, since older accounts never had the newer automatic job switched on. Either way, the fix is the same. You need a backup that doesn't depend on Bluehost's size thresholds, Bluehost's uptime, or Bluehost's account status to keep existing.
What an offsite backup actually changes
This is the exact gap an offsite, host-independent backup is built to close. Our BackupYourSite backup plans run on a separate schedule from whatever Bluehost is or isn't doing automatically. Copies are stored off Bluehost's infrastructure entirely. They stay retrievable even if your hosting account itself becomes inaccessible for billing or security reasons.
The pattern is consistent: sites that already have an independent backup in place before the 30GB cap or the account-tied storage ever becomes relevant recover fastest. Sites that wait until the incident to look for a backup risk losing anywhere from a few hours to several days of content and orders.
This gap isn't unique to Bluehost. We've written about the same structural problem on SiteGround and on GoDaddy. The shape repeats across almost every host that ties backups to the account they're protecting. A backup stored in the same place as the thing it protects shares that thing's risks: a compromised login, a lapsed card on file, a shared-server incident that takes out dozens of accounts at once.
What outside guidance says about this
Government guidance on data protection points the same direction. The Cybersecurity and Infrastructure Security Agency's advice (cisa.gov) recommends keeping backup copies physically or logically separate from the system being protected. The reason is specific: a single compromised account or server shouldn't be able to take out both the live site and its only backup in one event.
FEMA's small-business continuity guidance at ready.gov makes a parallel point for operators who aren't running enterprise IT teams. A recovery plan that depends on one provider, one account, and one physical location isn't really a recovery plan. It's a hope that nothing ever goes wrong with that one provider, account, or location at the same time something else does.
A size, a signup date, or an account status problem they didn't know existed until the week they needed a restore — that's a common way these conversations start. That's not a criticism of Bluehost specifically. It's what happens any time a backup and the thing it protects share a single point of failure.
Signs your current backup setup won't hold up
A few warning signs come up again and again, and most of them are easy to check without any technical background. If the Backups tab shows a last-run date that's more than two weeks old, the automatic job has probably stopped running, even if it ran reliably when the account was first set up. If your media library has grown past a few thousand images, or your orders table has thousands of rows, you're likely closer to that 30GB line than you think, since database size grows quietly in the background while nobody's watching it.
Another sign is simpler to spot. If you've never tried restoring from a Bluehost backup, you don't really know whether it works. You only know a file exists somewhere in their system. The rule worth repeating: a backup you haven't test-restored at least once is just an assumption, not a real safety net. The test itself costs nothing but twenty quiet minutes on a staging copy.
One more sign, and the easiest one to miss: check whether your plan is even on the list of accounts that qualify for the free automatic job in the first place. Some older Bluehost plans were grandfathered out of the 2024 rollout entirely, which means the Backups tab can look empty for reasons that have nothing to do with your site size at all.
Cost of doing nothing vs. cost of closing the gap
A 2026 site rebuild after total data loss commonly runs from several hundred to several thousand dollars in developer time alone. That's before counting lost orders or lost search rankings during the downtime itself. An independent, offsite backup plan costs a small monthly fraction of that single rebuild cost. Most site owners only run this comparison once, after the first incident hits them. The ones who run it earlier tend to skip the incident entirely, because the gap gets closed before it ever gets tested by bad luck.
None of this requires technical skill to act on. It just requires treating the free backup as what Bluehost itself says it is: a convenience, not a guarantee, and a reason to keep one more copy somewhere Bluehost doesn't control.
Frequently Asked Questions
Does Bluehost automatically back up my WordPress site?
Yes, for shared-hosting accounts opened after July 10, 2024, and only for sites under 30GB. Older accounts and larger sites may not be covered by the automatic job at all.
What happens if my site is bigger than 30GB on Bluehost?
Per Bluehost's own documentation, the automatic weekly backup only covers sites under 30GB. Past that size, the free automatic backup stops protecting the full site. There's no built-in alert telling you this has happened.
Can I rely on the Bluehost backup as my only copy?
We wouldn't recommend it. Bluehost itself says plainly that it does not provide mirrored or redundant copies of customer data, and treats the automatic job as a convenience rather than a formal recovery commitment.
Does the paid Site Backup & Restore Tool fix the 30GB problem?
It moves you to daily backups, which helps. But the backup still lives on Bluehost's own infrastructure, tied to your account. It doesn't make the backup portable if the account itself becomes inaccessible.
Can I back up my Bluehost site manually for free?
Yes, manual backups through cPanel are free on any Bluehost plan. The trade-off: someone has to remember to run them before something goes wrong, which in practice happens less often than people assume.
Why would I need a backup separate from my host?
Because a backup stored on the same account as your live site shares that account's risks: suspension, billing disputes, shared-server incidents. CISA's own data-protection guidance recommends keeping backups logically separate from the system they protect for this exact reason.
How is BackupYourSite different from Bluehost's built-in backup?
BackupYourSite stores copies off Bluehost's infrastructure on an independent schedule, so the backup stays retrievable even if your Bluehost account, server, or billing status changes. See our features page for the full breakdown.
Does this apply to Bluehost WooCommerce stores too?
Yes. If anything, stores hit the 30GB ceiling sooner than blogs, since product images and order history grow the database faster than typical content pages.
How long does a Bluehost restore usually take?
It varies by site size and incident type, but restores that stay inside Bluehost's own tools during a live outage can take hours rather than minutes, since the backup and the broken site share the same infrastructure.