A free Drupal theme is only free if it is still maintained, still compatible, and structured so you can extend it without forking it. Most of the "top free themes" lists you will find rank on screenshots. That is the wrong axis. Below is the checklist I apply before committing a project to any free theme, followed by how Solo — the theme I build and maintain — measures against it.
Six things to check before you adopt a free Drupal theme
1. Read the core_version_requirement in the theme's .info.yml
Not the project page, not the blog post announcing it — the file. This is the single most reliably out-of-date fact in the Drupal ecosystem, and a theme whose page says "Drupal 10" while its .info.yml already declares ^11 tells you the maintainer ships faster than they update marketing copy, which is the good failure mode. The reverse is the one that costs you a migration.
2. Check whether it is a base theme or a sub-theme
A sub-theme inherits from a parent, so you inherit that parent's release cadence too. A standalone base theme has a shorter dependency chain. Read the base theme key: base theme: false means standalone; a machine name means you now have two projects to track.
3. Count the regions, and check whether one of them is hidden
Region count is the crudest possible proxy for layout freedom, but it is a real constraint: you cannot place a block where there is no region. A hidden region matters more than it sounds — it lets you keep a block configured without rendering it, instead of deleting and rebuilding it.
4. Does it ship a sub-theme starter?
You will eventually need to write CSS or override a template. A theme that ships an empty starter sub-theme has decided how you should extend it; one that does not leaves you to guess, and the usual guess is editing the theme directly, which the next update erases.
5. How much is configurable from the admin, and how much needs code?
Every theme claims to be configurable. The question is which specific things. Colours per region? Layout per content type? Menu behaviour? Ask for the list, then look for those settings in the shipped code.
6. What does the maintainer promise, and what do they not?
Be sceptical of any theme that guarantees WCAG conformance, Section 508 compliance, SEO performance or Core Web Vitals scores. No theme can guarantee those outcomes, because all four depend on your content, your modules and your hosting. A maintainer who says so plainly is telling you something useful about the rest of their claims.
Running these six checks against a shortlist is an afternoon. If you would rather have the shortlist made for you, Drupal theming starts there.
How Solo measures up, counted from the source
Every figure below was read out of the theme's own files rather than its project page. If you want to see the settings screen these numbers describe before reading further, there is a walkthrough of Solo's settings page.
| Check | Solo | Where the figure comes from |
|---|---|---|
| Core compatibility | ^10.1 || ^11 || ^12 | solo.info.yml |
| PHP | ^8.1 | solo.info.yml |
| Base theme | false — standalone, no parent | solo.info.yml |
| Regions | 24 placeable, plus a hidden utility region | the regions: block, counted |
| Sub-theme starter | Yes — solo_subtheme, ships inside the theme | solo_subtheme/solo_subtheme.info.yml |
| Colour controls | 15 colour inputs across 30 configurable areas | the region-attribute map, counted |
| Predefined schemes | 50, grouped into 12 categories | css/predefined/ and the scheme option list, cross-checked |
| Site widths | 8 presets, 800px to 2560px plus 100% | the width option list |
| Breakpoints | 5 selectable site values and 5 menu values: 576, 768, 992, 1200, 1400px | the breakpoint option lists |
Two of those deserve a note. The colour figure is 15 inputs — background, text, headings, link and link-hover, borders, form field background, menu link text and background with their hover states, and button text and background with theirs — applied across 30 areas, which include the page wrapper and the four grouped-region containers as well as the individual regions. And the 50 predefined schemes were counted twice, once by listing the stylesheet files and once by parsing the selector the settings form builds; both give 50, and neither set contains an entry the other is missing.
What Solo does not claim
Solo does not guarantee accessibility conformance, SEO results or performance scores, and the project page has been rewritten specifically to remove those claims. What it ships is semantic markup, skip links, keyboard handling in the menu, and configurable heading levels. Whether the finished site passes an audit depends on the content and modules you put into it, and testing that remains your job or your contractor's.
It also does not require you to write CSS to get a working site — but that is a narrower statement than it sounds, and I have set out exactly where the line falls in what the Drupal admin covers and where code starts.
Common questions
Is a free theme a false economy on a commercial project?
Not inherently. The cost of a theme is never the licence, it is the hours spent bending it to a design. A free theme with the settings you need is cheaper than a paid theme without them. Judge on the checklist above, not on price.
Do I need a sub-theme, or can I use Solo directly?
Use it directly for anything you can configure in the admin. Create a sub-theme the moment you need to own a Twig template, a stylesheet, a script or a preprocess function — that is the boundary, and Solo ships the starter so it is a one-minute decision rather than a project.
What is the risk with a single-maintainer theme?
It is real, and it applies to Solo as much as to anything else on drupal.org. Mitigate it the way you would for any contributed project: check the issue queue is answered, check the release history is recent, and confirm the licence lets you fork it if you have to. Solo is GPL-2.0-or-later, so you can.
Will it survive the jump to Drupal 12?
Solo already declares ^12, which means the maintainer has done the work and tested it. That is a stronger signal than a promise on a project page. Whether your site survives is a separate question that depends on your contributed modules, not your theme.
Next steps
Run the six checks against whatever theme you are considering. If it passes, you have saved yourself a rebuild in eighteen months. If you want to see Solo running on real sites rather than in a demo, the portfolio is the honest version. And if the answer turns out to be that no free theme fits and you need a custom front end built properly on top of one, that is Drupal theming work — tell me the design and I will tell you which base theme gets you there fastest.
