WordPress Backup: A Simple Guide to Safe, Tested Copies

Spread the love

A WordPress backup is a saved copy of your site's database and files that you can restore after a hack, a failed update or a deleted page. This guide explains what to save, how often, where to keep it, and how to prove that your copies actually work. Also, this guide shows how to choose a backup plugin for your site.

Quick answer: Back up both the database and the files, run the backup on a schedule (weekly for a quiet site, daily for a busy one), and always take one before an update. Then keep at least one copy somewhere other than your web host. Finally, test a restore on a staging site, because a backup you have never restored is only a hope. In this guide, every WordPress backup step is explained in plain English.

What should a WordPress backup include?

A WordPress site has two parts, and you need both. According to the WordPress.org backup documentation, the database holds your posts, comments and links, while the files hold core, plugins, themes, images and uploads. The same page says you need both to fully restore a typical site.

In practice, a complete backup set contains:

  • The database: every post, page, comment, setting and user account.
  • The wp-content folder: themes, plugins and your media uploads.
  • Configuration files: such as wp-config.php, which holds database connection details, and any custom .htaccess rules.
  • Anything custom: for example extra scripts or files that your host added.

WordPress.org also advises backing up the database first, then the files, and keeping them as one set made around the same time. For this reason, mixing a database from Monday with files from Friday can break a restore.

How often should you back up your WordPress site?

The right rhythm depends on how often your content changes. WordPress.org suggests backing up regularly and always before an upgrade. It also gives a simple rule of thumb: weekly for smaller sites with few posts, and daily for sites with a lot of activity.

Ask yourself one question: how much work could I afford to lose? For example, a brochure site that changes twice a year can live with a weekly copy. However, a shop that takes orders every hour needs daily backups, or more often if your tool supports it.

Because updates are the most common moment when sites break, take a fresh WordPress backup before you update core, a theme or a plugin. The Patchstack State of WordPress Security in 2026 report counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 91% of them in plugins. That means updates are frequent, so backups should be too. Our WordPress security checklist covers the other half of the job.

Where should you keep an offsite backup?

An offsite backup is a copy stored away from your web server. If the server fails, is hacked or is deleted, a copy stored on that same server may disappear with it. WordPress.org recommends keeping at least three to five recent backups and storing them in different places, such as the hosting server, cloud storage and a local computer.

Many people summarise this as the 3-2-1 rule: three copies, on two kinds of storage, with one copy offsite. It is a widely used guideline in the backup industry rather than an official WordPress rule, but it is easy to remember. As a result, a simple setup might look like this:

CopyWhereWhy

|—|—|—|

Live siteYour web hostThe working version
Copy 1Host backup or server snapshotQuick restore
Copy 2Cloud storage account that you ownSurvives a host problem
Copy 3An occasional download to your own computerSurvives an account problem

Also protect the backup itself. A file containing your whole database includes customer and user data, so use a strong password on the storage account and turn on two-step login. If you collect personal data from people in Thailand or the EU, treat backups as personal data under the rules that apply to you, because they are.

An open hard drive showing its platter, a reminder that a WordPress backup protects real stored data
An open hard drive: your site lives on storage, so keep a copy elsewhere. Photo: Zzubnik, Public domain, via Wikimedia Commons, resized

Which WordPress backup method should you choose?

There are four common ways to back up a site. Each has trade-offs, so many owners combine two.

MethodHow it worksGood forWatch out for

|—|—|—|—|

Host backupsYour hosting company copies the siteZero setupOften kept on the same infrastructure, with limited history
Backup pluginA plugin schedules copies and sends them to cloud storageMost small sitesLarge sites may time out on cheap hosting
Manual exportYou export the database and download the filesA one-off copy before a big changeEasy to forget
Server snapshotA VPS provider images the whole serverFull-server restoreCosts extra and captures everything, including problems

For example, one VPS provider's pricing page lists percentage-based backups at 20% of the server cost for weekly copies or 30% for daily copies, as of November 2026. Prices differ by provider, so check yours.

How do you make a database backup?

A database backup is the most valuable single file, because your content lives there. You can export it from phpMyAdmin in your hosting panel, or with WP-CLI if your host offers command-line access. According to the WP-CLI command reference, the command `wp db export` writes the database to an SQL file, and you can name the file yourself.

After that, download the file and store it with your other copies. In addition, check that it is not empty: a database backup of a few bytes means something went wrong. For routine protection, though, a plugin usually handles this step for you.

How do you choose a WordPress backup plugin?

A good backup plugin is one you will actually keep running. Instead of asking which brand is popular, compare plugins against criteria:

  • Scope: does it save the database and files, or only one of them?
  • Schedule: can you set daily or weekly runs, and run one before updates?
  • Destinations: can it send copies to storage that you control?
  • Restore: can you restore from inside the dashboard, and from a copy on another site?
  • Reports: does it tell you when a backup fails?
  • Encryption and access: can you protect the files, and who can reach them?

As one example, the UpdraftPlus listing on WordPress.org says it backs up the database, plugins and themes, can run on a schedule from every two hours to monthly, and sends copies to destinations such as Dropbox, Google Drive and Amazon S3 in the free version. It also says that automatic backups before updates and incremental backups are premium features. Other plugins exist, so treat this as an example of how to read a feature list, not as a recommendation.

Why use a staging site for a restore test?

A staging site is a private copy of your website where you can test changes without risking the live version. It is also the safest place for a restore test. Many hosts offer one-click staging, and some plugins can build one for you.

Here is a simple restore test you can repeat every quarter:

  1. Take a fresh WordPress backup, or pick the latest scheduled one.
  2. Create a blank staging site, or a new empty WordPress install on a test address.
  3. Restore the files and database into it.
  4. Open the home page, a post, a form and the login page.
  5. Check that images load and that recent content is there.
  6. Write down how long it took and what went wrong.

WordPress.org does not describe a formal restore test, so this checklist reflects common practice. Even so, it turns a vague promise into a measured result. Because a restore test finds missing files, unsupported formats and expired storage logins, it is the cheapest insurance in this guide.

What should you do before updates and migrations?

Before any major change, follow the same short routine every time. First, take a fresh backup and confirm that it finished. Next, update on staging if you have one. Then update the live site, check the key pages, and keep the backup until you are sure everything works.

Moreover, the same routine applies when you move hosts. If you are choosing a new plan, our guides to choosing web hosting and cloud hosting vs shared hosting explain what to look for, including backup features. If you are building a new site, see how to build a WordPress website first.

A WordPress backup checklist

Use this list when you set up a new site or review an old one:

  • Database and files are both included in every backup.
  • Backups run on a schedule, with an extra one before updates.
  • At least one copy is offsite, in an account that you own.
  • You keep several recent copies, not just the latest.
  • You get a notice when a backup fails.
  • You have restored a copy to a staging site in the last three months.
  • Two-step login protects the storage account.
  • You know who can restore the site if you are away.

This is general information about website maintenance, not legal or security advice for your particular setup.

Need help with your WordPress backup?

Develop Marketing helps businesses with social media, AI content, SEO, AEO and GEO, WordPress websites and advertising. If you would like a second pair of eyes on your site's maintenance, see our services page (in Thai) or contact us.

Frequently asked questions

Is a hosting backup enough for a WordPress backup?

Not on its own. A host backup is convenient, but it may sit on the same infrastructure as your site, and the history can be short. Keep at least one extra copy in storage that you control.

How long should I keep old backups?

WordPress.org suggests keeping at least three to five recent backups. If you can afford the storage, keep a few older ones too, because a problem such as hidden malware may go unnoticed for weeks.

Can a backup plugin slow down my site?

It can, mostly while it runs. Large sites on small hosting plans may hit time limits. Schedule backups for quiet hours and check your plugin's settings for the size of each chunk.

Does a WordPress backup protect against hacking?

It helps you recover, but it does not prevent attacks. Combine backups with updates, strong passwords and two-step login. Also remember that a backup taken after a hack may contain the problem, so keep older copies.

What is the difference between a backup and a staging site?

A backup is a saved copy for recovery. A staging site is a working copy for testing. The two work together: you restore a backup onto staging to prove that it works.

Final thoughts

A WordPress backup is not exciting, but it is the one task that can turn a disaster into a bad afternoon. Save the database and the files, schedule the job, keep an offsite backup, and test a restore on a staging site every quarter. Start today by checking what your host already provides, then add one extra copy that you control. Good habits here protect your content, your customers and your search rankings.

Related Posts

Sell on Etsy from Thailand: Setup, Payoneer and Fees

Spread the love

How to sell on Etsy from Thailand as of November 2026: shop setup, Etsy Payments with Payoneer, the layers of seller fees and Offsite Ads.

YouTube Demonetization: Reasons, Appeals and How to Recover

Spread the love

YouTube demonetization as of November 2026: the difference between video and channel level, how appeals work, and which policies cause most problems.

You Missed

Ao Luek to Phi Phi: Road, Pier and Ferry Times from Krabi

Ao Luek to Phi Phi: Road, Pier and Ferry Times from Krabi

Susan Hoi Shell Cemetery: Fees, Low Tide and the Fossil Slabs of Krabi

Susan Hoi Shell Cemetery: Fees, Low Tide and the Fossil Slabs of Krabi

Thailand Digital Nomad Tax: The 180-Day Rule and Foreign Income

Thailand Digital Nomad Tax: The 180-Day Rule and Foreign Income

Best Beaches in Hua Hin: Khao Takiab, Suan Son Pradipat and Sai Noi

Best Beaches in Hua Hin: Khao Takiab, Suan Son Pradipat and Sai Noi

Khao Mok Gai: Thai Chicken Biryani, Green Sauce and Halal Tips

Khao Mok Gai: Thai Chicken Biryani, Green Sauce and Halal Tips

Thailand in November: Weather, Festivals and Which Coast to Pick

Thailand in November: Weather, Festivals and Which Coast to Pick