Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124


I lost a website once. Not to a hack — to my own stupidity. I was testing a plugin, it broke the database, and my host’s most recent backup was 9 days old.
Disclosure: This post contains affiliate links. If you make a purchase through these links, I may earn a small commission at no extra cost to you.
![]()
![]()
Photo by Brett Sayles — Pexels
I lost a website once. Not to a hack — to my own stupidity. I was testing a plugin, it broke the database, and my host’s most recent backup was 9 days old. Nine days of blog posts, design changes, and new pages — gone. That was seven years ago, and I still haven’t forgiven myself for not having my own backup system in place.
Don’t be me. Setting up proper website backups takes about 10 minutes and costs nothing. Here’s exactly how to do it, whether you’re on WordPress, a static site, or any other platform.
Most hosting providers include some form of backup. But relying solely on your host is risky for several reasons:
The golden rule of backups: 3-2-1. Three copies of your data, on two different types of storage, with one stored offsite. Your hosting server is copy #1. Your backup should be somewhere completely separate.
If you’re running WordPress — and roughly 43% of all websites do — plugins make backups dead simple.
This is what I use on every WordPress site I manage. The free version does everything most people need:
Setup takes 5 minutes:
That’s it. Your site now backs up automatically. I set database backups to daily because content changes (new posts, comments, settings) live in the database. File backups can be weekly since themes and plugins don’t change as often.
![]()
![]()
Photo by Sora Shimazaki — Pexels
If your host provides cPanel — and most shared hosts do, including InterServer and Hosting.com’s cPanel plans — you can create manual backups regardless of what CMS (or no CMS) you’re using.
Full account backup:
This captures everything: files, databases, email configurations, cron jobs, DNS settings. It’s the most complete backup you can get.
Partial backups: You can also download individual components — just the home directory (files), individual databases, or email forwarders. Useful if you only need to restore one piece.
For more on what cPanel can do, our cPanel hosting guide covers the full feature set.
For developers or anyone who wants full control, the manual approach works with any hosting setup:
Files: FTP download
Database: phpMyAdmin export
This method gives you the most portable backup. You can restore it on any server, any host, anywhere. The downside? It’s manual. Unless you script it (which is very doable with cron jobs and bash scripts), you have to remember to do it regularly.
| Component | What It Contains | How Often to Back Up | Priority |
|---|---|---|---|
| Database | Content, settings, users, comments | Daily | Critical |
| wp-content/uploads | Images, PDFs, media files | Weekly | High |
| wp-content/themes | Theme files, customizations | After changes | Medium |
| wp-content/plugins | Plugin files | After changes | Low (re-installable) |
| .htaccess / wp-config.php | Server config, DB credentials | After changes | Critical |
| Email accounts | Email data, forwarders | Weekly | Medium |
The database is the most important piece. Without it, your content is gone — and content is what takes the most time to recreate. Plugin files can be re-downloaded. Theme files can be re-installed (though custom modifications need their own backup). But 200 blog posts with custom formatting? You can’t re-download those.
Best free options:
Best paid options for serious sites:
For a small WordPress blog, Google Drive is more than enough. A typical backup (database + files) for a site with a few hundred posts runs about 500 MB – 2 GB. Google’s 15 GB free tier stores multiple backup versions easily.
Depends on how often your site changes:
And always — ALWAYS — back up before making changes. About to update WordPress core? Back up first. Installing a new plugin? Back up first. Changing themes? Back up first. This takes 2 minutes with UpdraftPlus and has saved me more times than I can count.
A backup you’ve never tested is a backup you can’t trust. At least once, go through the full restore process:
If you’re on shared hosting with Hosting.com or InterServer, you can create a test subdomain for free to practice restores. It’s worth the 20 minutes to know your backup actually works.
Your website represents hours, months, or years of work. A 10-minute backup setup protects all of that. Do it today — not tomorrow, not “when I get around to it.” Today. Future you will be grateful.
Most do, but with caveats. Budget hosts typically do weekly backups with limited retention. Check your host’s backup policy — and set up your own regardless. Our uptime and reliability guide covers what to look for in hosting reliability.
A typical small WordPress site (under 500 posts, few hundred images) generates backups around 500 MB – 2 GB. Large media-heavy sites can be 5-10 GB+. Google Drive’s 15 GB free tier handles most small sites easily.
Yes. Database exports (.sql files) and file archives work on any compatible server. This is actually how site migrations work — export from old host, import to new host. We cover this in our migration guide.
If you use hosting-based email (@yourdomain.com), yes. Download important emails to a local client like Thunderbird. Email isn’t always included in standard backup plugins. For critical business email, consider a dedicated email service — see our email hosting guide.