WebHD

Database Clean-up

Measures what has piled up in the database (old revisions, emptied-but-kept trash, expired sign-ins, old logs) and removes it by hand or on a schedule, always showing the count first.

Version 1.0.1Updated November 17, 2026Performance & Caching

Get in line

Not open yet No card

Description

Measures what has piled up in the database (old revisions, emptied-but-kept trash, expired sign-ins, old logs) and removes it by hand or on a schedule, always showing the count first.

What it does

  • Database clean-up: old revisions (keep the newest N of each item), old trash, spam and trashed comments, expired sign-ins, dead API tokens, old attempt counters, old not-found entries, old activity records, left-behind rows
  • The count is shown first, and nothing is removed without a confirmation tick
  • Scheduled clean-up, about once a day, off until switched on, with a limit on rows per run
  • A record of what each clean-up removed and who started it
  • Report of settings loaded with every page (the autoload report)
  • Rows and stored text per Core table, and rows per module table (read-only)
  • A reminder and a link to export the site before cleaning
  • Persistent object cache, cache status and flush: there is no Redis-style cache on this platform. The database is SQLite beside the code (a file on Node, D1 on Cloudflare), so there is nothing to fill or flush Not built yet.
  • Table optimisation (OPTIMIZE / VACUUM): a module may not run it, and D1 looks after its own storage Not built yet.
  • Expired transients: this platform has none Not built yet.
  • Emptying the trash on the schedule: Core's delete needs a signed-in person so that other modules are told, so trash is emptied by hand Not built yet.
  • Exact size on disk per table: the database does not report it to a module; rows and stored text are shown instead Not built yet.
  • A history of scheduled-task runs to trim: Core keeps only each task's last result Not built yet.

Stands in for

Redis Object Cache, WP-Optimize.

These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.

What comes across

What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.

From WP-Optimize
Comes across: Whether clean-up runs on a schedule, how many revisions to keep, and the keep-the-last-N-weeks rule (applied to trash and to spam and trashed comments, in days).
Does not: The schedule's exact timing (it runs about daily here), auto-drafts, transients, pingbacks and trackbacks, table optimisation, page cache, image compression and minify settings, and the running total of space saved. Each one found in the file is named in the import report.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
In place of Advanced Database Cleaner
It keeps no settings worth carrying. The groups it cleans that exist here (revisions, trash, spam comments, orphaned rows) are covered.
In place of WP-Sweep
A clean-up tool: its few settings only choose what a sweep removes, and its counts describe the old database. The clean-ups here show their counts first and remove nothing without a confirmation tick.

No importer yet for: Redis Object Cache.

Using a plugin that is not named here? It is built for your site On The Fly. How that works

Changelog

  1. 1.0.1 November 17, 2026

    Database Clean-up 1.0.1: WP-Sweep is listed as replaced. Its settings only choose what a sweep removes.

  2. 1.0.0 November 17, 2026

    Database Clean-up: counts old revisions, trash, expired sign-ins, dead tokens and other leftovers, removes only what you tick after showing the numbers, can run daily within a row limit, and keeps a log of every run. Imports WP-Optimize settings.

Get Database Clean-up when WebHD opens

Hold a place for your site.

One form on the home page: your WordPress address, then your email.

Get in line

No card Takes a minute No fake scan