Gin isn't replacing Claro — it's merging with it, and it's messier than the headline
For a year the Drupal world has been saying "Gin is replacing Claro as the admin theme." It's a satisfying headline — the slick, popular contrib admin theme finally becoming the default. The reality that landed in core is messier and, I think, more instructive: it's not a swap, it's a merge, it shipped late and experimental, and there's now an awkward third theme in the mix while the two are reconciled.
What actually shipped
There's a new experimental core theme, literally called Admin, created by merging Gin onto Claro's foundations. It committed to main on 1 March 2026 and to the 11.x branch two days later (issue #3556948, "Merging Gin as Admin theme"). Its status is alpha experimental — not held to core's usual gates, not feature-complete — and Claro remains the default while Admin matures. So if you went looking for "Gin is now my admin theme" in a stock install, you won't find it as the default yet.
Why it's a merge, not a swap
Here's the detail that explains the whole shape of this. Gin was never a from-scratch theme — it was built on top of Claro, extending its templates, CSS, and JS. So "replace Claro with Gin" was never a clean drop-in; the two codebases overlapped heavily and had to be reconciled into one. That's slower and fiddlier than adopting a standalone theme would have been, and it's exactly why the work slipped: the original June 2025 announcement targeted a "core-ready Gin" merged for 11.3 by December 2025, and instead it arrived ~three months late as an experimental theme in March 2026.
Merging two mature, overlapping themes is harder than adopting one. "Gin replaces Claro" was a press release; "reconcile two codebases that share a parent into an experimental third theme" is the engineering, and the engineering is what shipped.
What it means for your sites
Practically, for now:
- Don't switch production to it. It's alpha/experimental, Claro is still the default, and the CSS/class-name untangling from Claro is explicitly deferred. Stay on contrib Gin (or Claro) for real sites.
- gin_toolbar and Gin-dependent contrib are in a transitional spot. The Admin theme supports the legacy Toolbar (one position) until it's removed from core, and the "gin" machine names are being kept in classes/config for now — so the big class-name churn is coming later, not today, but it is coming.
- Timeline: Drupal 12 is scheduled for the week of 7 December 2026. That's the realistic horizon for Admin becoming the default and Claro's eventual removal — but stabilization (#3576488) is still open, so treat "default in Drupal 12" as likely, not guaranteed.
Credit where due: the work is led by Jürgen Haas with Sascha Eggenberger (Gin's maintainer) as technical lead, and committed by Lauri Eskelinen. It reads as largely community-driven — I've seen the "big vendor sponsored Gin into core" framing floated, but I couldn't confirm a specific corporate sponsor, so I won't repeat it as fact.
The honest read
This is good news, delivered realistically. Gin genuinely is a better admin experience than Claro, and folding it into core is the right call. But the tidy "swap" narrative oversold a multi-release migration as a version-bump rebrand. What actually happens when you merge two mature themes is: an interim experimental theme, deferred cleanup, transitional contrib, and a "default" that's a release or two away. If you run Drupal admin daily, the takeaway is simple — nothing changes for you yet, keep using contrib Gin, and watch #3576488 for when Admin is actually ready. The exciting version was true in spirit; the boring version is true in the changelog.