Which Drupal 7 themes have a Drupal 10 or 11 release?

How to read a row

The status column is mechanical, and identical to the one on the module table. For each project we read every published release in drupal.org's feed, take the core_compatibility constraint that ships with it, and ask whether a release exists that runs on Drupal 10 or 11 — preferring a stable release over an alpha, beta, RC or dev snapshot.

• No Drupal 8+ release (9) — Nothing has been published for Drupal 8 or later. The theme ends at Drupal 7; whatever your site looks like has to be rebuilt on something else.
• Stopped at Drupal 8/9 (13) — The port stopped before Drupal 10. Same consequence as the row above — plan a rebuild, not an upgrade.
• Only a pre-release for Drupal 10/11 (4) — There is a Drupal 10 or 11 release, but only an alpha, beta, RC or dev snapshot. Usable, but you are choosing to build your site's appearance on unreleased code.
• Stable release for Drupal 10 (3) — A stable release runs on Drupal 10 but nothing yet declares Drupal 11. Fine for a migration to 10; re-check before targeting 11.
• Stable release for Drupal 11 (12) — A stable release declares Drupal 11 compatibility. The theme exists on the other side — your sub-theme and its templates still have to be rewritten.

Maintenance is the status the maintainers publish on drupal.org; 12 of these 41 projects are unsupported, abandoned or seeking a new maintainer. What to do instead is the only hand-written column on the page: 7 of the 22 themes with no Drupal 10 or 11 release carry a note, because core took the job over — Drupal 10 and 11 ship Olivero as the default front-end theme and Claro as the administration theme, which is what several of the rows here were doing on Drupal 7. The rest carry no note, and that means exactly what it says: we have nothing to tell you beyond the release data.

The 26 that need a decision

Every one is named here, not just the most-used, because this table is short enough to read in full.

• No Drupal 8+ release (9) — rubik, shiny, responsive_bartik, venture_theme, nucleus, simplecorp, framework, lexus_zymphonies_theme, aurora.
• Stopped at Drupal 8/9 (13) — zen, omega, tao, mayo, skeletontheme, nexus, professional_theme, marinelli, corolla, pixture_reloaded, fusion, ember, bluemasters.
• Only a pre-release for Drupal 10/11 (4) — business, danland, zurb_foundation, basic.

What this table is not

• It is not every contributed theme. It is every theme project with reported Drupal 7 usage among the projects whose total reported usage clears 1,000 sites, which is where the crawl of drupal.org's usage index stops. A very small theme can be missing from this page; the scanner reports anything outside the table as "not in this tool's table" rather than guessing at it.
• Your own theme is not here and never will be. Most Drupal 7 sites run a custom sub-theme, and that is the part nobody else can give a verdict on. This page tells you whether its base survived; the scanner counts your own templates and preprocess functions, which is the other half of the number.
• The site counts are a floor, not a census. They come from drupal.org's usage statistics, which only count sites running the core Update Status module and reporting in. The ranking is what the numbers are for, not the absolute figures.
• It is a snapshot, dated 2026-09-29. Releases happen. Re-check anything you are depending on against drupal.org before you commit to a plan.
• A stable Drupal 11 release does not mean the upgrade is easy, and for a theme it means less than it does for a module. The base theme existing is the precondition. Your templates, regions, settings and CSS still have to be rewritten.

Next: what is in your codebase

This table answers the question for a theme you already know you have. Finding out what you have — the custom sub-theme, its .tpl.php files, the preprocess functions, and everything on the module side — is what the free scanner does, offline, in one file with no dependencies.

Get the free scanner

It gives every contributed project it finds a verdict from these tables, flags the ones needing a decision, and links each finding to the matching section of the free Drupal 7 migration kickoff checklist. For modules, see the Drupal 7 module status table.