How to Fix WordPress Destination Folder Already Exists Error

By ErrorFix · Updated October 14, 2026 · 6 min read

What Destination folder already exists means

When you install or update a plugin or theme, WordPress downloads a zip package and unpacks it into a folder under wp-content/plugins/ or wp-content/themes/. Before unpacking, WordPress checks whether a folder with that name is already there. If it is, WordPress refuses to continue — it will not silently overwrite existing files — and shows you the "Destination folder already exists" message instead.

It is not a bug in WordPress, and it is not a hack or malware warning. It is a safety stop. The same message can appear during a fresh install and during an update, and the fix is the same in both cases: find the folder WordPress is complaining about, make sure you have a copy of anything important inside it, remove it from the server, and run the install or update again.

Common causes

• A failed previous install: an earlier install or update crashed partway through, unpacking some files and leaving the folder behind. The next attempt finds it and stops.
• A manual FTP upload: someone previously uploaded the plugin or theme by hand to the same location, so WordPress now sees a folder it did not create.
• An interrupted update: a server timeout, a PHP memory limit hit, or a dropped connection during an automatic update can strand a half-written folder.
• Two copies with colliding names: a premium and free version (or two forks) of the same plugin using the same folder name — deleting one does not help if the other is re-added.
• Stuck caches masking the real state: aggressive server or CDN caching can make a deleted folder appear to still exist to the install routine; clearing caches exposes the actual state.

How to fix Destination folder already exists — step by step

The whole fix takes about fifteen minutes and needs nothing fancier than access to your hosting account.

1. Confirm which folder WordPress is tripping over. Read the full error message in the WordPress dashboard — it names the path, for example wp-content/plugins/akismet or wp-content/themes/twentytwentyfive. Knowing whether the folder is under plugins or themes tells you exactly where to look on the server, so don't click Install again blindly; repeated attempts just re-create the same failure.
2. Back up the existing folder before deleting anything. Download the old folder to your computer before you remove it. If the plugin or theme holds settings, custom templates, or translated files you didn't keep elsewhere, this copy is your safety net — deleting without a backup means losing whatever was inside that folder for good.
3. Delete the folder with an FTP client. Connect with FileZilla or another FTP client using the credentials from your hosting account. Navigate to wp-content/plugins or wp-content/themes, right-click the folder named in the error, and delete it. Wait until the transfer queue finishes — a half-deleted folder triggers the same error on the next attempt.
4. No FTP? Delete the folder in your host's File Manager. Log in to cPanel, Plesk, or your host's panel and open File Manager. Go to public_html/wp-content/plugins or /themes, select the offending folder, and delete it (empty the trash/recycle bin if your panel uses one — files there still count as existing). This does the exact same job as FTP.
5. Re-run the install or update from the WordPress dashboard. Back in WordPress, go to Plugins, then Add New (or Appearance, then Themes, then Add New) and install the item again. If this was a failed update, go to Dashboard, then Updates and run the update. With the destination folder gone, WordPress unpacks the package cleanly and the error disappears.
6. If the error persists, check permissions and clear the cache. First make sure you deleted the right folder — theme folders live under wp-content/themes and plugin folders under wp-content/plugins, and mixing them up leaves the real culprit behind. Then check the folder permissions on wp-content (folders should normally be 755) so WordPress can write the new files, clear any caching plugin or CDN cache, and retry. If it still fails, install manually: unzip the package on your computer and upload the folder by FTP to the same location.

Did this fix it? Quick checklist

• The old folder is fully gone from wp-content/plugins/ or wp-content/themes/ (trash emptied)
• You have a backup of the folder, or confirmed there was nothing important inside it
• The install or update completed in the WordPress dashboard with no error
• The plugin activates (or the theme previews correctly) and the rest of the site still looks right

A special warning for themes: if the folder you are deleting belongs to your currently active theme, switch to a different theme first (Appearance, then Themes, then Activate) — deleting an active theme's folder mid-session can white-screen the site. And if you edited theme files directly instead of using a child theme, those edits are inside the folder you are about to delete: copy them to your computer first, or accept that they will be lost.