Find Us At

901, Shapath V, Sarkhej - Gandhinagar Hwy, opp. Karnavati Club Road, Prahlad Nagar, Ahmedabad, Gujarat 380015.

Call On

+91 79-48000011

Mail Us

info@codecaste.com

Find us here
WordPress Plugin

Database Cleaner & Optimizer by CodeCaste

Find out what is bloating your WordPress database, then clean it safely. Scan, review and clean in batches, with nothing deleted until you confirm.

  • Version 1.0.0
  • Price Free
  • License GPL
Read FAQs
Database Cleaner & Optimizer by CodeCaste
Why it exists

Built for the moment your database has grown past what you can see

You approve every cleanup

Scanning never changes data, and each cleanup waits for your confirmation. On a client site, that one pause separates a tidy database from a broken plugin.

Built for databases that have grown past you

Cleanup runs in batches you control, so sites with huge transient, revision or Action Scheduler tables are processed without overloading the server.

It says potentially orphaned, not safe to delete

WordPress does not record which plugin owns a custom table or meta row. So the plugin labels what it finds honestly and asks you to review before removing it.

How it works in practice

Every WordPress database grows quietly. Expired transients pile up, old revisions stack by the dozen, plugins leave orphaned meta behind, and a store running Action Scheduler can collect hundreds of thousands of finished task records. Before long the site feels slower and nobody can say which table is the culprit.

Database Cleaner & Optimizer shows you what is making your database large, then lets you clean it safely. The workflow is strict: Scan, Analyze, Review, Clean. Scanning never modifies your data. Every cleanup needs your explicit confirmation and runs in small, batched steps, so it keeps working on large databases without hitting PHP timeouts.

Records that might be orphaned are labeled potentially orphaned on purpose, so you review them before anything is removed. The plugin never deletes automatically and never optimizes on its own.

What it scans

  • Autoloaded options: total autoload size and the largest individual options
  • Expired transients
  • Post revisions beyond the number you choose to keep per post
  • Abandoned auto-drafts older than a day
  • Orphaned post meta, term meta and comment meta
  • Action Scheduler records (completed, failed and canceled actions) when present, for example through WooCommerce
  • Database and table sizes, plus possible leftover tables from removed plugins and themes

Key features

  • Database health score from 0 to 100 on a single-page dashboard
  • Per-item review with record counts and estimated size
  • Batched, confirmation-gated cleanup plus an Optimize All runner
  • Configurable batch size, revisions to keep and Action Scheduler retention
  • Scan history with date, size, score, issues and duration
  • Switch individual scanners on or off
  • Unused table detection that checks installed plugin, theme and must-use plugin sources before flagging a table

Safety notes (read before you clean)

Take a database backup before any cleanup. Dropping a database table requires typing the exact table name and runs a fresh reference scan immediately beforehand. Table detection is described as possible orphan detection, not proof, because WordPress and MySQL do not record which plugin created a custom table. The health score is an indicator, not an absolute measurement, so large legitimate tables such as WooCommerce order tables are not automatically treated as unhealthy.

Prefer to read the source before you install it on a client site? You can also find it on GitHub.

View on GitHub
Capabilities

What you get when you install it

Database health score

A simple 0 to 100 score based on autoloaded data, table sizes, expired transients, revisions, orphaned metadata and Action Scheduler buildup, shown on a single-page dashboard.

Eight focused scanners

Autoloaded options, expired transients, post revisions, auto-drafts, orphaned post, term and comment meta, and Action Scheduler records, each switchable on or off.

Review before you clean

See record counts and estimated size per item, then clean one item or run Optimize All, with confirmation on every destructive action.

Batched cleanup

Cleanup runs in small steps with a configurable batch size, so large databases finish without PHP timeouts.

Unused table finder

Flags possible leftover tables from removed plugins and themes, and requires the exact table name before any table is dropped.

Scan history

Every scan is logged with date, size, score, issues found and duration so you can track database health over time.

FAQs

Questions? We've got answers

Everything you need to know before running a cleanup on a client site.

Install Database Cleaner & Optimizer, open DB Optimizer in wp-admin and click Scan Database. Review each item under Cleanup Items, then clean a single item or use Optimize All and confirm.

No. Scanning never modifies data, and cleanup only runs after you review and explicitly confirm an action. The plugin never performs automatic optimization.

Yes. A backup is recommended before any cleanup. Cleanup actions remove records permanently, so keep a restore point.

Yes. Cleanup runs in configurable batches (500 records per step by default), so large databases are processed in small steps instead of one heavy query. Lower the batch size on weak shared hosting if you see errors or timeouts.

It sets how many of the newest revisions are kept for each post. Older revisions become eligible for cleanup. The default is 5, and setting it to 0 means earlier versions of a post can no longer be restored after cleanup.

Yes, when Action Scheduler is present. Finished, failed and canceled actions older than your retention period (30 days by default) can be cleaned. Tasks that are still waiting to run are never touched.

The Database Tables scanner inspects every installed plugin and theme, not only active ones, so tables belonging to an installed but inactive plugin stay protected. Detection is labeled possible orphan, not absolute proof.

The initial release targets standard single-site WordPress installs. Multisite support is planned for a future release, so do not use it network-wide yet.

Deactivating leaves everything untouched. Deleting the plugin removes only its own settings and scan-history records, never your posts, comments, users or other plugins' data.

Built here. Supported here.

If it breaks on a client site, we want to hear it.

This is not a ticket that lands in a void. Someone on this team wrote the scanner you just ran, and they still read what comes in.

Something broke?

Walk us through the last thing you did before it failed. We will look for the conflict with you, not send you a canned reply.

Need a change?

If you caught yourself wishing it did something else on a client call, tell us. Those notes from real shops shape the next version.

Found an issue, or not sure yet?

Ask before you run a cleanup on production. A five-minute question now is cheaper than rolling a live library back on Friday.

Contact Us

Let's Connect

Found a bug after a scan, need a change, or have feedback before this goes on a client site? Send it over. We read these ourselves.

Address

901, Shapath V, Sarkhej - Gandhinagar Hwy,
opp. Karnavati Club Road, Prahlad Nagar,
Ahmedabad, Gujarat 380015.

Send us a note







     

    We'll only use your details to reply. We never share them or add you to any list.

    From the workshop floor

    More tools we are building right now

    Grab what is ready, follow what is cooking, and tell us what you would use on your next client site.