Ipsum: WordPress's New Default Theme for 7.2, Explained (and How to Test It)

WordPress has a new default theme on the way, and for the first time in years it doesn't carry a year in its name. Ipsum is the theme the core team plans to bundle with WordPress 7.2, and it is deliberately plain: a minimal blog theme meant to be a starting point you reshape, not a finished design you inherit. It was announced on the Make WordPress Core blog on September 16, 2026, and the code is already public on GitHub for testing.

This guide covers what Ipsum is, how it got here (it was supposed to be called Twenty Twenty-Seven), what is actually inside the theme files, and how to try it without putting a live site at risk. If you run client sites or a WooCommerce store, the later sections on block theme customizations and core updates matter more than the design details.

TL;DR

• Ipsum is the proposed default theme for WordPress 7.2, which is scheduled for December 8, 2026. It is a block theme aimed at blogging, with as much styling as possible handled through theme.json and Global Styles.
• It replaces the year-based naming tradition. The project started as "Twenty Twenty-Seven," then a more expressive design called Mētis, before the team switched to a simpler blank-canvas approach.
• The current build includes 7 color variations, 5 typography variations, 7 archive layout patterns, sidebar versions of the main templates, and three header styles.
• It requires WordPress 7.1 or later and PHP 7.4 or later. The version number stays at 1.0.0 during development, so a copy you install today will not update itself.
• Test it in WordPress Playground or on a staging site. Don't switch a production site to it before 7.2 ships, and know that any template you edit in the Site Editor stops receiving theme updates.

What is the Ipsum theme?

Ipsum is a WordPress block theme built around writing and publishing posts. The name comes from lorem ipsum, the filler text designers drop into a layout before real content exists. The idea behind the name is the idea behind the theme: it looks finished enough to use as is, but it is meant to be changed as soon as you start adding your own content.

The core team describes it as a blank canvas. In practice that means a quiet layout with a narrow reading column, small typographic details (the announcement mentions dotted underlines meant to look like an editor's pencil marks), and optional pieces like hero sections, headers, and sidebars that stay out of the way until you add them.

It is also the first default theme planned around the goal of shipping with almost no custom CSS. According to the project README, the team wants all theme styles to be set in theme.json and editable through Global Styles in the Site Editor, and plans to work with Gutenberg contributors to build any editor tools needed to make that possible. That goal matters more than it sounds, and we will come back to it.

Why the default theme is no longer called Twenty Twenty-Seven

For more than a decade, WordPress default themes have been named after the year they launch: Twenty Twenty, Twenty Twenty-One, up through Twenty Twenty-Five. The 7.2 theme started out the same way. The team announcement published in April 2026 was titled "Twenty Twenty-Seven," with Henrique Iamarino as lead designer, Maggie Cabrera and Carolina Nymark as co-lead developers, and Juanfra Aldasoro in a new lead mentor role.

The September announcement changed both the name and the direction. The design work first produced a theme called Mētis, aimed at writers, makers, and thinkers, and built to show off what the block editor can do. After a review with Matt Mullenweg, who is also the 7.2 release lead, the team moved to a simpler design that more people could quickly make their own. Mētis continues as a separate theme, but it will not ship with 7.2. The team says it will get its own announcement once it is ready to download.

The naming change is a policy change, not a one-off. Going forward, default themes will have their own names and will change when the design needs to change, not on a yearly schedule. For anyone who builds on default themes, that is a useful signal: don't assume a new default theme will arrive every December.

Ipsum at a glance

The table below summarizes the verifiable facts about the current build. Values marked as development state may change before 7.2 ships.

The "Tested up to" header currently says 7.1, which makes sense for a theme that is being developed ahead of a release that doesn't exist yet. Expect that to change during the 7.2 beta.

What's inside the theme

The announcement post focuses on the design philosophy, so it is worth looking at the actual files to see what you get. Everything below comes from the theme repository as of early October 2026. Because development review has not finished, treat the exact counts as a snapshot.

Style variations: seven color palettes and five type sets

Ipsum ships with two kinds of style variations, which you can switch in Appearance > Editor > Styles.

The color variations are named after times of day: Blue Hour, Sunrise, Morning, High Noon, Golden Hour, Evening, and After Hours. The announcement says these variations recolor the whole page, including images, and that every combination meets WCAG AA contrast requirements. That accessibility claim comes from the theme team; if contrast matters for a client project, check your own color and content combinations with a contrast tool rather than relying on it.

The typography variations swap the type system. There are five: Archivo, Archivo Condensed, Besley, JetBrains Mono, and STIX Two Text. In total the theme bundles seven font families (those five plus Manrope and Inter), all served locally from the theme's assets/fonts folder rather than from a third-party font service. That is good for privacy and for performance, since visitors' browsers don't need to connect to another domain to load fonts.

There is also a block-level style variation called Display, defined in styles/blocks/display.json, for large display text.

Templates and sidebar layouts

The theme includes the standard templates you would expect: index, single, page, archive, search, and 404. What is less common for a default theme is that it also ships sidebar versions of the main ones: Index Sidebar, All Archives Sidebar, Single Posts Sidebar, and Pages Sidebar.

The single post and page sidebar versions are registered as custom templates in theme.json, so you can pick them per post or page from the editor's template panel. The index and archive sidebar versions are registered as template types through a small filter in functions.php. The README lists the sidebar templates as one of the areas where testing would help most right now.

Headers, footers, and the navigation overlay

Template parts cover three header styles (default, collapsed, and sticky), two footers (default and wide), a sidebar, a search bar, and a navigation overlay. The navigation overlay is registered in its own template part area, which is what the core Navigation block uses for its mobile menu.

Patterns for archives and heroes

The pattern set is focused rather than large. There are seven archive layouts for listing posts (Columns, Compact, Full, Minimal, Photographic, Simple, and Standard), two hero patterns (Colophon and Epigraph), and header patterns that match the three header parts. The rest are hidden patterns used internally to build templates.

If you want a blog home page that looks like a magazine grid, start with the Columns or Photographic archive patterns. If you want a simple chronological list, Minimal or Compact will get you there faster than editing a grid down.

The small PHP that is there

The theme's functions.php is short, which fits the minimal-CSS goal. Besides loading the stylesheet and editor styles, it does three things worth knowing about:

• It registers a block bindings source called ipsum/comments-cta. This outputs a link that says "Be the first to comment" when a post has no comments and "Join the conversation" when it does. It is a small, practical example of the Block Bindings API, and a good pattern to copy if you build your own block themes.
• It registers two block styles: an "Evening" style for the Code block, which keeps a dark background under every color variation, and a "Sharp" style for the Site Logo block that removes rounded corners.
• It adds the two sidebar template types mentioned above.

The stylesheet also turns on a crossfade between pages using the CSS View Transitions API, and the motion-based styles are wrapped in a prefers-reduced-motion check, so visitors who ask their system for less motion get a calmer experience.

Why "as little CSS as possible" matters for site owners

It is easy to read the minimal-CSS goal as a developer preference. It actually changes how much of the theme you can customize without code.

In older themes, a lot of the design lived in CSS files. To change a link style or a heading size, you either found the setting in the Customizer (if the theme author added one) or wrote CSS that fought the theme's own rules. In a theme where styling lives in theme.json, those same values show up in the Site Editor's Styles panel. You change them in the interface, WordPress saves your changes to the database, and your changes sit on top of the theme's defaults without needing overrides.

The trade-off is that some visual details are only possible if the block editor has a tool for them. That is why the README talks about working with Gutenberg contributors. Some of what Ipsum wants to do may depend on editor features that are still being built, which is one reason the final 7.2 version could differ from what you can test today.

For agencies, the practical upshot is simple. Ipsum is a good base when the client wants to adjust the look themselves in the Site Editor. It is a weaker base when the project needs heavy custom layout work that the editor's design tools don't cover yet.

When to expect Ipsum: the WordPress 7.2 schedule

WordPress 7.2 is planned as the final major release of 2026. The published schedule on the 7.2 release page is:

Release schedules can move, so check the official 7.2 page before planning client work around these dates.

The window between now and Beta 1 is short, and the team said so directly in the announcement: it is asking for testing now so feedback can still shape the release. What can't be fixed before 7.2 will go into later updates, as with previous default themes.

How to try Ipsum without touching a live site

There are three official ways to try the theme. Pick based on what you want to learn.

Option 1: WordPress Playground (fastest)

The README links to a WordPress Playground blueprint that loads a temporary WordPress install in your browser, installs Ipsum from the GitHub repository, activates it, and imports the demo content. Nothing is installed on any server, and closing the tab throws everything away.

This is the best option for looking at the style variations and patterns. It is not useful for checking how Ipsum works with your own plugins or content.

Option 2: The hosted demo site

The project also runs a demo site with the same content as the screenshots. It's useful for a quick look on a phone, but you can't change anything there.

Option 3: Install it on a staging site

This is the option that tells you something about your own sites. Use a staging copy, not production. On MagicWP's managed WordPress hosting, you can create a one-click staging environment for any site and work on it with SSH and WP-CLI.

Important: Take a backup before changing the active theme, even on staging. MagicWP's backup and restore docs cover on-demand backups and one-click restores. If you later push staging to production, you want a known-good restore point on both sides.

Check the requirements first

Ipsum requires WordPress 7.1 or later and PHP 7.4 or later. Check both from the command line:

wp core version
wp eval 'echo PHP_VERSION . PHP_EOL;'

If the site is on an older WordPress version, update core on staging first and test that change on its own before adding a theme switch on top of it.

Record the current theme and back up

Write down which theme is active now so you can switch back quickly:

wp option get template
wp option get stylesheet
wp db export before-ipsum.sql

If the site uses a child theme, template returns the parent and stylesheet returns the child. You need the stylesheet value to roll back.

Install the theme into the right folder

The README gives two install methods: download the repository as a ZIP, or clone it into wp-content/themes/ipsum. Cloning is the better choice for testing, because it puts the theme in a folder named exactly ipsum and lets you pull new commits later:

cd wp-content/themes
git clone --depth 1 https://github.com/WordPress/ipsum.git ipsum
wp theme activate ipsum
wp theme list --status=active

If you use GitHub's Download ZIP button instead, the folder inside the ZIP is usually named after the repository and branch (for example ipsum-trunk) rather than ipsum. It will still work, but the theme then lives under a different folder name than the copy WordPress will bundle, which can leave you with two Ipsum entries on the Themes screen later. Rename the folder to ipsum before uploading if you go the ZIP route.

Import the demo content (Optional)

To see the theme the way it appears in the screenshots, import the demo content file from the repository's .github folder. Do this on a throwaway staging site, not on a staging copy of a real site, because it adds posts, pages, and media:

wp plugin install wordpress-importer --activate
wp import ipsum-demo-content.xml --authors=create

You can also do this from Tools > Import > WordPress in the dashboard.

What to check once it is active

Spend your time on the things that differ from site to site, because those are what the theme team can't test for you:

• Your real content: long titles, posts without featured images, very long posts, galleries, embeds, and code blocks.
• Comments: threaded replies and the comments call-to-action text.
• Navigation: your actual menu depth on mobile, inside the navigation overlay.
• Plugins that add front-end output: forms, SEO breadcrumbs, related posts, and especially WooCommerce. Ipsum is a blog theme and its theme tags don't claim WooCommerce support, so test store pages carefully before considering it for a shop.
• Each color variation against your images and brand colors.
• Right-to-left languages, if you publish in one. The theme declares RTL support in its tags, which makes it worth testing rather than assuming.

Roll back

Switching back is one command, using the stylesheet value you saved earlier:

wp theme activate <previous-stylesheet>

Switching themes does not delete your posts or pages. What it can affect is anything stored per theme, which is covered in the next section.

Things that catch people out with Ipsum and block themes

Most problems with a new default theme come from how WordPress stores theme changes, not from the theme itself. These are the ones to plan for.

A copy installed from GitHub won't update itself

The README is clear that the theme version stays at 1.0.0 during development and that changes are logged in pull requests, not a changelog. A copy you install today is a snapshot. WordPress won't offer you updates for it from the dashboard. If you cloned the repository, run git pull inside the theme folder to get newer commits. If you uploaded a ZIP, you have to replace the folder by hand.

Once 7.2 is out, use the version that ships with WordPress, and remove any development copy so you aren't comparing against an old build.

Edited templates stop following the theme

This is the big one for any block theme. When you change a template or template part in the Site Editor, WordPress saves your version in the database, and from then on your version wins over the theme's file. If Ipsum later fixes a bug in its single post template, sites where that template was customized won't get the fix.

You can see which templates and parts have been customized:

wp post list --post_type=wp_template,wp_template_part --fields=ID,post_name,post_status

For testing, avoid editing templates on a copy of Ipsum you plan to keep. If you have already customized some, the Site Editor lets you reset a template to the theme's version. Global Styles changes are stored separately (in a wp_global_styles post) and behave the same way: your saved choices override the theme's defaults.

Switching from a classic theme isn't one-to-one

If your site runs a classic theme today, switching to any block theme means widgets, Customizer settings, and some menu locations don't carry over the way they would between two classic themes. Menus can usually be brought into the Navigation block, but widget areas need to be rebuilt as blocks in templates. Budget time for this on any real site, and treat it as a redesign rather than a theme swap.

Default themes and core updates

In the past, when a major WordPress release introduced a new default theme, the core updater copied that theme into wp-content/themes on existing sites during the update, without activating it. If that happens again with 7.2, existing sites will get an inactive Ipsum folder after updating. That is harmless, but if you keep a strict list of installed themes for security reasons, plan to remove it or keep it updated. How 7.2 handles this should be confirmed once the release ships.

Not every site should switch

Ipsum is a strong choice for new blogs, personal sites, and as a clean base for developers learning block themes. It is a weaker choice for an established site that already works well on another theme. A new default theme is not a reason to redesign a site that has no problem to fix.

How to give feedback on Ipsum

The theme is developed in the open on GitHub. Bugs and design feedback go in the repository's issue tracker, and pull requests are preferred when they link to an existing issue. The README specifically asks for testing on the style variations, the archive pattern pack, and the sidebar templates.

You don't have to write code to help. Testing on real content, reporting what breaks on your setup, and checking accessibility are all useful. If you connect your GitHub account to your WordPress.org profile, contributions to the repository can count toward WordPress props.

Frequently Asked Questions

Is Ipsum the official name of the WordPress 7.2 default theme?

Ipsum is the proposed default theme planned to be bundled with WordPress 7.2, and the repository describes it as the default theme that will launch with 7.2. It replaces the earlier working name Twenty Twenty-Seven. Because the theme is still going through development review, details of the design and features can change before the final release on the planned date of December 8, 2026.

What happened to Twenty Twenty-Seven?

Twenty Twenty-Seven was the working name for the 7.2 default theme project when its team was announced in April 2026. The design that came out of that work, called Mētis, was set aside as the bundled theme after a review with Matt Mullenweg, and the team moved to the simpler Ipsum design. Mētis will continue as a separate theme, and WordPress is dropping year-based names for default themes going forward.

Can I use Ipsum on my site right now?

You can install it from GitHub today, but it is a development build and shouldn't run on a production site yet. It requires WordPress 7.1 and PHP 7.4 or later. The version stays at 1.0.0 during development, so you won't get automatic updates for a GitHub copy. Use WordPress Playground or a staging site for testing, then use the bundled version once 7.2 is released.

Is Ipsum a block theme or a classic theme?

Ipsum is a block theme. Its layouts are built from block templates and template parts, and its design is controlled through theme.json, which means you customize it in the Site Editor under Appearance > Editor rather than in the Customizer. The team's stated goal is to keep custom CSS to a minimum so that almost every style can be changed through Global Styles.

Does Ipsum work with WooCommerce?

Ipsum is designed as a blog theme, and its theme tags don't list WooCommerce or e-commerce support. Block themes can still display WooCommerce pages using WooCommerce's own block templates, but how well that looks in Ipsum hasn't been documented by the theme team. If you run a store, test product, cart, and checkout pages on staging before considering it, and expect to adjust templates.

Will Ipsum replace my current theme when I update to WordPress 7.2?

No. Updating WordPress does not change your active theme. Based on how past releases handled new default themes, the update may add Ipsum to your installed themes without activating it, though this should be confirmed when 7.2 ships. Your current theme, content, and settings stay as they are until you switch themes yourself.

What fonts does Ipsum use, and are they loaded from Google?

Ipsum bundles seven font families: Manrope, Inter, Archivo, Archivo Condensed, Besley, STIX Two Text, and JetBrains Mono. They are stored in the theme's own font folder and served from your site, not from Google Fonts or another external service. All of them are licensed under the SIL Open Font License, which allows them to ship with a GPL theme.

How do I switch back if I don't like Ipsum?

Activate your previous theme from Appearance > Themes, or run wp theme activate with your old theme's folder name. Your posts and pages are not affected by switching themes. Template and style customizations you made in Ipsum's Site Editor stay saved in the database but only apply while Ipsum is active, and Customizer settings from a previous classic theme are usually still there when you switch back, though widget placement can need a quick check.

Conclusion

Ipsum is a deliberate reset for WordPress default themes: a minimal block theme with seven color palettes, five type sets, sidebar templates, and a focused pattern set, designed to be reshaped in the Site Editor rather than used as delivered. It also ends the yearly naming tradition, which says a lot about how the project now thinks about default themes.

For most site owners, the right move is to look at Ipsum in Playground now, test it on staging with your real content during the 7.2 beta, and decide after the December release whether it fits. Don't move a production site to a development build, and remember that any template you customize in the Site Editor stops receiving theme fixes.

If you want a safe place to try it, a MagicWP staging site gives you a one-click copy of your site with SSH and WP-CLI access, and on-demand backups so you can roll back if something breaks. Explore MagicWP's WordPress tools to see how staging and backups fit into a testing workflow.