Blog Backup Basics: What to Save Before You Break the Site

A blog backup is not a zip you hope is fine. It is a kit you have opened on a spare URL.

This page is the Restore Kit. It is not managed WordPress hosting and not a hosting scorecard. Those decide where the site lives. This decides whether you can survive a bad plugin update on a Tuesday.

WordPress is the usual case here. Ghost and static sites still need the content store plus the theme—same idea, fewer folders.

Disclosure: Backup plugins and hosts are commercial. CashPilot may earn a commission through links we add later. No invented “99.99% restore” claims.

Table of contents

1. The three pieces people forget
2. The Restore Kit
3. When to run a backup
4. A 30-minute test restore
5. FAQ

The three pieces people forget

Host “full account” backups often include all three. Download one. If the host only snapshots the disk, you still want a copy that is not on that disk.

For HTTPS cleanup that rewrites URLs, back up before search-replace. See mixed content / HTTPS.

The Restore Kit

              RESTORE KIT
  ┌────────────────────────────────────────────┬───┐
  │ Files zip dated (uploads included)         │ □ │
  │ Database export dated                      │ □ │
  │ Secrets copied to a password manager       │ □ │
  │ Off-site copy (drive / object storage)     │ □ │
  │ Test restore on staging this month         │ □ │
  └────────────────────────────────────────────┴───┘
  5/5 = you may click Update

A plugin that emails “backup complete” without a file you can download is a notification, not a kit.

Official WordPress backup overview: WordPress.org — backing up your site. Use that as the generic process; your host’s UI will differ.

When to run a backup

• Before WordPress, theme, or plugin updates
• Before a host move (Bluehost alternatives if that is why you are leaving)
• Before a search-replace on URLs
• Weekly if you publish more than you can rewrite from memory

If you use Cloudflare, a backup is still on the origin. The CDN will not reconstruct your database. See Cloudflare for small blogs.

A 30-minute test restore

1. Create a staging site or a cheap temporary domain.
2. Upload files. Import the database. Point wp-config at the new database.
3. Open a post that has images. Click three images. Log into wp-admin.
4. If that works, the kit is real. If not, fix the kit now, not during an outage.

Then go back to publishing. How often should you publish still matters more than a prettier backup dashboard.

FAQ

What should a small blog back up?

Files, database, and secrets. A folder zip without the database is incomplete.

How often should I back up?

Before updates, and weekly if you publish often. Off-site copies beat a perfect calendar.

Is a host backup enough?

Only if you have restored it once and you also keep a downloaded copy.

Is this a hosting guide?

No. This is only the Restore Kit.

Do I need a paid backup plugin?

Not on day one. Paid tools help schedules and off-site storage—verify on the vendor’s official page.

What is a test restore?

You load the backup somewhere and confirm posts and images appear.

Should I back up before changing hosts?

Yes. Keep the old plan paid until the new origin works.

Where do backups fail most often?

Missing uploads, skipped database, or secrets pointing at the old database.

If the Restore Kit is 5/5, update the plugin. If it is not, do not click Update—finish the kit first.