Storefront Theme Review (2026): Free, Steady and No Longer Growing

Our verdict for a store opening this quarter

Short version first, because store owners have inventory to count. If your shop already runs on Storefront and sells without complaint, keep it, test updates on a staging copy, and ignore the headlines. If you are starting a store from nothing in October 2026, Storefront is no longer the default we would reach for. It works, and it costs nothing. But you would be building on a theme whose own repository limits work to urgent repairs, while WooCommerce's design effort has visibly moved to block themes.

None of that makes Storefront a bad theme. It makes it a finished one. The rest of this review explains what finished means for setup, speed, WooCommerce, phones and the bill, and ends with who should install it anyway. If you would rather see the theme set against a custom build on twenty-two rows, that lives in Storefront vs Next.js.

WooCommerce's own theme, now in caretaker hands

Storefront comes from the WooCommerce team at Automattic. It entered the wordpress.org directory on November 19, 2014, and has passed 9 million downloads since. The directory counts 90,000+ active installs as of our October 2026 check. WooCommerce's Marketplace page shows 30K+ installations, which measures something different, so do not read the gap as a collapse. The theme is free for unlimited sites, and the Marketplace listing includes free updates and support.

The owner has not changed. The attention has. A file named STOREFRONT_STATUS.md still says the theme is in active development, then defines the phrase narrowly: urgent bugs, bugs that hit many stores, compatibility updates and release fixes. Enhancement requests and feature pull requests are mostly closed. About 93 issues and 15 pull requests were open when we looked, and the repository is not archived. The file carries no date, so we cannot say when the narrower scope began.

The version headers read like a postcard from 2024. The README says tested up to WordPress 6.5 and WooCommerce 8.8, style.css says WordPress 6.7, and the current releases are WordPress 7.1.3 and WooCommerce 11.1.2. Nothing breaks on the day a header goes stale. It simply means the version pairing on your server is one WooCommerce has not certified, so your staging copy does the certifying.

Setup takes an afternoon; changing the design takes a developer

Installing Storefront is the easy part. Activate it, and WooCommerce's shop, cart, checkout and account pages already look the way WooCommerce intended. The Customizer handles colors and header options. Two page templates do the structural work: a homepage template, template-homepage.php, built around product sections, and a full-width template for pages that should lose the sidebar. Version 4.6.0 added support for Appearance Tools, which gives classic themes extra design controls inside the block editor.

Past the Customizer, Storefront expects code. Its templates are threaded with action hooks, so a developer moves the search bar, adds a trust badge or reorders the homepage from a child theme's functions.php. That is a gift to a PHP developer and a locked door to an owner. The review summary on WooCommerce's own Marketplace page says as much: it could be better with more controls. A long-standing GitHub request asks for Site Editor control of shop templates, and under the current status file that work is not scheduled.

Page builders: blocks yes, Elementor unstated

Storefront enqueues a gutenberg-blocks.css file and an editor stylesheet, so pages built in the block editor match the front end, and 4.6.2 made the editor respect the browser's default font size. We found no official Storefront statement on Elementor. Nothing stops you installing it, but you would be pairing a theme that rarely changes with a builder that changes often, and nothing we found says anyone tests that pair. The block editor for content and hooks for the shop is the combination with the fewest surprises.

What it costs to own

The theme is $0 as of October 2026, for unlimited sites, with no license key and no renewal date. Storefront has no Pro tier and no pricing page of its own, so the spending happens beside it: WooCommerce extensions for payments, shipping, subscriptions or product add-ons, hosting sized for a store, and developer hours for the child theme. We did not check the status of older paid Storefront extensions, so confirm any you own with its vendor before relying on it.

Storefront scored row by row

No invented numbers here. Each row gets a verdict in words and the reason behind it, drawn from the theme's code, its repository and WooCommerce's own pages as checked in October 2026.

Read down the verdicts and a pattern appears. Every row about the store as it runs today is strong. Every row about the future is soft. That is the whole review in one table, and it is why the answer turns on whether your store already exists.

What a shopper's browser downloads, and what Google sees

Storefront's speed story is short because its file list is short. The theme enqueues style.css, an icons.css file, gutenberg-blocks.css, a navigation script and a homepage script. WooCommerce adds wc-cart-fragments so the header cart can show a current total. Source Sans Pro arrives from fonts.googleapis.com rather than your own domain. The theme's README promises a lean and extensible codebase, and in this case the file list backs the vendor up.

So where does a slow Storefront store come from? Usually from everything around the theme: oversized product photos, a homepage slider, review widgets, a chat bubble and tracking tags from three ad platforms. The theme-level levers are few. Self-host the font, and decide whether a live header cart earns its background request on every content page. The Storefront speed guide walks through both, and our theme speed test method explains why a single PageSpeed run proves very little.

On search, Storefront stays out of the way. It has no SEO panel, so titles, descriptions and redirects come from an SEO plugin, the XML sitemap from WordPress core or that plugin, and product structured data from WooCommerce. That division is healthy: a future theme change will not take your metadata with it. What the theme does control is markup and weight, which matter more to a store's rankings than any theme option. Our guide to themes that suit SEO puts that in context.

The checkout fit no other theme can claim

This is the row where Storefront earns its decade. WooCommerce describes the integration as bespoke, covering WooCommerce itself and its popular extensions, and it shows in use: product grids, single product pages, the cart and the checkout render the way WooCommerce's developers meant. The theme makes no attempt to reinvent the shop, which is the point. Fewer custom shop templates means fewer places for a WooCommerce release to disagree with the theme.

The recent changelog reads like a list of small store embarrassments, repaired. The price-filter slider got the right color. Sale prices reached AAA contrast, which helps shoppers with low vision. Coupon errors got proper styling. And 4.6.2 fixed a query that could make product pages time out with a 504 on WordPress 6.9 when neighboring products shared publish dates and were hidden. That last fix is a fair portrait of the caretaker model: the repair came, but a core release found the fault first.

If you run a shop on it, the companion guide to Storefront with WooCommerce covers settings, hooks and extension templates in depth. When product pages fall apart after an update, start with Storefront WooCommerce layout broken. When orders stop arriving, WooCommerce checkout not working comes first.

Purple, Storefront or a third theme: choosing in October 2026

Here is the decision most readers came for. On September 15, 2026, WooCommerce announced a beta of Purple, published on GitHub in its woo-themes repository and planned for the Theme Directory and the Marketplace. The announcement says nothing about Storefront's future, and we found no WooCommerce statement telling anyone to switch. Its theme-choosing guide from February 2025 does say block themes allow much more customization without code, which shows where the company's thinking sits.

One caution about Purple itself. A beta block theme can change its templates and patterns between releases, and a checkout is the last place you want to absorb that. Install it on a test site and watch. Move a live shop when Purple has a stable release and a few months of fixes behind it, and budget for rebuilding the header, homepage and any hook-based changes, because none of them transfer between themes.

Known Storefront problems, with the pages that fix them

• A header that vanishes or half-draws. A child theme hook that removes more than intended, or a plugin that prints into the same spot, is the usual cause. Work through Storefront header not showing.
• A phone menu that opens to nothing. Storefront registers a separate Handheld Menu location and runs the toggle through its own navigation script, so check the menu assignment and the browser console. Steps are in Storefront mobile menu not working.
• Two scrollbars on a long dropdown. Menus with many sub-items can produce double scroll lines and extra space. It was escalated as GitHub issue 2222, and the answer so far is a CSS workaround, not a release.
• Child theme edits that never appear. Page caches, minifiers and stylesheet load order are the usual suspects: Storefront CSS not updating.
• 504 errors on product pages. The WordPress 6.9 adjacent-product timeout is fixed in 4.6.2. If yours persists after updating, the cause lies elsewhere; see 504 gateway timeout.

When the list grows longer than your patience, our WooCommerce repair team works on live stores, and WordPress theme troubleshooting handles the theme layer on its own. Faults that appear right after an update usually trace to one vendor's release; theme broke after update shows how to find which.

Install it, skip it, or plan past it

For that last group, the theme was never the ceiling. The whole stack is. A Next.js store build puts the catalog on prerendered pages and the checkout in tested code, and Athena CMS gives staff plain product fields, a real preview and built-in e-commerce, so a price change stays a two-minute job without a plugin update in sight. The route out, products and orders included, is mapped in Storefront to Next.js.

Still comparing? Every other review lives in the WordPress themes section, and a free site audit will tell you which column your store belongs in before anyone quotes a redesign.