How to install a WordPress plugin safely

The WordPress.org directory lists over 74,000 free plugins, and every one of them installs with the same two clicks. The clicks are rarely where things go wrong. Installs fail because of the server, the account or the file you uploaded. Activation is where a site breaks, because that is when the plugin’s code starts running next to your theme and every other plugin.

This guide covers the four ways to install a plugin, how to read the error when one fails, and what to do if the site breaks after you activate.

Which kind of WordPress site do you have?

Check this first. Most “I can’t install plugins” threads turn out to be about the platform, not the plugin, and each platform has a different fix.

• Self-hosted WordPress (WordPress.org software on your own hosting). Any Administrator can install plugins. Everything in this guide applies.
• WordPress.com. This is a hosted service. Its support documentation says plugins need a paid plan, and some plugins are marked “Not supported”. On a free plan the option is simply not there.
• Multisite. WordPress’s Roles and Capabilities documentation says only the Super Admin can install plugins by default. Site admins don’t see the option. The Super Admin installs from Network Admin → Plugins. People often end up on Multisite by choosing it during setup without meaning to. Our guide to WordPress Multisite installation explains how a network is set up.
• A local install on your own computer. These often ask for FTP details because the web server can’t write to your files. The fix for that is further down.

You also need the Administrator role on a single site. Editors and Authors can’t install plugins. The menu doesn’t show an error. It just leaves the option out.

What to check before you click Install

Thirty seconds on the plugin’s listing saves most of the trouble later. On the Add Plugins screen and the plugin’s directory page, look at:

• Compatibility. WordPress shows whether the plugin is compatible with your version or untested with it. “Tested up to” gives the latest WordPress version the developer has confirmed.
• Last updated and active installations. A plugin that hasn’t been updated in years has probably not been tested against current PHP. The install count is a rough tier, not an exact number.
• The Support tab. Look for recent unanswered reports of fatal errors or conflicts with plugins you already run.
• The changelog and readme. WordPress’s Plugin Handbook describes the changelog as the record of each release. Minimum PHP versions, dependencies and known bugs are usually listed there.

Only install from the official directory or from a developer you trust. A “free” copy of a paid plugin from a download site is the usual way malware gets onto a WordPress site. Install one plugin per job, too. Two SEO plugins or two caching plugins on the same site will conflict.

Then make a way back. Take a backup before you install anything on a site that matters, and use a staging copy for stores and for plugins that change checkout, forms or logins. If you aren’t sure what your backup actually includes, read our explainer on what a backup plugin covers.

Method 1: install from the plugin directory

Use this for any free plugin listed on WordPress.org.

1. In the dashboard, go to Plugins → Add New Plugin. Older versions of WordPress label it Add New.
2. Search for the plugin by name. Check the author on the card, because several plugins often share similar names.
3. Click Install Now and wait while WordPress downloads and unpacks the files.
4. Click Activate. The plugin does nothing until you do.

Method 2: upload a ZIP file

Use this for paid plugins and private plugins that don’t come from the directory.

1. Go to Plugins → Add New Plugin and click Upload Plugin at the top.
2. Choose the plugin’s ZIP file. Don’t extract it first.
3. Click Install Now, then Activate Plugin.

Upload the right ZIP. Marketplace downloads, ThemeForest in particular, often come as one big archive holding documentation, license files and several smaller ZIPs. The plugin is one of the inner ZIPs. If you upload the outer bundle, WordPress replies “No valid plugins were found.” The same error appears if you upload a theme here. Themes go in Appearance → Themes → Add New Theme.

Paid WooCommerce extensions have their own route. WooCommerce’s documentation says automatic installation and updates need the WooCommerce.com Update Manager plugin. A manual ZIP upload works, but the site still has to be connected to your WooCommerce.com account before the extension gets updates and support.

Method 3: upload the folder by SFTP or File Manager

WordPress’s Manage Plugins documentation describes this for cases where the server isn’t set up for automatic installs. In practice you also use it when the upload hits a size limit.

1. Extract the ZIP on your computer.
2. Open the extracted folder and make sure the plugin’s main PHP file sits directly inside it. A folder nested inside a second folder is a common reason WordPress can’t see the plugin.
3. Connect with SFTP, or open your host’s File Manager, and upload the folder to wp-content/plugins/.
4. In the dashboard, go to Plugins → Installed Plugins, find the plugin and click Activate.

Method 4: WP-CLI, for developers

If you have SSH access, one command installs and activates a plugin. It takes a directory slug, a ZIP path or a URL:

wp plugin install contact-form-7 --activate
wp plugin install ./my-plugin.zip --activate

To confirm the result and see versions, run wp plugin list. Our guide to wp plugin list covers the filters.

What a correct result looks like

Go to Plugins → Installed Plugins. The plugin should be listed and show as active, usually with a new menu item or a Settings link. Many plugins do nothing until you finish their setup, so open the settings before you decide it’s broken.

Then open the site in a private window, logged out. Look at the home page and at whatever the plugin affects. Submit a test form, or add a product to the cart and go as far as the checkout. Visitors see the logged-out site, and conflicts often show up only there.

“Installed” doesn’t mean “working”. Google’s structured data documentation says to check a plugin’s markup with the Rich Results Test. A header-and-footer plugin can be active while your tracking tags never fire. If the plugin is supposed to produce output, check the output itself.

Why the install failed, by error message

Read the exact message. Each one points to a different cause:

What you see	Usual cause	Fix
The package could not be installed. No valid plugins were found.	Vendor bundle, theme ZIP or nested folder	Upload the inner plugin ZIP, or install the theme under Appearance
A prompt asking for FTP hostname, username and password	File ownership	Ask the host to fix ownership. Use SFTP in the meantime
Installation failed: Could not create directory	Permissions or ownership on wp-content	Same as above
The uploaded file exceeds the upload_max_filesize directive in php.ini, or a 413 error	Host or PHP upload limit	Upload by SFTP, or ask the host to raise the limit
Destination folder already exists	A leftover folder from an earlier attempt	Rename the old folder and try again
No Add New Plugin button, no error	Role, Multisite or WordPress.com plan	See the platform section above

The FTP prompt means an ownership problem

WordPress’s Updating WordPress documentation says it asks for FTP details when it can’t create files with the correct ownership. You don’t actually need FTP. The web server user doesn’t own your files. The fix is to give ownership to the right user, and which user that is depends on the host, so ask them.

Don’t set folders to 777 to make the prompt go away. WordPress’s Hardening handbook advises keeping write access to a minimum and warns that it is risky on shared hosting. Forum threads also suggest adding FS_METHOD to wp-config.php. Practitioners report it often fails when the underlying ownership is wrong. One wordpress.org case was traced to code a migration plugin had left in wp-config.php, so look there if the permissions seem right.

Upload limits are set by the host

Two PHP settings decide how big an upload can be: upload_max_filesize and post_max_size. The lower of the two wins. Raising memory_limit changes nothing here, and some cheap or free hosts don’t let you change the limits at all. Uploading the extracted folder by SFTP avoids the limit entirely.

A leftover folder blocks a fresh copy

A failed install or update can leave a half-written folder in wp-content/plugins/. WordPress won’t write over it. Rename the folder, for example to plugin-name-old, instead of deleting it, so you still have a copy. Then install again. Reinstalling WordPress does not fix this. A plugin’s settings usually live in the database, so a fresh copy normally picks them up again.

If the site breaks after you activate a plugin

A white screen, a “critical error” message or a broken checkout right after activation almost always means the new plugin. WordPress’s Recovery Mode, added in version 5.2, emails the admin address a link that lets you log in and deactivate the plugin that caused the fatal error.

If the email never arrives, open wp-content/plugins/ by SFTP or File Manager and rename the plugin’s folder. WordPress deactivates a plugin whose folder it can’t find. Our WordPress white screen guide covers the case where you aren’t sure which plugin to blame.

Deactivating gets you back in. It doesn’t tell you what the plugin conflicts with. WooCommerce’s conflict-testing documentation gives a method that works on any site:

1. Work on a staging copy with a backup.
2. Update WordPress, the theme and the plugins.
3. Switch to a default theme and deactivate everything except the new plugin, plus WooCommerce if you run a store.
4. Check whether the problem happens again.
5. Reactivate the other plugins one at a time, testing after each, until the problem comes back.

Don’t do this on a live store, because every step changes what customers see. When you report the problem to the developer, include the plugin and theme versions, your WordPress and PHP versions, and the exact error text. For plugins that activate cleanly but misbehave, see fixing plugins that are not working.

Installing is the first step. Updates are the rest

Each plugin you install has to be updated as long as it stays on the site, and each update can conflict with something just as the first activation could. Read the changelog before you update. Delete plugins you no longer use, because an inactive plugin’s files are still on the server and still need patching. Plugin maintenance is a regular job, not something you do once. If you’d rather not do it yourself, SiteSelf handles plugin updates and cleanup on request from chat and reports what changed and what it checked.

When to stop and get help

Stop and contact your host if the FTP prompt or “Could not create directory” doesn’t go away. Ownership is a server setting, and guessing at permissions can open security holes. Stop if a store’s checkout breaks and you have no staging copy or backup to test against. Get help, too, if one plugin fails on several sites at once, or if a reinstall keeps failing after you have renamed the leftover folder.