Installation Failed: Destination Folder Already Exists

Why it happens

• The plugin or theme is already installed, and you uploaded its zip again or clicked Install Now on it.
• A folder with files was left behind, for example by a delete that did not finish or a manual copy. It is not a working plugin, so it never shows on the Plugins screen.
• You copied or renamed a plugin folder by hand, for example with FTP, and its name now matches the one you want to install.

How to fix it

Try the fixes in this order. Each one is independent: stop as soon as the error is gone.

WordPress installs a plugin by moving its files into a folder named after it. If that folder already holds files, WordPress stops instead of mixing old and new files. Your site is not harmed. If you want the zip to replace what is there, use the Replace current with uploaded button, or --force in WP-CLI. If the folder is a stale leftover, move it away.

What you see#

It depends on where you started. The words are the same, the page around them is not.

Only the Install Now button adds the words "Installation failed:". That prefix comes from the Add Plugin screen's JavaScript (wp.updates.installPluginError() in wp-admin/js/updates.js), not from the upload page or WP-CLI.

On the Upload Plugin screen, when the folder is a plugin WordPress knows, you get a choice instead of a dead end:

When the folder is not a plugin WordPress recognises, there is no table and no button:

How the check works#

Every install runs through WP_Upgrader::install_package(). WordPress unzips the file into wp-content/upgrade. The top folder inside the zip gives the plugin's folder name. Then WordPress looks for that folder in wp-content/plugins.

Two details in the code explain the results:

• Only a folder with files counts. The code reads the folder's contents, and only stops when the list is not empty. With an empty plugins/ghost folder, wp plugin install goes through with "Plugin installed successfully."
• Overwriting is a separate switch. The Replace button and --force set clear_destination. WordPress then deletes the old folder first and skips the check. This is why replace is safe for a clean upgrade and risky for a folder where you keep your own files.

On the upload screen, Plugin_Installer_Skin::do_overwrite() looks through the installed plugins for one whose file path starts with that folder name. This is a prefix match, not an exact one, so a leftover folder ghost also matches an installed ghost-pro/ghost.php, and you then get a table and a Replace button for the wrong plugin. If it finds none, there is nothing to compare, so you only get the error. That is why a leftover folder usually gives the dead end. Themes differ: a folder holding only a text file still got the comparison and the Replace installed with uploaded button, and clicking it gave "Theme updated successfully." So a stray theme folder is easier to clear than a stray plugin folder.

Try it yourself: terminal output#

A small test plugin, installed twice with WP-CLI on WordPress 7.1.4.

wp plugin install /tmp/opening-hours.zipwp plugin install /tmp/opening-hours.zip

Unpacking the package...Installing the plugin...Plugin installed successfully.Success: Installed 1 of 1 plugins.Unpacking the package...Installing the plugin...Warning: Destination folder already exists. "/var/www/html/wp-content/plugins/opening-hours/"Plugin installation failed.Warning: The '/tmp/opening-hours.zip' plugin could not be found.Error: No plugins installed.

The second warning, "could not be found", is a side effect. WP-CLI looks for the plugin after the failed install and cannot find the files it expected. The real error is the first warning. Directory installs print the same warning:

wp plugin install classic-editor --force

Unpacking the package...Installing the plugin...Removing the old version of the plugin...Plugin updated successfully.Success: Installed 1 of 1 plugins.

Why renaming inside plugins is a trap#

Several guides say to rename the folder instead of deleting it. That clears the error, but it leaves a second copy of the plugin in the same place, and WordPress treats each folder in plugins as its own plugin:

name	title	statusakismet	Akismet Anti-spam: Spam Protection	inactiveghost	Ghost Plugin	inactiveghost-old	Ghost Plugin	inactive

Two copies with one name and two sets of functions can break the site if both are active. Move the old folder outside plugins, or delete it after you have copied out what you need.

A zip with no folder inside#

Some zips put the plugin file at the top, with no folder around it. On WordPress 7.1.4 these never hit this error. The upgrader names its unpacking folder after the zip plus 16 random characters (get_working_dir_name(), added in 7.1.4), and that name becomes the plugin folder. Installing the same flat zip twice gives two separate folders:

flat-one-EIG1tpL1Q0g2vgKmflat-one-XP4Je9Zs2f80tbAE

So you get duplicates, not an error. Older WordPress versions were not tested; they name the folder after the zip file. If a zip from GitHub installs under an odd folder name, unpack it, put the files in one folder with the right name, and zip that folder.

If it keeps happening#

If the install still fails after you clear the folder, the message will be different. A folder that WordPress cannot write to is covered in could not create directory. A zip that holds no plugin file gives an "Incompatible Archive" message instead. If the old folder cannot be removed, see could not copy file and could not remove the old plugin. If the plugin installs but will not switch on, see plugin could not be activated. For a calmer routine on updates, read how to update plugins safely.