Twenty Twenty-Five Theme Review (2026): The Free Default, Judged Like a Purchase

The short verdict, before the long one

Twenty Twenty-Five is the theme WordPress installs for you, and it deserves more credit than defaults usually get. It shipped with WordPress 6.7, the Rollins release, on November 12, 2024, and reached version 1.5 on May 20, 2026. Wordpress.org counts more than 1,000,000 active installs. The price is $0 under GPLv2 or later, on as many sites as you like, with no license key and no upgrade screen waiting behind the dashboard.

Its job is to show off WordPress's own design tools, and it does that job well. It does not try to run a store, host a page builder or sell you a Pro add-on, and it never pretends otherwise. Read the scorecard as a summary of fit, not a grade. A verdict of "thin" is a warning only if your site needs the thing in that row.

The rest of this review explains each row. If you came for speed numbers, the Twenty Twenty-Five speed guide shows how to measure your own site instead of trusting a demo, ours included. Every other theme we have tested this way sits in the WordPress theme reviews section.

Who answers for a theme that nobody sells

A review of a commercial theme starts with the company, because the company decides the price, the roadmap and how long your license stays useful. Here there is no company. Twenty Twenty-Five is maintained by the WordPress project and published in the wordpress.org directory under the slug twentytwentyfive. Nobody can buy it, raise its price or move it to a yearly subscription. In 2026 that is worth something: Kadence was folded into its parent company's new plans this year, and its customers learned what a pricing overhaul means at renewal time.

The trade is support. There is no ticket desk, only the theme's forum on wordpress.org, where volunteers and other owners answer when they can. Some threads wait. A report of long titles overlapping on narrow screens had no reply when we checked. Releases have been steady: 1.1 in February 2025, 1.2 in April, 1.3 in July, 1.4 in December, 1.5 in May 2026. The readme still says it is tested up to WordPress 7.0 while WordPress sits at 7.1.3, and as of October 2026 no newer default theme has appeared in the directory.

Setting it up: nine looks, 98 pattern files, no settings page

There is no Customizer panel and no Theme Options screen. Everything happens in Appearance, then Editor: Styles, Navigation, Pages, Templates and Patterns. The nine style variations are Default, Morning, Noon, Afternoon, Evening, Dusk, Twilight, Sunrise and Midnight, and each one's palette and font pair is also offered on its own, so a site can wear the Dusk colors with the default type. Text styles named Display, Subtitle and Annotation handle the small typographic jobs, and section styles recolor a whole group of blocks at once.

The documentation promises more than 70 patterns. The 1.5 package actually holds 98 pattern files, 28 of them template patterns and 5 hidden, including full landing pages. Alternate blog designs (Personal, Text-Only, Photo, News and a vertical header layout) are swapped in from the Design panel of a template. For a writer or a photographer, that is a finished site waiting for words.

A sensible first afternoon

1. 1.Choose a style variation before writing anything, because it changes color and type on every page at once.
2. 2.Open the header template part and decide how the Navigation block should behave on phones, before a visitor decides for you.
3. 3.Build the home page from a full-page pattern rather than an empty canvas, then replace the words and images.
4. 4.Pick one blog design in the template's Design panel and leave the other templates alone until there is a reason to touch them.
5. 5.Keep a short log of every Site Editor change, since those edits are stored in the database rather than in theme files.

Builder fit is simple to state. The theme was built for the Site Editor, Styles, Templates, Patterns and the Zoom Out view that arrived in WordPress 6.7. There is no official statement about Elementor or any other builder. You can install one on top, but you would be paying a builder to ignore the theme's best work. If drag-and-drop is the requirement, choose a theme made for it, such as Hello Elementor, which exists to stay out of a builder's way, and read the Elementor theme conflict guide before mixing tools.

Speed and search: what theme.json does for you

Most of the design lives in theme.json, which WordPress turns into styles itself. The theme's own style.min.css is small and registered so that WordPress can print it inline instead of making the browser fetch another file. Fonts are local .woff2 files: Manrope and Fira Code in the default style, with Beiruti, Fira Sans, Literata, Platypi, Roboto Slab, Vollkorn and Ysabeau Office tucked into the variations. Nothing calls out to Google's font servers unless you add something that does.

Notice what is missing: speed claims. The WordPress project makes no performance promises for this theme, which is honest and also means the only number that matters is your own. What slows a Twenty Twenty-Five site is rarely the theme. It is the 3,000-pixel photo dropped into a hero pattern, the video embed above the fold, and the plugins that load their scripts on every page. The slow LCP guide covers the first, and our list of lightweight WordPress themes shows where this one sits among its peers.

Search: clean markup, missing fields

Block markup is plain, readable HTML, and WordPress core already publishes an XML sitemap. That is a fair start. What core does not give you is a field for a meta description, a redirect manager or structured data beyond the basics, so nearly every business install adds an SEO plugin. The theme neither helps nor hinders that choice. Our roundup of themes that help SEO explains why a fast, plain theme matters more to rankings than any feature list.

Can it run a shop? Barely, and on purpose

Open the theme's templates folder and the scope is clear: 404, archive, home, index, page-no-title, page, search and single. There is no product template, no cart and no checkout. WooCommerce brings its own block templates for block themes, so a store will work, but its pages will look like WooCommerce's defaults until someone rebuilds them in the Site Editor. The theme's contribution is a Shop homepage pattern and a product grid pattern with a call to action.

That is enough for a band selling shirts, a nonprofit taking a few orders or a writer selling a book. It is not enough for a store that is the business. Those owners should look at themes built for selling: Storefront, which is free and made by WooCommerce but now mostly limited to critical fixes; Ollie, a block theme with WooCommerce templates whose paid plans start at $89 a year as of October 2026; or WoodMart, which builds the store features in. If shop pages already look broken, start with WooCommerce layout problems.

The header, the hamburger and the phone in your pocket

The header template part inserts a pattern called twentytwentyfive/header, which holds the core Navigation block with its own overlay background and text colors. One setting controls phones: the Navigation block's Overlay Menu, with the choices Off, Mobile and Always. Left as shipped, the menu collapses to a hamburger on small screens even when it holds a single link, which surprises owners who expected two words across the top.

The fix takes a minute: open the header template part in the Site Editor, select the Navigation block and change Overlay Menu to Off. The step-by-step version, with the other causes of a dead menu, is in Twenty Twenty-Five mobile menu not working. Alternate header patterns (centered, columns, large title and a vertical header) swap in the same way. If a header disappears from one template after an edit, the missing header guide explains how it happened.

Then test on a real phone, not only a narrowed browser. Long page and post titles have been reported overlapping instead of wrapping on narrow screens, and it is the sort of flaw a desktop preview hides. Our guide to mobile speed on WordPress themes lists what else to check while you are holding the phone.

Four forum complaints, ranked by how likely they are to reach you

The theme's support forum is quieter than a commercial theme's, and its recurring threads say more about block themes than about this code. In the order a new owner tends to meet them:

1. 1.The phone hamburger. Covered above, and the one you meet on launch day.
2. 2.Nowhere obvious for custom CSS. Owners returning from classic themes look for style.css and find theme.json and the Styles panel instead. Twenty Twenty-Five CSS not updating sorts out which layer wins.
3. 3.Fonts that refuse to appear. Type can be set in theme.json, in a style variation and through the Font Library, so there are three places to look. The checks are in Twenty Twenty-Five fonts not loading.
4. 4.Excerpts that ignore you. A forum thread reports the Excerpt block overriding hand-written excerpts, which matters on archive pages where those summaries do the selling.

One habit prevents most of the pain. Site Editor changes are saved as database records that override the theme's files, so a template edited on the live site is invisible to anyone reading the theme folder. Write down what you changed, and export templates before switching themes. When the trouble goes deeper than a setting, the WordPress troubleshooting library covers the platform-wide failures.

The theme is free. The hour you spend hunting for the setting that hides the hamburger is not.

Install it, or keep shopping

Against its neighbors: Twenty Twenty-Four, the previous default, has fewer style variations and fewer patterns but the same editing model. Ollie is the closest commercial block theme, with store templates and a small two-person team behind it. GeneratePress suits builders who prefer a classic theme with hooks. Our fastest WordPress themes list compares the speed approach of each.

When the free theme stops being the cheap option

Twenty Twenty-Five removes the vendor from the equation, which makes its limits easy to see: they belong to WordPress. Business features still arrive as plugins from different companies, each updating on its own schedule and each adding code to pages that never use it. For a blog that rarely matters. For a site that must win calls from paid ads, publish hundreds of service pages from data or run member areas, it decides the outcome. Twenty Twenty-Five vs Next.js runs that comparison row by row.

If you do move, this is one of the easiest themes to leave, because block markup is close to plain HTML. Moving Twenty Twenty-Five to Next.js explains how Site Editor changes are pulled out of the database. Owners land in Athena CMS, where pages are plain fields with a real preview, every version is kept, and agents such as Calliope (articles) and Iris (search titles and social cards) draft the chores for approval. If you want to stay and polish instead, our theme customization service works inside the Site Editor, and a free site audit tells you which path is cheaper.