What Is WordPress? The Complete Guide for 2026

Most explanations of WordPress are a definition, a market-share statistic, a list of famous users, and a paragraph about how it started as a blogging tool. That tells you what WordPress is without telling you anything you can act on.

What people actually need is a map: what the software does, what it costs once the free part ends, how .org and .com differ in ways that matter later, what the block editor changed, and the cases where WordPress is genuinely the wrong answer. That last one is missing from almost every guide, because almost every guide is published by somebody who sells WordPress services. ThemesCraft builds for WordPress, so treat the section on when not to use it as the part where we argue against ourselves, and judge it on that basis.

What WordPress actually is

WordPress is a content management system: PHP application code plus a MySQL or MariaDB database. Your posts and pages live as rows in database tables. Your images live as files on disk. When someone visits a URL, WordPress works out which content that URL refers to, fetches it, hands it to a theme that decides how it looks, and returns HTML.

That separation is the whole idea, and it is why the platform has lasted twenty years. Content is not welded to presentation. You can redesign a site completely without retyping a word, because the words were never in the design.

Three concepts sit on top, and once they click the rest of WordPress makes sense.

Concept	What it controls	Rule of thumb
Themes	Appearance. Layout, typography, colour, templates	One active at a time. Switching changes the look, not the content
Plugins	Behaviour. Adds features WordPress does not ship with	Many at once. Each one is code you are trusting
The block editor	How you compose a page, block by block	Introduced in WordPress 5.0, 2018. Replaced the classic editor

The plugin model is the reason WordPress does everything and also the reason WordPress sites break. Core ships deliberately lean. Contact forms, SEO controls, ecommerce, caching, backups: none are built in. You add them, which means you are running code from a dozen different authors with different standards and different levels of ongoing maintenance.

WordPress.org and WordPress.com: the distinction that costs people money

Two different things share a name. WordPress.org is the free open-source software, maintained by the WordPress project, that you install on hosting you choose. WordPress.com is a commercial hosting product run by Automattic that uses that software and adds plan tiers on top.

The trap is not that one is better. It is that the entire internet of WordPress tutorials assumes .org, so a beginner who signs up at .com follows advice that does not apply, hits a wall where a feature is not available on their tier, and concludes WordPress is broken.

	WordPress.org (self-hosted)	WordPress.com (hosted service)
Software cost	Free	Free tier available, paid plans above it
You also pay for	Hosting and a domain	Nothing else, it is bundled
Install any plugin	Yes, from day one	Only on the higher business-grade plans
Install any theme	Yes, including custom code	Restricted on lower tiers
Edit files and add custom PHP	Yes	Only on plans that allow it
Ads shown on your site	Never, unless you add them	On the free tier, yes
Who handles updates and security	You, or your host	Automattic
Who most tutorials are written for	This one	Not this one

What WordPress actually costs

The software is free. The website is not. This is the section most introductions skip, and it is the one that determines whether the project is viable.

Line item	Typical annual cost	Can you avoid it
Domain name	10 to 20 USD	No, if you want your own address
Shared hosting	50 to 150 USD	No. Something has to serve the site
Managed WordPress hosting	300 to 500 USD and up	Yes, but you inherit the maintenance
Premium theme	0 to 100 USD, often one-off	Yes, thousands of free themes exist
Page builder	0 to 100 USD per year	Yes, the block editor is capable now
Essential plugins	0 to 300 USD per year	Partly. Good free versions exist for most jobs
SSL certificate	0	Included free by every credible host

The honest floor is a domain and shared hosting. Everything above that is a choice. The cost that catches people is not any line in that table but the renewal: introductory hosting prices are frequently a third of the renewal rate, and the discount applies only to the first term.

The block editor, and why older tutorials look wrong

WordPress 5.0 replaced a single rich-text box with a block editor, internally called Gutenberg. Every element is a block: paragraph, image, heading, table, button, gallery. You stack and configure them.

This matters when you are learning, because a large share of WordPress tutorials online predate 2018 and describe an interface you do not have. If a guide tells you to paste HTML into a box marked Text, it was written for the classic editor.

The second phase, full site editing, extended blocks beyond content into the templates themselves: header, footer, archive pages, the lot. Themes that support it are called block themes. Themes built the traditional way, with PHP template files, still work and remain extremely common. Both are valid in 2026, and a beginner does not need to pick a side to get started.

What people build with it

• Business and brochure sites. The default case. Pages, a blog, a contact form. WordPress is comfortably overpowered for this, which is fine.
• Blogs and publications. What it was built for, and still the thing it does with the least friction. Editorial workflow, categories, authors and scheduling are native rather than bolted on.
• Ecommerce, through WooCommerce. Turns WordPress into a store. Strong when you want full control of content and checkout; more maintenance than a hosted platform.
• Membership sites and online courses. Gated content, subscriptions, drip-fed lessons. A mature plugin ecosystem covers this well.
• Directories, listings and catalogues. Custom post types and taxonomies are genuinely good at structured content, and this is where WordPress quietly outperforms simpler site builders.
• Headless front ends. WordPress as the editing interface and REST or GraphQL API only, with a separate framework rendering the site. A real pattern, and more work than it sounds.

When WordPress is the wrong choice

A platform that runs 43% of the web is not universally correct; it is universally available, which is different. Four cases where something else wins.

• A pure ecommerce business with no appetite for maintenance. A hosted platform handles PCI scope, uptime, updates and payments as someone else’s problem. WooCommerce gives more control and hands you the operational burden. If nobody on your team will own updates, that burden becomes an outage.
• A five-page site that will never change. A static site or a simple builder is faster, cheaper and has effectively no attack surface. Installing a database-backed CMS to serve five pages that nobody will edit is work you are volunteering for.
• A genuine web application. Dashboards, real-time features, complex user-specific state. WordPress can be bent into this shape and the result is usually worse than a purpose-built application. The request lifecycle is designed to render pages.
• Nobody is responsible for updates. This is the decisive one. WordPress security incidents overwhelmingly involve outdated plugins rather than core. If no person and no managed host owns patching, the site will eventually be compromised, and no theme choice changes that.

Where it came from, briefly

Matt Mullenweg and Mike Little forked an abandoned blogging tool called b2/cafelog in 2003. It is released under the GPL, which is the fact with lasting consequences: anyone can use, modify and redistribute it, nobody can revoke your licence, and any theme or plugin derived from it inherits the same freedoms. That licence is why an ecosystem of tens of thousands of plugins exists and why your site cannot be taken away by a vendor decision.

Automattic, Mullenweg’s company, runs WordPress.com and employs many contributors, but does not own the open-source project, which is stewarded by the WordPress Foundation. The distinction matters when you are assessing platform risk.

Getting started, honestly

1. Decide .org or .com. If you want any plugin, any theme, or your own code, it is .org. That is most people reading this.
2. Buy a domain and hosting. Almost every host offers one-click WordPress installation. Pay attention to the renewal price, not the headline.
3. Pick a theme and leave it alone for a month. Beginners lose weeks switching themes. A default like Twenty Twenty-Five is genuinely fine while you learn.
4. Install four plugins, not thirty. An SEO plugin, a backup plugin, a security plugin, a form plugin. Add more only when you hit a specific limitation.
5. Set permalinks to Post name under Settings, then Permalinks, before you publish anything. Changing it later breaks every URL you have already published.
6. Publish something. The site teaches you more in a week of use than a month of configuration will.

Step four is where most people go wrong, and our list of essential WordPress plugins is organised around what each one actually does rather than how many you can install. If you are weighing whether the platform will hold up in search, we cover that directly in is WordPress good for SEO, and if you are hiring rather than building, what WordPress development involves sets out scope and realistic costs.

Frequently asked questions