If WordPress’s Add New Plugin control is missing, first check which site and account you are using, then ask who controls software installation. A missing button does not automatically mean WordPress is broken. It can reflect your permissions, a Multisite network, a hosting plan or an intentional deployment policy.
This guide is for a business owner who can sign in but cannot find the expected installation controls. It is not a reason to promote every user to Administrator, disable security or upload code through another route. The goal is to get the required feature installed through the right owner, with a recovery plan and a useful completion check.
Identify what is missing before trying a fix
Open the site’s administration area through your usual trusted address. Record the public domain and whether you are viewing production, staging or a network dashboard. Being signed into a hosting account, WordPress.com or another copy of the site is not proof that you are in the intended installation.
Then describe the exact symptom: no Plugins menu, a plugin list without Add New or Add Plugin, no Upload Plugin control, or an error after you start installing. Those are different stages. WordPress’s Plugins screen documentation separates installed-plugin management from adding software.
Take a redacted screenshot of the relevant area and note when the control last worked, if known. Hide account details, customer information and private notices. Do not post a full dashboard screenshot or configuration file in a public support thread.
Match the visible symptom to its likely owner
| What you see | What to establish | Next safe step |
|---|---|---|
| No Plugins menu | Your intended account capabilities and any site-management policy | Ask the known administrator to review access without immediately broadening it. |
| Installed plugins are visible, but Add New is absent | Whether installation belongs to a network or managed deployment | Ask who installs approved packages and how to request one. |
| A WordPress.com plan message appears | The actual hosting service and current plan’s plugin support | Check current official plan guidance before buying an upgrade. |
| Installation starts but reports an error | The exact package, error, time and current installed state | Stop treating it as only a missing-menu problem; send the failed step to the maintainer. |
| The plugin is installed but Activate is unavailable | Dependencies, network control or another activation restriction | Review the plugin’s requirements, not the installation menu. |
This table routes the investigation; it does not diagnose your site from one screen. A menu can also be customized. The responsible administrator must distinguish presentation from the underlying permission or policy before changing either.
Separate page editing from plugin installation
A person who can publish pages may still be unable to install plugins. WordPress’s roles and capabilities reference lists install_plugins separately from content-editing permissions. On a standard single-site installation, this is an Administrator capability, not a normal Editor capability. Custom roles and management restrictions can change the practical result.
Ask an authorized administrator to confirm the intended access for your work. A role name alone does not establish that every software action is permitted. If you only need one feature, having the maintainer install and verify it may be more appropriate than changing your role permanently.
Do not create another administrator or install a role-management tool to bypass the missing control. If an unexplained privileged account appears during this review, use the separate unknown WordPress administrator guide. A missing Plugins menu by itself is not evidence of compromise.
Check whether the site belongs to a Multisite network
In Multisite, the network owner controls installation. WordPress documents plugin-installation capability as a Super Admin responsibility in that context. A site administrator may manage one site’s content and settings without being allowed to add software to the whole network.
Ask the network administrator whether the requested plugin is already installed, permitted for your site or subject to a network-wide review. Explain the feature you need and which site needs it. Installing one package can affect shared code, so the decision needs more context than a screenshot of a missing button.
Network installation, network activation and site activation are not interchangeable steps. Do not ask someone to network-activate a plugin merely because installation is managed centrally. The administrator should choose the intended scope and test the relevant sites.
On WordPress.com, verify the current plan
First establish that the site is actually hosted on WordPress.com. Using WordPress software on another host does not place the site under WordPress.com’s plan rules.
As checked on October 18, 2026, WordPress.com’s official plugin-installation guide lists installation on its paid Personal, Premium, Business and Commerce plans. Its free-site guidance requires a plan upgrade for installation. Older advice that only Business supports plugins should not be your buying decision.
Check the site’s actual plan and the message shown in its dashboard. If the plan should support installation but the control is absent, ask WordPress.com support to review that site and account. Do not purchase a more expensive plan merely because a dated tutorial says to.
A managed deployment can intentionally hide installation
Some sites receive code through a host or developer’s release process instead of dashboard installation. Ask whether plugin changes must be reviewed, tested or deployed from a controlled source. A useful answer identifies the responsible person, approved package source and route for requesting the change.
WordPress’s configuration documentation distinguishes DISALLOW_FILE_MODS, which blocks dashboard plugin/theme installation and updates, from DISALLOW_FILE_EDIT, which disables the file editors. A disabled editor does not, on its own, explain a missing installation control.
These names are useful questions for your maintainer, not instructions to edit configuration. Do not turn a restriction off, change file permissions broadly or use a file manager to bypass it. First establish why it exists and whether the intended deployment process is working.
A missing core-update offer is a separate problem. Our WordPress core update guide covers version detection and deployment evidence. A plugin that cannot be deactivated has its own dependency and removal checks.
When installation begins but fails
If you can choose a package and start installation, the original problem has changed. Preserve the exact error and inspect the fresh plugin list before retrying. Tell the maintainer whether the package is absent, installed but inactive, or reporting a failed activation.
The official plugin-management guide describes installation and troubleshooting paths. Package identity, compatibility, storage, connectivity and filesystem access may need separate investigation. Do not apply a missing-button workaround to every installation error or repeatedly upload the same archive without checking the result.
Use the known WordPress.org listing or authenticated vendor source. Our plugin-source safety guide explains why an email attachment or unknown mirror is not an adequate substitute. If the public site has already failed, stop installation experiments and follow the agreed recovery process.
Work through the missing control in order
On a standard self-hosted installation, WordPress documents the installation route as Plugins > Add New, with an upload option for a plugin ZIP. If that route is absent, the first useful result is knowing which restriction applies.
- Check the site address. Confirm that this is the intended WordPress dashboard, not a hosting panel, another staging copy or a different website.
- Describe the missing control. No Plugins menu, no Add New button and a failed ZIP upload are different problems. Capture the exact screen and any error without exposing account details.
- Ask an existing authorized administrator to compare access. If the control appears for that person on the same site, investigate your intended capabilities. There is no need to create another privileged account just to make the comparison.
- Check network or managed deployment ownership. On Multisite, ask the network administrator about installation. Where a host or developer manages packages, use that installation process rather than trying another upload route.
For example, an Editor who can publish pages may legitimately lack plugin installation access. The practical request is to have the maintainer install the approved feature and verify it, not automatically change the Editor into an Administrator. If authorized administrators also lack the control, investigate network, hosting and configuration restrictions before changing permissions.
Request the feature, then verify its job
Send a small, specific request: the affected site, missing control or exact error, desired plugin and trusted source, feature it must provide, and any recent account or hosting change. Do not include passwords, recovery codes or customer records in a general enquiry.
| Stage | Completion evidence | Do not accept as a substitute |
|---|---|---|
| Ownership | A named authorized installer and an agreed deployment route | An unexplained new administrator account |
| Preparation | Verified package, compatibility review and a recoverable before state | A promise that any plugin can be installed safely |
| Installation | The expected package/version is present in the intended environment | A visible Add Plugin button alone |
| Acceptance | The requested feature and affected public paths work in approved tests | An active-plugin badge or a healthy homepage alone |
Test a consequential installation on protected staging first. Keep real emails, bookings and payments isolated unless their side effects are explicitly approved. Stop if the feature fails, an important existing path breaks or recovery is unclear. Reverse the scoped change through its owner rather than restoring an old database over newer business data.
Webless can review the installation boundary and scope a repair through existing WordPress development services. For ongoing ownership, the maintenance onboarding checklist helps document access and recovery. Success is an understood, working feature, not a button made visible at any cost.