About this plugin
CodingBunny Database Cleaner is a WordPress plugin that helps you analyze, filter, and safely remove unnecessary data from your database. It can identify orphaned options, leftover post meta, unused comments, transients, and other types of residual data, giving you a clear overview of what is stored in your database and allowing you to clean it when needed. On WooCommerce stores it also covers the data the shop leaves behind: products, orders, coupons, and customers.
The plugin attempts to detect the likely origin of database entries — such as plugin, theme, or WordPress core — so you can review data with additional context before performing any deletion.
Why use CodingBunny Database Cleaner?
- View database contents with detected origin information
- Remove unnecessary data with safety checks in place
- Improve database performance and reduce overhead
- Schedule automated cleanup tasks
- Contribute corrections when origin detection is inaccurate
Features
Tables
* Optimize, repair, and convert tables to InnoDB
* Delete unused tables
* Detect table sources
* Inspect the contents of any table in a paginated viewer
Options
* Delete unused options
* Manage and optimize autoloaded options
Posts
* Delete posts, revisions, auto drafts, and trashed posts
* Scheduled cleanup support
Post Meta
* Remove orphaned and unused post meta
* Scheduled cleanup support
Comments
* Delete spam, trashed, orphaned comments, pingbacks, and trackbacks
* Scheduled cleanup support
Comment Meta
* Remove orphaned and unused comment meta
* Scheduled cleanup support
User Meta
* Remove orphaned and unused user meta
* Scheduled cleanup support
Term Meta
* Remove orphaned and unused term meta
* Scheduled cleanup support
Term Relationships
* Remove unused term relationships
* Scheduled cleanup support
Post Types
* Remove unused post types
Transients
* Delete expired and unused transients
* Scheduled cleanup support
Cron Jobs
* Remove unused scheduled cron jobs
* Scheduled cleanup support
Action Scheduler
* Delete completed, failed, and canceled actions
* Clean up Action Scheduler logs
* Scheduled cleanup support
oEmbed Cache
* Remove oEmbed caches (all or expired only)
* Scheduled cleanup support
WooCommerce
* A dedicated section that appears only on stores, with one tab for products, orders, coupons, and customers
* Products: trashed products, auto drafts, revisions, orphaned variations, unused attributes, orphaned product terms and product meta, and products with missing data
* Orders: pending, abandoned, failed, canceled, and trashed orders, orphaned items, item meta, addresses, and operational data, plus orders whose customer no longer exists, which can be turned into guest orders
* Coupons: expired, unused, and trashed coupons
* Customers: customers with no orders, orphaned customer meta and analytics, inactive customers, and expired customer sessions
* Real orders, products, and customer accounts are only listed for review and are never deleted automatically
* Every WooCommerce entry is counted in one tab only, so nothing is reported twice
* The section keeps working after WooCommerce is uninstalled, so the data it left behind can still be removed
* Scheduled cleanup support, per tab or per single group
Full Database Cleanup
* Run a complete database cleanup in a single operation
* Works within a time budget, so it can be run again to continue on very large databases
Prefix Scanner
* Identify which plugin or theme an unknown database prefix belongs to
org directory
General Tools
* Multisite support (per-site or network-wide cleanup)
* Filtering, searching, and sorting across all modules
* Paginated results for large datasets
* Preview the stored value of options, meta keys, transients, and scheduled actions before deleting them
* Safety confirmations and nonce protection for all actions
* Counts refresh automatically when the database changes, when a plugin or theme is activated or removed, and after every cleanup
* Recognition of the custom fields, post types and taxonomies created with Advanced Custom Fields, Secure Custom Fields and JetEngine
* Recognition of the post types and taxonomies registered in code by a plugin or by your theme
* Option to contribute detection corrections
Learn More
For additional information about WordPress database optimization and maintenance practices, you can refer to the following resource:
com
Video Guide
A video overview of WordPress database cleanup and optimization techniques is available here:
External services
This plugin can connect to two external services. Both are used only inside the
Prefix Scanner tool (DB Cleaner → Report Match), never during normal database cleaning,
and never on the front end of your site.
1. WordPress.org Plugin and Theme Directory API
org
directory to find out which published plugin or theme a database prefix belongs to.
What is sent: the prefix you typed into the Prefix Scanner field, and nothing else. No site URL,
no user data, no database content.
When it is sent: only when you click “Start scan” in the Prefix Scanner, and only after the
local scans have failed to produce an exact match.
org, run by the WordPress Foundation.
org/about/privacy/
org/about/privacy/
2. Veloria code search
What it is used for: an optional extended search that looks for the prefix inside the published
source code of plugins and themes that are not installed on your site — the case the local scan
cannot cover.
What is sent: the prefix you typed into the Prefix Scanner field, and nothing else. No site URL,
no user data, no database content.
When it is sent: only when you click “Start scan” in the Prefix Scanner, and only if you have
explicitly enabled this option. The option is disabled by default. You can turn it on or off at
any time from the checkbox in the Prefix Scanner panel; while it is off, no request is made and
no data leaves your site.
What the service does with it: Veloria stores the search query and its results so that they can
be revisited, and keeps temporary server logs that include the IP address the request came from.
Veloria states that it does not sell, share or transfer data to third parties.
dev)
dev/terms
dev/privacy
Reporting an unknown match
The separate “Report Match” form sends an email to the plugin author with only the fields you
fill in yourself: the item type, the item name, the plugin or theme you associate it with, and
your notes, plus the plugin, WordPress and PHP version numbers. It is sent through your own
site’s mail system, it carries no site URL and no user data, and nothing is sent unless you
press the button.