Common hosting task

How to back up a WordPress site

A WordPress backup needs files, database, off-server storage, and a restore test. A dashboard that says backup exists is not enough.

Use this as a focused checklist for one common hosting task. The larger setup guides still cover full-site and full-server builds.

Difficulty
Beginner to intermediate
Time
30 to 90 minutes
Images
4 official examples

1. Back up both files and database

The files hold WordPress core, plugins, themes, uploads, and configuration. The database holds posts, pages, settings, users, orders, and form entries. You need both.

ScalaHosting SWordPress Manager
ScalaHosting managed VPS KB: WordPress management and backup tools should be part of the operating workflow.
ScalaHosting SBackup panel
ScalaHosting managed VPS KB: Backup panels are useful only when restore scope and retention are clear.

2. Store a copy off the hosting account

Host-level backups are useful, but one copy should live somewhere else: object storage, cloud drive, remote backup service, or another server. This protects against account, disk, malware, and billing problems.

GreenGeeks WordPress hosting feature section
GreenGeeks WordPress hosting: Plan pages often reveal whether backups are standard or plan dependent.

3. Run a restore test

Restore to staging, a temporary folder, or a spare server. Verify login, homepage, media library, forms, checkout, and plugin settings. Record the steps that worked.

Warning

If no one has restored it, the backup is still an assumption.

4. Match schedule to site risk

Static brochure

Weekly backups may be enough if content changes rarely.

Publishing site

Daily database backups reduce content loss.

WooCommerce

Order data may require frequent or real-time database protection.

Before updates

Run a manual backup before theme, plugin, PHP, or WordPress core updates.

Official sources checked

ScalaHosting managed VPS KB

Used for WordPress and backup panel context.

GreenGeeks WordPress hosting

Used for backup feature checklist context.

© 2026 WebHostWatch. We may earn affiliate commissions from links. Recommendations remain editorially independent.