How to Fix WordPress Could Not Insert Attachment into Database
This error occurs when WordPress cannot save an uploaded file's record to the database;…
How to Fix WordPress Destination Folder Already Exists Error
- Error
WordPress Destination Folder Already Exists Plugin Installation Error- Affects
- WordPress Errors
What Is This Error?
When you install a plugin through the WordPress dashboard, WordPress downloads the plugin’s zip file, unpacks it, and moves the contents into your wp-content/plugins/ directory. The “Destination Folder Already Exists” error fires when WordPress finds a folder with the exact same name already sitting at that path — and rather than risk overwriting something important, it halts the installation completely.
The full message usually reads something like: Destination Folder Already Exists. /wp-content/plugins/your-plugin-name/ It looks alarming, but your site is almost certainly fine. The culprit is typically a leftover folder from a failed install attempt, a manual FTP upload, or a previous version that wasn’t fully cleaned up.
The fix is straightforward: locate that orphaned folder, remove it, and retry the installation. You’ll need access to your site’s file system through your hosting control panel’s File Manager or an FTP client like FileZilla.
Why Does This Happen?
- A previous installation failed midway: WordPress started unpacking the plugin but hit a timeout or permissions error, leaving a partial folder behind with no mechanism to clean itself up automatically.
- The plugin was uploaded manually via FTP first: If someone copied plugin files directly to the server before also attempting the dashboard installer, both paths collide on the same folder name.
- The plugin was deleted incorrectly: Removing a plugin by wiping its files via FTP — without deactivating and deleting it through the WordPress dashboard — can leave a registered but empty folder sitting in the plugins directory.
- A site migration or backup restore brought old files along: Moving from staging to production or restoring from a snapshot can repopulate plugin folders even when those plugins no longer appear in the dashboard’s installed list.
- The plugin is already installed and active: WordPress won’t overwrite a live plugin’s folder. If you’re trying to reinstall something that’s already running, the existing folder is what triggers the conflict.
How to Fix It — Step by Step
- Log in to your hosting control panel and open the File Manager (available in cPanel, Plesk, or similar panels), or connect via FTP using your hosting credentials and a client like FileZilla.
You should see: A file browser displaying your website’s root directory.
- Navigate to your plugins directory. If WordPress is installed in your root folder, the path is
/public_html/wp-content/plugins/. Adjust if WordPress is in a subdirectory.You should see: A list of folders, one per installed plugin on your site.
- Find the conflicting folder. Look for a folder whose name matches the slug of the plugin you’re trying to install. The error message tells you the exact name — for example, installing Contact Form 7 would show a folder named
contact-form-7.You should see: The folder present, possibly empty or partially filled from a failed install attempt.
- Delete or rename the folder. Right-click the folder and choose Delete. If you’re unsure whether it holds important data, rename it first (e.g.,
contact-form-7-backup) so you can restore it if needed. Via SSH, you can remove it with:rm -rf /path/to/public_html/wp-content/plugins/your-plugin-nameYou should see: The folder is gone from the directory listing, or shows its new renamed name.
- Return to your WordPress dashboard and go to Plugins → Add New. Search for your plugin and click Install Now.
You should see: An installation progress bar, followed by a green “Plugin installed successfully” message and an Activate button.
- Click Activate to enable the plugin. If you renamed the old folder as a backup, you can safely delete it now once you’ve confirmed everything is working.
You should see: The plugin listed as Active on your Plugins page with no errors.
Common Mistakes When Fixing This
- Deleting the wrong folder: Plugin folder names are slugified, so “WooCommerce” becomes
woocommerceand “Yoast SEO” becomeswordpress-seo. Deleting the wrong folder can break an active plugin. Always cross-reference the exact folder name shown in the error message before touching anything. - Not checking if the plugin is already installed: Head to your Plugins list first. If the plugin is already there and active, you don’t need to reinstall it — and you definitely should not delete its folder. Reinstalling an active plugin without deactivating first can cause brief disruption.
- Trying to fix it from the WordPress dashboard alone: If the folder is from a partial install, it won’t appear in your dashboard’s plugin list, so there’s nothing to click. You must go directly to the file system via File Manager or FTP to remove an orphaned folder the dashboard can’t see.
- Ignoring file permission issues after the folder is gone: If the error persists even after you’ve deleted the conflicting folder, the
plugins/directory itself may not be writable by the web server. The correct permission for that folder is755— check and correct it in File Manager if needed.
Get free WordPress & AI tips
Join 500+ readers. No spam, unsubscribe anytime.
Frequently Asked Questions
Will deleting the plugin folder erase my settings?
In most cases, no. WordPress plugins store their configuration in the database, not in the plugin folder — so deleting the folder removes only the code files, not your saved settings. The exception is plugins that store user-generated files (like PDFs, form submissions, or generated images) inside their own folder. Peek inside before deleting to make sure there’s nothing you need to preserve.
What if I don’t have FTP access or a File Manager?
Contact your hosting provider’s support team and ask them to delete the specific plugin folder at wp-content/plugins/folder-name. Most hosts can do this in minutes via live chat. If you have SSH access, a single rm -rf command pointed at the correct path will handle it just as well.
Can this same error happen when installing a theme?
Yes, exactly the same error can occur during theme installation if a folder with a matching name already exists inside wp-content/themes/. The fix is identical — navigate to that directory in File Manager or via FTP, remove the conflicting folder, and retry the installation from Appearance → Themes → Add New.
What if the folder keeps reappearing after I delete it?
A backup plugin or file sync tool running in the background may be restoring the folder automatically. Temporarily disable any active backup or staging sync plugins, clear all caches, then retry the install. Persistent reappearance can also indicate a deeper permissions problem where WordPress lacks the write access needed to properly replace files during installation.
