How to clean and optimize a WordPress database

Create and download a current database backup, and make sure you know how to restore it. A database cleanup is permanent; if a plugin stores important settings in an option or custom table, there may be no undo button.

Run the cleanup during a quiet period and pause scheduled imports, orders or bulk content edits. On a live WooCommerce site, do not take a backup snapshot and then leave it unverified: check that the backup completed and contains the database before continuing.

Check Tools > Site Health > Info and your host’s database-size report. Look for a large wp_options table, a high volume of revisions, spam comments, expired transients, or tables belonging to plugins you no longer use.

Do not assume that the biggest database is the slowest one. Autoloaded options are loaded together on regular requests, so one oversized plugin setting can matter more than thousands of legitimate orders. WordPress flags excessive autoloaded data in Site Health, but the option owner still needs to be identified before changing it.

Remove old post revisions, auto-drafts, items in the trash, spam comments and trashed comments from the WordPress admin or a trusted maintenance tool. Keep a sensible revision limit rather than disabling revisions completely; WordPress stores revisions in the posts table and supports a limit through WP_POST_REVISIONS in wp-config.php.

If you have shell access, WP-CLI can list revision posts and delete selected revisions with wp post list and wp post delete --force. Check the IDs first, especially on a site using page builders, custom fields or revision-dependent workflows.

Delete expired transients rather than blindly deleting every transient. Transients are temporary cached values, and WordPress can store them in wp_options or, with an external object cache, outside the database. WP-CLI provides wp transient delete --expired; the WordPress API also has a function for deleting expired transients.

Do not panic if transients return after cleanup. Plugins may recreate them, and some stores or integrations depend on them. Deleting all transients can also cause a temporary increase in database queries while caches are rebuilt, so use the expired-only option unless you have a specific reason to clear everything.

Inspect the largest rows in the options table and identify which active plugin or theme created each one. Change autoload behaviour only for a non-essential option that you have confirmed does not need to load on every request. Never delete or disable core settings simply because their names are unfamiliar.

Do not run a generic SQL deletion against rows matching a plugin name. Plugins can use serialized data, shared settings or custom tables, and deleting one row can break the admin, permalinks, checkout or scheduled tasks. If you cannot identify an option’s owner, leave it alone and ask the plugin developer or host for advice.

After deleting data, run a database check and table optimisation from your hosting panel or with wp db optimize. WP-CLI runs the host’s MySQL optimisation utility, but table optimisation can use substantial disk space and may lock writes, so avoid doing it during checkout traffic or a busy publishing window.

For the fast way, use Meow Database Cleaner Pro to schedule cleanup, review database reports and create backups before maintenance. It is a practical option for large sites that need recurring removal of revisions, spam and transients instead of repeating the manual process.