The Best Drupal Modules in 2026 (The Ones We Actually Install)

There are around 50,000 modules on Drupal.org. Most of them you will never touch, and a good number have not seen a commit since Drupal 7. So a list of “the best Drupal modules” is only useful if someone tells you which ones they put their own name on. We build Drupal sites for clients, so this is that list: the modules that go on nearly every project we ship, the ones we reach for in specific cases, and a few popular names we have quietly stopped installing.

If you want the catalog view instead of the opinion, our Drupal modules archive groups them by job. This post is the agency take.

The modules that go on almost every build

These five are close to muscle memory. We install them before we have even decided what the site does, because every Drupal site ends up needing them.

Token

Token gives you placeholder values like [node:title] or [site:name] that other modules read. On its own it does nothing you can see. But Pathauto, Metatag, and half the SEO stack depend on it, so it is the quiet foundation under a lot of configuration. Install it first and stop thinking about it.

Pathauto

Pathauto turns /node/1432 into /services/drupal-support automatically, using patterns you set once per content type. Without it, someone is hand-typing URL aliases, and someone always forgets. For anything that cares about SEO, this is not optional. We cover why in the Drupal SEO guide.

Metatag

Metatag controls your title tags, meta descriptions, Open Graph, and Twitter cards per content type and per node. Drupal core ships almost nothing for this, which surprises people coming from WordPress and Yoast. Metatag is how you close that gap. Pair it with the token patterns above and your meta data writes itself for 90 percent of pages.

Admin Toolbar

Core’s admin menu makes you click into a page to see its children. Admin Toolbar turns the whole thing into dropdowns, so reaching Configuration > Performance is one hover instead of four clicks. It saves a few seconds hundreds of times a day. Editors notice it immediately, which is reason enough.

Paragraphs

Paragraphs lets you build flexible content out of reusable components: a hero, a two-column block, a quote, a gallery. Editors assemble pages from those pieces instead of dumping everything into one body field. It is the single biggest quality-of-life jump for content teams on Drupal, and we model most client sites around it.

The SEO and housekeeping set

Past the core five, these handle the unglamorous work that keeps a site healthy.

Simple XML Sitemap generates the sitemap.xml you hand to Google, with control over which content types and languages get included. Redirect catches old URLs and 301s them to new ones, which matters every single time you rename a page or migrate a site. Pathauto and Redirect together mean you can restructure URLs without bleeding traffic. Webform is the form builder we use for everything from a contact form to a multi-step application, and it has no real competition in the Drupal world.

Content modeling: Paragraphs or Layout Builder?

This is the argument that splits Drupal teams, so here is where we land. Layout Builder is in core and lets editors drag blocks around a real visual canvas. It demos beautifully. In practice, give a non-technical editor a blank canvas and you will get inconsistent pages and broken layouts within a month.

We use Paragraphs for structured content where the design should stay on rails, and Layout Builder only for landing pages where one trained person needs freedom. Most clients are happier with Paragraphs and a tight set of components than with a layout tool that lets them paint outside every line. Your mileage depends on who is editing.

The AI modules everyone is asking about

The fastest-growing corner of the module directory in 2026 is AI. The Drupal AI module (and its provider submodules for OpenAI, Anthropic, and others) can generate alt text, draft meta descriptions, and suggest taxonomy terms during editing. The alt-text automation alone is worth the install for any image-heavy site, since accessibility work is exactly the chore editors skip.

We are more cautious about the content-generation features. Auto-drafted body copy reads like auto-drafted body copy, and it will need the same humanizing edit as anything else. Use the AI modules for the boring metadata tasks, not to write the pages people actually read.

Popular modules we have stopped reaching for

Not every famous module earns its place. Panels was essential for years; Layout Builder now covers most of what it did, and we no longer start projects with it. Features made sense before Configuration Management landed in core, and on a modern Drupal 10 or 11 site it usually adds confusion rather than removing it. And a pile of single-purpose modules that each add one small field setting can almost always be replaced by a few lines in a custom module, which is one fewer thing to keep patched.

What is actually Drupal 11 ready

Drupal 11 shipped and the contributed ecosystem mostly caught up, but not evenly. Everything in our core-five list (Token, Pathauto, Metatag, Admin Toolbar, Paragraphs) has stable Drupal 11 releases, as do Simple XML Sitemap, Redirect, and Webform. Before you install anything off this list or any other, check the release page on Drupal.org for a green “11.x” compatibility flag. A module with only an 8.x-era release and no recent commits is a maintenance risk no matter how good the old reviews are.

How we pick modules for a client

The rule we give clients is simple: every contributed module is code you now have to keep updated and patched. A module that saves an editor ten seconds a day is worth that cost. A module that saves a developer one afternoon, once, usually is not, because you will be applying its security updates for years. Fewer, well-maintained modules beat a long impressive list. That is also why our Drupal services work starts with an audit of what is already installed.

Frequently asked questions

How many Drupal modules is too many?

There is no hard number, but every module is attack surface and update work. We have run lean corporate sites on under 25 contributed modules and complex platforms on over 80. The question is never the count, it is whether each module is maintained and actually used. Audit your enabled list once a year and turn off what you stopped needing.

Are contributed Drupal modules safe to use?

Modules covered by the Drupal Security Team get coordinated security advisories, and that coverage is shown on the project page. Stick to covered modules with recent releases and a real maintainer, keep them updated, and you are in good shape. We go deeper on this in our notes on Drupal security best practices.

Do I still need the Views module?

Views is in core now, so there is nothing to install. You almost certainly use it: any list of content, any filtered grid, any block of recent articles is a View under the hood. It is one of the reasons Drupal handles structured content better than most platforms out of the box.

Paragraphs or Layout Builder for a content site?

For most editorial and corporate sites, Paragraphs with a curated set of components. It keeps pages consistent and editors out of trouble. Reach for Layout Builder when one trained person needs to build free-form landing pages and you can accept the extra training that comes with the freedom.

Want a second opinion on your current module stack, or a build that starts clean? That is the kind of thing our Drupal team does every week. Tell us what the site needs to do and we will tell you what belongs on it.