If you have spent any time on the internet, you have used WordPress. You just may not have noticed. News sites, small-business homepages, online stores, university blogs, restaurant menus, and personal journals all run on it. As of 8 September 2026, W3Techs reports that WordPress is used by 58.9 percent of websites whose content management system can be identified — about 40.7 percent of all websites on the public web.
That is not a vanity statistic. It means a single open-source project, started by two people who were annoyed that their blogging software had been abandoned, still sits at the center of how millions of people publish online. This article explains what WordPress actually is, how it got here, how the two “WordPresses” differ, what it can and cannot do well, and where it stands in 2026.
The short answer
WordPress is free, open-source software for building and managing websites. It began as a blogging tool. Over more than two decades it grew into a full content management system (CMS). You install it on a web server (or let a host install it for you), then use a browser-based dashboard to write posts, build pages, change the design, and add features.
It is written mainly in PHP and stores content in a MySQL or MariaDB database. The license is GPLv2 or later, which means anyone can run it, study it, change it, and share those changes. That legal foundation is not a footnote. It is why a huge plugin and theme economy exists around it.
There are two products that share the name, and mixing them up is the most common beginner mistake:
- WordPress.org is the free software. You download it and run it on hosting you control. This is what people usually mean by “WordPress.”
- WordPress.com is a commercial hosted service run by Automattic. It uses the same software underneath, but Automattic manages the servers, updates, and many restrictions.
Same engine. Different ownership model.
How it started
The story does not begin with a pitch deck. It begins with a stalled project.
In 2001, French developer Michel Valdrighi released b2/cafelog, a simple PHP blogging tool. By late 2002 he had stepped away. Users were left with software that no longer received updates.
On 24 January 2003, a 19-year-old American blogger named Matt Mullenweg wrote a post called “The Blogging Software Dilemma.” He liked b2 but did not want to keep using something that was effectively dead. He said he was willing to fork it.
The next day, British developer Mike Little commented that he would help. On 1 April 2003 they created a new branch on SourceForge. A friend of Mullenweg’s, Christine Tremoulet, suggested the name WordPress. On 27 May 2003 they released version 0.7. It was small: a basic admin screen, a plain-text editor, no plugin system, no theme system as we know it today.
The official description still matches the original intent: an elegant, well-architected personal publishing system built on PHP and MySQL and licensed under the GPL. WordPress is the official successor of b2/cafelog.
From there the project moved fast:
- 2004: plugins arrived in version 1.2 (“Mingus”).
- 2005: themes and static pages arrived in 1.5 (“Strayhorn”). The same year Matt Mullenweg founded Automattic and launched WordPress.com.
- 2010: version 3.0 (“Thelonious”) added custom post types, better taxonomies, custom menus, and Multisite. That is the moment WordPress stopped being “just a blog platform” in any serious sense.
- 2018: the block editor, known as Gutenberg, shipped in WordPress 5.0 and replaced the old TinyMCE “classic” editor as the default way to write.
- Early 2020s: Full Site Editing brought headers, footers, templates, and global styles into the same block model.
Major releases are traditionally named after jazz musicians. The current line is the 7.x series. WordPress 7.0 (“Armstrong”) arrived in mid-2026 with AI building blocks and a refreshed admin. WordPress 7.1 followed in late August / early September 2026, with responsive block styles, a cleaner media editor, richer Notes, and other editor improvements. As of this writing, 7.1 is the current maintained release.
How WordPress actually works
You do not need to be a developer to use it, but it helps to know the pieces.
A typical WordPress site has:
- Core — the software from WordPress.org.
- A database — posts, pages, users, settings, comments.
- A theme — the design layer: layout, typography, colors, templates.
- Plugins — extra features: SEO, forms, shops, membership, backups, security.
- Uploads — images, PDFs, videos stored in
wp-content.
When someone visits a page, PHP pulls the right content from the database, wraps it in the theme, and sends HTML to the browser. Caching plugins and good hosting sit in front of that process so the site does not rebuild every page from scratch on every visit.
The dashboard (wp-admin) is where you write and manage. The public site is what visitors see. That split is ordinary CMS design, but WordPress made it approachable enough that non-programmers could run serious sites.
The block editor is the modern heart of content work. Instead of one big text box, you stack blocks: paragraph, heading, image, gallery, quote, buttons, columns, and thousands of third-party blocks. Full Site Editing extends that idea to the whole site, so you can change the header without opening a PHP template file. You can still use classic themes and the older editor if you want. Many established sites still do.
WordPress.org versus WordPress.com
This distinction is worth repeating because it changes cost, control, and risk.
WordPress.org (self-hosted) You choose a host, point a domain at it, install WordPress (most hosts do this in one click), and you own the files and database. You can install any theme or plugin. You can sell products, run ads, add custom code, move to another host, or hire any developer. You are also responsible for updates, backups, and security — unless you pay a managed WordPress host to do that for you.
WordPress.com (hosted) You sign up, pick a plan, and Automattic runs the infrastructure. The free plan is limited: WordPress.com subdomain, ads, restricted themes, no custom plugins. Paid plans remove ads, add a custom domain, and — after policy changes in 2026 — open plugin access on paid tiers, with some platform restrictions still in place. Higher plans add SFTP, more storage, WooCommerce features, and better support.
A simple way to decide:
- Hobby blog, almost no technical interest, no plans to monetize heavily → WordPress.com can be fine.
- Business site, store, SEO-focused content site, client work, or anything you expect to grow for years → WordPress.org plus decent hosting is usually the better long-term choice.
The software is the same. The contract is not.
The ecosystem: themes, plugins, and commerce
WordPress would not dominate without the marketplace around it.
The official plugin directory still holds tens of thousands of free plugins — commonly cited in 2026 in the 60,000-plus range, with the wider paid ecosystem pushing the total much higher. Themes in the official directory number in the mid-teens of thousands, though a smaller set of popular themes accounts for most real-world installs.
Common building blocks of a “real” WordPress site:
- SEO: Yoast, Rank Math, AIOSEO and similar tools.
- Page building: native blocks for many sites; Elementor, Bricks, and others for people who want more visual control. Elementor still appears on a large share of WordPress sites in usage surveys.
- Commerce: WooCommerce, which turns WordPress into a store. It remains one of the most important e-commerce platforms on the web.
- Forms, memberships, LMS, forums, bookings: there is almost always a plugin, and often several competing ones.
That abundance is the point and the problem. You can build almost anything. You can also install too much, slow the site down, and create update conflicts.
Who uses WordPress
The range is wider than the “blog software” stereotype suggests:
- Personal blogs and newsletters
- Small and mid-size business sites
- Magazines and newsrooms
- Portfolios and agency sites
- Online stores (especially content-led stores)
- Membership communities and course platforms
- Government, nonprofit, and education sites
- Large publishers that need editorial workflows
Enterprises often run WordPress through managed platforms such as WordPress VIP (Automattic) or other specialist hosts. Developers also use WordPress as a headless CMS, keeping the admin for editors and sending content to a separate front end. That setup can be fast and secure, but it is two systems to maintain, not one.
Strengths that still matter
It is free to start. The software costs nothing. Hosting and a domain are the real baseline costs.
You own the site on self-hosted WordPress. You can export, migrate, and change vendors. Closed builders make that harder.
SEO remains a genuine advantage. Clean URLs, structured content, and mature SEO plugins give editors more control than most all-in-one website builders.
The community is enormous. Twenty-plus years of tutorials, WordCamps, Slack teams, Stack Overflow answers, and local meetups mean most problems have already been solved in public.
It scales in more than one direction. A single blog and a network of sites can run on the same software. Performance depends on hosting, caching, and restraint with plugins, not on WordPress being “only for small sites.”
Customization has a high ceiling. Themes, plugins, hooks, REST API, custom post types, and now block themes give developers room that rigid SaaS builders do not.
The honest downsides
WordPress is popular, so it is attacked. Most breaches come from outdated plugins, weak passwords, cheap hosting, or abandoned themes — not from a mysterious flaw in core that nobody patches. Core updates are frequent. Plugin updates are your job (or your host’s).
Maintenance is real. Core, PHP version, plugins, themes, backups, and malware scans do not manage themselves on a bargain shared host.
Performance is not automatic. A default install on good hosting is fine. A site with a heavy page builder, unoptimized images, and twenty plugins will feel slow. That is a configuration problem more than a brand problem, but it is common.
The learning curve is milder than Drupal and steeper than Wix. You can publish a post in minutes. Building a durable, fast, secure business site still takes judgment.
There is also market context. After years near the mid-40s as a share of all websites, W3Techs and other trackers showed a gradual slide through 2025 and 2026. WordPress is still far ahead of Shopify, Wix, Squarespace, and everyone else, but the era of effortless share growth is over. Hosted builders keep taking simple brochure sites. Some developers prefer static generators or other CMS tools. That does not make WordPress “dying.” It makes it mature.
WordPress in 2026: blocks, collaboration, and AI
The Gutenberg project was planned in phases: easier editing, site customization, collaboration, then multilingual work. By 2026 the block editor and Site Editor are no longer experiments. They are the default path.
WordPress 6.9 introduced the Abilities API — a way for WordPress and plugins to describe what they can do in a form other software, including AI agents, can use. WordPress 7.0 added a provider-agnostic AI client and connectors so sites can talk to models from OpenAI, Anthropic, Google, and others through a shared layer instead of every plugin inventing its own integration. WordPress.com has gone further for its own customers, letting connected AI agents draft posts, update pages, and manage comments. Core WordPress is more cautious: foundations first, then features with user control.
WordPress 7.1 focused on practical editor work: responsive styles per breakpoint without writing CSS, better media editing, richer collaboration notes, and a persistent admin bar across editors. Real-time collaborative editing has been tested in Gutenberg and remains on the roadmap rather than a finished everyday feature for every site.
The direction is clear. WordPress is trying to stay a publishing system people can run themselves, while also becoming a platform that other tools — including AI — can operate against in a standard way.
Who is behind it
This part is messy, and pretending otherwise is how people get confused.
The open-source software is a community project. Contributors include volunteers and employees of many companies. Releases list hundreds of contributors.
The WordPress Foundation holds trademarks and supports the project’s independence in a limited official sense.
Automattic, founded by Matt Mullenweg in 2005, runs WordPress.com, WooCommerce, Jetpack, WordPress VIP, and other products. It has historically contributed a large amount of paid engineering time to core. It is not “the owner of WordPress,” even though Mullenweg is both co-founder of the software and CEO of Automattic. WordPress.org as a website and infrastructure has long been closely associated with Mullenweg personally. Public disputes in recent years — including the conflict with WP Engine — made those overlapping roles more visible and more controversial.
For a site owner, the practical takeaway is simpler than the politics: the GPL software is yours to run. Hosting, plugins, and commercial services are separate choices.
Is WordPress still the right choice?
Choose WordPress if content is central to what you do, you want long-term ownership, you care about SEO, or you expect the site to change shape over years. It is still one of the best tools on earth for blogs, editorial sites, marketing sites that publish often , and WooCommerce stores that need more than a simple product catalog.
Think twice if you need a one-page event site you will throw away, if you want zero maintenance and are happy inside a closed builder, or if your “website” is really an application that happens to have a homepage. In those cases a static site, a hosted builder, or a purpose-built app platform may waste less of your time.
WordPress is not magic. It is a publishing engine with an unusually large spare-parts bin and an unusually large community. Used with some discipline — decent hosting, few well-chosen plugins, regular updates, backups — it remains one of the most practical ways to put a serious website on the internet. That was true in 2005 when it was still mostly blogs. It is still true in 2026, even if the rest of the web has finally started catching up around the edges.