Mike

<p>WP Backup is a comprehensive backup solution for WordPress. Effortlessly create and restore backups of your entire site, including database, plugins, themes, uploads, and demo content. Designed for reliability, speed, and ease of use, with a modern React-powered admin interface.</p>
<h4>Features</h4>
<ul>
<li>One-Click Backup & Restore</li>
<li>Database Import/Export</li>
<li>Plugin & Theme Backup</li>
<li>Uploads & Folder Backup</li>
<li>Demo Content Import (for theme/plugin developers – coming soon)</li>
<li>Modern Admin UI (React-powered)</li>
<li>AJAX & Nonce Security</li>
</ul>
<h4>Demo Content Import Solution</h4>
<p>WP Backup provides a developer-friendly way to package and import demo content, making it ideal for theme and plugin authors who want to offer a quick start for their users.</p>
<h4>⚠️ PHP 8.0 or Higher Required – Why?</h4>
<p>Worry Proof Backup is built with modern techniques to ensure your data restores safely, quickly, and reliably—even when working with large backup files.</p>
<p>We require PHP 8.0 or higher for the following reasons:</p>
<h3>🚀 1. Superior Performance</h3>
<p>PHP 8 introduces Just-In-Time (JIT) compilation, which significantly speeds up operations like:<br />
* Extracting ZIP archives with tens of thousands of files<br />
* Reading and writing large file contents in memory<br />
* Fast, stable looping over file lists</p>
<h3>🔒 2. Improved Stability and Accuracy</h3>
<p>In PHP 7, some built-in functions like <code>stream_get_contents()</code> can behave inconsistently with large files or streams. PHP 8 provides:<br />
* More reliable file extraction<br />
* Fewer write failures and timeouts<br />
* Better handling of memory streams</p>
<h3>🧠 3. Better File System Handling</h3>
<p>Our plugin supports restoring entire folders with thousands of files, which demands fast and reliable filesystem operations—something PHP 8 handles far better than PHP 7.</p>
<h4>💡 Still Using PHP 7?</h4>
<p>We strongly recommend upgrading to PHP 8.0+ for optimal compatibility, performance, and security—not just for this plugin, but for your entire WordPress site.</p>
<p>Most hosting providers support PHP 8—feel free to reach out to your hosting support team and ask for an upgrade.</p>
<h3>External services</h3>
<ul>
<li>No External services</li>
</ul>
<h3>Github repository</h3>
<ul>
<li><a href="https://github.com/miketropi/worry-proof-backup" rel="nofollow ugc">Plugin Source</a></li>
</ul>
<h3>License</h3>
<p>GPL v2 or later. See https://www.gnu.org/licenses/gpl-2.0.html for details.</p>


Worry Proof Backup

Effortless, reliable WordPress backups and restores—database, plugins, themes, uploads, and more.

andrewjbaker

<p>Most backup plugins fail on large or busy sites. They hit PHP memory limits, execution timeouts, or external storage quotas. <strong>CloudScale Backup & Restore</strong> is built differently.</p>
<p>It uses a pure PHP streaming implementation for database dumps and restores that reads the database in chunks and never loads the whole thing into memory at once, so it works reliably on any WordPress host without requiring server-level tools.</p>
<p><strong>What it backs up</strong></p>
<p>Choose any combination of:</p>
<ul>
<li>Full WordPress database: all tables, all data</li>
<li>Media uploads folder (<code>/wp-content/uploads/</code>)</li>
<li>Plugins folder (<code>/wp-content/plugins/</code>)</li>
<li>Themes folder (<code>/wp-content/themes/</code>)</li>
</ul>
<p>Each backup is packaged as a single <code>.zip</code> file with a descriptive filename that reflects exactly what it contains.</p>
<p><strong>Key features</strong></p>
<ul>
<li>Run manual backups with one click: choose which components to include each time</li>
<li>Configurable automatic scheduling: set your interval in days (1, 7, 30, or any number) and the exact hour of day to run</li>
<li>Configurable retention: keep the last N backups; older ones are deleted automatically after each run</li>
<li>Full backup history: view all stored backups with filename, type label, size, creation date, and age</li>
<li>Download any backup directly from the WordPress admin</li>
<li>Restore the database from any stored backup or by uploading a <code>.zip</code> or <code>.sql</code> file</li>
<li>Safe restore workflow: puts the site into WordPress maintenance mode before restoring and removes it after</li>
<li>Explicit snapshot warning before any restore operation: requires confirmation before proceeding</li>
<li>System info panel: shows which backup and restore method will be used on your server, memory limits, and backup storage path</li>
<li>Backup directory protected from direct web access with <code>.htaccess</code> deny-all</li>
<li>All passwords passed to CLI tools via environment variable, not shell arguments</li>
</ul>
<p><strong>Automatic backups are off by default.</strong> Run your first backup manually to confirm everything works on your server, then configure a schedule if you need one.</p>
<p><strong>Reliable PHP-native implementation</strong></p>
<p>The plugin uses a pure PHP streaming implementation for all database operations: no server-level tools required.</p>
<p>For database backup:</p>
<ul>
<li>Reads each table in 500-row chunks via <code>$wpdb</code>. Never loads the full database into memory. Works on any WordPress host.</li>
</ul>
<p>For database restore:</p>
<ul>
<li>Parses SQL statement by statement with a character-level parser that correctly handles quoted strings, escaped characters, and multi-line <code>INSERT</code> statements. Handles files of any size.</li>
</ul>
<p>The System Info card on the plugin page shows the backup and restore method in use on your server.</p>
<p><strong>Backup file naming</strong></p>
<p>Backup filenames describe their contents exactly, making them easy to identify without opening them:</p>
<ul>
<li><code>backup_full_2026-02-21_03-00-00.zip</code>: all four components</li>
<li><code>backup_db_2026-02-21_14-35-00.zip</code>: database only</li>
<li><code>backup_db-media-plugins_2026-02-21_09-10-00.zip</code>: three components</li>
<li><code>backup_plugins-themes_2026-02-21_22-00-00.zip</code>: files only, no database</li>
</ul>
<p><strong>Restore safety</strong></p>
<p>Clicking Restore DB opens a confirmation modal that:</p>
<ol>
<li>Shows the exact backup file name and creation date you are restoring from</li>
<li>Displays a warning box explaining what will happen step by step</li>
<li>Requires you to tick a checkbox: <em>“I have taken a server snapshot and understand this will overwrite the live database”</em></li>
<li>Only enables the Restore button after that checkbox is ticked</li>
</ol>
<p>During restore, WordPress’s native <code>.maintenance</code> file is created so visitors see the standard maintenance page. It is always removed when restore finishes, whether the restore succeeded or failed. The plugin header shows a live badge indicating whether the site is online or in maintenance mode.</p>
<p><strong>Backup zip contents</strong></p>
<p>Each zip includes a <code>backup-meta.json</code> with metadata: plugin version, creation timestamp, WordPress version, site URL, table prefix, and which components were included. This makes it easy to verify a backup without restoring it.</p>
<h3>External Services</h3>
<h4>Telegram Bot API</h4>
<p><strong>Service:</strong> Telegram Messenger Inc.<br />
<strong>Website:</strong> https://telegram.org<br />
<strong>Endpoint:</strong> https://api.telegram.org/bot{token}/sendMessage<br />
<strong>Data sent:</strong> An error summary message containing: the PHP error message, the file name and line number where the error occurred, and the relevant operation context (e.g. backup or restore task name). No personal visitor data or post content is transmitted.<br />
<strong>When data is sent:</strong> Only when a plugin error is caught and you have configured a Telegram bot token and chat ID in the plugin’s Notifications settings. No data is sent if the Telegram integration is not configured.<br />
<strong>Purpose:</strong> Sends real-time error alert notifications to a Telegram chat of your choosing so site owners can respond to backup or restore failures quickly.</p>
<p>Telegram Privacy Policy: https://telegram.org/privacy<br />
Telegram Terms of Service: https://telegram.org/tos<br />
Telegram Bot API documentation: https://core.telegram.org/bots/api</p>
<h3>External services</h3>
<p>This plugin optionally connects to third-party services when those features are configured by the site administrator. No data is sent to any external service unless the administrator has explicitly enabled the relevant integration.</p>
<h4>Amazon S3 (optional cloud backup)</h4>
<p>When S3 settings are configured, the plugin uploads backup zip files directly<br />
to the administrator’s own S3 bucket via the AWS S3 REST API (no external<br />
tools required). Only the backup zip file is transmitted. Credentials (bucket<br />
name, access key ID, secret access key, region) are stored in the WordPress<br />
options table and are never sent anywhere except to the AWS S3 endpoint.<br />
API endpoint contacted: https://s3.{region}.amazonaws.com/<br />
Terms of Service: https://aws.amazon.com/service-terms/<br />
Privacy Policy: https://aws.amazon.com/privacy/</p>
<h4>Google Drive (optional cloud backup)</h4>
<p>When Google Drive settings are configured, the plugin transfers backup zip files<br />
to the administrator’s own Google Drive account using the Google Drive v3 REST<br />
API and OAuth 2.0. No data is sent unless the administrator has completed the<br />
OAuth authorisation flow (entered a Client ID and Client Secret from Google<br />
Cloud Console and clicked “Connect to Google Drive”). Only the backup zip file<br />
is uploaded. OAuth tokens (access token and refresh token) are stored in the<br />
WordPress options table.<br />
API endpoint contacted: https://www.googleapis.com/ and https://oauth2.googleapis.com/<br />
Terms of Service: https://policies.google.com/terms<br />
Privacy Policy: https://policies.google.com/privacy</p>
<h4>Dropbox (optional cloud backup)</h4>
<p>When Dropbox settings are configured, the plugin transfers backup zip files to<br />
the administrator’s own Dropbox account using the Dropbox v2 REST API and<br />
OAuth 2.0. No data is sent unless the administrator has completed the OAuth<br />
authorisation flow (entered an App Key and App Secret from the Dropbox App<br />
Console and clicked “Connect to Dropbox”). Only the backup zip file is<br />
uploaded. OAuth tokens are stored in the WordPress options table.<br />
API endpoint contacted: https://api.dropboxapi.com/ and https://content.dropboxapi.com/<br />
Terms of Service: https://www.dropbox.com/terms<br />
Privacy Policy: https://www.dropbox.com/privacy</p>
<h4>Microsoft OneDrive (optional cloud backup)</h4>
<p>When OneDrive settings are configured, the plugin transfers backup zip files to<br />
the administrator’s own Microsoft OneDrive account using the Microsoft Graph<br />
REST API and OAuth 2.0. No data is sent unless the administrator has completed<br />
the OAuth authorisation flow (entered an Azure App Client ID and Client Secret<br />
and clicked “Connect to OneDrive”). Only the backup zip file is uploaded.<br />
OAuth tokens are stored in the WordPress options table.<br />
API endpoint contacted: https://graph.microsoft.com/ and https://login.microsoftonline.com/<br />
Terms of Service: https://www.microsoft.com/en-us/servicesagreement/<br />
Privacy Policy: https://privacy.microsoft.com/en-us/privacystatement</p>
<h4>CloudScale Managed Cloud Backup (optional, paid service)</h4>
<p>When the administrator subscribes to the optional CloudScale Managed Cloud Backup<br />
service, the plugin contacts the CloudScale broker to request a short-lived,<br />
prefix-scoped Amazon S3 access token, then uploads backup zip files directly to<br />
CloudScale’s managed S3 storage (hosted in the EU, eu-west-1). Only the site’s<br />
domain name, the subscription licence key, and the backup zip file are involved;<br />
the backup bytes are uploaded straight to S3 and do not pass through the broker.<br />
No data is sent unless the administrator has subscribed and entered a licence key.<br />
API endpoint contacted: https://api.cloudscale.consulting/ (broker) and<br />
https://cloudscale-backup-restore-global.s3.eu-west-1.amazonaws.com/ (storage)<br />
Terms of Service: https://cloudscale.consulting/terms<br />
Privacy Policy: https://cloudscale.consulting/privacy</p>
<h4>PayPal (optional, payment for Managed Cloud Backup)</h4>
<p>Subscription payments for the optional CloudScale Managed Cloud Backup service are<br />
processed by PayPal. Payment details are entered on PayPal’s own hosted checkout<br />
page and are never collected, stored, or transmitted by this plugin. When the<br />
administrator starts a subscription, the subscriber’s email address and a PayPal<br />
order amount ($10.00 USD) are sent directly from the WordPress server to the PayPal<br />
REST API (api-m.paypal.com) to create a checkout session; no payment-card data is<br />
handled by the plugin or the WordPress site. No data is sent unless the administrator<br />
chooses to subscribe to the paid service.<br />
API endpoint contacted: https://api-m.paypal.com/ (live) or<br />
https://api-m.sandbox.paypal.com/ (sandbox testing)<br />
Terms of Service: https://www.paypal.com/us/legalhub/useragreement-full<br />
Privacy Policy: https://www.paypal.com/us/legalhub/privacy-full</p>
<h4>Paystack (legacy fallback, payment for Managed Cloud Backup)</h4>
<p>When PayPal credentials are not configured, subscription payments fall back to<br />
Paystack. Card details are entered on Paystack’s own hosted checkout page and are<br />
never collected, stored, or transmitted by this plugin. When the administrator starts<br />
a subscription, the subscriber’s email address is sent to CloudScale to create the<br />
Paystack checkout session; no payment-card data is handled by the plugin or the<br />
WordPress site. No data is sent unless the administrator chooses to subscribe.<br />
API endpoint contacted: https://api.paystack.co/ (via the CloudScale broker) and<br />
https://checkout.paystack.com/ (hosted checkout)<br />
Terms of Service: https://paystack.com/terms<br />
Privacy Policy: https://paystack.com/privacy</p>
<h4>AWS EC2 / AMI snapshots (optional, AMI snapshot feature only)</h4>
<p>When the AMI snapshot feature is used, the plugin reads instance metadata<br />
(instance ID and region) from the local EC2 Instance Metadata Service at<br />
http://169.254.169.254. This address is only reachable from within an EC2<br />
instance and no data leaves the server at this step. AMI creation, status poll,<br />
deregister, and snapshot delete requests are then issued directly to the AWS<br />
EC2 REST API (no external tools required). The same AWS credentials<br />
(access key ID and secret key) used for S3 are used; if none are configured<br />
the plugin attempts to use the EC2 instance role via IMDS.<br />
API endpoint contacted: https://ec2.{region}.amazonaws.com/<br />
Terms of Service: https://aws.amazon.com/service-terms/<br />
Privacy Policy: https://aws.amazon.com/privacy/</p>
<h4>Automatic Crash Recovery: health check probe (optional)</h4>
<p>When Automatic Crash Recovery is enabled, the plugin periodically sends an HTTP<br />
request to the administrator-configured health check URL to verify the site is<br />
responding. The URL defaults to the site’s own home URL. No personal data is<br />
transmitted. The request is a plain GET with no authentication payload. The<br />
same probe is made when the administrator clicks “Test Health Check” in the<br />
plugin settings. If a system-cron watchdog script is installed on the server,<br />
that script also probes this URL independently via curl. The health check URL<br />
is set by the administrator and is never shared with any third party.<br />
No Terms of Service or Privacy Policy apply (the request goes to a URL you own).</p>
<h4>Twilio (optional SMS crash alerts)</h4>
<p>When Twilio SMS alerting is configured, the plugin sends an SMS notification to<br />
the administrator’s phone number via the Twilio Messaging API whenever Automatic<br />
Crash Recovery rolls back a plugin. Only the alert text, the configured “from”<br />
number, and the configured “to” number are transmitted. No backup data or<br />
personal user data is sent. No data is transmitted unless Twilio credentials<br />
have been explicitly entered and the SMS feature is enabled.<br />
Terms of Service: https://www.twilio.com/en-us/legal/tos<br />
Privacy Policy: https://www.twilio.com/en-us/legal/privacy</p>
<h4>ntfy (optional push notifications)</h4>
<p>When ntfy is enabled, the plugin sends a push notification to the<br />
administrator-configured ntfy topic URL on backup, restore, and plugin rollback<br />
events. The notification contains the site name and a brief status message (e.g.<br />
“Backup completed” or “Plugin rolled back”). No backup data, no personal user<br />
data, and no authentication credentials are transmitted in the notification<br />
payload. No data is sent unless ntfy has been explicitly enabled and a topic URL<br />
entered by the administrator.</p>
<p>The plugin defaults to the hosted ntfy.sh service, but any self-hosted ntfy<br />
server URL may be entered instead. When using the hosted ntfy.sh service:<br />
Terms of Service: https://ntfy.sh/tos<br />
Privacy Policy: https://ntfy.sh/privacy</p>
<h3>Files written outside the plugin folder</h3>
<p>The Automatic Crash Recovery feature writes a single file outside the plugin<br />
folder when it is enabled: <code>wp-content/fatal-error-handler.php</code>. This is a<br />
WordPress-recognised drop-in file (documented in the WordPress Developer<br />
Handbook under <code>get_dropins()</code>). WordPress core checks for this file on every<br />
request; if present, it replaces the default fatal-error screen with a custom<br />
handler. The plugin uses this mechanism to show a branded recovery page to<br />
visitors while a crash is being fixed, instead of a blank white screen.</p>
<p>The file is written using the WordPress Filesystem API (WP_Filesystem). It is<br />
only written when the feature is enabled, only overwritten if it was written by<br />
this plugin (identified by an internal marker), and is deleted when the feature<br />
is disabled or the plugin is uninstalled. No personal data is stored in this file.</p>
<h3>Privacy Policy</h3>
<p>CloudScale Backup & Restore does not collect, transmit, or store any personal data. All backups are stored locally in the <code>cloudscale-backups/</code> folder inside your WordPress uploads directory. No telemetry or analytics are sent by this plugin. Optional cloud backup features (S3, Google Drive, Dropbox, OneDrive, AMI snapshots) transmit data only when explicitly configured by the site administrator. See the External services section above.</p>


CloudScale Backup & Restore

WordPress backup and restore. Backs up database, media, plugins and themes into a single zip. No timeouts, no limits.

Worry Proof Backup vs CloudScale Backup & Restore