WordPress.com: find the theme and plugin installation menus

Distinguish a missing menu from a failed installation

You are looking for Add Plugin or Upload Theme, and no button matches a tutorial video. Start by recording what is actually missing. A completely absent menu, a button replaced by a plan offer and a specific plugin marked unsupported are three different situations. They do not call for the same correction.

This guide concerns WordPress.com, the managed hosting service. A custom domain may be hosted there; conversely, a WordPress site may be installed with another provider. Verify the service hosting the site before following instructions specific to its plans. The WordPress name alone does not settle the question.

The desired result is access to the functions intended for your account and site. It is not immediate installation of a component. We will follow two routes: find authorized access in the correct interface, then verify the plan and activation of necessary features. A normal restriction may also lead you to use an already available feature.

Preserve context before changing the site

Record the site address, logged-in account, visible sections and any message text. If consulting a tutorial, note its date and the interface shown. A menu screenshot may help support, provided personal information, other sites and billing details are hidden.

Preserve unsaved content before logging in again. Simply checking menus requires no file or database changes. Before subsequently activating a theme or plugin, identify available backups and rollback options under your plan. A content export is a useful precaution but does not replace a complete backup of all settings and files.

Record the active theme and components already used if installation is genuinely planned. Also retain the reason for the change: form, presentation, store or another specific need. You can then check whether the site already has that function. Do not import a theme demo or deactivate existing tools merely to make a button appear.

Confirm the selected site and invited identity

When several sites appear in your WordPress.com account, open the one whose domain matches the request. Two sites may have the same title, especially after a trial or migration. Compare the domain and dashboard with those specified by the owner. A subscription purchased for another site proves nothing about this site’s permissions.

Next check the account in use. A person may have personal and professional identities. Ask the administrator to confirm which identity received the invitation and what role it grants on this site. Subscribing to blog updates is not an invitation to administer its components.

If you need to switch accounts, save your work and use normal login. A separate browser profile may simplify comparison. Borrow neither a password nor a cookie from another administrator. The expected result is individual access to the correct site; if the account is not intended for this assignment, the owner must decide the appropriate assignment.

Check the active plan without relying on an old threshold

As of November 3, 2026, WordPress.com documentation states that plugin installation and third-party theme uploads are available on all paid plans: Personal, Premium, Business and Commerce. A free site does not have these installation features. Older tutorials systematically reserving these operations for Business therefore do not describe the current rule.

Have the purchaser verify the exact site’s active subscription. Distinguish a hosting plan from a domain, email address or subscription for another site. A domain invoice does not prove an eligible plan is active for your site.

Do not immediately order a higher plan to resolve a missing menu. If the intended plan is already active, continue checking permissions, interface and feature activation. If using a legacy plan or special case, request confirmation from support through your account before deciding on an upgrade.

1. With the purchaser’s account logged in to WordPress.com, hover over its name at the top right, then open My WordPress.com account.
2. Open Billing, then Active upgrades: this list contains current subscriptions purchased by this account.
3. Open the relevant plan and compare its associated site with the intended domain. Do not touch upgrade, renewal or cancellation controls while recording this information.

Have the role confirmed without confusing access and ownership

Themes and plugins normally require an administrator. An editor can manage substantial content without these functions. With the owner or an authorized administrator, open the correct site’s dashboard, then Users. Find the exact person and open their record to read the assigned role. Compare their identity with the one they use to log in.

If installation genuinely belongs to their assignment, the administrator can perform it personally or correct only this role. An Administrator role allows much more than installing a product: reserve it for the person responsible for that assignment.

An administrator does not necessarily own the plan or domain. Their purchases do not include those of another account. Absence of a purchase from their billing therefore does not prove the site has no plan.

Do not change the default role for every new registrant. The site owner remains an administrator; transferring ownership is not part of this repair.

1. The administrator records the exact account’s initial role under Users, then opens its record.
2. They select the authorized role under Role and confirm if prompted. They reopen the record to confirm the saved value.
3. The person reloads the dashboard and checks the expected access without installing an unnecessary component.
4. If permissions were temporary, the administrator restores the initial role after the intervention and checks permissions again.

Separate the catalog, uploads and customization

The theme catalog under Appearance is different from the button that uploads your own archive. A free theme offered in that catalog may be usable even though a free site cannot add a third-party theme. Likewise, seeing a selection of paid themes does not mean every other choice is prohibited.

The Site Editor for a block theme modifies templates and styles. A classic theme organizes customization differently. A screen expected by a tutorial may therefore be absent because of the theme type. Do not install another plugin to artificially recreate an interface that is not your theme’s.

Define the exact operation: change themes within the catalog, upload a file, add a plugin or modify an existing presentation. For a color, menu or form, first look for the existing tool. The correct result may be a saved customization using the site’s own tools, with no new installation. If you need a particular third-party product, continue only with its identified prerequisites.

For plugins, also distinguish the first Marketplace tab from the whole catalog. In WP Admin, Plugins > Add Plugin initially opens premium products. Featured, Popular, Recommended and Favorites correspond to the WordPress.org directory. Their labels may be translated. Paid offers in Marketplace do not mean you must buy a plugin to use a free function.

Approach 1: find the entry from the correct site’s dashboard

This approach applies when the account and role are correct but you cannot find the screen shown in a tutorial. Use the English labels below as reference points if your interface translation differs.

WordPress.com offers Classic and Default styles, which organize the same authorized functions differently. The WP Admin link opens classic administration. The site address followed by /wp-admin is also a documented access route; it does not unlock a function excluded from the plan.

You do not need to change the global style for this check: that setting affects all site users. If the correct section remains absent with an authorized account, continue to checking the plan and its activation.

If a style change is actually agreed with affected users, the route is Settings, General, then Admin Interface Style. Record Classic style or Default style, select the other choice and use Save Changes. The setting affects the site and its users. Check the desired screen; to roll back, restore the initial choice in the same place and save. This change grants no additional capability.

1. Open the WordPress.com hosting dashboard at my.wordpress.com and locate the site by domain.
2. Hover over its row and click the WP Admin link. Verify the administrative domain belongs to the expected site.
3. For a plugin, open Plugins > Add Plugin. For a theme, open Appearance > Themes. Expand the menu or widen the window if necessary.
4. If the desired button appears, stop menu diagnosis. Prepare the intended installation separately; its appearance requires no activation test.

Approach 2: confirm eligibility and feature activation

If the site is free, first check whether its built-in tools meet the need. A paid upgrade to install a third-party product is a separate decision based on usefulness and accepted terms; diagnosis requires no purchase. If an eligible plan is already paid, do not order it again.

For a newly subscribed Personal, Premium or Business plan, initial hosting-feature activation may still be necessary. Commerce activates automatically. If you genuinely planned a compatible plugin, open Plugins in the correct site’s dashboard, find that product and use Install and activate when offered. Read its effects before proceeding: this installs and activates, rather than simply checking a menu. If no component is needed and the site has Business, use the backup route described next. For other cases, have service status confirmed instead of choosing a random product.

Wait for completion, then reopen the list and expected menu. Documentation warns of a possible change to the default technical address and the need for an active certificate to install. Do not change DNS in response to this transition.

This hosting activation is an initial service operation. Subsequently deactivating the added plugin does not restore the site’s previous hosting state. If blocked, retain the message and have the state checked before another attempt. For the component itself, use its prepared deactivation if necessary, without canceling the plan as an attempted rollback.

On Business, activate the service through backups

This variant is for the administrator of a site whose Business plan is already paid. It triggers hosting features through the included backup service without installing a third-party plugin for a test. It does not apply to Personal or Premium; Commerce is already activated automatically.

This remains an initial service activation. The route must not lead you to order VaultPress or another plan. If a purchase is offered instead of the described button, return to verifying the site and subscription.

1. In the site dashboard, open Jetpack > Backup.
2. If Activate Jetpack VaultPress Backup now is offered for your included plan, use it and wait for activation to finish.
3. If a backup with Restore is already visible, backups are active: do not launch a restoration to check. Then reopen the plugin or theme screen. If the button remains absent, report this state to support.

Once access returns, install only the intended plugin

In WP Admin, the documented route is Plugins, then Add Plugin. Search the exact name and check the author before choosing a result. If you have an official archive, use the offered upload function and select the plugin ZIP file. An archive from an unknown source must not be a troubleshooting test.

Read the button before clicking: depending on the interface, installation and activation may be separate or combined. Activation executes the component and may change site behavior. Do not assume an upload will remain inactive. Prepare settings, possible effects and rollback before proceeding on a live site.

The restored menu proves only that you reached the correct screen. Then verify the desired function in a low-stakes case without activating several new components together. If one product is refused or the archive is declared invalid, retain the message and address that specific problem. Retrying through another channel does not repair a compatibility restriction.

For a theme, prepare the preview before activation

Under Appearance, open the theme screen and then Add Theme or Install New Theme, depending on the interface. For a theme purchased elsewhere, upload expects an installable theme archive. The full commercial package may contain documentation and several files; do not upload the entire package as though it were necessarily the theme. Then use Upload Theme, Choose File and Install Now. The Activate button subsequently applies the theme to the site: do not use it before preparing that change.

The catalog, upload and activation remain separate operations. Use the preview with your content when offered. For an uploaded theme, preview options vary: a test copy is preferable if presentation or functions depend heavily on the current theme. Absence of a preview identical to the catalog’s does not mean the upload menu has disappeared.

Record the active theme and settings before applying the replacement. Then check the home page, a page, navigation and important mobile elements. Do not automatically import demo content to resolve a presentation difference. If the result is unsuitable, reactivate the previous theme and separately examine changed settings or added content.

Recognize an unsupported plugin

A particular plugin may show an unsupported notice while the rest of the catalog works. WordPress.com maintains a list of components incompatible with its environment. This block proves neither a wrong password nor absence of the paid plan. Record the exact product name, version and associated message.

Some tools overlap functions already supplied by the platform or operate on technical layers it administers. Consult the current explanation and ask which solution is intended for the need. A similar built-in function may suffice, but verify its actual capabilities before treating the replacement as equivalent.

Directly uploading the ZIP of a prohibited component does not authorize activation. Do not rename files or modify code to conceal its identity. If the platform keeps it disabled, request a compatible option. A component that activates and then causes a failure is another case: investigate the conflict and prepare rollback without multiplying installations.

If site status seems inconsistent, have the service checked

A paid site still being prepared, interrupted activation or persistent message may require a platform-side check. Keep the time, message and stage reached. Compare with reopening the same screen before retrying. Avoid repeated clicks when the service says it is already processing the request.

Do not assume SFTP access or database manipulation will repair the situation. These access methods are not supplied identically across all plans and do not replace state managed by WordPress.com. Support must confirm consistency between site, plan and activated features before technical changes.

You can compare display in another browser profile after saving work. If only one browser fails, record differences before deleting data. If all authorized accounts encounter the same block, report that observation to support. Do not collectively deactivate existing plugins to explain an initial installation feature that was never made available.

If the site is self-hosted or multisite, change diagnosis

If the site turns out to be hosted elsewhere, WordPress.com plans do not explain its menus. Examine account capabilities and hosting policy with the administrator. Configuration may prohibit file modifications or reserve deployments for a technical team. An absent button may be an intentional operational choice.

In a multisite network, a site administrator does not automatically have super-administrator powers. New theme and plugin installation is normally managed at network level. The administrator can then make necessary items available to the site under the intended rules. Buying a WordPress.com plan does not change these permissions on an independent installation.

Do not force a screen to load by copying a tutorial address or remove a configuration constant without knowing its purpose. Ask which installation procedure is authorized for this site. If it goes through the maintainer, prepare the component name and need, then let them verify compatibility, backup and impact on other sites.

Validate access and prepare a proportionate rollback

Reopen the dashboard with the normally intended account. Verify the correct site is selected and the necessary action appears. Installing an unnecessary component is not essential to confirm this troubleshooting stage. If installation was genuinely planned, proceed with one item and verify its result before any other change.

After activation, check a public page, editor and affected function. For a theme, also check navigation and important templates. For a tool sending email or triggering commercial operations, prepare tests avoiding unintended real messages or transactions. Do not confuse a button appearing with the product working correctly.

If the change worsens the site, return to the previous theme or deactivate the new component under the prepared plan. Deactivation does not necessarily undo data or settings it created. Use restoration only after assessing its effect on recent content. Also restore interface style and temporary roles when those changes are no longer needed.

Prepare a support request that identifies the right check

In your WordPress.com dashboard help center, specify the affected site, confirmed plan, account and role, interface used and desired action. Attach a sanitized screenshot of the missing menu or exact rejection. Say whether another administrator sees the same issue. These details distinguish individual permissions from site state.

Explain what was already checked without claiming changes that were not made: purchases viewed by their owner, selected site checked, WP Admin opened or activation attempted. Do not send passwords, cookies, verification codes or complete invoices in a public forum. Any supporting evidence must use the requested secure channel.

Finally retain the established cause, correction and plan-verification date. Document who owns the site, plan and domain, and who is authorized to install components. For the next tutorial, first compare its environment and date: this avoids searching again for buttons belonging to another interface or outdated commercial rules.

Check whether menus follow the role on a copy

Open the same site in two browser profiles with two authorized test accounts. Compare an Editor account and an Administrator account without changing plans or installing a component. Separately record access to the plugin catalog, ZIP upload button and add-theme button. A visible catalog can coexist with an unavailable button.

Run commands from the copy’s directory. On a single WordPress installation with standard roles, the first account returns two denials and the second two authorizations. The commands read permissions. On WordPress.com, verify the plan and available dashboard features. In multisite, have network permissions confirmed.

1. On WordPress.com, ask the owner to verify both accounts open the same domain and the plan belongs to that site. Record visible sections in each profile.
2. If the menu is missing only for the Editor, have the responsible administrator perform installation. If both accounts show a plan or activation offer, record the exact text and check the site’s purchase before changing anything.
3. If you have a self-hosted copy with WP-CLI, compare core capabilities with both test accounts. Replace editeur-copie and admin-copie with their local usernames.

wp --user=editeur-copie eval 'printf("Extensions : %s / Thèmes : %s\n", current_user_can("install_plugins") ? "oui" : "non", current_user_can("install_themes") ? "oui" : "non");'
wp --user=admin-copie eval 'printf("Extensions : %s / Thèmes : %s\n", current_user_can("install_plugins") ? "oui" : "non", current_user_can("install_themes") ? "oui" : "non");'

Distinguish a free plugin from installation eligibility

The component’s price and hosting price are separate questions. A plugin distributed free on WordPress.org may require a WordPress.com plan allowing installation. Conversely, paying for a plan does not make every plugin’s commercial features free. Before purchasing, identify the exact required function and check what its free version actually includes.

For a simple need, start with blocks and features already present in your editor. For a third-party component, consult its official listing: author, compatibility, free features and any external services. A free connector may still require a subscription to the service it connects to. The installation button also does not guarantee that external service is available in your country or for your use.

WordPress.com documentation currently confirms plugin installation on all paid plans. If your eligible plan is already active and access remains absent, retain the guide’s role and activation evidence; purchasing a second plan is not a technical test.

The expected result before spending is a simple record: need, possible built-in solution, intended plugin, included features and any external cost. If this check reveals no installation need, keep the current configuration: no change or plan cancellation is required.