You deleted a plugin months ago, but its name still turns up. Maybe your host’s database tool lists tables with that plugin’s name in them, maybe a backup is bigger than the site seems to justify, or maybe a page shows a line of square-bracket text where a slider used to be. The plugin is gone. Its belongings are not.
This post shows you how to remove leftover plugin data carefully: what a plugin can leave behind, where each kind of leftover lives, and which pieces are safe to clear. Most of it you can do from the dashboard and your hosting panel, as long as you take a backup first and leave alone anything you cannot identify. It is one of the housekeeping jobs in our guide on how to manage a WordPress website.
What a deleted plugin can leave behind
A plugin is more than the folder you see in wp-content/plugins. While it runs, it can write to several other places, and deleting the folder does not reach any of them unless the plugin cleans up after itself.
- Settings in the options table. Nearly every plugin stores its configuration as rows in the WordPress options table, usually with names starting with the plugin’s own prefix.
- Its own database tables. Form, booking, statistics, redirect and security plugins often create tables of their own to hold entries, logs or rules.
- Extra data attached to your posts. SEO and page builder plugins save fields against each page, and some plugins create their own content types, such as form entries or testimonials, stored among your posts.
- Files outside its folder. Folders inside wp-content/uploads, cache folders, and “drop-in” files such as advanced-cache.php or object-cache.php placed directly in wp-content by caching plugins.
- Server configuration. Caching and security plugins sometimes add rules to .htaccess, or lines to wp-config.php or a .user.ini file.
- Scheduled tasks. Jobs the plugin asked WordPress to run on a timer, which can stay registered after the code is gone.
- User roles. Membership, shop and staff plugins can add roles that remain in the list.
- Shortcodes in your content. Text like [gallery-slider id=”3″] that only meant something while the plugin was active.
Not all of this matters. A handful of settings rows is harmless. A drop-in file from a caching plugin you removed, or an .htaccess rule pointing at a folder that no longer exists, can cause real errors. That difference decides where you spend your effort.
Start with the plugin’s own clean-up option
Plugins can include an uninstall routine that WordPress runs when you delete the plugin from the Plugins screen. A well-built plugin uses it to remove its own tables, options and scheduled tasks. Many plugins only do this when you have switched it on, through a setting with a name along the lines of “remove all data when uninstalling”, often found under an Advanced or Tools tab in the plugin’s settings. A few ask you to add a line to wp-config.php instead, and their documentation will say so.
Two details catch people out. First, the routine only runs when you delete through the dashboard. If someone removed the folder by FTP or the hosting file manager, nothing was cleaned. Second, deactivating is not deleting; if you are unsure which of the two you did, the difference between deactivating and deleting a plugin is explained separately.
That gives you a tidy method for a plugin that was removed the rough way:
- Install the same plugin again from Plugins → Add Plugin (or upload its zip if it was a paid plugin).
- Activate it, but do not run its setup wizard.
- Open its settings and turn on the option to delete its data on uninstall, if it has one.
- Deactivate it, then delete it from the Plugins screen.
The plugin’s own code knows exactly which tables and options it created, which is far more reliable than you guessing from names. If the plugin has no such option, or it is no longer available, move on to the manual route below.
Back up before you remove leftover plugin data
Database changes are the one part of WordPress housekeeping that reinstalling cannot reverse. Take a full backup that includes the database, download a copy to your own computer, and note the date. If you have not done this before, our walkthrough on backing up a WordPress website covers it. If your host offers a staging copy, doing the clean-up there first and repeating it on the live site is even better.
Clearing each kind of leftover
Shortcodes in pages and posts
These are the ones visitors see, so deal with them first. Go to Pages or Posts, type the opening part of the shortcode (for example [gallery-slider) into the search box, and WordPress will list every item whose content contains it. Open each one. In the block editor a shortcode usually sits in a Shortcode block, or in a Classic block on older content. Replace it with whatever does the job now, or delete it. Remember widget areas and footer templates too, since shortcodes can live there as well.
Database tables
Open phpMyAdmin (or your host’s database tool) from the hosting panel. On a normal single site, WordPress itself creates twelve tables: commentmeta, comments, links, options, postmeta, posts, termmeta, terms, term_relationships, term_taxonomy, usermeta and users, each with your prefix in front (often wp_, but it can be anything). Every other table came from a plugin or theme.
A table called something like wp_oldformplugin_entries is easy to place. Before you drop it, confirm three things: the plugin is truly gone (not just deactivated), no other plugin from the same developer is still active, and the table does not hold data you need, such as old form entries. If it does, export the table first. When the name gives no clue, leave the table where it is.
Rows in the options table
In phpMyAdmin, search the options table’s option_name column for the plugin’s prefix. Delete only rows that clearly carry that prefix. Do not touch rows you do not recognise, and never delete core settings such as siteurl, home, active_plugins or anything starting with your table prefix followed by “user_roles”. This is careful, row-by-row work, and for most sites the gain is small, so it is fine to skip it entirely.
Files, drop-ins and server rules
- On the Plugins screen, look for a Drop-ins link above the list. If it shows a caching drop-in and you no longer run a caching plugin, remove that file from wp-content.
- In wp-content/uploads, folders named after a plugin often hold its logs, exports or generated files. Download anything useful, then delete the folder.
- Open .htaccess and look for blocks between # BEGIN PluginName and # END PluginName. Remove only the block belonging to the deleted plugin, and keep the WordPress block.
- Check wp-config.php and any .user.ini file for lines the plugin added, such as a cache setting or a file it loaded before WordPress. A line pointing to a file that no longer exists can stop the site loading, so this is worth a look after removing a security or caching plugin.
Scheduled tasks
WordPress has no screen for scheduled tasks. The free WP Crontrol plugin adds one, usually found under Tools, listing each task with its hook name. Tasks named after the removed plugin can be deleted there. If you install WP Crontrol only for this job, you can remove it afterwards.
Leftover user roles
If Users shows a role from a plugin you no longer use, move anyone with that role to a standard role first. A role editor such as Members or User Role Editor can then delete the empty role.
What not to clean
A slightly smaller database is a small prize; a missing table your shop depends on is a bad week. Leave these alone:
- Anything belonging to a plugin that is still installed, even if inactive.
- Tables and rows you cannot tie to a specific removed plugin.
- Data from your theme, your shop or your forms, even if a cleanup tool flags it as unused.
- Post data from an SEO plugin you replaced, until you are sure the new one imported everything.
Some database cleanup plugins try to match orphaned tables and options to the plugin that made them. Treat their matches as suggestions to check, not instructions. General database tidying, such as revisions and expired temporary data, is a separate job covered in our post on WordPress database optimization.
Checking your work afterwards
- Load the home page, a few inner pages and any page that used the old plugin.
- Submit each form and confirm the message arrives.
- Open Tools → Site Health and see whether anything new appears.
- Keep the backup from before the clean-up for a few weeks, in case something turns up later.
For the full life of a plugin, from choosing it to taking it off again, see the WordPress plugins guide for owners.
Frequently asked questions
Will reinstalling an old plugin bring back my previous settings?
Often, yes. If the plugin left its settings and tables behind, reinstalling it picks them up again, which can be helpful if you removed it by mistake. It also means a fresh install is not truly fresh, so if you want to start over, use the plugin’s delete-data option first.
Is leftover plugin data a security risk?
Leftover settings and tables are usually inert, because no code is running to use them. The risk lies elsewhere: old plugin files still sitting on the server, or stored data such as form entries containing personal details you no longer need. Delete unused plugins fully and remove personal data you have no reason to keep.
Do I need to clean up after every plugin I delete?
No. A small plugin that left a few settings rows can be ignored. Spend your effort on leftovers that can cause errors or expose data: caching drop-ins, server rules, lines in wp-config.php, shortcodes visitors can see, and tables holding personal details such as old form entries. Everything else can wait for an occasional tidy.
Should I delete the data of a plugin I might use again?
No. If there is a realistic chance you will reinstall it, keeping its settings saves you setting it up again, and a few rows cost almost nothing. Clean up only once you are sure the plugin has gone for good, and export anything useful, such as past form entries, before you do.
Database work is the one place in this post where a wrong click is hard to undo. If you would rather not open phpMyAdmin yourself, this sort of clean-up can be handed to our WordPress support service, with a backup taken first and a note of what was removed.
Next in this series: How to Find Which Plugin Does What in WordPress
