What is big
Options and tables, largest first. Rows that share a prefix become one line with a count and a total size, so 3,000 cache options read as one row. Post, comment, term and user meta get the same treatment, key by key.
Version 0.11.0 · Free WordPress plugin
See what is making your database big, who owns it, and what is safe to do about it. Anything it removes goes to a trash for 30 days first, so you can put it back.
It isn't on WordPress.org yet. The download link will appear here once the plugin is approved. WordPress 6.6+ and PHP 8.1+. Tested on MariaDB 10.6 and 11 and MySQL 8.4. The WooCommerce features were tested on WooCommerce 9.3 and newer. AI assistant access needs WordPress 6.9+.
| Size | 41 MB in 3,000 rows, all in one line. |
|---|---|
| Belongs to | Nothing installed. No active or inactive plugin or theme mentions this name. |
| Next step | Move them to the trash. Nothing is deleted for 30 days, and restore puts them back as they were. |
Nothing changes until you press a button, and every button shows its count first. A scan only reads your database and the files of your installed plugins.
Options and tables, largest first. Rows that share a prefix become one line with a count and a total size, so 3,000 cache options read as one row. Post, comment, term and user meta get the same treatment, key by key.
Each group gets an owner and the evidence behind it: WordPress core, an active plugin or theme, an inactive one, or "nothing installed uses this". A name that only looks similar is never proof, and when the plugin can't tell, it says unknown.
Options, meta rows, duplicate meta, cron events and leftover tables go to a trash for 30 days first. Tables are renamed, not dropped. A restore puts everything back, including the autoload flag.
Expired transients, old revisions, Action Scheduler history, orphan meta, spam and trashed comments, auto-drafts and trashed posts, the oEmbed cache, orphan term links, stale edit locks and duplicate meta. Each one re-checks its count before it acts, caps what one click does, and asks you to type DELETE when it can't be undone.
Stale order cleaning for drafts, failed, cancelled and pending orders, plus expired sessions and rate limits. Orders that were ever paid, refunded or part of a subscription are never offered. Works with custom order tables and legacy posts.
The biggest meta keys and who uses them, what fills the cron option, and tables that use a different character set than WordPress. The last one shows the statement to run and leaves the rest to you.
Every cleanup has a wp tablewright command. It only says what it would do until you add --yes.
Five jobs can run daily once you switch them on, each with a cap and a safety stop that holds back when the numbers look wrong. Deleting orders for good and posts is never automatic.
Off by default. An administrator can let an assistant read scan results. It can't delete or change anything.
The plugin makes no outside requests. A scan reads your database and the PHP files of your installed plugins and themes, and keeps the results on your site. It needs no account, and AmazingPlugins doesn't receive anything from your site.
Previews show names, counts and sizes. They never show a stored value, a customer name, a comment, or the arguments of a scheduled event.
Core data can't be touched. Before anything moves you see the exact count, and if the numbers changed since you looked, nothing happens. Big groups and every table ask you to type the name to confirm.
The trash keeps what you removed for 30 days, and you can download a backup file of any group first. The few things that can't be undone, like old revisions or deleting a comment for good, say so on the button.