Version 0.16.1 · Free WordPress plugin

Tablewright Database Manager.

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+.

Example rowOptions, biggest first
Probably leftover

3,000 options that start with example_cache_

Size41 MB in 3,000 rows, all in one line.
Belongs toNothing installed. No active or inactive plugin or theme mentions this name.
Next stepMove them to the trash. Nothing is deleted for 30 days, and restore puts them back as they were.
Example layout, not a scan of your site.

What's in version 0.16.1

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.

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.

Who owns it

Each group gets an owner and the evidence behind it: WordPress core, an active or inactive plugin or theme, a plugin you removed, or "nothing installed uses this". It reads the code of what you have installed and knows the names about 100 popular plugins use, so leftovers say whose they are.

Findings, sorted by urgency

After a scan the Overview lists what needs attention as errors, warnings, recommended and optional, each marked safe (you can restore it), unsafe (deleted for good) or report only. The count shows next to the menu item.

A trash you can restore from

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.

Cleanups that show a count first

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.

WooCommerce

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.

Reports that change nothing

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.

The command line

Every cleanup has a wp tablewright command. It only says what it would do until you add --yes.

Automatic cleanup, off by default

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.

AI assistant access, read only

Off by default. An administrator can let an assistant read scan results. It can't delete or change anything.

Your data stays on your server.

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.

A way back.

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.

What it doesn't do.

  • It doesn't guess when it isn't sure. If an installed plugin might use a name, it says "review it", never "leftover".
  • It doesn't change character sets or collations. It shows the statement and leaves the rest to you.
  • It doesn't clean by itself unless you switch that on. Five jobs can run daily, and all of them are off by default.
  • It has no paid version.

How it compares

The three most installed database cleaners on WordPress.org, from their own pages and support forums, checked on 16 November 2026. Prices change, so follow the links.

TablewrightWP-OptimizeAdvanced Database CleanerWP-Sweep
Names the plugin that left data behindYes, free, for options, tables and metaTables only, matched by name (source)Premium, from $39 a year (source)No (source)
Undo after you cleanTrash for 30 days, restore in one clickNo, back up first (source)No, back up first (source)No, "there is no undo" (source)
Leftover tables of removed pluginsRenamed, not dropped, so they come backPurging them is Premium (source)Ownership is Premium (source)Not offered (source)
Groups 3,000 rows of one prefix into one lineYesNot seen in their documentation
WP-CLIYesPremium (source)Not documentedYes (source)
PriceFree, no paid versionFree, Premium from $49 a year (source)Free, Premium from $39 a year (source)Free

WP-Optimize also caches pages and compresses images, which Tablewright doesn't. If you need those, use both.

How we tested it.

We installed the 200 most popular plugins on WordPress.org one at a time on a clean site and recorded every option and table each one created. A fifth of them were kept aside and never taught the plugin anything.

Then we installed those 29 together, scanned, uninstalled half the normal way and scanned again. With all of them active, Tablewright called none of their data leftover. After the uninstalls it found 94% of the groups they left behind (90% by size) and named the plugin for 66%.

The test runs again before every release, and a release that calls any live data leftover doesn't ship.

Questions.

Is "probably leftover" safe to remove?

It means no installed code uses the name. Some plugins build names while they run, which can make data look unused. That's why removal goes to the trash first, and Restore puts it back.

What can't be undone?

Expired transients, old revisions, finished Action Scheduler history, and comments or posts deleted for good. Those are marked unsafe and ask you to confirm. Everything else goes to the trash.

Does it clean anything by itself?

Only if you switch it on. Five daily cleanups exist, each with a cap and a stop that holds back when the numbers look wrong. All are off by default.

What about WooCommerce?

It cleans orders that never became a sale (old checkout drafts, failed, cancelled and pending orders) into the WooCommerce trash first. Completed, processing, on-hold, refunded, paid and subscription orders are never offered. It works with custom order tables.

Does it slow my site down?

It does nothing until you press Scan, then works in short steps and shows its progress. A site with 100,000 options and a million meta rows scanned in about 2 seconds in our tests.

Does it work on multisite?

Yes, per site. A site admin sees only that site's tables, and shared user tables aren't cleaned from a subsite.