CodingBunny Database Cleaner
Keep your WordPress database fast and clean by removing orphaned data left behind by plugins, themes, and WordPress core.
Solid choice
CodingBunny Database Cleaner is a solid plugin choice in 2026, with a few things worth checking first. It runs on 200+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 76/100 on our health check.
- Actively developed — last update 2 weeks ago
- Tested with the latest WordPress (7.1)
- Momentum — downloads up 17% vs the previous 30 days
- Small user base (200+ active installs)
- Very few reviews so far
- Needs PHP 8.2 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where CodingBunny Database Cleaner stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| clean | #28 |
| database | #16 |
| Optimize | >100 |
| performance | >100 |
| schedule | #90 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 2 reviews
About CodingBunny Database Cleaner
From the official readme · v1.5.3Description
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
* Local pattern and source code scan, with an optional lookup on the WordPress.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:
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
What it is used for: when you run a prefix scan, the plugin queries the official WordPress.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.
Service provider: WordPress.org, run by the WordPress Foundation.
Terms of service: https://wordpress.org/about/privacy/
Privacy policy: https://wordpress.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.
Service provider: Veloria (https://veloria.dev)
Terms of service: https://veloria.dev/terms
Privacy policy: https://veloria.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.
Installation
1. Via WordPress dashboard
- Go to Plugins → Add New
- Search for “CodingBunny Database Cleaner”
- Click Install Now and then Activate
2. Via upload
- Download the plugin ZIP file
- Go to Plugins → Add New → Upload Plugin
- Select the ZIP file and install it
- Activate the plugin
3. Via FTP
- Extract the plugin archive
- Upload the folder to /wp-content/plugins/
- Activate it from the Plugins menu
After activation
Open the DB Cleaner menu in your WordPress dashboard sidebar.
Frequently asked questions
Is this plugin safe?
All cleanup actions require administrator permissions and are protected by nonces and confirmation prompts. Before deleting anything, the plugin checks again that each row is still eligible for removal. It is still recommended to back up your database before performing any cleanup.
Can deleted data be recovered?
No. Deleted data cannot be automatically restored. Always create a backup before cleanup operations.
Does it support Multisite?
Yes. You can clean individual subsites or the entire network. Network-wide operations require network administrator permissions.
How does detection work?
The plugin matches database entries against known patterns to identify their likely origin (plugin, theme, or core). Custom fields and custom post types are a special case, because their names are chosen by whoever created them rather than by the plugin: for Advanced Custom Fields, Secure Custom Fields and JetEngine the plugin reads the definitions stored in your own database instead of guessing from the name, and for the post types and taxonomies registered in code it records which plugin or theme registered them. Users can submit corrections to improve accuracy.
Is it suitable for large databases?
Yes. Counting, filtering, and sorting are performed by the database itself rather than in PHP, results are paginated, and deletions run in batches within a time budget. For very large databases, running the full cleanup more than once is normal: each run continues where the previous one stopped.
Does the plugin send any data anywhere?
Only inside the Prefix Scanner, and only when you start a scan. The scanner can query the WordPress.org directory, and it can optionally use an external code search service that is disabled until you enable it yourself. In both cases the only thing sent is the prefix you typed. See the “External services” section below for the full details.
Does it work with WooCommerce?
Yes. When a store is detected the plugin adds a WooCommerce section with four tabs — Products, Orders, Coupons, and Customers — that cover the data WooCommerce leaves behind. Orders are deleted through WooCommerce itself, so items, notes, and analytics go with them. Real orders, products, and customer accounts are never removed automatically: they are listed for you to review. If WooCommerce is uninstalled and its data stays in the database, the section remains available so you can remove the leftovers.
What are the system requirements?
PHP 8.2 or later and WordPress 6.2 or later. If your server does not meet these requirements the plugin will not load and will tell you why, leaving the rest of your site untouched.
Changelog
Custom fields and post types made with ACF, Secure Custom Fields or JetEngine are no longer reported as unknown, unused product attributes and leftover settings of deleted themes can finally be removed, and the counters now match what the cleanup actually deletes.
1.5.3 – 10/01/2026
- New: custom fields created with Advanced Custom Fields or Secure Custom Fields are now attributed to the plugin instead of being reported as unknown, including the fields registered in code, the values stored on users, terms and options pages, and the post types and taxonomies created from their interface
- New: the same recognition for JetEngine — its custom post types, taxonomies and meta fields are read from its own definitions instead of being guessed from the name, which could attribute them to an unrelated plugin
- New: post types and taxonomies registered in code, by a plugin or by your theme, are now attributed to whoever registered them, and keep that attribution even after that plugin or theme has been removed
- Fixed: the settings left behind by a deleted theme (theme_mods_) were reported as unused but could not be removed; they can now be deleted, while the settings of the active theme and of any theme still installed stay protected
- Fixed: the Unused relationships filter counted the orphaned rows but did not list them, so the number and the table disagreed; both now use the same query
- Fixed: in the Products tab the unused product attributes could not be removed and were reported as still in use, because the query that checks each row again failed on MySQL
- Fixed: attribute values left behind by an attribute that had already been deleted can now be removed; before, WordPress refused them because their taxonomy no longer exists
- Fixed: the detected origins were kept until the plugin version changed, so a newly recognised field or plugin only showed up later; any cleanup now refreshes them
- Improved: a theme that is installed but not currently active is now recognised as installed, so the entries that belong to it are no longer reported as unused
- Improved: the “Delete unused options” button now counts only the options that can actually be removed, so the number always matches what the cleanup deletes
- Improved: the counts are refreshed automatically when a theme is installed or deleted, as already happens for plugins
- Improved: every cleanup now refreshes the same set of caches, so counts and detected origins can no longer fall out of step with each other
- Improved: scheduled cleanups left over from features that no longer exist are now removed from the WordPress cron, instead of staying there for good
- Improved: added recognition for additional plugins
1.5.2 – 09/29/2026
- Improved: added recognition for additional plugins
1.5.1 – 09/27/2026
- Fixed: on sites without WooCommerce the plugin no longer queries the columns of tables that do not exist, which caused database errors while WordPress was starting up
- Fixed: the WooCommerce tabs now build their queries only when a store or its leftover data is actually found
- Improved: the WooCommerce queries are now assembled when a screen or a cleanup runs, instead of on every request
1.5.0 – 09/24/2026
- New: WooCommerce section with four dedicated tabs — Products, Orders, Coupons, and Customers
- New: Products tab — trashed products, auto drafts, revisions, orphaned variations, unused attributes, orphaned product terms, orphaned product meta, and products without a title, a price, or variations
- New: Orders tab — old pending, failed, and canceled orders, abandoned guest orders, trashed orders, orphaned items, item meta, addresses, and operational data, plus orders linked to a deleted customer, which can be turned into guest orders instead of being deleted
- New: Coupons tab — expired, unused, and trashed coupons
- New: Customers tab — customers with no orders, orphaned customer meta, orphaned customer analytics, inactive customers, and expired customer sessions
- New: the WooCommerce tabs keep working after WooCommerce is uninstalled, so the data left in the database can still be removed
- New: scheduled cleanup for each WooCommerce tab and for each single group
- Improved: every WooCommerce entry is counted in one tab only, so products, orders, and coupons are no longer reported both in their tab and in the Posts, Post Meta, User Meta, or Term Relationships tabs
- Improved: product reviews and comments on products are managed in the Comments tab together with every other comment
- Improved: a comment is now considered orphaned also when the comment it replied to no longer exists
- Improved: the counts are refreshed automatically when a plugin or a theme is activated, deactivated, or removed
- Improved: the counts of the Posts and Comments tabs are refreshed as soon as posts or comments change in WordPress
- Fixed: clearing a whole group from a WooCommerce tab now refreshes the counts of the other tabs as well
- Fixed: the plugin no longer creates a new transient for every prefix scan and every change of the installed plugins, and it removes the ones left by previous versions
1.4.7 – 09/17/2026
- Improved: added recognition for additional plugins
- Improved: rewrote every module for large databases — counting, filtering, sorting, and pagination are now handled by the database instead of loading whole tables into PHP
- Improved: greatly reduced memory usage and the number of queries needed to display each screen
- Improved: the cleanup totals in the sidebar are now cached and refreshed automatically when the data changes
- Improved: rewrote multisite handling across all modules, including network-wide pagination and cleanup
- Improved: the full database cleanup now runs within a time budget and can be repeated to continue, instead of timing out on large databases
- Improved: the full database cleanup now deletes posts and comments through the WordPress API, so related data and caches stay consistent
- Improved: deletions are checked once more before they run, and protected WordPress core entries are never removed
- Improved: scheduled cleanups are more reliable and no longer leave stale data in the interface
- Improved: reworked the admin interface — clearer bulk selections, accessible confirmations, keyboard support in the value preview windows
- Improved: the plugin is now fully translatable, including the interface texts and the summary messages
- Improved: the Prefix Scanner is faster, caches its results, and can be cancelled while running
- Improved: the extended code search in the Prefix Scanner is now disabled until you explicitly enable it, and clearly states what is sent and to whom
- Improved: added a requirements check that prevents the plugin from loading on unsupported PHP or WordPress versions
- Fixed: corrected the item counts shown in the sidebar and in the individual tabs, which could differ from each other
- Fixed: expired transients and oEmbed caches are now detected and counted correctly
- Fixed: deleting orphaned or unused meta no longer leaves related records behind
- Fixed: sorting and pagination settings no longer interfere between tabs
- Fixed: several actions could fail silently or report the wrong result message
- Fixed: scheduled cleanup events are now removed when the plugin is deactivated
1.4.6 – 09/12/2026
- Improved: added recognition for additional plugins
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best CodingBunny Database Cleaner alternatives
All clean plugins →
FAQ
CodingBunny Database Cleaner: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 15, 2026
Is CodingBunny Database Cleaner free?
Yes. CodingBunny Database Cleaner is free to download and use from the official WordPress.org plugin directory.
Is CodingBunny Database Cleaner safe to use in 2026?
CodingBunny Database Cleaner is a solid plugin choice in 2026, with a few things worth checking first. It runs on 200+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 76/100 on our health check.
How many websites use CodingBunny Database Cleaner?
CodingBunny Database Cleaner is active on 200+ WordPress websites and has been downloaded 4,889 times since it launched in June 2026. It was downloaded 1,581 times in the last 30 days.
Does CodingBunny Database Cleaner work with WordPress 7.1?
Yes. The developer has tested CodingBunny Database Cleaner up to WordPress 7.1.3, the latest release. It requires WordPress 6.2 or newer.
What PHP version does CodingBunny Database Cleaner need?
CodingBunny Database Cleaner requires PHP 8.2 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was CodingBunny Database Cleaner last updated?
The latest version, 1.5.3, was released on October 1, 2026 (2 weeks ago).
Who makes CodingBunny Database Cleaner?
CodingBunny Database Cleaner is developed and maintained by CodingBunny.
What are the best alternatives to CodingBunny Database Cleaner?
The most popular alternatives to CodingBunny Database Cleaner are Advanced Database Cleaner (100K+ installs), Media Cleaner: Delete Unuse… (90K+ installs) and Advanced WordPress Reset (10K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
