Manage Plugin Changes and Site Data

How to Uninstall a WordPress Plugin Without Losing Data You Want to Keep

Uninstall a WordPress plugin safely: check what it deletes, remove its files, and verify whether its settings and database data remain.

Editorial illustration for How to Uninstall a WordPress Plugin Without Losing Data You Want to Keep

Deleting a WordPress plugin does not reliably answer what happens to its settings and stored data. Decide whether you want to keep that data first, then check the specific plugin’s uninstall instructions before you delete it. If you may reinstall it, retaining data may preserve your settings; if you want a clean removal, you need to identify what its uninstall process removes and what, if anything, remains.

Decide whether to keep the data

A plugin’s files and its stored data are separate concerns. Removing the files may leave data in the database, while a plugin’s uninstall process may remove some of it. Neither outcome is a safe assumption for every plugin. Kinsta notes that retaining data can make settings available on a later reinstall; Rank Math cautions that deletion can also remove settings and stored data, depending on how the plugin is designed.

Write down your intended outcome: keep the settings and data for a possible reinstall, or remove the plugin and its identified data. If the data matters and you cannot establish what uninstall will do, pause rather than treating Delete as a reversible experiment. Make a full site backup before proceeding.

If you are removing the plugin because a feature broke, first establish whether the plugin is the cause.

Check this plugin’s uninstall behavior

Read the developer’s uninstall documentation or ask the developer what deletion removes and what it leaves behind. Ask specifically about settings, any data you need to retain, and database tables the plugin created. Record the exact items the developer identifies; a table with a familiar-looking name is not enough evidence to delete it.

If you can inspect the plugin files, look for an uninstall.php file in its own folder. WordPress’s uninstall_plugin() reference shows that WordPress checks for that file; it can also use a registered uninstall callback. The presence of uninstall.php tells you there is an uninstall routine, not which settings, tables or other data it actually removes. Review the routine where available, and use the developer’s documentation or answer to resolve anything unclear. Do this before invoking an uninstall procedure if keeping the data is important.

Back up, then uninstall the plugin

With the intended data outcome established and a full backup made, deactivate the plugin in the WordPress dashboard, then select Delete. This removes the installed plugin; do not treat the disappearance of its dashboard entry as proof that its database data is gone.

If you use WP-CLI, specify the plugin you intend to remove rather than an all-plugins option:

wp plugin uninstall <plugin-slug>
wp plugin uninstall <plugin-slug> --deactivate
wp plugin uninstall <plugin-slug> --skip-delete

These are alternatives, not three commands to run in sequence. The first invokes uninstall for the named plugin, but WP-CLI warns and skips an active plugin by default. Use --deactivate if it is still active. --skip-delete runs the uninstall procedure without deleting the plugin files. That makes it unsuitable as a complete file-removal step—and potentially unsuitable for a keep-data decision, because the uninstall procedure still runs. Check the plugin’s behavior before choosing it.

If dashboard deletion is unavailable, access the site’s wp-content/plugins directory by FTP or SFTP, or through a hosting file manager that exposes that directory. Identify the exact folder belonging to the plugin before removing it; do not delete a similarly named folder on a guess. Manual folder removal removes files, but may leave the plugin’s database data behind. It also is not a substitute for assuming the plugin’s uninstall routine ran.

Check the result before cleaning up data

Confirm that the plugin is no longer listed as installed in WordPress. After manual removal, confirm that its exact folder is absent from wp-content/plugins. Then compare your original keep-or-delete choice with the plugin’s documented uninstall behavior and the database items its developer identified. A successful file deletion alone does not settle the data question.

If you chose to keep the data, verify that the specifically identified settings or tables you intend to retain are still present. If you chose to remove it, check which identified items the uninstall process already removed before doing anything manually. Do not broaden cleanup to unrelated tables or to entries identified only by a similar name.

For any identified plugin tables that still need removal, make sure you have a backup before deleting them in phpMyAdmin. Rank Math warns that dropping tables is permanent without a backup from which to recover them. After cleanup, verify that the documented tables or other specifically identified data were retained or removed as you intended. If you cannot identify an item confidently, leave it in place and ask the plugin developer rather than guessing.

← All articles

Type at least two characters.

Press <kbd>Esc</kbd> to closeOpen the search page