Search this question and you get one answer everywhere: back up daily. It sounds responsible. For a lot of sites it is also either overkill or nowhere near enough, because frequency has nothing to do with what is fashionable and everything to do with how fast your site changes.
There is a simple way to work out the right number for your site, and it takes about five minutes.
Start with the only question that matters
Backup frequency is really one question in disguise: how much work are you willing to redo?
Every scheduled backup has a gap. If backups run weekly and the site dies on day six, you lose six days. If they run four times a month, the worst case is roughly a week. If they run hourly, you lose an hour. Nothing removes the gap entirely, it only gets smaller and more expensive.
So put a number on the gap. Ask yourself: if everything from the last seven days vanished right now, what exactly disappears, and what would it take to rebuild?
For a lot of small business sites, the honest answer is "two blog posts and a couple of contact form entries that also went to my email anyway." That site does not need hourly backups. For a store doing 40 orders a day, the answer is very different, and so is the schedule.
Match the schedule to what actually changes
Sort your site into one of these and the answer usually falls out.
- Static brochure sites. Five pages, updated when the phone number changes. Content barely moves. A regular scheduled backup is genuinely fine here, because the thing most likely to break is a plugin update, not lost data.
- Sites with a blog and forms. New content weekly, leads arriving through forms. The leads matter more than the posts. Most form plugins email you a copy, which is an accidental second backup, but do not rely on it without checking.
- Membership sites and anything with user accounts. Users sign up, change passwords, post comments. Their data is not reconstructable from your side. Frequency needs to go up.
- WooCommerce and any store. Orders are money and they arrive continuously. Losing a day of orders is not an inconvenience, it is a customer service crisis. Stores need the tightest schedule you can justify, and often a real-time or incremental approach on top.
The fix: pick your category, then write the maximum acceptable data loss in hours next to it. That number is your schedule. Everything else is guesswork.
Frequency is not the only variable
People obsess over frequency and ignore three settings that matter just as much.
Retention. Backing up daily and keeping backups for three days is worse protection than backing up weekly and keeping eight weeks. Problems you discover late, malware sitting quietly, a corrupted table, a plugin that has been mangling data for a fortnight, need old copies to recover from. Short retention just gives you a stack of freshly broken sites.
Completeness. A backup should include the database and the files, including the uploads folder. Plenty of plugins default to database only, which restores your posts and leaves every image broken.
Location. A backup sitting on the same server as the site is a copy, not a safety net. If you lose the account, you lose both.
Take a backup before you touch anything
Whatever the schedule, one rule beats it: take an extra backup immediately before any risky change. Major plugin update, theme swap, PHP version bump, WooCommerce upgrade, editing anything in a theme file.
That is the moment sites break, and it is the one moment you can perfectly predict. A backup taken 30 seconds before the change means the rollback costs you nothing at all. It is the cheapest insurance in WordPress and it takes two minutes.
The fix: add "take a manual backup first" to the top of your update routine. If you never remember to do it, that is a strong sign updates should not be yours to run.
Where a real schedule leaves you
Here is the thing worth being straight about: most WordPress sites are not backed up on any schedule at all. They are backed up whenever the owner last remembered, or whenever the host happened to snapshot the server. A predictable schedule you can name puts you ahead of the majority of sites on the internet.
Up Speed runs scheduled off-site backups on every plan, roughly four times a month, kept for 30 days, with one-click restore. Off-site means separate storage, so a problem with your hosting account does not take the backups with it. And we test restores quarterly, which is the step almost everyone skips.
To be clear about the tradeoff: a scheduled backup means anything changed since the last run is not in it. For a brochure site, a blog or a lead-gen site, that is a schedule that fits. If you are running a busy store with orders arriving all day, be honest with yourself that you need something tighter, and say so before you sign up for anything.
Stop making it your job
The real reason backups fail is not the wrong frequency. It is that nobody owns them. A schedule set up two years ago silently stops working, and nobody notices because nobody is looking.
If you would rather someone else set the schedule, watch it, store it off-site and prove it restores, that is the whole idea behind the Starter plan at $99 a month per site.