WordPress plugins add extra features to your website. If a plugin is no longer needed, causes issues, or is to be replaced by another solution, you can first deactivate it and then, if necessary, delete it completely.
There is an important difference: In the Deactivate remains installed on the server. When Delete its plugin files are removed from the WordPress installation.
Briefly explained: If you want to disable a plugin only temporarily or investigate an error, you should deactivate it first. If you are sure that you no longer need the plugin, you can delete it afterward. In the case of important plugins, you should check beforehand what impact the deactivation will have on your website.
What happens when you deactivate a WordPress plugin? #
When you deactivate a plugin, its program code is no longer executed by WordPress as an active plugin during normal operation.
However, the plugin files remain on the server. Therefore, you can usually reactivate a deactivated plugin later without having to install it again.
Many plugins also retain their settings and stored data when deactivated. As a result, these are often available again after reactivation.
However, whether and which data are retained depends on the respective plugin.
What happens when you delete a plugin? #
When deleting, WordPress removes the plugin's files from the plugin directory.
Plugins are usually located under:
wp-content/plugins/
However, this does not automatically mean that all of the plugin's data will disappear from the WordPress database.
For example, a plugin can leave behind data such as:
- Settings
- custom database tables
- Options in existing WordPress tables
- Metadata
- scheduled tasks
- Protocols
- own uploaded files
Important: „Plugin deleted“ does not necessarily mean „all plugin data deleted.“ How a plugin handles its data during uninstallation is decided by the respective developer.
Disable plugin or delete it directly? #
In many cases, it makes sense to deactivate a plugin first.
This allows you to check whether your website also functions correctly without the plugin. This is especially important if you are not entirely sure what a plugin is used for.
Deactivating is suitable, for example, if you:
- you want to investigate a plugin conflict
- want to temporarily disable a function
- you want to test if a plugin is responsible for an error
- might need a plugin again later
- want to check the impact before final deletion
If you are sure that the plugin will no longer be needed permanently, you can delete it afterwards.
Disable WordPress plugin in the admin area #
Normal deactivation is done directly via the WordPress plugin management.
- Log in to your WordPress admin area.
- Open Plugins → Installed Plugins.
- Find the desired plugin.
- Check again to make sure you selected the right plugin.
- Click on Deactivate.
- Then check your website.
After deactivation, the plugin remains in the list of installed plugins, but is no longer active.
What should be checked after deactivation? #
Whether deactivation has visible effects depends on the task of the plugin.
Therefore, check in particular functions that could be related to the plugin.
Depending on the plugin, these can be, for example:
- Contact forms
- SEO features
- Redirects
- Backups
- Cache and Performance
- Safety features
- WooCommerce Extensions
- Page Builder extensions
- Cookie or privacy features
- Shortcodes
- Widgets or blocks
Practical Tip: If you don't know the purpose of a plugin, don't just disable it on suspicion, and definitely don't delete it immediately. First, check what function the plugin performs on your website.
Delete deactivated WordPress plugin #
If you want to remove the plugin permanently, you can delete it via the plugin management after deactivating it.
- Open Plugins → Installed Plugins.
- Search for the already deactivated plugin.
- Click on Delete.
- Confirm the WordPress security check.
- Wait until WordPress has finished the deletion.
After that, the plugin should no longer appear in the normal list of installed plugins.
Why can't an active plugin be deleted normally? #
WordPress provides for initially deactivating a plugin in the normal admin area and only deleting it afterward.
This makes sense because it clearly distinguishes between disabling a feature and actually removing the plugin files.
If you only want to disable a plugin for testing purposes, deactivating it is sufficient.
Are plugin settings deleted when deactivated? #
Usually not automatically.
Many plugins store their settings in the WordPress database and retain them even during deactivation.
If the plugin is activated again later, the previous settings may become available again as a result.
However, this behavior is not identical for every plugin.
Are plugin data removed when deleting? #
That depends on the respective plugin.
WordPress provides plugin developers with mechanisms that allow certain data to be removed upon uninstallation. However, whether a plugin uses these options and what data is actually deleted is determined by the plugin itself.
Some plugins remove a large portion of their data when deleted. Others keep settings or database tables so they can be reused during a later reinstall.
Some plugins additionally offer their own setting, roughly translated as:
Delete data upon uninstallation
Such an option should only be enabled if you actually no longer need the saved data.
Attention: If a plugin manages important data, you should check before complete removal whether this data is still needed or needs to be exported or backed up beforehand.
Check a backup before deleting important plugins #
For a simple plugin without relevant stored data, removal is usually straightforward. For extensive plugins, the situation can look different.
You should be particularly careful, for example, with plugins that:
- Process orders or customer data
- Save forms and form entries
- Manage redirects
- Save SEO metadata
- Manage memberships
- create custom content types
- Store tables or other structured data
Therefore, before making major changes, you should ensure that a current and usable backup exists.
What happens to the shortcodes of a deleted plugin? #
Some plugins provide shortcodes that you use in pages, posts, or other content areas.
If the associated plugin is deactivated or deleted, WordPress can no longer replace these shortcodes with the intended function.
Depending on the plugin and integration, this can, for example:
- Functions disappear
- content is no longer displayed
- Keep shortcode texts visible
- layouts appear incomplete
Therefore, check before deleting whether the plugin is embedded in your content via shortcodes.
What happens to plugin blocks? #
Many modern plugins extend the WordPress block editor with their own blocks.
If you deactivate the corresponding plugin, the functionality behind these blocks may no longer be available.
Before final removal, you should therefore check whether corresponding plugin blocks are used on important pages or in posts.
What happens to a plugin's widgets? #
Plugins can also provide their own widgets or other elements for widget areas.
If the plugin is deactivated, the corresponding element can no longer be output as intended.
This may concern, for example, sidebars or footer areas.
Can deleting a plugin break the website? #
Yes, if the website depends on the plugin's functionality.
A typical example would be a form plugin. If it is removed, a previously embedded contact form may no longer work.
The same applies, for example, to:
- Page Builder
- WooCommerce Extensions
- Multilingual plugins
- Member areas
- Redirection plugins
- Custom Post Type Plugins
- Custom field plugins
Therefore, the crucial question is not only whether a plugin is active, but what dependencies your website has on this plugin.
Deactivate plugin to investigate an error #
The targeted deactivation of plugins is one of the most common methods in WordPress troubleshooting.
For example, if an error occurs after an update, controlled deactivation can be used to investigate whether a specific plugin is involved.
You should proceed systematically and not randomly change several components at the same time.
Recommendation: When troubleshooting, change only one thing at a time if possible. If you deactivate multiple plugins at once, you might not know afterward which change actually affected the error.
Detect plugin conflicts #
A plugin is not necessarily defective just because a problem occurs after it is activated.
A conflict is also possible between:
- two plugins
- Plugin and Theme
- Plugin and WordPress version
- Plugin and PHP version
- multiple components that influence the same function
Therefore, deactivation should be viewed as a diagnosis and not automatically as proof that a plugin is poorly coded.
Disable multiple plugins at once #
In the WordPress plugin management, multiple plugins can be selected and deactivated via a bulk action.
This can be helpful for certain maintenance work. However, for targeted troubleshooting, individual deactivation is often more informative.
For a production website, you should also consider that multiple plugins disabled at the same time can affect numerous functions all at once.
Plugin cannot be deactivated #
If the normal deactivation in the WordPress admin area does not work, you should first check the exact error message.
Possible causes may include, among others:
- a PHP error
- missing permissions
- a damaged plugin installation
- a critical WordPress error
- Trouble accessing the admin area
In the event of a technical error, it is advisable to investigate the cause before manually deleting files.
WordPress admin area no longer accessible due to a plugin #
In certain cases, a faulty plugin can cause the WordPress admin area to no longer be accessible normally.
Then a deactivation via Plugins → Installed Plugins may no longer be possible.
Experienced users can temporarily disable an affected plugin, for example via file access, by renaming its plugin directory.
The plugins are usually located under:
wp-content/plugins/
For example, a plugin directory could look like this:
wp-content/plugins/beispiel-plugin/
By renaming the folder in question, WordPress can no longer load the plugin under its previous path.
Attention: Manually renaming or editing plugin directories is a troubleshooting measure and no substitute for normal plugin management. Only change the directory of the plugin that is actually to be investigated.
Do not delete the entire plugin folder #
If you only want to examine a specific plugin, you must not blindly examine the entire directory
wp-content/plugins/
delete or rename.
This usually contains numerous different plugins for your website.
Therefore, work only with the uniquely identified subdirectory of the affected plugin.
Must-use plugins are a special case #
WordPress also knows, in addition to regular plugins, so-called Must-Use Plugins, short for must-use plugins.
These can be found at:
wp-content/mu-plugins/
are treated differently than normal plugins.
They do not appear like ordinary plugins with a normal deactivate function in the plugin management. MU-plugins are often used by hosting, management, or special solutions.
If you don't know why an MU-plugin is there, you shouldn't remove it arbitrarily.
Drop-ins and other special cases #
Certain WordPress extensions can additionally use so-called drop-ins or other files outside their normal plugin directory.
Therefore, manually deleting an individual plugin folder is not always equivalent to a complete and clean uninstallation.
For a regular removal, use the uninstallation function provided by the plugin or by WordPress, if possible.
Is it better to delete unused plugins? #
A plugin that you have only temporarily deactivated can remain installed.
On the other hand, you should not leave plugins that are definitely no longer needed sitting unused on the server for years.
Even deactivated plugins still consist of files. If these contain a security vulnerability, an unnecessarily installed and unmaintained plugin can represent an avoidable attack surface.
Practical Tip: Keep only plugins that you actually use or have temporarily disabled for a specific reason. You should cleanly remove plugins that are no longer needed after checking dependencies and data.
Still update deactivated plugins? #
If a deactivated plugin is deliberately kept installed and is to be used again later, it should continue to be maintained and updated.
Deactivation does not replace maintenance.
If the plugin is definitely no longer needed, a clean removal is usually more sensible than leaving it installed permanently disabled and unmaintained.
Reinstall plugin after deletion #
A deleted plugin can generally be reinstalled, provided it is still available and compatible with your WordPress environment.
Whether previous settings are still present after a reinstall depends on whether the plugin removed its data when it was deleted.
Therefore, you should not rely on a reinstallation automatically restoring the previous state.
Check premium plugins before deleting #
In the case of a paid plugin, you should also check beforehand whether you will still have access later to:
- installation file
- License key
- Customer account with the manufacturer
- current plugin version
has.
This is especially important if the plugin could be reinstalled later.
Do not manually delete plugin data from the database #
After uninstalling a plugin, database entries may remain. However, this does not mean that they should generally be removed manually.
Without precise knowledge of the data structure, entries required by WordPress or other plugins can be accidentally deleted.
Attention: Do not delete database tables or options just because their name looks like an old plugin. Manual database cleanup should only be done when it is clearly established which data can be removed and a current backup is available.
What should be checked after deleting a plugin? #
Check in particular after removal:
- Home
- important subpages
- Navigation
- Forms
- Frontend representation
- WordPress admin area
- Functions that were related to the plugin
- WooCommerce, if affected
- Mobile view
If the plugin provided shortcodes, blocks, or widgets, you should specifically search for where they were previously used.
Typical errors when disabling and deleting plugins #
- Delete plugin without knowing its function
- removing multiple plugins at once and subsequently no longer being able to trace the cause of the error
- not checking a backup before a major change
- overlooked saved plugin data
- Forget shortcodes or plugin blocks on existing pages
- Remove parent or base plugin of an extension
- Delete premium plugin without saving installation file or license access
- Manually delete the plugin folder, even though a normal uninstallation would be possible
- delete alleged plugin data from the database without checking
- leaving deactivated and obsolete plugins permanently installed and unmaintained
Pre-deletion plugin checklist #
- Do you know exactly what function the plugin performs?
- Is it used on pages, in posts, or in templates?
- Does the website use shortcodes, blocks, or widgets from the plugin?
- Do other plugins or features depend on this?
- Does the plugin contain any data that is still needed?
- Do data need to be exported beforehand?
- Is there a current backup available in case of a major change?
- Did you deactivate the plugin first and check the website?
- Do you still retain access to the license and installation file with a premium plugin?
- Have you tested the most important website features after the removal?
When should you contact CURIAWEB support? #
If a plugin causes a technical error, cannot be deactivated normally, or the WordPress admin area is no longer accessible after a plugin modification, a technical review may be useful.
Helpful in this regard are:
- the affected domain
- Plugin name
- Plugin version, if known
- exact error message
- what change was made immediately before the error
- whether the WordPress admin area is still accessible
Do not indiscriminately remove multiple plugins and files when an error occurs before the cause has been narrowed down. This can unnecessarily complicate troubleshooting.
Summary #
You can find a WordPress plugin at Plugins → Installed Plugins first deactivate and then delete if needed. When deactivating, the plugin files remain on the server. When deleting, the plugin files are removed.
Whether this also removes settings, database tables, and other saved plugin data depends on the respective plugin.
Check which features and data depend on the plugin before final deletion. This is especially true for plugins that provide forms, shop features, SEO data, shortcodes, blocks, or other important components of your website.
If a plugin causes a technical error and the WordPress admin area is no longer accessible, manual deactivation via the plugin folder can be considered as a troubleshooting measure. However, such interventions should be carried out selectively and not indiscriminately.
