Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Backuply · Version history

Backuply changelog and version history

Latest version
1.6.0
Oct 22, 2026 (17 days ago)
Releases
38
since 2023
In the last year
10
about one every 38 days
Tested up to
WordPress 7.1.4
PHP 5.5 or later

Releases each year

  • 202310 releases
  • 20249 releases
  • 202510 releases
  • 20269 releases

20269 releases

  1. Backuply 1.6.0Latest

    • [Feature Pro] Backup Before Auto Updates: Automatic WordPress Core updates now wait until a backup is taken with your Auto Backup settings. If the backup fails, the update is held and retried later.
    • [Improvement Pro] Renamed the “Backup Before Updates” option to “Backup Before Manual Updates” to tell it apart from the new auto update option.
    • [Improvement] Hardened the database restore by restricting unserialization of restored option/meta values to data only (no objects).
    • [Bug-Fix] On some servers loopback request was getting blocked because the request did not had referrer set this has been fixed.
    • [Bug-Fix] If the config file could not be created when starting a restore, a PHP warning was thrown and the restoration file was not cleaned up. This has been fixed.
    • [Bug-Fix] Google Drive upload errors were shown as “100 Continue” instead of the actual error returned by Google Drive, and temporary Google Drive errors failed the backup instead of being retried. This has been fixed.
    • [Bug-Fix] PHP 8.5 was logging deprecation notices for curl_close() and finfo_close(). This has been fixed.
    • [Task Pro] A dependency has been update to it’s latest version.

  2. Backuply 1.5.9

    • [Security Fix] Fixed an issue related to the restoration process, reported by daroo [Wordfence].
    • [Bug-Fix] Cookie values with special characters like “;” were forwarded decoded in loopback requests, splitting them into invalid cookies which firewalls could block. This has been fixed.
    • [Bug-Fix] Check for an already running backup was not working, so a second backup could be started and the Stop Backup button stayed disabled. This has been fixed.
    • [Bug-Fix] Backups list was sorted by the site name in the backup file name instead of the backup time, showing backups out of order. This has been fixed.

  3. Backuply 1.5.8

    • [Improvement Pro] Added Code Signing: Every update now verifies the code signature to ensure secure updates.

  4. Backuply 1.5.7

    • [Bug-Fix] All cookies were not being passed in a backup request, that has been handled now.
    • [Bug-Fix] Restore was showing to have failed security check, this has been fixed.
    • [Bug-Fix] On migration the maintenance mode was not getting started because of wrong path, fixed now.
    • [Bug-Fix] In certain cases, when attempting to make a final call after import of DB in restoration process the database connection would not respond, this has been handled.

  5. Backuply 1.5.6

    • [Bug-Fix] There was an issue related to Windows path that has been fixed, reported by “Youssef EL MSIYAH”

  6. Backuply 1.5.5

    • [Feature Pro] pCloud Backup location support added.
    • [Improvement] noabort rule for LiteSpeed cache was added earlier if litespeed PHP extension was present, now it adds based on PHP SAPI or SERVER_SOFTWARE.
    • [Improvement] Option to scan and add LiteSpeed noabort rule added to Backuply support tab.
    • [Bug-Fix] There was a Google Drive access token cache issue, that has been fixed.

  7. Backuply 1.5.4

    • [Feature Pro] Option to trigger Backup when updating WordPress Core.
    • [Improvement] Added Self Diagnosis, help knowing if some firewall is blocking Backuply’s requests, and quick access to Backuply debug logs.
    • [Bug-Fix] There was an issue with the quota updating, if 2 locations of same Cloud location type were added.
    • [Bug-Fix] Minor UI fixes caused because of incompatibility with the new WordPress 7.0.
    • [Task] backup-migration and backup folders inside wp-content won’t be backed up.

  8. Backuply 1.5.3

    • [Improvement] Added option to use custom Backup rotation.
    • [Bug-Fix Pro] When AWS and AWS compatible locations were edited they were changing the base backup path, this has been fixed.
    • [Bug-Fix] There was an issue when activating of the Backuply plugin on Multi Site, this has been fixed.
    • [Task] Tested with WordPress 7.0.

  9. Backuply 1.5.2

    • [Improvement] Backup history is now sorted based on time, with recent backups at the top.
    • [Improvement] Backup history now includes pagination, displaying 20 backups per page.
    • [Bug-Fix] On backup database connection was not closing after usage, which cause issue for a user, this has been fixed.
    • [Task] .htaccess file has been excluded from restoration, it causes issue if environment of the server changes.
    • [Task] Adding Cache burst in case where backup requests were hitting Cloudflare cache.

202510 releases

  1. Backuply 1.5.1

    • [Bug-Fix] Backups could get stuck when certain special characters were present in file names.
    • [Bug-Fix] An issue with uploading backups to Backuply Cloud and AWS has been resolved.
    • [Bug-Fix] On some servers, the status logs stopped updating during backups because the server flagged the update requests as a loop. This issue has been addressed.

  2. Backuply 1.5.0

    • [Bug-Fix Pro] Custom cron key was getting updated on every update which was breaking Auto Backups for the users who were using Custom cron, this has been fixed.
    • [Bug-Fix] There was an issue with restore from custom locations, this has been fixed.

  3. Backuply 1.4.9

    • [Improvement Pro] Now you can use any S3 Compatible storage with Backuply.
    • [Bug Fix] Improved variable sanitization.

  4. Backuply 1.4.8

    • [Bug-Fix] There was an issue with migration, when WP_HOME and WP_SITEURL constants were set in the wp-config.php of the backup.
    • [Task] All .log files will be excluded form backups.
    • [Task] Minor refactor of the code.

  5. Backuply 1.4.7

    • [Bug-Fix Pro] For some cases, upload to OneDrive was getting stuck because OneDrive’s servers were either breaking the request abruptly or not responding. This has been fixed.
    • [Bug-Fix] In certain cases, the info file and version file were not getting added to the backup; this has been fixed.
    • [Bug-Fix] Size of a file uploaded through FTP was showing wrong when the backup size was more than 2GB; this has been fixed.
    • [Task] Backuply now handles UTC-based time zones as well. Earlier, it used to handle just the city-based based timezones of WordPress General settings.

  6. Backuply 1.4.6

    • [Bug-Fix] There was issue with restore on sites where Cyrillic characters were getting used, this has been fixed.
    • [Bug-Fix] In some specific case, backups were getting corrupt, due to some files were getting updated while the backup was happening so some default exclusions have been added.
    • [Task] Backuply will add LiteSpeed noabort rule in the htaccess file on install. LiteSpeed’s default config was causing issue with backups for some users.

  7. Backuply 1.4.5

    • [Task] Tested with WordPress 6.8.
    • [Task] Added Environment info in the support tab for easier debugging.
    • [Task] Cleanup of WP Cron after uninstall.

  8. Backuply 1.4.4

    • [Improvement] Backup upload speed has been improved, so now uploads will be faster.
    • [Improvement] Cleanup after restore has been made better.
    • [Security Improvements] Made some files at restore more random.
    • [Bug-Fix] On restore failure, email notification was not getting sent, this has been fixed.
    • [Bug-Fix] If the backup file tar.gz was not there on the remote storage and a attempt to restore was made then the restore was stuck in download loop, this has been fixed.

  9. Backuply 1.4.3

    • [Bug-Fix] There was an issue which was causing downloaded file to be of size 0, this has been fixed.

  10. Backuply 1.4.2

    • [Bug-Fix] For some users the download file was returning different file name, this has been fixed.
    • [Improvement] Restore was getting blocked in case where htaccess rules had some blocking rule, this has been handled.

20249 releases

  1. Backuply 1.4.1

    • [Improvement] The backup logs were overwhelming the browsers of some users, we have improved that by just logging the required info which reduces the backup logs.

  2. Backuply 1.4.0

    • [Task] Made some internal code changes.

  3. Backuply 1.3.9

    • [Task] Improved some internal codes and tested the same.

  4. Backuply 1.3.8

    • [Task] Tested with WordPress 6.7
    • [Bug-Fix] Settings page was getting killed when some data was not integer.
    • [Bug-Fix] functions.php was loading later than few of the registered hooks, which was causing issue to some users this has been fixed.

  5. Backuply 1.3.7

    • [Improvement] Added retries in Backuply cloud upload.

  6. Backuply 1.3.6

    • [Improvement] Error reporting has been improved.
    • [Task] Improved license handling.

  7. Backuply 1.3.5

  8. Backuply 1.3.4

  9. Backuply 1.2.6

202310 releases

  1. Backuply 1.2.2

  2. Backuply 1.2.1

  3. Backuply 1.1.8

  4. Backuply 1.1.6

  5. Backuply 1.1.4

  6. Backuply 1.1.3

  7. Backuply 1.1.2

  8. Backuply 1.1.1

  9. Backuply 1.1.0

  10. Backuply 1.0.9

Questions about Backuply’s releases

What is the latest version of Backuply?

1.6.0, released on Oct 22, 2026 (2 weeks ago). It’s tested up to WordPress 7.1.4 and needs PHP 5.5 or later.

How often is Backuply updated?

10 releases in the last year, about one every 38 days. Its first release on WordPress.org dates from February 2023.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Backuply’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.