What WordPress Themes Do Famous Brands Use? 50 Sites Revealed

Key Findings

How We Verified These 50 Sites

Two claims get conflated in almost every article on this topic: "this site runs WordPress" and "this site runs theme X". The first is often easy. The second is frequently impossible from the outside. We treated them as separate questions with separate evidence bars.

How the sample was chosen

Every property in the list meets three criteria: broad brand or institutional recognition, coverage across the industries people actually ask about, and an entry in the official WordPress.org Showcase, which is WordPress's own curated collection of sites built on the platform. That gives the WordPress classification a first-party source rather than a secondhand one.

This is a purposeful case study of prominent adopters, not a prevalence survey. Because inclusion required official WordPress evidence, the fact that nearly every site here runs WordPress is by design, not a discovery.

What counts as proof of a theme

The strongest public fingerprint is a stylesheet path that names a theme directory, followed by the header block inside that stylesheet:

WordPress registers every theme through that style.css header, and a child theme's Template: line names its parent directory. When you can read those four fields, you have an answer. Everything below that is inference.

Secondary fingerprints help but prove less: a <meta name="generator" content="WordPress 6.x"> tag, plugin asset paths under /wp-content/plugins/, and REST API routes under /wp-json/. A detected plugin URL is strong evidence. A missing generator tag is very weak negative evidence, because removing it takes one line of code.

Property level, not company level

For Microsoft, Meta, Spotify and PlayStation, the WordPress property is the newsroom or blog, not the storefront, the app, or the console. We classify what we can actually observe. Claiming an entire corporation "runs WordPress" because one high-profile subsite does is the second most common error in these lists.

Where a theme could not be established, the tables below say Not disclosed. That means the evidence did not support a name, not that no theme exists.

Media and Publishing

The publishing tier is where WordPress is least like a "website with a theme installed" and most like a bespoke editorial application.

TechCrunch is the clearest illustration of why the question breaks down. Its documented redesign introduced a semi-decoupled WordPress and React application, on top of which the subscription product was later built. Asking "what theme is this?" describes a small fraction of the system, because WordPress here is a content API inside an application stack rather than a template engine rendering pages.

Pew Research Center is the exception that proves the rule. It is one of only three sites in the entire sample that states plainly, on the record, that it runs a custom block theme. And the description of that theme reads like a product spec rather than a design: blocks for articles, archive filtering, mega menus, newsletter signups, interactive charts and quizzes, with developers extending the WordPress Interactivity API to make them behave.

Technology and Software

Every entry here is a newsroom, developer hub or corporate marketing site. None of them is the company's core product.

Capgemini is worth pausing on. A global consultancy migrating its main corporate site off Drupal and onto WordPress is a procurement decision, not a theme decision. Nobody at that scale evaluates Astra against Divi. They evaluate content models, governance, translation workflows and who is going to maintain the thing for the next eight years.

Entertainment, Gaming and Music

This is the most art-directed group in the sample, and unsurprisingly the least willing to expose anything.

Disney Connect names its design system rather than its theme, and that is the tell. "Aloha" is the component library and design language; the theme is just the WordPress-shaped container that ships it. Once an organisation has a design system with a name, the theme stops being the interesting artefact.

Taylor Swift's site is a useful reminder that "custom" does not have to mean enterprise. Event calendars, tour date feeds, galleries and fan features are exactly the kind of functionality that gets built once for a specific client and never packaged for resale.

Automotive, Finance and Business

Hodge Bank is the most instructive entry in this group. A regulated UK bank chose WordPress for flexibility and scalability, built its site around blocks so that non-technical staff can create and edit pages, and integrated secure account access alongside the public experience. That is a governance decision dressed up as a CMS decision, and the theme name is completely beside the point.

Hospitality, Food and Retail

Noma is the strongest single data point about how these builds get made. The site is credited to Automattic's Special Projects Team - the group inside the company behind WordPress.com that takes on commissioned, high-design client work. There is no theme name because there is no theme product. It is a bespoke digital brand experience that happens to run on WordPress.

If you are looking at The LINE, Relais de Chambord, Holzweiler or Caesarstone hoping to find a hospitality or fashion theme you can buy, the honest answer is that the evidence does not support naming one.

Nonprofits and Advocacy

This group is the most transparent in the entire sample - and it produced two of our three confirmed custom themes.

Food Banks Mississauga is also the single clearest plugin finding in all 50 sites: its official profile names Advanced Custom Fields as part of the content workflow. That is one confirmed plugin across fifty famous brands, which tells you how little these organisations publish about their stacks.

The pattern across the nonprofit group is consistent and worth stealing. Every one of them invests in editor-controlled modularity: pre-styled blocks, reusable layouts and field schemas that let a two-person communications team publish quickly without any single page turning into an unconstrained visual experiment. Flexibility with guardrails, not flexibility instead of them.

Education

Universities expose a different reason the question is malformed. When Georgia State runs 150+ sites on one multisite network, there is no single "Georgia State theme" to find. There is a theme family, a shared component framework, a set of child themes, and department sites that deviate from all of it. Whichever theme you detect on one hostname may be true of that hostname and nothing else.

Harvard Gazette's 33 custom blocks are the more transferable number. That is a newsroom that decided its editorial capability lives in the block library, and treated the theme as the wrapper around it.

Government and Science

The White House is the best longitudinal example in the sample. WordPress has stayed in place across three administrations while the design, content priorities and entire frontend were rebuilt. The 2021 implementation by 10up and Wide Eye Creative used native blocks, custom blocks, block patterns, a deliberately curated block inserter, custom post types and role-based permissions for different editorial teams.

That is the enterprise pattern in one sentence: the CMS outlives the theme. You can replace the entire presentation layer without touching the content model, the editorial workflow, the APIs or the platform underneath.

The Only Three Confirmed Custom Themes

Out of 50 sites, exactly three state on the record that the active implementation is a custom theme.

Read that carefully, because the distinction matters. This is not a finding that only three of the 50 use custom themes. It is a finding that only three of them say so in documentation we could verify. Vox, TIME, Disney, Noma and the White House are almost certainly running equally bespoke presentation layers. "Almost certainly" is a reasonable belief and a bad citation.

Why Big Brands Skip Astra, Divi and Avada

The absence is the story. Not one of these 50 properties could be confirmed running Hello Elementor, Astra, GeneratePress, Divi, Flatsome, Newspaper, Kadence, Avada or Genesis - the products that dominate WordPress theme detection everywhere else.

There are two very different models at work here.

Once you are in the second model, buying a multipurpose theme actively works against you. You would be paying for 2,000 layouts you will never use, inheriting an options framework your editors must be trained around, and coupling your publishing operation to a vendor's release schedule. Enterprises pay engineers to remove that surface area, not to add it.

There is one honest caveat. None of this proves that no starter framework or parent theme sits underneath any of these proprietary builds. It proves that no retail theme is the publicly meaningful technical identity of any of them.

What the Rest of WordPress Actually Runs

Zoom out from the famous tier and the picture inverts completely. Across WordPress as a whole, a handful of recognisable theme products account for an enormous share of detections: Hello Elementor, Astra, GeneratePress, Divi, Flatsome, Newspaper, Kadence, Avada and the Genesis framework sit at the top of every current theme distribution.

We measured this ourselves. In our scan of 50,000 WordPress sites for the most popular WordPress themes report, Hello Elementor led high-traffic sites at 12.8%, with Divi and Astra roughly tied around 6% of all WordPress sites each.

So both things are true at once:

• Most WordPress sites run a theme you can download or buy today
• Most famous WordPress sites do not, and do not consider the theme their technical identity

The gap between those two sentences is the entire answer to the question in the title.

Why Detection Gets Harder at the Top

Automated theme detectors underperform on exactly the sites people most want to investigate. Here is why, and none of these reasons mean "there is no theme".

Compiled assets and CDNs

Enterprise build pipelines compile theme CSS and JavaScript into hashed bundles and serve them from a CDN hostname. The original /wp-content/themes/slug/ directory never appears in the HTML a browser receives.

Decoupled and headless frontends

A React frontend consuming WordPress through the REST API produces almost no conventional theme markup. TechCrunch's semi-decoupled architecture is the documented example in this sample.

Removed fingerprints

The generator meta tag is trivially removable and routinely removed. Its absence tells you nothing about whether a site runs WordPress.

Private internal naming

A style.css header reading Theme Name: brand-platform-v4 is a real, correct answer to "what theme is this?" and completely useless to anyone hoping to install it. There is no product to find.

Multisite variation

On a network like Harvard's or Georgia State's, one hostname is one site among hundreds. Themes and child themes coexist across the network, so a detection on one subdomain does not generalise.

How to Check Any Site Yourself

Every finding above came from signals you can read on any site in about a minute. Here is the sequence we used, in order of effort.

What to Actually Copy From Famous Brands

If you came here hoping to buy the theme Vox uses, the useful takeaway is a different one. The repeatable pattern across all 50 sites has nothing to do with theme selection.

• Treat WordPress as a content platform, not a website. The content model outlives every redesign you will ever do
• Define the design system before the theme. Disney names Aloha, not a theme. Decide what your components are, then build the container
• Encode the system as blocks and patterns. Harvard Gazette's 33 blocks and the Prostate Cancer Foundation's nine standard layouts are the same idea at different scales
• Give editors freedom inside guardrails. A curated block inserter, like the White House's, is a feature, not a restriction
• Scope custom functionality narrowly. Tata Motors ships custom plugins; Food Banks Mississauga uses ACF. Neither built a framework they now have to maintain
• Let the design change without changing platforms. Three administrations, one CMS

For a small site or a growing business, the practical version of this is smaller but identical in shape: pick a lightweight, well-maintained theme, put your identity in a small set of reusable patterns, and keep custom code to the pieces that are genuinely specific to you.

Sources

Every row in the tables above rests on a public document. Where a theme is called custom, that word appears in the source rather than in our inference, which is why only three sites get that label.

Frequently Asked Questions

Conclusion

The most defensible answer to "what WordPress themes do famous brands use?" is that the question stops being useful the more sophisticated the site gets. At the top of the market, the theme is the least interesting file in the repository.

Here is the workflow we would suggest. Confirm the platform first. Read the theme and plugins where they are readable. When they are not, go looking for who built the site rather than what it was built with - the agency write-up will tell you more than any fingerprint. And date-check everything before you repeat it.

Then go and check a site yourself. The most interesting results are rarely the famous ones - they are the mid-sized sites in your own market, which are far more likely to be running something you can actually learn from.