How to Install a WordPress Plugin (Step-by-Step)

Quick answer

This guide is part of the Start with WordPress hub. If you have not built your site yet, start with how to make a website with WordPress, then learn how to install a WordPress theme and how to use the WordPress block editor. To install a WordPress plugin, go to your dashboard, then Plugins → Add New, search for the plugin, click Install Now, then Activate. That is the whole process for most plugins, and it takes under a minute.

If the plugin is not in the WordPress plugin directory — a premium plugin, or one from a developer’s site — upload its ZIP file from the same screen with the Upload Plugin button. If your dashboard cannot write files at all, the fallback is FTP.

The rest of this guide covers what the one-minute version skips: what to check first, how to update without breaking your site, deactivate vs delete, and the exact error messages that stop beginners — with the fix for each one.

Tested on

Tested on

  • WordPress version: 7.1.4
  • Theme: GeneratePress 3.6.1
  • Plugins tested: UpdraftPlus 1.26.14, and Health Check & Troubleshooting 1.7.1
  • PHP version: 8.4.27
  • Test environment: WordPress test install (WordPress pre-installed)
  • Test date: 15 November 2026

The dashboard install and activation steps in this article were checked on a WordPress test install on the date above. The ZIP upload, FTP install, plugin update, deactivation and deletion, and the error cases were not tested in that run — see the test script at the end of this article.

Before you install anything: 5 checks that save you an hour later

A plugin is code that runs on your site. A bad one can slow it down, break a page, or open a security hole. Five minutes of checking first beats an hour of fixing later.

1. Do you actually need it? If WordPress or your theme already does the job, do not add a plugin for it. Every active plugin adds code your site has to load, and a site with 40 plugins is harder to keep healthy than a site with 12.

2. Check the plugin page, not just the star rating. On the plugin’s page in the WordPress plugin directory, look at four things: when it was last updated, whether it says it is tested with your version of WordPress, how many active installations it has, and whether the support forum shows recent replies from the developer. A plugin that has not been updated in over a year is a warning sign. On the test install, UpdraftPlus was last updated 3 weeks ago, while Health Check & Troubleshooting was last updated 2 years ago — wordpress.org warns it “hasn’t been tested with the latest 3 major releases of WordPress”.

3. Read the one-star reviews first. Five-star reviews tell you what works; one-star reviews tell you what breaks and whether the developer answers.

4. Take a backup. Before installing on a live site, back it up — files and database. A backup turns a disaster into a ten-minute restore. If your host offers one-click backups, use them.

5. Check that it fits your site. Some plugins need a minimum WordPress or PHP version, or only work with a specific theme or another plugin. The plugin page lists its requirements — check them before you install, not after it fails.

Method 1: Install from the dashboard (the way most plugins are installed)

This is the method for any free plugin in the official WordPress plugin directory.

  1. Log in to your WordPress dashboard.
  2. Go to Plugins → Add New. On the test install, the menu item is labelled “Add New”.
  3. Type the plugin’s name in the search box at the top right.
  4. Find the right plugin. Check the author name and active installations — popular plugins sometimes have copycats with similar names.
  5. Click Install Now. WordPress downloads the plugin and installs it.
  6. When the button changes to Activate, click it. The plugin is now running on your site.

After activation, most plugins add a menu item to your dashboard sidebar or a settings link under Settings. If nothing appears, the plugin’s directory page usually says where its settings live.

Install one plugin at a time and check your site still works before installing the next — if something breaks, you will know which one caused it.

Method 2: Upload a ZIP file (premium plugins and plugins from other sites)

Use this method when you have a plugin as a ZIP file — a premium plugin you bought, or a free plugin downloaded from a developer’s website. Note: the ZIP upload was not completed on the test install in this run — see the test script at the end of this article.

  1. Go to Plugins → Add New.
  2. Click Upload Plugin at the top of the screen.
  3. Click Choose File, select the plugin’s ZIP file, then click Install Now.
  4. When WordPress finishes, click Activate Plugin.

The wrong-file trap. WordPress expects a ZIP that contains the plugin folder at its top level. Two mistakes are common: uploading a theme ZIP, or a download that contains documentation, licence files and the plugin ZIP nested inside it — unzip the download first and upload only the inner plugin ZIP — or a “nested ZIP”, a ZIP inside a ZIP. If WordPress says “No valid plugins were found”, this is almost always the cause.

The double-zip trap on Mac. Some Mac browsers automatically unzip downloads, leaving you with a folder instead of a ZIP. Right-click the folder and compress it back into a ZIP before uploading.

Method 3: Install with FTP (when the dashboard cannot do it)

FTP is the fallback when the dashboard methods fail — for example when your server will not let WordPress write files, or a plugin ZIP is too large to upload. It needs an FTP client such as FileZilla and your hosting login details.

  1. Unzip the plugin file on your computer. You should have a single folder named after the plugin.
  2. Connect to your site with your FTP client.
  3. Go to the /wp-content/plugins/ folder on your server.
  4. Upload the plugin folder into it — the folder itself, not the ZIP.
  5. Go to your dashboard, Plugins → Installed Plugins. The plugin will be listed there, inactive.
  6. Click Activate.

Once the files are in place, an FTP install is identical to a dashboard install. If you are not comfortable with FTP, ask your host’s support team — most will do it for you, or point you to their file manager.

Updating plugins: one at a time, and never on a live site without a backup

Plugins need updates. Updates fix security problems and bugs, and keep the plugin working with new WordPress versions. Ignoring them is one of the easiest ways to get a site hacked.

How to update: Go to Dashboard → Updates, or find the “new version available” notice under a plugin on the Installed Plugins screen. Click Update Now on one plugin, wait for it to finish, then check your site before updating the next one.

Update one at a time. If you update ten plugins at once and your site breaks, you have no idea which one did it. One at a time takes longer and saves you far more time when something goes wrong.

Auto-updates. You can enable automatic updates per plugin from the Installed Plugins screen. That is sensible for small, well-maintained plugins, and risky for ones running something critical, such as your shop or booking form, where you want to test the update first.

Before a big update, back up. A bad update then costs you a restore, not a rebuild.

Deactivate vs delete: what actually happens to your data

Deactivating and deleting a plugin are not the same thing, and mixing them up is how people lose settings they wanted to keep — or keep files they wanted gone.

Deactivate switches the plugin off. Its files and usually its settings stay put, so you can reactivate it later with your settings intact. Use it when testing whether a plugin is causing a problem, or when you are not sure you want it gone yet.

Delete removes the plugin’s files from your server. Whether it also removes its database settings depends on the plugin — some clean up, some leave settings behind in case you reinstall. Do not assume old settings will be there if you reinstall later.

The safe removal sequence: deactivate first, check your site still works without it, then delete. If the site breaks after deactivation, reactivate and investigate — you have lost nothing.

“Installation failed: Could not create directory”

This is the most common plugin installation error, and it almost always means one thing: WordPress does not have permission to write to your server’s plugin folder.

What causes it: your server’s file permissions do not allow WordPress to create a new folder inside /wp-content/plugins/. This often happens after a site is moved to a new host, or when files were uploaded by a different user account than the one WordPress runs as.

How to fix it:

  1. Try again — a one-off server hiccup sometimes causes this.
  2. If it fails again, install the plugin by FTP instead (Method 3 above). FTP uses your own login, which usually has the permissions WordPress lacks.
  3. If FTP also fails, contact your host and ask them to check the file ownership and permissions on your /wp-content/plugins/ folder — a hosting-level fix.

Do not fix file permissions yourself unless you know what you are doing — wrong permissions can lock you out of your own site.

“Destination folder already exists”

WordPress shows this when a folder with the plugin’s name is already sitting in /wp-content/plugins/, usually because a previous install failed halfway, or because you deleted the plugin from the dashboard but its folder was left behind.

How to fix it:

  1. Go to Plugins → Installed Plugins and check whether the plugin is already listed. If it is, activate it — or delete it and install it fresh.
  2. If it is not listed, the folder is orphaned. Connect with FTP or your host’s file manager, go to /wp-content/plugins/, and delete the folder with the plugin’s name.
  3. Install the plugin again.

Delete only the folder that matches the plugin you are installing — deleting the wrong folder removes a different plugin’s files.

“The link you followed has expired”

This message looks like a broken link. In practice, when it appears during a plugin upload, it almost always means the file you are uploading is larger than your server’s PHP upload limit.

How to fix it:

  1. Check the size of the ZIP file you are uploading. Large premium plugins can be several megabytes.
  2. Ask your host to increase your PHP upload limit, or change it yourself in your hosting control panel if it lets you. The setting is called upload_max_filesize.
  3. If you cannot change the limit, install the plugin by FTP instead. FTP does not go through the browser upload limit.

If you see this message when you are not uploading anything, it can mean your login session timed out. Log out, log back in, and try again.

“Plugin could not be activated because it triggered a fatal error”

WordPress blocks the activation and shows you this message, with the error details underneath. That is actually good news: WordPress caught the problem before the plugin could break your site.

How to fix it:

  1. Read the error message. It usually names the file and line where the failure happened, and often the cause — a function that already exists, a missing file, or an unsupported version.
  2. Check the plugin’s requirements against your site. The most common cause is a version mismatch: the plugin needs a newer WordPress or PHP version than your site runs.
  3. If the plugin is a premium one, contact the developer’s support with the full error message. If it is free, post in its support forum on WordPress.org with the error text.
  4. Do not try to edit the plugin’s code to force it to activate. If it fails on activation, it will fail again — and next time it may take the site down with it.

WordPress white screen after activating a plugin / plugin broke my site

You activate a plugin and your site goes blank — white screen, no error, nothing. This is the most frightening plugin problem, and it is usually fixable in minutes.

First, stay calm and do not keep clicking. The plugin you just activated is almost certainly the cause, so the fix is to switch it off.

If you can still reach your dashboard: go to Plugins → Installed Plugins, find the plugin you just activated, and click Deactivate. Check your site. If it is back, the plugin was the problem — leave it deactivated and contact the developer, or find an alternative.

If you cannot reach your dashboard either: use FTP or your host’s file manager. Go to /wp-content/plugins/, find the folder for the plugin you just activated, and rename it — add -off to the end of the folder name, for example. Renaming the folder deactivates the plugin instantly, because WordPress can no longer find it. Reload your site. If it is back, you have found your culprit.

If the site is still white: rename the whole plugins folder to plugins-off, deactivating every plugin at once. If the site comes back, rename the folder back, then rename plugin folders one at a time until you find the culprit.

Add Plugin button missing / can’t install plugins at all

Sometimes the problem is not an error message — the Add Plugin button simply is not there, or the Plugins menu is missing entirely. That is not a bug. Something is preventing installation.

Check these, in order:

  1. Your user role. Only Administrators can install plugins. If your account is an Editor, Author or Shop Manager, you will not see the option. Ask a site administrator to install it for you, or to upgrade your role.
  2. Multisite. On a WordPress multisite network, only the network administrator can install plugins. Individual site administrators cannot.
  3. File modifications disabled. Some hosts or security setups disable file changes in WordPress — a line in wp-config.php, or a security plugin, may be blocking installs. Your host can tell you whether this is set.
  4. WordPress.com. Sites hosted on WordPress.com have different rules from self-hosted WordPress.org sites, and whether you can install plugins depends on your plan.

If none of these apply, ask your host — they can see the setting blocking you, and it is usually a quick fix on their side.

Locked out of your site completely? Recovery mode is your way back in

Since WordPress 5.2, a fatal error caused by a plugin triggers an email to the site administrator with a special recovery-mode link. If you get that email, click the link, log in, and WordPress will let you deactivate the faulty plugin from a recovery dashboard.

If the email never arrives — it happens, especially if your site’s email is not set up properly — use the FTP rename method from the white-screen section above. Rename the plugin’s folder, and your site should come back. Then log in normally and delete the plugin properly from the dashboard.

With no FTP access and no recovery email, contact your host. They can rename the folder for you, or restore a backup from before the plugin was installed.

What I tested / what failed (test script)

Test script — results from the real test run on the WordPress test install, 15 November 2026. The dashboard install was tested; the ZIP upload, FTP install, update, deactivation/deletion and error cases were not tested in that run — see the list below.

  1. Install a free plugin from the dashboard — TESTED: UpdraftPlus 1.26.14 was installed from Plugins → Add New (search “UpdraftPlus”, 130 results; the live search was slow and results arrived only after a page reload). The plugin card is by David Anderson / Team Updraft, 5.0 rating based on 8,731 ratings, Last Updated 3 weeks ago, 4+ Million Active Installations, “Compatible with your version of WordPress”. After Install Now and Activate, the Plugins list showed “Plugin activated.” and “Plugin dependencies check completed successfully.” A test backup ran and succeeded: “The backup succeeded and is now complete (Nov 15 11:27:31)” — Existing backups 1: Database, Plugins (22.9 MB), Themes (3.1 MB), Uploads (21 KB), Others (1.5 KB).
  2. Install a plugin from a ZIP file via Upload Plugin — NOT TESTED: the ZIP file could not be uploaded in the test environment (the file picker cannot be driven), so no ZIP upload was completed. The Upload Plugin panel itself was checked: “If you have a plugin in a .zip format, you may install or update it by uploading it here.”, “Choose file” / “No file chosen”, and “Install Now” is disabled until a file is chosen.
  3. Install a plugin via FTP into /wp-content/plugins/, then activate it from the dashboard — NOT TESTED: there was no file manager or FTP access from wp-admin on the test install, so no FTP install was done.
  4. Update one plugin, then check the site. Then enable auto-updates on one plugin and record the setting — NOT TESTED in this run: no plugin update or auto-update was run on the test install.
  5. Deactivate a plugin, check the site, then delete it and note whether its settings remained in the database — NOT TESTED in this run: no plugin was deactivated or deleted on the test install.
  6. Reproduce each error in this article and record the exact wording shown and the fix that worked — NOT TESTED: none of the errors in this article was reproduced on the test install in this run.
  7. Reproduce the missing Add Plugin button by testing with a non-administrator user role, and record what the dashboard shows — NOT TESTED in this run: no non-administrator role was tested.
  8. Trigger a fatal error with a faulty plugin and record whether the recovery email arrived and whether Recovery Mode worked — NOT TESTED: no fatal error was triggered on the test install (the file editor rolls back fatal PHP changes), so no recovery email arrived and Recovery Mode was not used.

Results: UpdraftPlus 1.26.14 was installed and activated from the dashboard and a test backup succeeded on 15 November 2026. Health Check & Troubleshooting 1.7.1 was also installed from the directory (3.5 rating based on 181 ratings, Last Updated 2 years ago, 200,000+ Active Installations, “Untested with your version of WordPress”; wordpress.org warns it “hasn’t been tested with the latest 3 major releases of WordPress”). The UpdraftPlus settings page works: tabs Backup / Restore, Migrate / Clone, Settings, Advanced Tools, Premium / Extensions; “Next scheduled backups: Files: Nothing currently scheduled; Database: Nothing currently scheduled”; the onboarding overlay was dismissed via “Exit setup”.

What failed: the ZIP upload was not completed (the file picker could not be driven in the test environment), and the FTP install, plugin update, deactivation/deletion and error reproductions were not tested in this run. Nothing that was tested failed.

Next steps

You now know the full plugin lifecycle: check before you install, install from the dashboard, ZIP or FTP, update one at a time, deactivate before you delete, and fix the exact error when one appears.

The habit that prevents most plugin problems is the boring one: back up before you install or update, and change one thing at a time.

Next, learn how to choose plugins worth keeping — and how to tell when a plugin is slowing your site down.

— Mohd Shah Ahmad, WordPress & WooCommerce specialist based in Pretoria, South Africa. I build and run live WooCommerce stores, and manage the live stores Stanley’s Bakery (stanleysbakery.co.za) and Aaliyah Perfumes (aaliyahperfumes.co.za).

Learn WordPress Online is an independent tutorial site. It is not affiliated with, endorsed by, or sponsored by the WordPress Foundation or Automattic Inc. 'WordPress' is a registered trademark of the WordPress Foundation.