Clean your database without fearing a timeout

See exactly what will be removed — before anything is

Every category is scanned and shown with an exact row count and a risk level. Conservative defaults keep the risky stuff unchecked, so a single click can never surprise you.

• Expired transients (including site transients)
• Orphaned post meta, comment meta, term relationships and user meta
• Spam and trashed comments, trackbacks and pingbacks
• Post revisions — with a “keep the most recent N” option
• Auto-drafts, oEmbed caches, old Action Scheduler entries
• Trashed posts and pages — high risk, never selected by default

Find the sneakiest performance killer

The report most cleaners skip: the largest autoloaded options and the total autoload size — the data loaded into memory on every page view. Report-only by design, since deleting the wrong option can break the plugin that owns it — we tell you what to ask your developer instead of handing you a footgun.

Table size, engine and overhead — one click to optimize

A dedicated Tables tab shows every table’s size, storage engine and reclaimable overhead, sorted so the most reclaimable table is always at the top. Optimize any single table with one click — no bulk “optimize everything” button, because a large table can briefly lock and that should always be a deliberate, one-table-at-a-time choice.

• Per-table size, engine and overhead at a glance
• Sorted by reclaimable space, largest first
• One-click OPTIMIZE TABLE, no bulk actions
• Honest “N/A” instead of a misleading number on shared-tablespace InnoDB setups

Set it, forget it, or keep full control

Turn on weekly automatic cleanup of the low-risk categories only — off by default, you switch it on only if you want it. Every run, manual or automatic, is written to a full history log with timestamp, category and row count, so nothing ever happens invisibly.

• Optional weekly automatic cleanup — low-risk categories only
• Configurable revision retention count
• Full history log for every run
• Timeout-free: work runs in small batches chained in the background, resumable if interrupted