WordPress backups: save files and the database
Create a matched WordPress recovery set, restore safely in staging, and check the pages and application tasks visitors depend on.
Read the 6-minute guideWeb & servers
WordPress Insta Backups
Pair the files with the right database.
WordPress recovery needs the pieces that work together: database content, uploads, theme and plugin files, configuration, and any custom additions. The official file-backup documentation distinguishes the database from the website directory. Plan both sides and label them as one coherent recovery set.
What to preserve
- The database export, including relevant custom application tables.
- Uploads, themes, plugins, custom code, and configuration requirements.
- External media, scheduled jobs, and connected-service dependencies.
Your starting workflow
Review the selected backup tool’s inclusions and exclusions. Coordinate the database with related files, protect the resulting archive outside the public web directory, and store an independent copy. Keep the restore instructions with the release and secrets in an approved separate system.
Test the recovered copy
Restore into access-controlled staging. Disable real mail, payments, and webhooks before starting the application. Browse recent and older pages, open full-size images, sign in with a test account, and check important custom functionality.
Do I always need a full rollback?
No. Identify the damaged component first. A targeted file or content recovery may preserve newer work better than replacing the entire site. Test the repair and obtain approval before changing production data.
From Insta Backups Lab
Put the plan into practice.