Project Browser

Project Browser lets site builders find and add Drupal modules from inside the admin UI, instead of searching drupal.org in another tab.

Drupal lerenDrupal-woordenlijst Laatst bijgewerkt

Project Browser is a contributed module, drupal/project_browser, that adds a catalog of Drupal projects to the admin interface. It lists drupal.org modules that are compatible with your site, with search, categories and filters, and can also list recipes in your codebase. A site builder no longer has to leave the site and read project pages on drupal.org first.

How Project Browser works in Drupal 11

The module queries the drupal.org API in real time, so the list is current. Its 2.1.5 release (23 September 2026) requires Drupal ^11.2 or ^12 in its core_version_requirement. Its README says it requires no modules outside Drupal core.

After composer require and enabling the module, the screen is at Extend › Browse. Each enabled source gets its own tab there. The route is /admin/modules/browse/{source} and it needs the administer modules permission. The settings form is at /admin/config/development/project_browser, with an Actions tab next to it; both need administer site configuration.

The README lists the screen controls: switch between Recommended and All projects, search, sort, filter by category, and show results as a list or a grid. Each module in the list comes with its Composer command. Other sources can be added by writing a source plugin, according to the project documentation.

Example

A site builder opens Extend › Browse, switches to All projects and searches for "redirect". The result list shows only projects compatible with the site, and the site builder sends the chosen project to the developer who maintains the codebase.

In Drupal CMS, Extend › Recommended (admin/modules/browse/recommended) lists add-ons, and which ones appear depends on the site template. The Drupal CMS Basics project lists Project Browser among its included modules (checked 26 October 2026).

Common mistakes

  • Turning on installs on the live server. The project page says automatic installation is intended for local development environments such as DDEV. On the live site, add modules through Composer and your normal deployment.
  • Combining it with an old Automatic Updates release. The 2.1.5 composer.json declares conflicts with drupal/automatic_updates below version 4 and with drupal/gin below 4.0.6. If you also run Automatic Updates, use version 4 or later.

For marketing and content teams

Project Browser is a site builder tool, not an editor tool: opening it takes the administer modules permission. Use it to discuss options. Browse the Recommended and All views with your developer, then agree which feature to add. Adding a module still changes the code of the live site, so schedule it like any other release.

Sources

Questions about Project Browser

No. On 26 October 2026 its drupal.org page describes it as part of a Drupal core strategic initiative, but it ships as a separate contributed project. You add it with Composer: composer require 'drupal/project_browser:^2.1'.

Release 2.1.5, published on 23 September 2026, works with Drupal ^11.2 and ^12. The 2.0.3 release, published the same day, works with Drupal ^10.4, 11.0 and 11.1. Both are stable releases covered by the security advisory policy.

It can, when the web server user has write access to the project codebase; the project page names this as the condition for automatic installation. Without it, the screen still finds projects and shows the Composer command that a developer can run.

Yes. The project page names three sources, each with its own tab: contributed modules from drupal.org, recipes already in your codebase, and core modules. The core source is disabled by default and can be turned on in the Project Browser settings.

Cite this definition

"Project Browser." DXPR Drupal glossary, https://dxpr.com/hc/documentation/learn-drupal/drupal-glossary/project-browser. Last updated oktober 26, 2026.

Related terms

All Drupal terms from A to Z