Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
WordPress shows “Destination folder already exists” when the plugin or theme it is installing already has a directory at the target location. The folder may be left over from an interrupted install, or it may belong to a copy that WordPress does not recognize in the dashboard. Check the dashboard first, back up your site, then remove or rename only the matching folder before retrying the install.
What the error means
During installation, WordPress extracts or moves the package into a destination directory. If that directory already exists and the operation is not allowed to overwrite it, the move can fail with destination_already_exists_move_dir. WordPress also reports a separate error if it cannot delete an existing destination. See the WordPress developer documentation for move_dir().
A common cause is a leftover directory from a failed, interrupted, or incomplete install or update. The dashboard and server files can get out of sync, so a folder may exist even though the plugin or theme does not appear as installed in WordPress.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Fix it safely
- Check the WordPress dashboard. For a plugin, open
Plugins > Installed Plugins; for a theme, openAppearance > Themes. If the item is already listed, activate it or use the available update or replace option rather than installing a second copy. WordPress 5.5 and newer supports an overwrite option when uploading a plugin or theme ZIP; the exact flow may depend on the upload and item. See Yoast’s guidance on this error. - Make a current backup. Back up your site before deleting or renaming server files. This gives you a recovery point if you select the wrong directory or the installation has other problems. Themeisle also recommends backing up before removing a folder: Themeisle’s troubleshooting guide.
- Find the exact directory. Use your hosting provider’s File Manager or an FTP/SFTP client. Plugin folders are normally in
wp-content/plugins/<plugin-slug>; theme folders are normally inwp-content/themes/<theme-slug>. The slug is the directory name, which may differ slightly from the product’s display name. See the WordPress support discussion and Beaver Builder’s explanation. - Preserve or remove only that folder. If you want to inspect its contents or retain a copy, download it or rename it first. Otherwise, delete only the matching plugin or theme directory. Do not delete neighboring folders or the entire
pluginsorthemesdirectory. Removing the plugin’s files does not, by itself, remove its database data, according to Beaver Builder. - Retry with a fresh ZIP. Download a clean package from the plugin or theme’s legitimate source, then install it through the WordPress dashboard as usual. Confirm that it appears in the dashboard and activate it if appropriate. Themeisle recommends retrying with a clean ZIP and checking that the plugin appears and activates: Themeisle’s troubleshooting guide.
Choose the repair method that fits your situation
| Situation | Approach | Trade-off |
|---|---|---|
| The item appears in the dashboard | Activate it, update it, or use the dashboard’s overwrite or replace flow. | Usually avoids manual file access. Availability depends on the WordPress version and the install or upload flow. |
| The item is absent, but its folder exists | Back up, then rename or delete only the matching directory and reinstall. | Requires File Manager or FTP/SFTP access; renaming or downloading first preserves the files for inspection. |
| You cannot access or remove the directory | Ask your hosting provider to inspect or remove the named directory. | Host assistance may be necessary if your account lacks filesystem access or the server blocks the operation. |
Use the right path for a plugin or theme
The same repair applies to either type of install, but the destination differs. For a plugin, inspect wp-content/plugins/; for a theme, inspect wp-content/themes/. Removing a folder from the wrong location will not resolve the conflict and could affect an unrelated item.
If you cannot delete the folder
A deletion failure points to a filesystem or hosting issue rather than simply a duplicate folder. Possible causes include permissions, file ownership, a full disk or inode quota, or a host restriction. Yoast recommends making the path writable or contacting the host; Stack Harbor also identifies these filesystem issues as causes of directory-install failures: Yoast and Stack Harbor.
- Check with your host before changing permissions or ownership if you are unsure of the correct values.
- If File Manager or FTP/SFTP denies deletion, provide the host with the exact path of the conflicting directory and ask them to check access and available quota.
- If WordPress requests FTP credentials during installation, follow your host’s instructions rather than guessing credentials or changing server settings blindly.
Why a plugin folder can exist when the plugin is not listed
WordPress may not recognize a directory as an installed plugin if the files are incomplete, the folder name was changed, or the installation did not finish. Yoast also notes that the message can occur if the plugin is already installed or if its folder under wp-content has been renamed. In either case, identify the exact directory before taking action; the dashboard’s list alone does not establish that no files remain on the server.
Quick Recap
Rank #3
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
