Activate WPBakery in phpMyAdmin: A Beginner’s Guide
WPBakery is a powerful page builder, but what if you suddenly find it deactivated or missing from your WordPress admin...
When you remove a plugin from your WordPress site, it doesn’t always take all its data with it. Things like settings, custom tables, or hidden options often stay behind in your database.
Over time, this leftover data adds up. It can slow down your site, especially if you’ve tried many plugins or haven’t cleaned your database for some time.
If you’re just starting or dealing with a large pile of old plugin data, it’s a smart move to hire a WordPress development company. They can safely clean things up without breaking your site. Here, we’ll break down the common types of plugin residue, how to find them, and the best ways to clean them up.
Table of Contents
When you uninstall a WordPress plugin, you might think everything related to it is gone. But in most cases, plugins leave behind bits of data in your database.
These leftovers might seem harmless at first, but over time, they can slow down your site and make your database complicated. Cleaning them up is one of the easiest ways to speed up WordPress dashboard performance and keep things running smoothly. Here are the most common types of old plugin data to watch for:
Some plugins create their own database tables (like wp_pluginname_data) to store complex data. These custom tables don’t get removed unless the plugin includes a special uninstall script.
Example:
A form plugin might create:
Even after you delete the plugin, these tables stick around unless you remove them manually.
Plugins often store their settings and configuration data in the wp_options table. Many of these entries stay even after the plugin is deactivated. To check for leftover options:
SELECT * FROM wp_options WHERE option_name LIKE '%pluginname%';
Note: Just replace the pluginname with the actual plugin slug to find related entries.
Some plugins add extra data to posts or user profiles like SEO details, form responses, or membership info. This data is saved in the wp_postmeta and wp_usermeta tables. To find post meta from a plugin:
SELECT * FROM wp_postmeta WHERE meta_key LIKE '%pluginname%';
These meta entries often get ignored, but they can pile up over time and bloat your database.
WordPress transients are temporary bits of cached data, but some plugins don’t clean them up, especially if they were set to expire after a long time or not at all.
They usually live in the wp_options table and can be set to autoload, which slows down your site.
Plugins that handle automated tasks (like syncing or sending emails) set up cron jobs. If the plugin is removed but doesn’t clear its cron jobs, these tasks may still try to run in the background and use server resources. To check scheduled cron jobs using WP-CLI:
wp cron event list
Look for jobs that have plugin-specific names or prefixes. Most plugin authors prioritize functionality over cleanup, so it’s common for this data to linger long after you’ve stopped using the plugin. Knowing what to look for gives you a solid starting point before starting the database cleanup.
Before cleaning anything from your WordPress database, it’s important first to know what exactly was left behind by the old plugin.
Residual data can exist across several tables, so this step helps you avoid accidentally deleting useful or unrelated information. Here’s how to find leftover plugin data using different tools.
phpMyAdmin or Adminer are visual database tools provided by most hosting panels. You can inspect your tables and run SQL queries directly. Here’s how to do it:
1. Look for unused plugin tables like:
wp_oldplugin_logs
wp_oldplugin_data
2. Search for leftover options in the wp_options table:
SELECT * FROM wp_options WHERE option_name LIKE '%pluginname%';
3. Replace pluginname with the actual name or slug of the plugin (e.g., yoast, woo, elementor).
4. Check metadata tables:
SELECT * FROM wp_postmeta WHERE meta_key LIKE '%pluginname%';
SELECT * FROM wp_usermeta WHERE meta_key LIKE '%pluginname%';
These queries help spot data that plugins quietly leave behind in posts or user settings.
If you are comfortable with command-line tools, WP-CLI offers quick and powerful ways to search your database.
1. List matching options:
wp option list --search=pluginname
2. Check for plugin-specific tables:
wp db tables | grep pluginname
WP-CLI is especially useful for automation or when managing multiple WordPress installs.
For a more visual and real-time approach, install the Query Monitor plugin.
By combining these methods, you can confidently identify plugin-related data spread across your WordPress database. Once you’re sure what’s safe to remove, you’re ready to move on to the cleanup process.
If you’re comfortable working directly with databases, manual cleanup gives you the most control. It lets you target only the data you’re sure you no longer need.
This is especially useful for advanced users managing high-performance or legacy WordPress setups. But you need to be cautious also, so work with backups before deleting anything manually.
Before making any changes, create a full site and database backup using tools like:
This ensures you can roll back if anything goes wrong.
Some plugins create their own tables, which won’t be removed automatically. Here’s an example command:
DROP TABLE wp_pluginname_data;
Replace wp_pluginname_data with the actual table name. Always double-check that any other plugin is not using the table.
Plugin settings stored in wp_options can remain after deletion. Here’s a query to remove them:
DELETE FROM wp_options WHERE option_name LIKE '%pluginname%';
You can adjust the LIKE filter for more precise targeting if needed.
Some plugins attach data to posts or user profiles. Here’s how to clean post meta:
DELETE FROM wp_postmeta WHERE meta_key LIKE '%pluginname%';
Here’s how to clean user meta:
DELETE FROM wp_usermeta WHERE meta_key LIKE '%pluginname%';
This step is important for form plugins, SEO tools, or user-based tracking plugins.
Autoloaded options are loaded on every page load, so cleaning unused ones improves performance.
Query to list large autoloaded options:
SELECT option_name, LENGTH(option_value) AS size
FROM wp_options
WHERE autoload = 'yes'
ORDER BY size DESC
LIMIT 20;
Review the results and remove only if you’re sure the data is obsolete. While manual methods offer accuracy, they also carry the highest risk.
Double-check queries, always work on a staging environment if possible, and keep backups handy. Done right, this approach gives your database a solid performance boost.
If you’re not comfortable with SQL or just want a quicker way to clean up your WordPress database, installing plugins can help do the job safely and effectively.
These tools are designed to identify leftover plugin data, orphaned entries, and other clutter without needing to write a single line of code. Here are some of the most trusted options:
Advanced Database Cleaner is best if you want a deep cleanup without manual SQL queries. Here are its key features:
Why it’s helpful: You can preview what’s going to be deleted and minimize the risk of removing critical data.
Plugins Garbage Collector is built specifically for tracking down unused plugin tables. Here are its key features:
Why it’s helpful:
Great for identifying tables not dropped during plugin removal–especially when managing older sites.
WP-Optimize is an all-in-one solution for optimizing your site’s performance and cleaning the database. Here are its key features:
Why it’s helpful:
If you want a mix of cleanup, caching, and media optimization in one place, this is a reliable pick.
Each of these plugins includes some form of backup prompt or preview function before deletion. Still, it’s best practice to create a manual backup before running any database cleaner.
You can clear old WordPress database tables manually with phpMyAdmin or Adminer. Tools like Advanced Database Cleaner or WP-Optimize also help you find and safely delete orphaned tables without touching essential data.
You can reset your WordPress database using plugins like WP Reset. It wipes all content, settings, and customizations and returns your site to a fresh WordPress install. Always take a full backup before resetting because this process is not reversible.
Post revisions can be removed using cleanup plugins like WP-Optimize or by running SQL queries via phpMyAdmin. You can also limit future revisions by adding a line to your wp-config.php file to reduce clutter going forward.
Yes, you can restore your WordPress database using backups from tools like UpdraftPlus, BlogVault, or manual SQL dump files. You’ll need access to your hosting panel or phpMyAdmin to import the backup file into your database.
To dump (export) your WordPress database, use phpMyAdmin’s “Export” option or run a command via WP-CLI:
wp db export filename.sql
This creates a full .sql backup of your database, useful for migrations or safety copies.
Old plugin data might be out of sight, but it’s definitely not out of your database. Over time, these leftover entries can slow down your site and make managing your backend a real hassle.
Cleaning your WordPress database isn’t just about saving space; it’s about improving performance and load speed and keeping things running smoothly. Whether you go manual or use tools, staying on top of plugin residue makes a big difference.
Not sure where to start? Our WordPress development team can help you clean, optimize, and future-proof your site. Let’s talk about how we can make your site faster and lighter.