Column 1
Skip to content
Column 1

How to Back Up WordPress: Complete Methods Guide

WordPress backup evidence checklist for support tickets

There is not one correct way to back up WordPress. There are many, and the right choice depends on your control panel, host, budget, access level, and how painful downtime would be. A flower shop with a five-page website needs a different backup rhythm than a WooCommerce store, agency client fleet, school site, membership platform, or hosting provider.

This guide is the map. Each method below gets its own step-by-step tutorial so you can pick the backup path you actually have available: cPanel, WHM, Plesk, WP Toolkit, Softaculous, Installatron, DirectAdmin, JetBackup, backup plugins, WP-CLI, and cron-based automation.

What every WordPress backup needs

A usable WordPress backup normally needs both pieces of the site: files and database. Files include WordPress core, plugins, themes, uploads, mu-plugins, custom code, and configuration files. The database includes posts, pages, menus, plugin settings, users, forms, orders, products, bookings, and most site settings.

If you only back up files, you may lose content and orders. If you only back up the database, you may lose images, theme changes, plugin files, and uploaded documents. If you leave every backup on the same server, a server failure, hacked account, or full disk can take the backup with the site.

WordPress backup methods covered

What should small businesses do?

For a basic business website, use at least one panel or host-level backup and one offsite backup. If your host gives you cPanel, Plesk, Softaculous, Installatron, or JetBackup, learn that first because it may restore even when WordPress itself is broken. Then add a plugin backup to Google Drive, Dropbox, S3-compatible storage, or another destination you control.

What should ecommerce and membership sites do?

WooCommerce, booking, LMS, donation, and membership sites need tighter timing. A daily backup may not be enough if orders or leads arrive all day. Use provider backups, database-aware backups, and a clear maintenance window before major changes. Export fresh orders, subscriptions, form entries, or booking data before restoring older backups.

What should agencies and hosting admins do?

Agencies and hosting admins should standardize the stack. Keep a list of every site, control panel, backup method, remote destination, schedule, retention, and restore test date. If twenty clients use the same plugin stack, one compatibility issue can become twenty tickets. Backup before batches of updates, then verify forms, checkout, cache, and logs after the batch.

Backup schedule recommendations

  • Static brochure site: weekly files and daily or weekly database, plus a manual backup before changes.
  • Active blog or lead site: daily database, weekly files, and manual backups before updates.
  • WooCommerce or bookings: at least daily full backups, more frequent database/order protection, and a tested rollback plan.
  • Developer work: backup before deployments, keep a staging copy, and export the database before destructive changes.
  • Hosting provider: server-level scheduled backups, remote storage, customer self-service restore where possible, and periodic restore audits.

Do cron jobs matter?

Yes. Many WordPress backup plugins rely on WordPress scheduled tasks. WordPress WP-Cron is triggered by site traffic, so low-traffic sites can run scheduled jobs late. Control-panel backups, JetBackup, WHM backups, Plesk Backup Manager, and real server cron are usually more predictable for timed backups. The cron tutorial in this cluster explains the difference.

Fix I.T. Phill recommendation

For most business sites, use layered backups: host-level backup, WordPress-level backup, and offsite storage. Do not trust a backup until you know how it restores. A backup that has never been opened, downloaded, or tested is a hope file, not a recovery plan.

Related Fix I.T. Phill guides

Sources checked

Related WordPress recovery help

2026 Support Update: WordPress Backup Evidence Checklist

Current action path: A backup guide is stronger when it tells a site owner what proof to collect before a support ticket, update, migration, or restore window.

Evidence to collect before work starts

  • Backup timestamp, storage location, retention window, and who can access it.
  • File backup scope, database backup scope, uploads coverage, plugin/theme list, and active PHP version.
  • Restore target, expected downtime, DNS/cache notes, login checks, forms, checkout/order checks where relevant, and rollback path.

Source-backed references and next reads

For support tickets, include the exact URL, backup identifier, restore point, changed setting, test account or checkout path used, and post-change public verification result. That makes the article useful for real recovery work, not just general reading.