Most people who use WordPress every day, publishing posts, installing plugins, picking a theme, never think much about where it came from or how it ended up running such a large share of the web. It started as a fork of a smaller blogging tool in 2003, built by two developers who wanted something better than what existed at the time. Two decades later, it’s the software quietly running behind news sites, online stores, personal blogs, and corporate homepages that most visitors never realize are WordPress at all.

Some of what follows is genuinely surprising even to people who’ve used WordPress for years. Some of it is useful context for understanding why WordPress works the way it does. All of it is worth knowing if you’re building on the platform rather than just using it, and a few of these facts directly explain decisions that seem odd until you know the history behind them.

This list runs longer than the usual quick roundup on purpose. Most WordPress trivia lists repeat the same five or six talking points, market share, the plugin count, the age of the software, without touching the parts of WordPress’s structure that actually explain why it has stayed dominant for over two decades rather than losing ground the way most software eventually does. The facts below cover both: the surprising details and the structural reasons behind them.

1. WordPress Predates Facebook and Twitter

WordPress’s first release shipped in 2003, two years before YouTube existed, a year before Facebook launched, and three years before Twitter did. It grew up alongside the early blogging era rather than the social media era, which explains a lot about its architecture: it was built as a publishing tool first, with social and community features added later through plugins rather than baked into the core from day one.

2. Nobody Owns WordPress

WordPress is open-source software released under the GPL license, and no single company owns it. The WordPress Foundation, a non-profit, holds the WordPress trademark specifically to keep it from being controlled or monetized exclusively by any one business, including Automattic, the company most closely associated with WordPress commercially. The software itself is built by a large, distributed community of volunteer contributors, developers, designers, and documentation writers who submit code and get it reviewed and merged through an open process, not by a corporate engineering team executing a roadmap alone.

3. It Runs Well Over Two in Five Websites

According to W3Techs, which tracks web technology usage across the internet, WordPress currently powers roughly 40.7% of all websites, and 58.9% of all websites that use a content management system WordPress can be identified for specifically. That’s not a niche tool anymore; it’s the default choice for a majority of the sites that run on any CMS at all, spanning everything from single-author blogs to major media outlets and e-commerce stores running WooCommerce on top of it.

4. The Plugin Directory Is Enormous

The official WordPress.org plugin directory holds tens of thousands of free plugins, covering everything from SEO and caching to full e-commerce platforms and membership systems, and that count doesn’t even include the large ecosystem of premium plugins sold outside the .org repository. That breadth is a big part of why WordPress dominates the way it does: almost any functionality a site owner wants already exists as a plugin, which means most sites can be built without writing custom code from scratch.

5. It Underpins a Genuinely Large Economy

WordPress itself is free, but the ecosystem around it, hosting companies, theme shops, plugin developers, freelance developers and agencies, page builders, security services, is a substantial commercial industry built entirely on top of open-source software nobody has to pay to use. That’s a somewhat unusual outcome for open-source projects generally: WordPress managed to stay free and community-governed while still supporting a large number of businesses and independent developers earning a living from the surrounding tools and services.

6. Education and Nonprofits Use It Heavily Too

Beyond the commercial world, WordPress is widely used by schools, universities, and nonprofit organizations, partly because the software itself costs nothing and partly because the open-source nature of the project lets students and researchers study, modify, and contribute back to it directly. A number of computer science programs use WordPress core or plugin development as a real-world teaching example precisely because the codebase is public, well-documented, and actively maintained by a visible community rather than hidden inside a private company.

7. HTTPS Went From Rare to Default

In WordPress’s earlier years, running a site over HTTPS required either an expensive certificate or enough technical know-how to configure one, so most WordPress sites, like most of the web, ran unencrypted for years after browsers started warning about it. That changed dramatically once free certificate services like Let’s Encrypt became widely available and most hosting providers started issuing and renewing SSL certificates automatically. HTTPS on a WordPress site went from something a site owner had to actively pursue to something most hosts now enable by default the moment a domain is connected.

8. Translation Is a Core Priority, Not an Afterthought

WordPress core and a large share of its most popular plugins and themes are translated into well over 100 languages through an organized, ongoing community translation effort rather than a one-time localization project. GlotPress, one of WordPress’s own sister projects, is the tool that specifically powers this translation workflow, letting contributors around the world submit and review translations collaboratively. That investment is part of why WordPress’s global usage isn’t concentrated in English-speaking markets the way some competing platforms’ usage is.

9. WordPress Has a Family of Sister Projects

bbPress (forum software), BuddyPress (social networking and community features), and GlotPress (translation management) all grew out of the WordPress project and share its open-source values and, in some cases, parts of its codebase. bbPress and BuddyPress in particular are still actively used today for adding forum and community functionality to a WordPress site, either directly or through newer plugins and platforms that build on the same underlying concepts.

10. WordPress.com and WordPress.org Are Genuinely Different Things

This is one of the most persistent points of confusion for new users, and it’s worth being precise about it. WordPress.org is the home of the open-source software itself, free to download and install on any hosting provider, with full control over plugins, themes, and server configuration. WordPress.com is a separate, commercial hosting service run by Automattic that runs WordPress software on your behalf, with tiered plans that range from a free, limited version to paid plans offering more flexibility. Choosing between them is really a choice between full control with more responsibility (.org) and managed convenience with more restrictions on the free and lower tiers (.com), not a choice between two different pieces of software.

11. Multisite Lets One Install Run Many Sites

A lesser-known built-in feature, WordPress Multisite, lets a single WordPress installation power an entire network of separate websites, each with its own domain or subdomain, its own content, and its own set of enabled plugins and themes, all managed from one central dashboard. Universities running a network of department blogs, media companies running multiple regional editions, and agencies managing several client sites from one backend all rely on this feature, even though most everyday WordPress users never encounter it because it isn’t enabled by default on a standard single-site install.

12. Every Major Release Is Named After a Jazz Musician

WordPress has followed a consistent, slightly whimsical tradition since its earliest days: every major version release gets an internal codename honoring a jazz musician, chosen by whoever is leading that particular release. Version 1.0, released in 2004, was named “Davis” after Miles Davis. It’s a small detail with no functional impact on the software, but it’s stayed consistent across two decades of releases, which says something about how much of WordPress’s culture still carries the personality of the small team that started it, even at its current scale.

13. The Editor Changed Completely in 2018

For most of WordPress’s history, writing a post meant working in a single large text box with formatting buttons on top, essentially a word processor bolted onto a publishing tool. That changed with the introduction of the block editor, known during development as Gutenberg, which restructured content into discrete, individually editable blocks: paragraphs, images, columns, embeds, and eventually far more complex layout elements. It was a genuinely divisive change when it shipped, with a large portion of the existing user base initially preferring the older editor, and WordPress maintained a Classic Editor plugin for years specifically to give sites time to migrate on their own schedule rather than forcing an abrupt switch.

That block-based foundation turned out to be the groundwork for something bigger than just a better writing experience. It eventually extended into Full Site Editing, letting the same block system control headers, footers, and template structure, not just post content, which is the architecture modern WordPress block themes are built on today.

14. WordPress Runs Headless Almost as Easily as It Runs Traditionally

WordPress ships with a built-in REST API that exposes posts, pages, media, and most other content as structured JSON data, which means WordPress doesn’t have to be the thing rendering the actual pages a visitor sees. A growing number of sites use WordPress purely as a content backend, where editors write and manage posts in the familiar WordPress dashboard, while a completely separate frontend, often built with a modern framework rather than PHP templates, fetches that content through the API and renders it however the frontend developer wants. This is exactly the setup this site runs on: WordPress as the editorial backend, a separate frontend handling the actual page rendering. It’s a meaningful departure from WordPress’s traditional all-in-one model, and it’s become common enough that “headless WordPress” is now a well-understood term rather than a niche experiment.

15. Security Updates Roll Out Automatically by Default

Since WordPress 3.7, released in 2013, the software has shipped with automatic background updates for minor releases, meaning security patches and small bug fixes get applied without a site owner needing to manually click “update” or even know a patch happened. Major version updates still require explicit action by default, since those can include changes that affect plugins or themes in ways an automatic silent update shouldn’t risk. That split, automatic for security-critical minor patches, manual for larger version jumps, has meaningfully reduced the number of WordPress sites left running known-vulnerable versions for years after a fix was already available.

16. There’s an Entire Global Conference Circuit Built Around It

WordCamps, community-organized conferences dedicated specifically to WordPress, run in cities all over the world, organized entirely by volunteers rather than a central corporate event team. They range from small regional gatherings with a few dozen attendees to large flagship events, and they’re one of the more visible signs of how much of WordPress’s growth has been driven by an actual community of people who show up in person, not just a userbase interacting anonymously through downloads and support forums. WordCamp Europe and WordCamp US in particular have grown into some of the largest open-source conferences in the world by attendance.

17. A Formal Program Pays Contributors to Work on WordPress Full-Time

Because WordPress is community-built rather than owned by a single company, sustaining that development effort at scale required more than volunteer hours squeezed in around a day job. The Five for the Future initiative asks companies that benefit commercially from WordPress, hosting providers, agencies, plugin businesses, to contribute the equivalent of 5% of their resources back to core development, often in the form of employees whose actual job is contributing to WordPress itself rather than their employer’s commercial product. It’s an unusual funding model for open-source software at this scale, and it’s a meaningful part of why WordPress core development has stayed consistent and well-resourced despite having no single corporate owner footing the bill.

18. Accessibility Is a Stated, Ongoing Commitment

WordPress core development follows accessibility standards intended to keep the software usable for people relying on screen readers, keyboard navigation, and other assistive technology, with an accessibility team that reviews new features specifically for compliance before they ship in core. That doesn’t mean every theme or plugin built on top of WordPress automatically inherits good accessibility, that still depends heavily on individual theme and plugin authors, but it does mean the underlying software and its default themes have had real, sustained attention paid to this rather than treating it as an afterthought bolted on after launch.

19. The Hosting Ecosystem Is Its Own Industry Within an Industry

Because WordPress can run on nearly any standard web host, a huge, competitive hosting industry has grown up specifically around optimizing for it: managed WordPress hosts that handle updates, caching, and security automatically, hosts that specialize in WooCommerce performance at scale, and hosts built around developer workflows with staging environments and git-based deployment. That specialization exists because WordPress’s flexibility, the same install can be a tiny blog or a massive e-commerce store, means “good hosting” means genuinely different things depending on what a specific site needs, and the market has responded with hosts built for each end of that spectrum rather than one-size-fits-all plans.

Why These Details Actually Matter

None of this is trivia for its own sake. Understanding that WordPress is community-governed rather than corporate-owned explains why core updates prioritize backward compatibility so heavily, breaking existing sites at scale would damage trust in a way no single company controls or can unilaterally fix. Understanding the scale of the plugin ecosystem explains why “there’s probably already a plugin for that” is usually true before writing custom code. And understanding the real difference between WordPress.com and WordPress.org saves a lot of frustration for anyone choosing where to start a new site.

WordPress’s dominance isn’t an accident of timing or a network effect nobody can escape. It’s a product of staying open, staying free, and building a plugin and theme ecosystem broad enough that almost any use case, from a personal blog to a large online store to a headless setup like this site runs, has a workable path built on the same core software.

What’s easy to miss from the outside is how much of that stability comes from decisions made deliberately, not by default. Backward compatibility, the automatic security update system, the Five for the Future funding model, the accessibility review process, none of these happened automatically just because WordPress got popular. They were built in response to real problems the project ran into as it scaled, and they’re a large part of why WordPress has stayed the dominant CMS for as long as it has instead of losing ground the way earlier dominant platforms eventually did.

What This Means If You’re Building on WordPress Today

For anyone starting a new WordPress project now, the practical takeaway from all of this isn’t just trivia, it’s a set of defaults worth actually using. Automatic minor updates should stay enabled rather than disabled out of caution, since they’re the main thing keeping most WordPress sites patched against known vulnerabilities without any manual effort. The plugin directory is worth searching thoroughly before writing custom functionality, since the odds that a well-maintained plugin already solves a common problem are genuinely high given the size of the ecosystem. And the REST API is worth knowing about even for a site with no plans to go headless, since it powers a lot of modern WordPress functionality, including the block editor itself, behind the scenes.

None of this requires becoming a WordPress core contributor or attending a WordCamp to benefit from. It just means understanding that the platform underneath a WordPress site is more actively maintained, more broadly supported, and more thoroughly battle-tested than most alternatives, open-source or proprietary, that a new project might otherwise default to without asking why WordPress ended up running so much of the web in the first place.