All solutionsIn development

WP OptimizerWordPress storage, cleanup and backup

Inventory what a WordPress site is storing, reclaim space safely, and keep backups that are known to restore.

This is not released. A site owner can now take a verified backup of a whole WordPress installation, have it taken daily or weekly without being asked, and restore from it, all from the WordPress admin. What is missing is not a feature but evidence from a second stack: all of it has been proven on Apache, MySQL 8, PHP 8.3 and about 6,900 files, and nothing yet says what happens on nginx with PHP-FPM, on MariaDB, at 200,000 files, or alongside WooCommerce and a page builder. Old backups can be deleted once a verified newer one supersedes them, but only when a person asks — the schedule never prunes. There is no undo and no selective restore, and a restore needs a site that still boots.

What exists today

  • A backup you start from the WordPress admin: the whole installation and this site's own database tables, in short steps so a request timeout cannot cut it off, resuming where it stopped
  • A schedule the site keeps for itself, daily or weekly: a firing that collides with a job already running is skipped with a reason rather than queued, and only the two intervals it offers are accepted, because WordPress will take a recurrence that does not exist and then schedule nothing
  • Deleting old backups, when you ask for it: only a backup that a verified newer one supersedes is ever a candidate, the newest verified backup can never be deleted at any setting, you see what would go and what is being kept and why before confirming by typing DELETE, and every deletion is recorded with who asked
  • A restore you start from the same place: staging and verification finish before any live file is touched, the screen says which side of that line the job is on, and it asks you to type the word RESTORE
  • A restored wp-config.php that keeps this server's database connection and the backup's table prefix, which is what makes a restore onto a different installation work rather than appear to
  • Visitors held at a 503 with an explanation while files are being replaced, and the login screen left reachable
  • A backup that has been restored from says so, and no other backup picks up the claim: digests matching and a restore actually performed are different things, and only the second stands a site back up
  • Refusals: too little free space to finish, a file that changed between being hashed and being archived, a destination proven downloadable over the web, and target directories the web user cannot write
  • Job state stored beside the archive rather than in the database, so it is still readable when the database is not
  • A read-only storage preview: files sampled by category, and the database tables belonging to this site's own prefix
  • Every route checks an administrator capability, not merely that somebody is signed in

Not available yet

  • Evidence from a second stack. All of the above was proven on Apache, MySQL 8, PHP 8.3 and about 6,900 files, and not on nginx with PHP-FPM, on MariaDB, at 200,000 files, or alongside WooCommerce and a page builder
  • Pruning that happens on its own. Deleting superseded backups is always something a person starts, so a site left to its schedule still fills its disk and is then refused its next backup by the free-space check, which now names what a prune would free and refuses anyway
  • Choosing the time of day it runs, or a different schedule per site. A scheduled backup also depends on WP-Cron, which fires only when somebody requests a page
  • Undo, and selective restore. Files a restore displaces are kept and their location reported, but putting them back is manual
  • Restoring a site that no longer boots, because the screen is served by WordPress. That case belongs to the separately distributed recovery tool, which inspects and verifies rather than restores
  • Deleting, quarantining or compressing anything in the site itself. What can be deleted today is an old backup, never site content
  • Backups kept offsite, and an agency console across several sites

What we plan to deliver

  • File and database inventory with honest coverage
  • Verified full backup before any cleanup
  • Preview-only cleanup with a reversible quarantine
  • Offsite copies and scheduling

Who it is for

Agencies and businesses running their own WordPress sites

Planned integrations

Self-hosted WordPress plugin, offsite object storage

How value will be measured

  • Restores proven on a disposable site
  • Storage reclaimed and verified
  • Sites covered by a recent backup

High-impact actions will require explicit authorization and human review.