Choose the method and the result you need
A plugin adds a feature to WordPress. Before installing one, describe the result you want: displaying a gallery, receiving an enquiry, or managing bookings. Check whether the WordPress editor, your theme, or a tool that is already active can do this. Installing two plugins for the same task makes configuration and troubleshooting more complicated without guaranteeing a better result.
Use the built-in directory when the plugin you need is listed there and that edition meets your requirements. Upload a ZIP when the developer provides one, particularly for a commercial edition. Both methods use the administration interface and are explained below. An agency-managed site may require a different process: in that case, ask the person responsible for deployment to integrate the product.
The aim is more than receiving a successful installation message. You need to identify the right product, activate it if necessary, configure the relevant settings, and check its effect. Also prepare a way to return to the previous state, especially if the site receives orders or registrations.
Check the site, account and access permissions
Check the dashboard address to avoid working on the wrong site. Open Plugins, then Installed Plugins, and search for the product you are considering. It may already be present but inactive, or installed under a slightly different commercial name. In that case, do not attempt a second installation before you understand its status and purpose.
Installing and activating require separate permissions. On a standard WordPress site, an administrator generally has these permissions. In a multisite network, installation is handled by the super administrator, and activation may apply to the whole network. Do not change roles or disable a restriction to make a button appear: ask an authorised person to carry out the operation.
Open Tools, Site Health, then Info. Expand WordPress to find its version and Server to find the PHP version, then compare them with the plugin requirements. Managed hosting may control changes even for an administrator account. If the site has a maintenance procedure, follow it instead of installing directly in production.
- Confirm the domain, working environment and account before taking any action.
- Note the name and version of tools that already perform a similar function.
- If the Add New menu is missing, first identify the role, multisite setting or hosting rule responsible.
Prepare a rollback without losing recent data
Check that you have a recent backup of the files and database, and know how to restore it. An export of a few posts is not a substitute for this backup. Keep the date and location of the copy, then make sure it corresponds to the site you are about to work on.
For a store, membership area or important site, start on a test copy. Avoid leaving automatic messages, real payments or connections active if they could trigger operations with a third party. Follow each service’s documented test mode; a staging environment does not automatically neutralise all its integrations.
The first rollback option will often be to deactivate only the plugin you added. A full restoration may erase orders, messages or posts received since the backup. It therefore requires a separate decision and preservation of recent data. Keep an important page open and note how it works before installation so you have a concrete point of comparison.
Identify the right plugin before downloading it
Compare the name, author and official website. Search results may include similar products or add-ons that require a main plugin. Read the full listing instead of relying on the icon. Note the edition you chose and the folder or file name if the developer specifies them.
Examine the required WordPress and PHP versions, the update date and how issues are handled. A “not tested with your version” notice does not automatically mean the plugin is unusable; it indicates that compatibility still needs checking. Conversely, a high rating or many installations does not prove it will suit your configuration.
Distinguish between the free plugin, its paid features and external services. A booking tool may be free to install while charging for some integrations. A licence key may provide updates or support. Read the terms for your chosen edition and its uninstall procedure before entrusting important data to it.
- Find the same identity on the directory listing and the developer’s official website.
- Check that the essential feature is included in your chosen edition and identify any declared dependencies.
- Avoid archives presented as unlocked commercial versions and downloads whose origin cannot be verified.
Method 1: install from the WordPress directory
This method avoids handling an archive when the product is distributed through the WordPress.org directory. Labels may vary slightly with language and version. In the standard WordPress administration interface, installation copies the files; activation is a separate action afterwards.
Wait for an operation to finish before clicking again. If a message reports a failure, record it: repeatedly starting installations does not tell you what state was actually saved. Once the plugin is active, its settings screen may appear in a new menu, under Settings, or on its row in the plugin list.
- Open Plugins, then Add New Plugin.
- Enter the exact product name in the search and open its details to confirm the author and requirements.
- If the listing reports missing dependencies, first install the required components as explained below. The Install Now button may remain unavailable until they are installed.
- Return to the chosen plugin’s listing, click Install Now, and wait for confirmation.
- Click Activate when the action is offered and the requirements are met.
- Return to Installed Plugins, find the plugin’s row, and check its status and any messages.
Method 2: upload the ZIP supplied by the developer
Download the installation archive from the official website or the account used for the purchase. Keep a copy of the original file and its version. A commercial download may contain documentation, a theme and several archives: choose the ZIP specifically identified as the installable plugin.
For an upload through the administration interface, keep the file in ZIP format. Do not upload an extracted folder or a theme on the plugins screen. If your browser automatically extracted the download, retrieve the original archive or follow the developer’s instructions instead of rebuilding a file at random.
If WordPress finds that this plugin is already installed and offers to replace the existing version, stop the first-installation procedure. Compare versions and update instructions. Replacement may change a tool that is already in use; it is not a harmless confirmation.
- In the standard WordPress administration interface, open Plugins, Add New Plugin, then Upload Plugin.
- Select the installation ZIP on your computer and check its name before uploading.
- Click Install Now, then wait for the upload and installation result.
- After a successful installation is confirmed, click Activate Plugin if that action is offered.
- Find the product in Installed Plugins and compare the displayed version with the one you expected.
Adapt these steps to WordPress.com
As of 3 November 2026, WordPress.com states that its paid Personal, Premium, Business and Commerce plans allow plugin installation. The free plan does not. Also check that the product is compatible with the platform: having a ZIP does not authorise you to bypass an explicit restriction.
The WP Admin interface follows the upload process described above. In WordPress.com’s own interface, the Plugins section also offers an upload button, and importing may automatically install and then activate the plugin. An “Install and activate” button also combines both operations. Read the label before clicking: do not assume that the plugin will always remain inactive after installation.
If your plan should allow the operation but the expected menus are missing, focus on that diagnosis. The guide to missing installation menus on WordPress.com addresses this situation. Changing plans or buying a licence at random does not distinguish insufficient access from a service activation problem.
Handle dependencies without installing an unnecessary collection
Some plugins extend another plugin and do not work on their own. WordPress can display declared dependencies. In the directory, installation may be blocked until the required components are installed; activating the dependent add-on then requires those components to be active. A mandatory dependency is different from a tool merely recommended in a promotional banner.
Read the exact name of the requested component and understand its role in your project. If it is genuinely required, check its own requirements, then install it through the same trusted channel. Activate it before returning to the add-on. If you do not need the main plugin, you may have chosen the wrong product for your use case.
Not every relationship between plugins is declared to WordPress. Also consult the developer’s instructions for required versions and paid editions. Do not conclude that there are no dependencies just because no warning appears. Record the relationship in your notes so that you do not later delete a component that another one depends on.
Configure only what you need
Open the documentation for the product and its edition. Start with the minimum configuration needed to achieve your goal. A wizard may suggest additional services, diagnostic data collection, a demo import or an external connection: read each of these choices separately.
Before connecting an account, identify the permissions requested, the data transmitted and any charges. A successful connection does not mean the service is free. For a commercial licence, use the legitimate owner’s account and check the number of permitted sites, including whether a test copy counts.
Save the necessary settings, then create just one demonstration item: a form, gallery or rule, depending on the plugin. Avoid importing an entire site to try a small feature. This lets you isolate the plugin’s effects without replacing the existing design or content.
Check a complete journey from the visitor’s perspective
Return to your written goal and check the result in a private window, then on a small screen. The dashboard may display something different from what a logged-out visitor sees. Also check an authorised user if the feature is restricted to members. Do not publish personal data to make your test easier.
For a form, send a test message to your own address and check the confirmation, delivery and intended storage. For a gallery, open several images, close the enlarged view, and use the keyboard. For a commercial feature, use only the provider’s designated test mode and make sure the public site does not accidentally switch into that mode.
Also check a journey that worked before: navigation, search, login or contact, depending on your site. If a cache hides a change, refresh only the relevant pages using the tools already provided. Do not install a second plugin to hide a symptom before identifying what changed.
- Compare the observed result with the goal, then record the exact steps if something fails.
- Check error messages and the data actually received; a correct appearance is not enough.
- Record the installed version, essential settings and the results of your own checks.
Roll back if activation breaks the site
If the administration interface is still accessible, open Installed Plugins, locate the new plugin, and click Deactivate. Then reload the journey that failed. A return to normal operation helps narrow the diagnosis, but does not yet prove which conflict or setting is responsible. Keep the version and error message so you can investigate on a copy.
Deactivating and deleting are different operations. Deletion may trigger removal of settings or data, depending on the plugin. Read its procedure before using Delete. If the plugin created forms, content or bookings, preserve anything that needs keeping. Deactivating it may also remove those items from view without erasing them.
If a critical error prevents access, WordPress may send a recovery link to the administration email address. When the link is available and belongs to your domain, sign in through it, read which component is identified, and deactivate it if it is the affected plugin. Exit recovery mode, then check the site normally. This feature is not guaranteed: the email may not arrive, and not every failure provides access to it.
- Do not deactivate every plugin on the site when the problem has just appeared after one specific change.
- If deactivation is blocked, identify any dependency, network activation or management rule before proceeding.
- If no recovery access is available, retain the error and follow the targeted procedure in the critical error guide with the person who has hosting access.
Handle installation failures and finish properly
When a ZIP is rejected, first check the file: a theme archive, documentation folder or incomplete download is not an installable plugin. If its size exceeds the stated limit, note the archive size and exact message, then have the appropriate limit checked. Changing a file’s extension does not fix an archive that is too large.
A request for FTP credentials or an inability to write files requires a different diagnosis. Note whether the failure happens before downloading, during uploading, or after extraction. The dedicated FTP credentials or disk-writing guide can then help address the cause. Do not make folders writable by everyone or bypass the site’s deployment policy.
Once the result is validated, remove test items and keep a record of the selected plugin. Decide who will monitor updates, any licence and security notices. If you abandon the product, disconnect associated services according to their documentation, then delete it only after checking the consequences. The site should retain a useful feature and an identifiable person responsible for it, not simply one more plugin.
Continue learning
- WordPress.com: find the theme and plugin installation menus
- WordPress critical error: regain access and fix the cause
- WordPress plugin: fix an invalid ZIP or an archive with no recognized plugin
- WordPress asks for FTP credentials: restore the correct access method
- WordPress installation blocked: the directory is not writable


