Yes. WordPress backup plugins such as UpdraftPlus, WPvivid, BackWPup, and Duplicator let you customize backup scope, schedules, destinations, and restoration options. You can choose full, database-only, or file-only backups, set frequencies from every hours to monthly in WPvivid, and retain selected numbers of scheduled backups, depending on the plugin and plan [1].
- WordPress files include core files, themes, plugins, uploads, wp-config.php, and.htaccess [2].
- A complete restoration typically requires both the WordPress database and the WordPress files [2].
- WPvivid supports schedules from every hours through monthly and lets you choose backup items and a destination [1].
- UpdraftPlus Free and Premium provide automatic schedules and one-click restores, while incremental backups are Premium-only [1].
- WordPress recommends keeping at least three to five recent backups in different locations [2].
Which backup settings can you customize in a WordPress backup plugin?
WordPress backup plugins can customize the backup scope, schedule, database selection, storage destination, and retention rules. WordPress site files include core files, themes, plugins, uploads, wp-config.php, and .htaccess [2].
The WordPress database is separate from the WordPress directory, so downloading the directory alone usually doesn’t capture the database [2]. A complete backup should therefore include both the files and the database [2]. Plugins may offer full backups, database-only backups, or file-only backups; BackUpWordPress, for example, supports the entire site or only the database or files [1].
A complete process should also cover website files, the database, media, plugins, and themes [3]. UpdraftPlus separates plugins, themes, uploads, and core files, allowing you to choose those components in its file-backup settings [4]. BackWPup lets you select database tables and backup types separately from website-file settings for content, plugins, and themes [5].
Frequency should follow site activity: WordPress recommends weekly backups for smaller websites and daily backups for high-activity websites with many posts [2].
How can you configure and schedule customized backups?
A typical setup involves installing and activating a backup plugin, creating a backup job, choosing files and database content, selecting a destination, and setting a schedule. BackWPup is installed from the WordPress plugin directory and activated before you create a new job [5]. The job is then created from the WordPress dashboard through BackWPup settings and “Add new job” [5].
WordPress states that plugins can provide automatic scheduled database backups [2]. UpdraftPlus users configure schedules under Settings and UpdraftPlus Backups on the Settings tab [4].
WPvivid lets you choose backup items, a destination, and a schedule ranging from every hours to daily, weekly, fortnightly, or monthly [1]. For a full manual backup, select “WordPress Files + Database,” choose “Save to local,” and click “Backup Now” [3]. Automatic backups are configured from the WPvivid Backup Schedule tab [3].
Manual and scheduled backups can coexist, and the schedule should reflect how often your site content changes rather than simply accepting a plugin default [6].
Which plugins support incremental backups, remote storage, scheduling, and selective restores?
UpdraftPlus, WPvivid, BackWPup, Jetpack Backup, and Duplicator offer different combinations of backup customization. UpdraftPlus Free and Premium include automatic schedules and one-click restores, while incremental backups are limited to Premium [1]. UpdraftPlus also supports separate database and file schedules [4] and component-specific restoration for database, plugins, themes, uploads, and core files [7].
BackWPup supports manual scheduling, WordPress cron, and third-party cron services [5]. The plugin lets you select database tables and types, configure website files separately, and push backups to a third-party storage service, directory, or FTP [5].
WPvivid’s free version includes automated scheduling, multiple cloud-storage destinations, and advanced backup options [7]. Duplicator Lite provides manual backups without scheduling; scheduled backups require Duplicator Pro [1]. Jetpack Backup provides real-time backup and is positioned for high-transaction ecommerce stores [6].
BlogVault uses incremental backups and offers staging for testing updates, but the ledger says it can’t restore individual files, although it can restore specific database tables [8].
What does a WordPress backup plugin cost, and what do free and premium plans include?
There is no universal typical price for all WordPress backup plugins in the available evidence. Some plugins provide free automated backups, while premium plans can add incremental backups, migration, or additional destinations [4].
Listed prices vary. UpdraftPlus Premium starts at $70 per year, WPvivid Pro starts at $49 per year, BackWPup Pro starts at $69 per year, Solid Backups starts at $99 for one site, and BlogVault Plus starts at $149 per year for one site [7]. Solid Backups’ listed starting plan includes daily incremental backups, one-click restore, and a centralized management dashboard [1].
UpdraftPlus Free supports scheduled backups to one destination and remote storage including Drive, S3, and Dropbox [6]. The free plugin can automate database and file backups without requiring a paid plan [4]. UpdraftPlus Premium adds incremental backups, migration, and multiple simultaneous destinations [6].
BackWPup is described as a free plugin with remote-storage support and database-backup scheduling [6]. The ledger doesn’t provide a complete feature-and-price matrix for every plan, so confirm the specific plan before relying on a feature.
What risks come from changing backup settings?
Changing backup settings can leave you without the data or files needed for a complete restoration. A typical WordPress restoration requires both the database and the files [2]. A files-only backup omits posts, pages, and images, while a database-only backup omits site structure, themes, and custom functionality [9].
WordPress core files, content, plugins, themes, and database data are essential for the website to run smoothly [5]. Damage to core or content files can make the website break or become inaccessible [5]. Excluding a component without understanding its role can therefore increase downtime and data-loss risk.
Backup plugins can also fail or add server load and slow a site; a failure is especially concerning on a busy site backed up only once per day [1]. Run a manual backup before updating a plugin, changing a theme, modifying code, or making significant core changes [4].
The ledger doesn’t specify a universal minimum retention period. It does support keeping at least three to five recent backups [2].
How can you test, restore, and verify a customized backup safely?
A safe validation process starts with a test backup and confirmation that the backup reaches the selected remote-storage destination [6]. Each backup file should be tested because files can become corrupted or damaged and later fail during restoration [9].
Perform the first restore test in a staging environment after configuring the backup [6]. BlogVault provides a free staging site for testing backups before moving one to production [1]. Its staging environment is also described as a place to make changes without crashing the website [8].
The typical restoration order is to restore WordPress files first and then restore or import the database [2]. In WPvivid, you can restore by uploading a compressed backup file under Backup and Restore or by clicking the Restore icon [3].
A full restore should be tested once or twice a year in staging or a local WordPress installation [4]. A staging or local test helps you verify that files, the database, media, themes, plugins, and site functionality are present before a live recovery is necessary.
What storage destinations and retention policies should you configure?
Reliable backup storage combines enough recent versions with copies in different locations. WordPress recommends keeping at least three to five recent backups and storing copies in different locations [2]. The 3-2-1 rule describes three copies on two different systems, with one copy stored offsite [4].
Possible destinations include the hosting server, cloud storage such as Google Drive or Dropbox, and a local computer [2]. WPvivid documents support for Dropbox, Google Drive, Amazon S3, Microsoft OneDrive, DigitalOcean Spaces, FTP, and SFTP [1]. UpdraftPlus supports remote destinations including Google Drive, Dropbox, and Amazon S3 [4].
Retention controls determine how long backup snapshots remain available. Many plugins provide archive-pruning options for deleting old backups [9]. UpdraftPlus lets you choose how many scheduled backups to retain before older copies are automatically deleted [4].
The source recommends checking whether backups are stored offsite and retained for at least days, while retention needs vary by site [10].
| Plugin | Scheduling | Storage destinations | Backup scope or mode | Restoration |
|---|---|---|---|---|
| UpdraftPlus [1] [6] [7] | automatic backup schedules [1] | several remote storage destinations, FTP, and email [1] | database, plugins, themes, uploads, and core files [7] | one-click restores [1] [7] |
| WPvivid [1] [7] | automated scheduling [7] | Dropbox, Google Drive, Amazon S3, Microsoft OneDrive, DigitalOcean Spaces, FTP, [1] | advanced backup options [7] | — |
| BackWPup [5] [5] [5] | schedule backups manually, with WordPress cron, or through third-party cron serv [5] | third-party storage service, directory, or FTP [8] | which database tables and types to back up; website files, including content, pl [5] [5] | automatic and emergency restore [5] |
| BackUpWordPress [1] [8] | hourly, daily, weekly, and monthly scheduled backups [1] | a file storage service, zip, or the user’s own server [8] | the entire site or only the database or files [1] | — |
| Duplicator [1] [11] | manual backups without scheduling [1] | — | entire site [11] | — |
| BlogVault [1] [8] [11] | begins creating a backup when activated [1] | its own servers [1] | incremental backups [1] [8] [11] | one-click free staging for testing updates [11] |
| Site type | Recommended backup frequency |
|---|---|
| Smaller websites [2] | once a week [2] |
| High-activity websites with many posts [2] | daily backups [2] |
| Sites with frequent updates [3] | every few days or hourly [3] |
| Infrequently updated sites [3] | weekly or monthly [3] |
| Low-traffic websites with few monthly updates [9] | monthly [9] |
| Websites updated weekly or less frequently than monthly [9] | weekly [9] |
| Plugin | Scheduling | Storage or backup mode | Scope or restoration |
|---|---|---|---|
| UpdraftPlus | Automatic schedules [1] | Several remote destinations, FTP, and email [1] | Database, plugins, themes, uploads, and core files; one-click restores [7] |
| WPvivid | Automated scheduling [7] | Dropbox, Google Drive, Amazon S3, Microsoft OneDrive, DigitalOcean Spaces, FTP, and SFTP [1] | Advanced backup options [7] |
| BackWPup | Manual scheduling, WordPress cron, or third-party cron services [5] | Third-party storage service, directory, or FTP [8] | Selectable database tables and separately configured website files; automatic and emergency restore [5] |
| Duplicator | Manual backups without scheduling in Lite; scheduling requires Pro [1] | Storage destinations are not specified in the cited comparison evidence | Entire-site backup and transfer [11] |
| Jetpack Backup | Real-time backup positioning [6] | Storage destination is not specified in the cited comparison evidence | Positioned for high-transaction ecommerce stores [6] |
Key Takeaways
- Include both WordPress files and the database when you need a complete recovery.
- Set frequency according to how often your site changes, rather than relying only on a plugin default.
- Keep at least three to five recent backups and place copies in different locations.
- Run a manual backup before plugin, theme, core, or code changes.
- Test backup files and perform restore drills in staging or a local WordPress installation.
Frequently Asked Questions
What is the best plugin for WordPress backup?
The ledger doesn’t identify one universally best plugin. UpdraftPlus supports automatic schedules and one-click restores, BackWPup supports selectable tables and storage methods, WPvivid supports automated scheduling and multiple destinations, and Duplicator Lite provides manual backups [1].
What is the best WordPress backup service?
The available evidence doesn’t establish one best service. BlogVault provides incremental backups, stores them on its own servers, and offers staging for testing updates [1]. Jetpack Backup provides real-time backup positioning for high-transaction ecommerce stores [6].
How can I modify a WordPress plugin?
The ledger doesn’t document how to modify a plugin’s code or settings generally. For backup plugins, it does document changing schedules, backup items, destinations, database tables, and retention settings through plugin controls such as WPvivid’s schedule tab and BackWPup’s job settings [3].
How to create a backup in WordPress?
In WPvivid, select “WordPress Files + Database,” choose “Save to local,” and click “Backup Now” to create a full manual backup [3]. You can also configure automatic scheduled backups from the WPvivid Backup Schedule tab [3].
Sources
- Backup Battle: Which is the Best WordPress Backup Plugin? (2024-12-05)
- Backups – Advanced Administration Handbook (2023-03-28)
- How To Perform a WordPress Backup In Simple Methods (2023-05-10)
- How often should you backup your wordpress site? (2026-06-03)
- WordPress Backup: Step-by-step Tutorial – BackWPup (2022-08-04)
- Best WordPress Backup Plugins 2025
- 6 Best WordPress Backup Plugin for (Expert Review) (2025-09-03)
- How to Backup a WordPress Website (2019-02-15)
- The Optimal WordPress Backup Schedule for Your Website (2018-09-07)
- What WordPress Maintenance Plans Actually Include and Cost
- 5 best free Backup Plugins for WordPress (2016-12-30)