Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The reliable way to automate WordPress backups is to capture both the database and the site files, copy the backup away from the production server, and regularly prove that you can restore it. The database holds posts, pages, comments, users and settings; files hold themes, plugins, uploads, configuration and custom code. A schedule that saves only one side cannot fully rebuild a broken site.
What a complete automated WordPress backup must contain
The database
Your WordPress database stores structured content and configuration, including posts, pages, comments and settings. WP-CLI can export it with wp db export or wp db dump; both read the connection details from wp-config.php. WordPress documentation strongly recommends backing up the database at regular intervals and before upgrades.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The site files
A database export does not contain your themes, plugins, media uploads or wp-config.php. Include at least the wp-content directory, the configuration file and any site-specific files in the web root. Custom rewrite rules, deployment files and other files your installation needs should be included as well. WordPress core files can normally be recreated from a clean release, but retaining the exact core version can make a recovery faster.
Why both parts are required
Restoring only the database may bring back text while leaving broken layouts, missing images and disabled functionality. Restoring only files leaves you without current content, settings and orders. Treat the database export and file archive as one backup set, with matching timestamps and an identifier that lets you restore them together.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Choose an automation method
| Method | What it can automate | Schedule details | Restore and access model |
|---|---|---|---|
| WP-CLI plus server cron | Database export, file archiving, encryption, transfer and retention when you script each stage | Any interval your cron and server can support; the interval is your responsibility | Requires shell or hosting access; restoration is a documented manual procedure unless you script it |
| UpdraftPlus | Separate database and file schedules, remote copies and component-level restores | Free schedules include every 2, 4 or 8 hours, daily, weekly, fortnightly and monthly. Premium adds a chosen start time and incremental backups | Managed from WordPress; confirm current remote-storage destinations, multisite support and retention limits for your edition |
| Jetpack VaultPress Backup | Automatic database and file backups, browsing and downloads of backup files, and one-click restoration | Backups run at least daily and can also run after events such as publishing or theme and plugin changes; the daily window can be moved to an off-peak time | Service-managed backup with a streamlined restore workflow |
| WordPress.com Business or Commerce | Hosted WordPress with Jetpack VaultPress Backup included | Real-time backup is included on these plans; support documentation says backups are saved at least daily and may run multiple times in a day when changes are frequent | Hosted administration and one-click restore options; other WordPress.com plans require manual content and media exports |
Pick the method that matches your operational access and recovery expectations. A server administrator may prefer a transparent WP-CLI script, while a team that cannot manage cron may prefer a managed service. For any option, verify that the resulting set contains the database, uploads, themes, plugins and configuration before relying on it.
Define what you need to recover before setting a schedule
- Inventory the data: list the database,
wp-content/uploads, active and inactive plugins, themes,wp-config.php, web-server rules and any custom root files. - Identify high-change areas: publishing, orders, memberships, comments and form submissions create more recovery exposure than a mostly static brochure site.
- Choose an acceptable loss window: decide how much recent work or transaction data the business can afford to lose. That decision determines how often backups must run.
- Choose an acceptable restoration time: a small site may tolerate a manual rebuild; a revenue-generating store may require a tested, one-click or scripted recovery.
- Decide where copies live: keep at least one copy outside the production server so a disk failure, compromised account or bad deployment cannot destroy every generation.
- Set retention deliberately: retain enough generations to cover accidental deletion and delayed discovery of corruption. There is no universal retention period; align it with business, legal and operational needs.
Automate backups with WP-CLI and cron
WP-CLI is designed to be scripted and run from cron or deployment steps. The following pattern creates a timestamped database export and file archive. Adapt the paths, archive contents, destination and transfer command to your host; do not place database passwords in the script.
1. Create a backup script
#!/usr/bin/env bash
set -euo pipefail
SITE=/var/www/example
STAMP=$(date -u +%Y%m%dT%H%M%SZ)
DEST=/var/backups/wordpress/$STAMP
mkdir -p $DEST
cd $SITE
# Export the database using credentials from wp-config.php
wp db export $DEST/database.sql --path=$SITE
# Add wp-content and site-specific root/configuration files
tar -czf $DEST/files.tar.gz wp-content wp-config.php .htaccess
# Create an integrity record
sha256sum $DEST/database.sql $DEST/files.tar.gz > $DEST/SHA256SUMS
# Encrypt and transfer this directory to storage outside the web server.
# Apply your storage provider's upload command here.
# Send a success notification only after the transfer completes.The wp db dump command is an alternative when you want the SQL written to a chosen file or standard output. The export command alone is not a complete WordPress backup because it contains no themes, plugins, uploads or configuration file.
2. Schedule it with cron
After making the script executable and testing it interactively, run it under the account that owns the WordPress files or has the required database and filesystem permissions. A six-hour example is:
15 */6 * * * /usr/local/sbin/wp-backup.sh >> /var/log/wp-backup.log 2>&1This line is only an example cadence. Set the interval from your acceptable loss window and change rate, not from the example itself. Use the server’s absolute paths because cron provides a smaller environment than an interactive shell.
3. Add transfer, retention and alerting
- Transfer: upload the completed archive to storage that is independent of the production server. Treat the upload as successful only after the remote service confirms completion.
- Protect: encrypt archives before transfer when the storage service does not provide the protection you require. Restrict access to the backup account and keep encryption keys separate from the archives.
- Retain: prune old generations only after confirming that newer remote copies are intact. Keep a failure-resistant copy while pruning so a failed job cannot delete your last usable backup.
- Alert: notify an operator when WP-CLI exits non-zero, the archive is unexpectedly small, the transfer fails or free disk space falls below your threshold. A green cron log is not proof that a usable off-site copy exists.
Automate with UpdraftPlus
UpdraftPlus exposes independent schedules for files and the database, which lets you capture frequently changing data without rebuilding every file archive at the same interval. In its free schedule choices, you can select every 2, 4 or 8 hours, daily, weekly, fortnightly or monthly. Premium adds a chosen start time and incremental backups, allowing a full backup cadence to be combined with more frequent change capture.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Configure the schedules
- Open the plugin’s settings in the WordPress administrator and locate the separate file-backup and database-backup schedule controls.
- Set the database interval from your content and transaction change rate. Set the file interval from how often uploads, plugins, themes or custom files change.
- Choose a remote destination and authenticate it. Do not treat a copy in the same hosting account as your only off-site copy.
- Set retention for scheduled file and database generations independently if the interface allows it, then save the settings.
- Run a manual backup immediately and inspect the resulting set before waiting for the first scheduled job.
- Perform a test restore of the database and files on staging, including media, theme behavior and plugin-dependent features.
Before committing to a plan, confirm the current destination list, multisite behavior, retention limits and restore granularity for the exact edition you use. Those details can change between editions and releases.
Automate with Jetpack VaultPress Backup
Jetpack VaultPress Backup automatically creates backups and provides one-click restoration, backup-file browsing and downloads. Its documented coverage includes the WordPress database, plugins, mu-plugins, themes and uploads, plus eligible files in the root and wp-content directories.
Understand what is and is not included
The service excludes WordPress core files, caches, logs, backup directories and some non-WordPress tables. Keep a record of custom files or external services that are outside this coverage. If your deployment depends on generated assets, server configuration or a separate database table, document and back up those items through another process.
Use event capture and off-peak timing
Backups occur at least daily and can also be triggered after events such as publishing or theme and plugin changes. You can configure the daily backup window for an off-peak period. After enabling the feature, open its activity and backup browser to confirm that a recent database snapshot and the expected file directories are present, then rehearse the one-click restore on a staging copy.
Use WordPress.com managed backups
WordPress.com documentation updated October 1, 2025, states that Business and Commerce plans include Jetpack VaultPress Backup with real-time backup and one-click restore options. Support documentation says automated backups require one of those plans; other plans provide manual exports of content and media instead.
Managed hosting reduces the amount of cron and storage administration you perform, but you still need to verify the recovery path. Confirm what happens to custom code, domain settings, DNS, external integrations and any data stored outside WordPress. Download or export a copy when your continuity policy requires an independently held archive.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
How often should WordPress back up?
There is no single correct interval. Match the schedule to the most valuable data that can change between captures:
- High-change stores, memberships and news sites: use frequent database captures, event-triggered backups or real-time coverage where available. A lost order or registration can be more costly than a lost theme change.
- Active business sites: schedule database backups at least as often as the team publishes or receives form submissions, and back up files whenever plugins, themes or media change.
- Low-change brochure sites: daily, weekly or monthly schedules may be reasonable when the owner can recreate recent edits, but still take a backup before upgrades and major edits.
- Before risky work: create an immediate full backup before core, plugin, theme, PHP or database changes, even if an automated job ran recently.
Measure the interval against two operational targets: the maximum data loss you accept and the time in which the site must be online again. These are site-specific decisions, not universal WordPress settings.
Free tools Windows power users keep installed
One-click scans. No signup required.
Store and protect backups outside production
- Use storage controlled separately from the web server and, when practical, from the same hosting account.
- Encrypt archives in transit and at rest, and restrict backup credentials to the smallest permissions needed.
- Keep encryption keys, API tokens and database credentials out of publicly served directories and version-control repositories.
- Monitor storage capacity and verify checksums or archive readability after transfer.
- Record the backup timestamp, WordPress version, PHP version, database engine, active theme and plugin list with each generation so a rebuild has the required context.
- Protect the backup repository itself; an archive containing user data, orders or configuration secrets is sensitive.
Prove that restoration works
A successful backup job is only evidence that files were written. A restoration rehearsal proves that the set is complete and that someone knows the recovery order. Use a staging server or isolated environment rather than experimenting on the live site.
- Prepare staging: create an empty WordPress installation with compatible server software and enough disk space. Block search indexing and public access.
- Restore files: unpack the file archive, including
wp-content,wp-config.phpand any custom root files. Check ownership and permissions. - Create and import the database: configure an empty database, update connection values as needed, and run
wp db import database.sqlfrom the staging WordPress directory. - Adjust the site address: if staging uses a different domain, perform a careful, serialized-data-aware search and replace with WP-CLI or the documented method for your platform. Never use a blind text replacement on a serialized WordPress database.
- Rebuild runtime state: flush caches, regenerate rewrite rules and clear object-cache entries so the restored files and database are read together.
- Test real user paths: open the front end and administrator, load old and recent media, publish a test post, submit a form, verify email delivery and exercise store or membership workflows if they exist.
- Record the result: note the backup generation, elapsed restoration time, missing files, manual fixes and the person who performed the test. Turn the notes into the next revision of your runbook.
Troubleshoot common automation failures
The site restores without images or styling
That usually means the database was restored without the matching wp-content archive, or the archive omitted uploads, the active theme or a required plugin. Inspect the archive contents and restore the file set from the same timestamp as the database.
The cron job runs but no usable backup appears
Check the cron user’s permissions, absolute paths, PHP and WP-CLI locations, available disk space and the exit status of every command. Make the script stop on errors, write a log, and verify the remote object after upload instead of reporting success immediately after file creation.
A plugin reports success but the remote copy is missing
Re-authenticate the destination, inspect quota and API errors, and run a manual backup while watching the activity log. A local temporary archive is not an off-site backup until the destination confirms receipt.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
The restored site redirects to the wrong domain
Check the serialized site URL and home URL values, then use a WordPress-aware search-and-replace process for the staging domain. Clear caches and test both HTTP and HTTPS behavior after the change.
Backups fill the server disk
Move completed archives off-server, enforce retention after successful remote verification, and exclude temporary backup directories from the next archive. Keep enough generations to cover delayed discovery of corruption rather than deleting everything except the newest file.
A backup cannot be decrypted or unpacked
Verify that the encryption key is available to the recovery operator and that checksums match the uploaded objects. Replace corrupted generations from an earlier verified copy and update the runbook with the exact decryption and extraction commands.
A practical operating pattern
For a self-managed site, schedule WP-CLI to export the database, archive wp-content and required configuration, encrypt and transfer the set off-server, enforce retention and alert on every failure. For teams that prefer an administrator interface, use separate database and file schedules in UpdraftPlus and validate its current storage and restore features. For managed coverage, Jetpack VaultPress Backup provides daily-or-better event-aware backups and one-click recovery; WordPress.com Business and Commerce add real-time backup within the hosted plans.
Whichever route you choose, the durable process is the same: define what must be recoverable, capture database and files together, keep independent copies, protect them, monitor the jobs and rehearse a restore before an outage makes the decision for you.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
