WordPress Plugin Install Fails: No Valid Plugins Found

The full error message reads: “The package could not be installed. No valid plugins were found.” It appears in the WordPress plugin installer after you attempt to upload a plugin zip file, and it is one of the more confusing WordPress errors because the message does not tell you why the package was rejected — only that it was. If you are seeing WordPress no valid plugins found, the installer examined the uploaded file and determined it does not meet the structural requirements for a valid WordPress plugin. That could mean the wrong file was uploaded, the correct file was downloaded incorrectly, the zip structure is wrong, or a server-side restriction prevented the file from being processed. In my experience, the WordPress no valid plugins found error is most commonly caused by uploading the wrong file — typically the full zip package from a marketplace rather than the specific plugin zip that goes inside WordPress — and the fix is to simply download the correct file. But there are several other causes that look identical, and this guide covers every one of them. This fits into the wider topic we cover in our WordPress Errors Complete Guide.

What WordPress Is Actually Checking When It Shows No Valid Plugins Found

When you upload a zip file to the WordPress plugin installer, WordPress extracts it to a temporary directory and checks the contents for a valid plugin structure. A valid WordPress plugin must include a PHP file in the root of the extracted folder that contains a specific comment block — the Plugin Header — declaring the plugin’s Name, Version, and other metadata. The WordPress no valid plugins found error appears when WordPress extracts the uploaded zip and cannot find a PHP file containing this header in the expected location.

This validation check is intentionally strict. WordPress is not simply checking whether the file is a zip or whether it contains PHP — it is checking whether the extracted structure matches what a WordPress plugin is supposed to look like. A zip that contains another zip inside it, a zip that contains the plugin in a nested subfolder with an unexpected name, a zip that contains only documentation and no PHP, or a zip whose PHP header has been corrupted — all of these produce the WordPress no valid plugins found error because none of them meet WordPress’s structural expectation for a plugin package.

The practical implication is that the WordPress no valid plugins found error is almost always a packaging or file selection problem rather than a WordPress configuration problem. The installer itself is working correctly — it is correctly rejecting a file that does not have the right structure. Understanding this reframes the fix: instead of adjusting WordPress settings, the task is to obtain the correctly structured plugin package. The cases where the WordPress no valid plugins found error is caused by a WordPress or server configuration problem are less common and are covered later in this guide.

Fix WordPress No Valid Plugins Found by Uploading the Correct Package

The most common cause of the WordPress no valid plugins found error — by a wide margin — is uploading the wrong zip file. Premium plugin marketplaces, in particular, frequently package their products in a way that wraps the actual WordPress plugin inside a larger archive that also contains documentation, license files, and other resources. If you upload this outer package to WordPress, you get the WordPress no valid plugins found error because WordPress finds the documentation and the nested archive but no PHP plugin header at the root level.

1. Go to the source where you downloaded the plugin — the marketplace, the developer’s website, or WordPress.org
2. Look for a “WordPress-ready” or “installable zip” download option specifically labeled for direct WordPress installation. On Envato/ThemeForest, this is typically “Install-ready files” rather than the “All files and documentation” option
3. Download the correct package — it should be a zip file that, when extracted locally, shows a single folder containing a main PHP file with the plugin header as the first thing inside
4. To verify before uploading: extract the zip on your own computer and look at the contents. There should be a folder named after the plugin, and inside that folder should be a .php file with the same or similar name. Open it in a text editor and confirm it starts with something like: /** Plugin Name: My Plugin Name */
5. If the structure looks correct, upload this zip to WordPress via Plugins → Add New → Upload Plugin
6. Confirm the WordPress no valid plugins found error does not appear and the plugin installs successfully

If you purchased a premium plugin and only received one zip file with no “installable” option, extract the outer zip on your computer, locate the inner folder or zip that contains the actual plugin (look for the folder containing the main PHP file), re-compress just that folder into a new zip, and upload the new zip. This manually creates the correctly structured installable package that prevents the WordPress no valid plugins found error. The process takes two minutes and is always cleaner than trying to adjust WordPress settings to accept a non-standard package structure.

Corrupted or Incomplete Downloads Behind the WordPress No Valid Plugins Found Error

A plugin zip file that downloaded incorrectly — whether due to a network interruption, a browser download error, or a server-side delivery problem — can produce the WordPress no valid plugins found error even when the plugin itself is correctly packaged. The file’s internal structure is damaged or incomplete, WordPress extracts partial contents, and the PHP header that WordPress is looking for is either absent or corrupted beyond recognition. The WordPress no valid plugins found error in this case is correctly identifying a problem with the file — the file is just not the right version of the problem that most guides address.

The simplest test for a corrupted download is to delete the downloaded zip, download it again from the original source using a fresh browser session (not the browser’s cached version), and attempt the upload again. If the WordPress no valid plugins found error clears after the re-download, the original file was corrupted in transit. Using a download manager or a different browser for large plugin zips reduces the likelihood of incomplete downloads — some browsers abort or silently truncate downloads on slow connections.

For very large premium plugin packages, some browser-server combinations produce partial downloads that look like complete files to the operating system but are structurally incomplete. The file size is the quickest diagnostic: compare the size of your downloaded file to the file size shown on the download page or in the marketplace. A file that is significantly smaller than expected is incomplete — WordPress will extract what it can and report the WordPress no valid plugins found error when the PHP header is in the missing portion. Re-downloading at a different time or using a direct download manager that verifies file integrity resolves this class of WordPress no valid plugins found error reliably.

File Upload Size Restrictions Interfering With Plugin Installation

The WordPress no valid plugins found error can also appear when a large plugin zip exceeds the maximum upload file size configured in PHP. When the upload limit is exceeded, the file transfer is truncated before completion — WordPress receives an incomplete zip file, extracts what it can, finds no valid plugin header in the partial contents, and reports the WordPress no valid plugins found error. This is technically a file size restriction error presenting as a WordPress no valid plugins found error, and it is identifiable by the combination of a large plugin file and an upload limit that is known to be low.

Check the current upload limit by navigating to Media → Add New in the WordPress admin and looking at the “Maximum upload file size” shown below the upload area. If the plugin zip is larger than this limit, the upload will fail. To increase the limit, add these values to a php.ini file in the WordPress root:

upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 300

Alternatively, add the equivalent .htaccess directives for Apache servers. After increasing the limit and reloading the WordPress admin to confirm the new limit is shown on the Media upload page, attempt the plugin upload again. If the file size was the cause of the WordPress no valid plugins found error, the upload now completes successfully. As an alternative to increasing server limits, large plugins can always be installed via FTP — placing the extracted plugin folder directly in wp-content/plugins/ bypasses the upload limit entirely and is not subject to the WordPress no valid plugins found validation check at all.

Manual FTP Installation When the Uploader Keeps Failing

When the WordPress plugin uploader consistently produces the WordPress no valid plugins found error despite using the correct plugin package, manual installation via FTP provides a reliable alternative path that avoids the uploader entirely. FTP installation is not affected by upload size limits, the WordPress nonce validation that can sometimes interfere with the uploader, or temporary directory configuration issues that can prevent the extraction process from completing correctly.

Extract the plugin zip on your local computer. You should see a single folder named after the plugin — for example, woocommerce/ — containing the plugin’s PHP files, subdirectories, and assets. Connect to your server via FTP, navigate to wp-content/plugins/, and upload the entire plugin folder (not just its contents) into that directory. Once the upload is complete, go to the WordPress admin → Plugins → Installed Plugins. The plugin appears in the list as an inactive plugin — click Activate to enable it.

Manual FTP installation bypasses the WordPress no valid plugins found validation check entirely because the installation is happening directly at the file system level rather than through the WordPress installer. WordPress simply finds the plugin folder in the plugins directory and treats it as an installed plugin. If the plugin does not appear in the Installed Plugins list after the FTP upload, verify that the folder structure is correct — the plugin folder should be directly inside wp-content/plugins/, not nested inside another folder. An incorrectly nested folder produces the WordPress no valid plugins found equivalent at activation — a plugin that does not appear in the list at all.

Server PHP Version and WordPress Compatibility Behind the Error

A final category of WordPress no valid plugins found error appears specifically with plugins that declare a minimum PHP version requirement in their header. If the server’s PHP version is below the plugin’s declared minimum, WordPress may reject the plugin at installation with the WordPress no valid plugins found error or a closely related message. This is a newer behaviour in WordPress that ensures incompatible plugins are not installed on environments that cannot run them.

Check the server’s current PHP version at Tools → Site Health → Info → Server. Cross-reference this with the plugin’s stated requirements, visible on the plugin’s WordPress.org page under “Requires PHP.” If the server is below the plugin’s minimum, upgrading PHP through the hosting control panel (cPanel → MultiPHP Manager or equivalent) resolves the WordPress no valid plugins found error for this specific cause. Modern WordPress development increasingly targets PHP 8.0 and above, and running PHP 7.x on a production WordPress site in 2026 creates both compatibility and security exposure that goes beyond the WordPress no valid plugins found error.

Our guide on fixing the WordPress automatic update failed error covers the update process failures that share some causes with the WordPress no valid plugins found error — particularly the temporary directory and file size issues that affect both plugin installation and the update process. Our guide on how to disable WordPress plugins safely covers the alternative installation paths and plugin management techniques relevant when the standard uploader is not reliable. The WordPress plugin header documentation specifies exactly what the PHP header comment must contain for WordPress to recognise a valid plugin — the definitive reference for understanding why the WordPress no valid plugins found error fires and what the validator is checking for in the uploaded package. You might also run into WordPress 404 Error.