Removing a WordPress install on DreamHost is not one action, it is three separate cleanups: the site’s files, the MySQL database, and DreamHost’s own site record connecting a domain to a specific installation. Skip any one of these and you end up with either leftover files eating disk quota, an orphaned database nobody remembers the credentials for, or a domain that still shows an error page months later because DreamHost’s panel never had the association removed. This walks through DreamHost’s control panel specifically, since its one-click installer and site management structure work differently from a typical cPanel host.
Before Anything: Decide What You Actually Need to Keep
If there is any chance you will want this content again, export it first. WordPress’s built-in exporter (Tools > Export in wp-admin) produces an XML file with posts, pages, comments, and media references, though not the media files themselves or your theme customizations. For a full, restorable copy including media and settings, a plugin like All-in-One WP Migration or Duplicator captures considerably more, and is worth running even if you are fairly sure you will not need it, since the alternative to a five-minute export now is no path back later.
If the site was installed through DreamHost’s one-click installer originally, check whether DreamHost’s panel offers a backup snapshot option for the install before you begin removal; not all plans include this, but it costs nothing to check first.
Step 1: Log Into the DreamHost Panel
- Go to the DreamHost panel login page and sign in with your account credentials.
- Navigate to Websites > Manage Websites (the exact menu label has shifted slightly across DreamHost panel redesigns, but “Manage Websites” or “Websites” is the consistent starting point).
Step 2: Locate the Specific WordPress Installation
DreamHost lists domains and subdomains together in the Manage Websites view. Find the specific domain or subdomain your WordPress install is attached to, this matters because DreamHost accounts frequently host multiple sites, and removing the wrong one is not reversible without a backup.
Click into that domain’s settings to see the options relevant to removal, which vary depending on whether the site was set up through DreamHost’s one-click WordPress installer or manually installed.
Step 3: Remove the WordPress Files
For a site installed through DreamHost’s one-click installer, the panel typically offers a direct “Uninstall” or “Remove Installation” option specifically for one-click installs, which removes both the files and, depending on the exact flow, may prompt you about the associated database at the same time.
For a manually installed WordPress site, or if the one-click uninstall option is not available for your specific setup, remove the files directly through SFTP or the panel’s built-in File Manager:
- Connect via SFTP using your DreamHost SFTP credentials (an FTP client like FileZilla, or DreamHost’s web-based File Manager if you prefer not to install a separate client).
- Navigate to the domain’s root directory, typically found under your username’s home folder, named after the domain.
- Select all WordPress files and folders (wp-admin, wp-content, wp-includes, wp-config.php, and the rest) and delete them.
Before deleting, note the database name and credentials from wp-config.php if you have not already recorded them elsewhere, you will need this exact information in the next step, and once the file is deleted, that specific record of the connection is gone unless you saved it.
Step 4: Remove the MySQL Database
This is the step people skip most often, and it is the one most likely to leave lasting clutter, since a deleted WordPress install with its database still intact contributes nothing useful but still counts against your hosting account’s database quota and (for DreamHost’s shared MySQL plans specifically) storage limits.
- In the DreamHost panel, go to Websites > MySQL Databases (or the equivalent current menu path; DreamHost occasionally relocates this under a broader “Databases” section).
- Find the database associated with the WordPress site you just removed, matching the database name you noted from wp-config.php.
- Select the option to delete or remove that database.
- Confirm the deletion when prompted.
If you are not certain which database belongs to which site, because DreamHost accounts with multiple WordPress installs often accumulate similarly-named databases over time, do not guess. Cross-reference the exact database name from the wp-config.php file you noted in Step 3 rather than deleting based on a database name that merely looks plausible.
DreamHost typically also lets you assign a specific MySQL hostname to each database at creation time, which can offer another confirmation point beyond the database name alone. If two candidate databases have similar names but were created against different MySQL hostnames, cross-checking that value from wp-config.php’s DB_HOST constant against what the panel shows is one more way to be certain before an action that cannot be undone.
Step 5: Remove the Site’s Panel Record
Beyond files and database, DreamHost’s panel maintains its own record connecting a domain or subdomain to a hosting configuration, separate from either the files or the database. If you are fully done with this domain (not planning to reinstall WordPress or host anything else there), remove this record too through the same Manage Websites screen where you started, using the “Remove” or equivalent option for that domain’s hosting configuration.
Skip this step if you plan to reuse the same domain or subdomain for a different install or a different CMS, since removing the panel-level hosting record along with the files means you will need to reconfigure hosting for that domain from scratch rather than simply pointing a fresh install at existing hosting.
Step 6: Check for Orphaned Cron Jobs and Email Accounts
WordPress does not typically create DreamHost-level cron jobs on its own (WP-Cron runs as a pseudo-cron triggered by site visits by default, not a true system cron entry), but if you or a plugin previously set up a genuine system-level cron job to trigger wp-cron.php more reliably, a common performance recommendation for busier sites, that cron entry does not get removed automatically when you delete the WordPress files it was calling.
Check Websites > Cron Jobs in the DreamHost panel and remove any entry referencing the deleted site’s wp-cron.php path. An orphaned cron job calling a URL that now 404s is harmless in the sense that it will not break anything, but it is unnecessary clutter and occasionally generates confusing error notifications if DreamHost’s monitoring flags the repeated failed requests.
Verifying the Removal Is Actually Complete
Visit the domain in a browser. It should show either a default DreamHost placeholder page, a 404, or whatever you configured to happen next (a redirect, a static holding page), rather than the old WordPress site or an error referencing missing WordPress core files. A “database connection error” message specifically indicates the files were removed but the site’s configuration in the panel still expects a database that no longer exists, meaning Step 5 was not completed correctly.
Check your DreamHost billing or usage dashboard a day or two later to confirm disk and database usage actually dropped by roughly the amount you expected. This is a useful sanity check that nothing was left behind that you missed.
If usage does not drop as expected, the most common culprit is a media library or uploads folder that was excluded from the deletion because it lived outside the standard WordPress directory structure, for instance a custom backup plugin that had been quietly storing full-site backup archives in its own separate folder on the server, unrelated to the wp-content directory a standard WordPress removal covers. Check the domain’s root directory manually through File Manager or SFTP one more time after the main removal to confirm nothing unexpected remains.
What to Do Differently If You Are Migrating Rather Than Deleting
If the goal is actually moving this WordPress site elsewhere rather than permanently removing it, do not follow the deletion steps above until the migration is fully verified working on the new host. Use a migration plugin (All-in-One WP Migration or Duplicator) to export the complete site, database included, import and confirm it functions correctly on the destination, and only then come back to DreamHost to remove the original, once you have confirmed the new copy actually works rather than trusting that it will.
Doing This on a DreamPress Plan Specifically
DreamPress, DreamHost’s managed WordPress product, works differently from a standard shared hosting account with a manually or one-click-installed WordPress site. On DreamPress, the WordPress installation is tightly bundled with the plan itself, rather than being one of potentially several independent sites on a general-purpose hosting account.
Removing a WordPress site on DreamPress typically means canceling or downgrading the DreamPress plan itself through the panel’s billing section, rather than the file-and-database steps described above for a standard shared hosting install. If you have multiple sites on the same DreamHost account and only want to remove one DreamPress-hosted site while keeping others, confirm through DreamHost’s support or documentation exactly how your specific plan structures multiple DreamPress instances before taking any billing action, since canceling the wrong plan tier can affect more than the single site you intended to remove.
What “Uninstall” Actually Means Versus a Fresh Reinstall
It is worth being precise about what you are actually trying to accomplish, since “uninstall WordPress” covers at least two different goals with different correct procedures.
If the goal is a genuinely clean slate to reinstall WordPress fresh on the same domain, removing files and database as described above and then running DreamHost’s one-click installer again accomplishes this cleanly. There is no need to also remove the panel-level hosting record in this case, since you want to keep that domain’s hosting configuration intact for the new install to use.
If the goal is retiring the domain from WordPress entirely, switching to a static site, a different CMS, or simply parking the domain, the panel-level record removal in Step 5 becomes relevant, along with considering whether you want the domain to redirect somewhere or simply return a default placeholder.
Conflating these two goals is a common source of confusion in DreamHost’s own support threads: someone follows full removal instructions intending to reinstall, then is confused why the one-click installer no longer offers WordPress as an option for that domain, because the underlying hosting record was removed along with the files.
Handling Subdirectory Versus Subdomain Installations Differently
WordPress on DreamHost can be installed at a domain’s root, in a subdirectory (yourdomain.com/blog), or on a subdomain (blog.yourdomain.com), and the removal path differs slightly depending on which pattern applies.
A subdirectory install shares hosting configuration with the parent domain, meaning file removal happens within a folder under the domain’s existing web root rather than the root itself, and there is no separate panel-level hosting record to remove in Step 5, since the subdirectory is not a distinct hosted entity in DreamHost’s panel the way a full domain or subdomain is.
A subdomain install does have its own distinct entry in Manage Websites, and needs the same file, database, and (if applicable) panel record removal as a root-domain install, treated as its own separate site throughout the process rather than a folder within a larger one.
Check which pattern applies to your specific setup before starting, since applying subdomain-removal steps to what is actually a subdirectory install (or the reverse) leads to confusion about why expected panel options are not appearing where the instructions describe them.
Common Mistakes During This Process
Deleting the database before confirming the site’s export or backup completed successfully. Always verify a backup file actually opened correctly, or a migration completed and imported cleanly elsewhere, before removing the source database it came from.
Confusing similarly named databases on an account hosting multiple WordPress sites. DreamHost does not prevent you from having several databases with easily confused names if you were not disciplined about naming them distinctly at creation time. Cross-check against wp-config.php’s exact database name every time, rather than trusting memory or a name that merely sounds right.
Removing the domain’s panel hosting record when the real intention was a clean reinstall. As covered above, this forces you to reconfigure hosting from scratch rather than simply running the one-click installer again on existing hosting.
Frequently Asked Questions
Will uninstalling WordPress cancel my DreamHost hosting plan?
No. Removing a WordPress installation only affects that specific site’s files and database. Your DreamHost hosting account and any other sites on it remain unaffected, and your billing continues based on your hosting plan, not on which specific software is installed under it.
Can I recover a WordPress site after deleting it from DreamHost?
Only if you took a backup or export beforehand. DreamHost does not maintain an automatic recovery window for manually deleted files and databases in the way some managed WordPress hosts do, so treat deletion as final unless you have confirmed a backup exists.
Do I need to remove the database separately, or does DreamHost do this automatically?
It depends on the removal method. One-click installer uninstalls sometimes handle both together; manual file deletion through SFTP never touches the database automatically. When in doubt, check the MySQL Databases section yourself rather than assuming it was handled.
What happens to email accounts on the same domain if I remove the WordPress hosting?
Email hosting on DreamHost is generally managed separately from web hosting for a domain. Removing a WordPress site’s hosting configuration should not affect email accounts on that domain, but confirm this in the panel before removal if email continuity matters, since account structures can vary.
How long does DreamHost take to actually free up disk space after deletion?
File deletion through SFTP or the panel takes effect immediately from your account’s perspective, though the usage figures shown in your billing dashboard can lag by a day or so before reflecting the change, since usage reporting often runs on its own periodic calculation cycle rather than updating in real time with every file operation.
Is there a faster way to remove everything at once instead of doing files, database, and panel record as three separate steps?
For sites originally set up through DreamHost’s one-click WordPress installer, the panel’s dedicated uninstall option (where available) does combine file and database removal into a single action, which is faster and less error-prone than doing it manually across three separate screens. Manually installed sites, or setups where the one-click uninstall path is not offered, require the three-step manual process described above.
