Delete a Plugin from cPanel
Back up first, then deactivate the plugin in WordPress so its own cleanup runs, then delete its folder at wp-content/plugins in cPanel File Manager. If the admin is locked by a fatal error, rename the folder to .disabled before deleting. Rows the plugin left in wp_options need a separate phpMyAdmin cleanup.
The file path, the lockout workaround and the database leftovers, in the order that protects the site.
knowledge
- Read time
- 4 min
- Sections
- 7
- Updated
- 14 Nov 2026
- Written by
- WebJi® team
Last editorial update: 15 November 2026.
What is the safe order for deleting a plugin from cPanel?
Three moves in one order — full backup, deactivate in WordPress, then delete the folder in File Manager — because each step protects the next. Deactivation lets the plugin run its own uninstall cleanup; deleting the folder first skips that and strands options and tables in the database.
- In cPanel, open Files › Backup and download a Full Account backup; the detailed walkthrough is the cPanel full backup guide.
- Open the WordPress admin at
/wp-adminand go to Plugins › Installed Plugins. - Click Deactivate under the plugin and wait for the page to reload.
- Only then move to File Manager for the delete (next section).
If the site breaks during deactivation, reactivate it and switch to the rename method below — that is the escape hatch this page exists for. One naming caveat: this guide covers a WordPress plugin. A “plugin” in the cPanel interface itself (cPAddons, server extensions) is installed server-side by the host and cannot be removed from a shared account.
How do you delete the plugin folder in cPanel File Manager?
A plugin's code lives in one folder under wp-content/plugins/ named by its slug, so deleting that folder removes the code — single-file plugins like Hello Dolly sit there as one .php file instead.
- In cPanel, open Files › File Manager.
- Open
public_html— on an addon domain, the folder named after that domain instead. - Open
wp-content, thenplugins: one folder per installed plugin. - Select the plugin's folder (or file).
- Click Delete in the toolbar and confirm; wait for the queue to finish on large folders.
- Reload Plugins › Installed Plugins — it should no longer be listed, and the site should load with no missing-file warning.
The deeper tour of the file browser — permissions, extraction, search — is in the cPanel File Manager guide.
What if a fatal error has locked the WordPress admin?
When a plugin's fatal error takes wp-admin down with it, there is no Deactivate button to press — so rename the folder instead of deleting it, which switches the plugin off without losing anything. WordPress cannot load a plugin whose folder it cannot find.
- In File Manager, open
wp-content/plugins. - Right-click the suspect folder, choose Rename, and append
.disabledto the name. - Open the site in a private window: if it loads, the plugin was the cause.
- Confirm the admin opens, then delete the renamed folder via the safe order above.
This rename trick is also the only switch you have for must-use plugins in wp-content/mu-plugins, which WordPress never shows as deactivate-able in the admin. Rename first, verify, then delete.
How do you clear the rows a deleted plugin leaves behind?
Deleting files deletes nothing from the database: most plugins store settings in wp_options, and some create their own tables — so the cleanup is a separate phpMyAdmin pass.
- Export the database first (the steps are in exporting a database from phpMyAdmin) — one wrong row in wp_options can reset site settings or break the admin login.
- In cPanel, open Databases › phpMyAdmin and select the WordPress database.
- In the options table (usually
wp_options), search theoption_namecolumn for the plugin slug. - Delete only rows you recognise as that plugin's settings.
- Scan the table list for custom tables prefixed like
wp_plus the plugin name, and drop them only if the plugin's documentation says they belong to it.
Leftover rows are harmless clutter most of the time; they matter when you plan to reinstall later and want a clean slate, or when a security scan flags old option rows.
What do you do when the folder will not delete?
Nine times out of ten the cause is folder permissions, not a broken cPanel — set the folder and contents to 755 and retry. The table matches each symptom to its fix.
| What you see | What to do |
|---|---|
| Permission denied | Select folder › Permissions › 755, tick recurse into subdirectories, delete again |
| File Manager returns 403 | The files belong to another system user; email the host to remove the folder |
| Delete hangs or times out | Delete subfolders one at a time — cache and vendor folders first |
| Disk quota or inode limit notice | Free space elsewhere and retry; the operation needs headroom to run |
On Windows hosting, a file locked by the running process can block deletion until the host releases it — one reason this job is simpler on Linux plans.
What must you never delete, and where does WebJi® fit?
Never delete wp-content/plugins itself — that folder holds every plugin on the site, and removing it takes the whole set down at once. Delete inside it, never the container.
- Never remove a folder you cannot identify — search the slug in the Plugins list first.
- Leave
mu-pluginsalone unless you know which theme or host put it there. - Never empty database tables “just in case”; export before any delete.
- Purge the page cache afterwards so old plugin output stops appearing.
WebJi® cPanel hosting — a separate product at ₹297 a month before 18% GST with 20 GB disk and 200 GB bandwidth — includes the File Manager, phpMyAdmin and backup tools this whole job runs on. If a delete has gone wrong, email support@webji.services with the domain and folder name: support is 24/7 in Hindi and English, average first reply under 60 minutes, and restoring your own backup is usually faster than reinstalling.
Frequently asked questions
Does deleting the plugin folder remove its settings and tables?
No. File deletion touches files only; rows in wp_options and any custom tables stay. Search the plugin slug in phpMyAdmin and remove what you recognise — after exporting the database, and dropping custom tables only when the plugin's documentation names them.
Can I delete a plugin while it is still active?
You can, but the next page load can throw a fatal error because other code still expects it. Deactivate first so the plugin runs its own cleanup hooks. If deactivation itself breaks the site, use the rename-to-.disabled method and delete after the admin is back.
Will deleting a plugin break my theme or other plugins?
Only when something else calls its functions — shortcodes in posts, widget areas it registered, or another plugin that depends on it. Symptoms are a widget that stops rendering or a shortcode showing as plain text. The deactivated-first order reveals these while rollback is still one click.
How do I delete a plugin without WordPress admin access at all?
File Manager alone is enough: delete (or first rename to .disabled) the plugin's folder under wp-content/plugins. WordPress then treats it as uninstalled on the next load. This is also the standard recovery route when a plugin has locked the admin.
Is there a way to delete plugins in bulk from cPanel?
File Manager's multi-select deletes several folders at once, and Software › WordPress Manager by Softaculous offers a Delete action per listed plugin. Bulk-delete only plugins you can name, one risky one at a time — a wrong multi-select takes out half the toolkit in one click.
Last editorial update: 15 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.