Introduction

The WordPress message that the destination folder already exists usually means WordPress is trying to install or replace a plugin or theme, but it found a folder with the same name already in place. That can happen after a partial install, a failed update, a manual upload, or a previous copy that was never removed cleanly. The right fix is to confirm whether the existing folder is the live copy you still need, a broken leftover, or a duplicate before you delete anything.

Symptoms

  • WordPress shows an error such as Installation failed: Destination folder already exists
  • A plugin or theme install stops before activation
  • An update fails and leaves the old version in place
  • The same plugin or theme appears to have been uploaded manually and through wp-admin
  • The problem started after an interrupted install, timeout, or manual file cleanup

Common Causes

  • A previous install or update created the folder but did not finish cleanly
  • The plugin or theme was uploaded manually, then installed again from wp-admin
  • A failed extraction left partial files in wp-content/plugins or wp-content/themes
  • The host restored files from backup while WordPress still tried to install the package again
  • The plugin or theme slug matches an existing folder that is incomplete, disabled, or outdated

Step-by-Step Fix

  1. Identify the exact plugin or theme involved and note whether WordPress was trying to install it for the first time or update an existing copy.
  2. Check whether the folder already exists in wp-content/plugins or wp-content/themes and confirm whether it is the active live version or a leftover partial install.
  3. If the plugin or theme is currently active and working, do not delete it blindly. Back up the site first and verify whether the failure came from an update package colliding with the existing installed folder.
  4. Compare the folder contents with what you expect from the official plugin or theme package. A partial or obviously incomplete folder often points to a failed earlier install.
  5. If the existing folder is only a broken leftover and not the working live copy, remove or rename that folder through your hosting file manager or SFTP so WordPress can install cleanly.
  6. If the folder is the current live plugin or theme and the issue happened during an update, use a maintenance window and backup before replacing files so you do not break the site mid-change.
  7. Re-run the install or update using a trusted package source and watch for related errors involving permissions, disk space, timeouts, or maintenance mode.
  8. Test the affected plugin or theme immediately after the install finishes so you confirm activation, front-end behavior, and admin access all still work.
  9. If this happens repeatedly, review your deployment workflow so plugins and themes are managed through one consistent method instead of mixing manual uploads, backups, and dashboard installs.