.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Uninstalling WordPress from cPanel sounds like deleting a folder, and that's roughly half of the job. A WordPress install is files plus a database plus a database user plus a few hooks into the account (cron entries, .htaccess rules, sometimes an installer's records). Miss the other half and you carry dead weight in your disk quota forever, or worse, an abandoned install that still answers requests. Here's the clean removal, three ways.
First, the step I won't negotiate on: take a full backup even when you're certain you want the site gone. cPanel » Files » Backup, download the home directory and the database. I've been asked to resurrect a "definitely never needed again" site three weeks after deletion more than once. A backup file costs nothing to keep for a month.
Before you delete: find every piece
Open wp-config.php in the site's folder and note three lines, because they name the database pieces you'll remove later:
define( 'DB_NAME', 'user_wp123' );
define( 'DB_USER', 'user_wpu45' );
$table_prefix = 'wp_';The table prefix matters when several WordPress installs share one database (a bad old pattern, still common). In that case you delete tables matching the prefix instead of dropping the whole database, and you'll be glad you checked.
Method 1: WP Toolkit (cleanest when you have it)
Most cPanel servers ship with WP Toolkit these days (the Lite tier comes free with cPanel; hosts choose the tier). Open cPanel » Domains » WP Toolkit, find the installation in the list, open its card menu and choose Remove. The toolkit deletes the files, drops the database and the database user and forgets the install in one pass, because it tracked all of those pieces from the start.
One catch: WP Toolkit only manages installs it created or scanned. If your site isn't listed, run Scan from the toolkit's menu first, let it detect the install, then remove it. Detached installs (ones you told the toolkit to ignore) reappear after a rescan too.
Method 2: Softaculous
Installed through Softaculous originally? Remove it there and it'll clean up after itself. cPanel » Software » Softaculous Apps Installer, click the top-right Installations icon (the box list), find the WordPress entry and hit the red X. Softaculous asks which parts to remove; tick directory, database and database user, then confirm.
Same limitation as WP Toolkit: Softaculous removes what Softaculous knows about. A manually-installed WordPress won't appear in that list, and importing it just for the pleasure of deleting it is more clicking than the manual method below. And if Softaculous won't even open its installations list, you're probably looking at the LiveAPI connection error, usually a full disk quota and worth fixing before you fall back to manual removal.
Method 3: Manual removal
No installer records? Manual it is. Three deletions in order.
Delete the files
File Manager » the site's document root (public_html for the main domain, or the addon domain's folder). Select the WordPress files: wp-admin, wp-content, wp-includes, the wp-*.php files, index.php, xmlrpc.php, license.txt, readme.html and .htaccess. Delete, then empty File Manager's Trash or the disk space won't return. If other things live in the same folder (another app in a subdirectory, random uploads), delete selectively rather than nuking the directory.
Drop the database and its user
cPanel » Databases » MySQL Databases. Under Current Databases, delete the database you noted from wp-config.php. Scroll to Current Users and delete the matching DB user too; orphaned users pile up over the years and every one is a credential that shouldn't exist. Shared-database installs: open phpMyAdmin instead, select the database, tick the tables with your prefix, Drop.
Clear the leftovers
Check cPanel » Advanced » Cron Jobs for entries calling wp-cron.php or anything in the deleted folder; plugins like backup tools love planting these and they'll email you errors nightly after the files vanish. If the domain should keep serving something else, put an index page in the empty document root so visitors don't get a directory listing or a 403.
Verify the removal
Load the domain: your placeholder (or a clean empty-directory page) should answer, not a WordPress error about database connections. Check Disk Usage in cPanel: the space from files and the database should be back. And glance at MySQL Databases once more to confirm neither the database nor the user survived. Thirty seconds, and you know it's fully gone rather than mostly gone.
Removing WordPress but keeping the domain live
Half the uninstalls I see are really migrations: WordPress goes away because a new stack replaces it. Upload the replacement before deleting DNS-visible things, keep the old .htaccess rules you still need (redirects especially, they're SEO you already paid for) and only then remove the WordPress pieces. The order saves you the gap where the domain serves nothing. If the replacement needs a different environment entirely, that's the point where people move from shared hosting to a cPanel VPS and carry the domain over rather than reshuffling the old account.
However you remove it, the test of a clean uninstall is dull and absolute: no files, no database, no user, no cron, no surprise emails. WordPress is tidy about what it creates; it just never volunteers the full list.
