If you’re trying to install a WordPress plugin or theme and suddenly see:
“Destination folder already exists.”
…then don’t worry — this is one of the most common WordPress errors, and luckily, also one of the easiest to fix.
This error blocks your installation and usually happens when WordPress detects a folder with the same name already present in your /wp-content/plugins/ or /wp-content/themes/ directory.
In this complete guide, I’ll walk you through:
-
Why the “Destination Folder Already Exists” error happens
-
The fastest ways to fix it (with screenshots-style explanations)
-
Code-based solutions if the folder doesn’t show
-
How to prevent this error permanently
-
Advanced troubleshooting for stubborn cases
-
FAQs + schema markup
Let’s get started.
What Causes “Destination Folder Already Exists” Error?
This WordPress error typically appears during plugin or theme installation and looks like this:
Here’s why it happens:
1. Previous Installation Failed Halfway
Sometimes WordPress starts extracting a plugin/theme but stops due to:
-
Timeout
-
Server crash
-
Memory issues
-
Permission problems
This leaves a leftover folder.
2. The Plugin/Theme Was Deleted Incorrectly
If you deleted a plugin via FTP or an auto-delete failed, WordPress might still think the folder exists.
3. You Installed the Same Plugin Before
Some users try to install a plugin they previously tested or uninstalled.
4. Zip File Name Mismatch
Sometimes developers rename plugins, causing mismatches between the zip name and the actual internal folder name.
5. A Corrupted Folder Exists
A partial or empty folder with the same slug can block installation.
How to Fix “Destination Folder Already Exists” (All Methods)
Below are all guaranteed working methods, starting from easiest to advanced.
Method 1: Delete the Existing Folder via FTP or File Manager (Fastest Fix)
This is the most common fix.
You simply remove the old folder, and WordPress will install the plugin/theme normally.
Step-by-Step:
1. Connect using File Manager (cPanel) or FTP
-
Login to your hosting panel
-
Open File Manager
OR
Use FTP (FileZilla, WinSCP, CyberPanel File Manager, etc.)
2. Navigate to:
For plugins:
For themes:
3. Locate the folder with the same name as the plugin/theme
Example:
Trying to install elementor.zip → look for /elementor/
4. Delete the folder
Right-click → Delete → Confirm
5. Reinstall the plugin/theme
Now go back to WordPress > Plugins or Themes → Upload again.
This fixes the error 90% of the time.
Method 2: Clear the Temporary Upgrade Folder
Sometimes the temp upgrade folder causes the issue.
Navigate to:
If you see leftover folders inside, delete them.
These folders are safe to remove — WordPress recreates them automatically.
Method 3: Rename the Existing Folder (Safe Solution)
If you are unsure about deleting the old folder, rename it instead.
Example:
Rename:
to:
Then try installing the plugin/theme again.
If everything works, you can delete the old folder later.
Method 4: Increase PHP Memory Limit (If extraction fails)
Sometimes the installation fails halfway because of low PHP memory.
Add this to wp-config.php:
Save and try again.
Method 5: Fix File Permissions
Incorrect permissions can leave ghost folders behind.
Set these permissions:
You can update permissions through cPanel or FTP.
Method 6: Manually Upload the Plugin or Theme
If WordPress installer keeps failing, upload manually.
For Plugins:
Upload the plugin folder into:
Then go to:
WordPress → Plugins → Activate
For Themes:
Upload into:
Then activate from Appearance → Themes
Method 7: Delete Plugins Using WP-CLI (For Power Users)
If you have SSH access, this is the fastest method.
Delete the stuck plugin folder:
Or for themes:
This immediately removes all leftover files.
Method 8: Fix “Destination Folder Already Exists” Inside a Multisite Network
In WordPress Multisite, plugin folders can become locked due to network-level installation.
Steps:
-
Go to Network Admin
-
Check if plugin/theme exists under Network Plugins/Themes
-
Deactivate → Delete → Reinstall
If it does not appear, manually remove the folder using FTP.
Method 9: Remove Corrupted .maintenance File
If WordPress got stuck during installation, a .maintenance file can block the install process.
Navigate to:
Check and delete:
Then retry installation.
Method 10: Reinstall WordPress Core Files (Safe Method)
No data is lost.
Go to:
Dashboard → Updates → Reinstall Now
This fixes file conflicts and updates the required core folders.
Advanced Fix: When Folder Exists But Doesn’t Appear in FTP
Sometimes the folder exists but is not visible due to hosting caching or permission errors.
Try this PHP script to list all items inside /wp-content/plugins/:
Create a file named scan.php in your root with:
Visit:
You will see the hidden folder name.
Delete it manually through SSH or file manager.
Remove the scan.php file after use.
Why This Error Is More Common in 2025
With new hosting limits, optimized file systems, and updated WordPress file validation, this error is happening more frequently due to:
-
Better security restrictions
-
Limited extraction permissions
-
Auto-cleaning conflicts
-
Faster hosting causing incomplete deletions
-
Auto-update failed processes
But thankfully, all fixes remain the same.
How to Prevent “Destination Folder Already Exists” Error in the Future
Here are the top best practices:
Delete plugins/themes correctly
Always delete from WordPress dashboard first.
Avoid duplicate zip uploads
Check if the plugin already exists before uploading.
Keep hosting updated
Use PHP 8.1+ and fast SSD hosting.
Increase memory limit
Avoid mid-installation crashes.
Disable aggressive caching plugins
Some caching systems block live installation.
Use safe uninstall scripts
Plugins like WP-Optimize, UpdraftPlus, and All-In-One WP Migration often leave leftover folders.
Common Plugins/Tools That Often Trigger This Error
-
Elementor
-
WPBakery
-
WooCommerce
-
Oxygen Builder
-
Astra Pro
-
Yoast SEO
-
WPForms
-
Wordfence
-
AI Builders / Page builders
-
Backup plugins
These plugins are large, and partial installations are very common.
Real Example: Fixing Elementor Installation Error
You try to install elementor.zip and see:
When you open:
You see a leftover folder:
Delete it → install again → fixed.
Fixing Themes That Throw This Error (Astra, Divi, Blocksy, etc.)
Themes often have leftover child theme folders too.
If installing Astra, check:
Also check:
Delete both if the installation failed earlier.
When You Should NOT Delete the Folder
Do NOT delete the folder if:
-
You have active custom code inside the plugin
-
You modified theme files manually
-
The folder belongs to a premium plugin with settings stored locally
In this case, use rename method:
Then reinstall.
Fix for WooCommerce Users
WooCommerce is a heavy plugin.
If installation/update breaks:
-
Delete old folder
-
Remove
/wp-content/upgrade/files -
Increase memory
-
Retry installation
Never delete WooCommerce data tables.
WordPress stores orders and settings inside the database — removing the folder does not delete your store data.
Fix for CyberPanel, cPanel, Plesk, DirectAdmin Users
✔ CyberPanel:
Use → Website → File Manager → navigate to /wp-content/
Delete plugin/theme folder
✔ cPanel:
Open File Manager → /public_html/wp-content/...
✔ Plesk:
Go to Files → navigate and delete the folder
✔ DirectAdmin:
Use File Manager → delete the folder
All support the same fix.
Complete Troubleshooting Checklist
Before installing again, verify:
-
Folder deleted
-
Upgrade folder cleared
-
Permissions correct
-
Memory limit increased
-
No
.maintenancefile -
Caching temporarily disabled
-
No duplicates of plugin or theme
If all good → installation should work without error.
Conclusion
The “Destination Folder Already Exists” error may look frustrating, but it’s actually very easy to solve. In most cases, simply deleting or renaming the existing folder fixes the problem instantly.
Whether you’re installing plugins like Elementor, WooCommerce, WPForms, or big themes like Astra, Divi, or OceanWP — this guide covers everything you need to fix the issue quickly and safely.
Now you’re fully equipped to handle this error anytime it appears — like a pro!
Frequently Asked Questions (FAQs)
1. Is it safe to delete the existing folder?
Yes — WordPress stores plugin settings in the database, not inside the folder.
2. Why does this error happen again and again?
Usually due to server timeout or low memory. Increase your PHP memory limit.
3. Can I fix this error without FTP?
Yes — rename the folder using a hosting file manager.
4. Will deleting the folder remove my settings?
No — for 99% of plugins, settings remain intact in the database.
5. What if the plugin folder doesn’t show in FTP?
Use SSH or a PHP scanner script to locate hidden folders.
6. Does this error affect website performance?
No — it only affects plugin/theme installation.
7. How do I stop this error from coming back?
Avoid duplicate installations, increase memory, and remove leftover folders regularly.