WordPress started as a simple publishing tool in 2003 and grew into the most widely used content management system on the web. This overview covers the latest version, how the platform evolved release by release, and the traditions behind it.
What Is the Latest WordPress Version?
The current stable release is WordPress 7.0.2, published on 17 July 2026, per the official release archive. It is a maintenance release in the 7.0 line, which began with WordPress 7.0 “Armstrong” on 20 May 2026. Only the most recent release in the 7.0 series is actively maintained, so 7.0.2 is the version you should be running. If keeping up with that is not a job you want, managed WordPress hosting applies minor releases for you and stages the major ones.
Version 7.0 is the first new major number since 6.0 arrived in 2022, and it is a genuine break rather than a numbering exercise. If you are still on a 6.x release, this is the upgrade worth planning properly.
Release Date
WordPress 7.0 “Armstrong” was released on 20 May 2026, named after Louis Armstrong. Point releases 7.0.1 and 7.0.2 followed on 9 and 17 July 2026. The WordPress release announcements carry the full notes.
Key Features
- AI abilities hub: AI features are surfaced directly in the site and managed from one central place, building on the Abilities API introduced in 6.9.
- A redesigned admin: a new admin theme applied across the dashboard, the first substantial visual overhaul in years.
- New blocks and design tools: further additions to the block library and the design controls around it.
- An expanded developer toolbox: more extension points for customisation.
Compatibility
Check your host’s PHP version before upgrading, because a major release is exactly where an old theme or plugin will show its age. On managed WordPress hosting you can switch PHP versions per site and test on staging first, which is the difference between a controlled upgrade and a broken afternoon.
Significance
7.0 marks the point where AI stopped being something you bolted on with a plugin and became part of the platform. Combined with the block-level collaboration added in 6.9, WordPress in 2026 is a noticeably different editing experience from the 6.6 release most guides still describe.
The Origin of WordPress
WordPress began as a simple content publishing solution and evolved into the most widely used CMS.
History and Development
- Birth of WordPress: it began in May 2003 when Matt Mullenweg and Mike Little forked code from b2/cafelog.
- Vision: they created an open-source CMS focused on ease of use and flexibility.
Why WordPress?
The name “WordPress” was suggested by Christine Tremoulet, reflecting the platform’s connection to press and blogging.
Initial Goals
WordPress aimed to provide an elegant, user-friendly and open-source content publishing solution.
Version 0.7
Released in May 2003, the first version introduced a basic admin interface, templates and XHTML compliance.
Evolution of WordPress Versions: Major Milestones
WordPress evolved from a simple blogging platform into a full-featured content management system. Key versions shaped its functionality, user experience and flexibility.
WordPress 1.x Series (2004 to 2005)
WordPress 1.0 “Miles” (January 2004)
This version introduced permalinks for cleaner, SEO-friendly URLs. It also added multiple categories for better content organisation and provided migration tools for users switching from other platforms.
WordPress 1.2 “Mingus” (May 2004)
The plugin architecture made WordPress highly extensible, letting developers add functionality without changing the core software. This was transformative for expanding what WordPress could do.
WordPress 2.x Series (2005 to 2009)
WordPress 2.0 “Duke” (December 2005)
This version added the visual editor (TinyMCE), which simplified content editing with a WYSIWYG interface. It also introduced the Akismet anti-spam plugin for built-in protection against comment spam.
WordPress 2.7 “Coltrane” (December 2008)
A major overhaul of the admin interface brought a new, more intuitive design. This version also introduced automatic updates, streamlining maintenance.
WordPress 3.x Series (2010 to 2014)
WordPress 3.0 “Thelonious” (June 2010)
A landmark release that introduced custom post types, letting WordPress handle content formats beyond posts and pages. It merged with WordPress MU to enable multisite functionality, and default themes like Twenty Ten began the yearly theme tradition.
WordPress 4.x Series (2014 to 2018)
The 4.x series refined WordPress with a focus on user experience and media management, benefiting developers and content creators alike.
WordPress 4.0 “Benny” (September 2014)
This version improved the media library, making file management and uploads easier, and introduced embed previews so users could see rich media like videos and tweets directly in the editor before publishing.
WordPress 4.9 “Tipton” (November 2017)
This release let users draft and schedule changes in the customizer, giving more control when making design changes and allowing them to preview and schedule theme and layout modifications.
WordPress 5.x Series (2018 to 2022)
The 5.x series marked a transformative phase with the introduction of a modern block editor that changed how users create content.
WordPress 5.0 “Bebo” (December 2018)
This version launched the block editor (Gutenberg), letting users build posts and pages with blocks of different elements instead of relying on a single text editor, which enabled more dynamic layouts.
WordPress 5.5 “Eckstine” (August 2020)
Version 5.5 introduced auto-updates for themes and plugins, improving security by keeping sites current without manual work. It also added lazy-loading for images to improve performance.
WordPress 6.x Series (2022 to 2026)
The 6.x line is where full site editing matured and where the block editor stopped being a novelty and became how WordPress works.
WordPress 6.0 “Arturo” (May 2022)
Made block editing smoother and more intuitive, adding new block controls for more flexibility when customising layouts.
WordPress 6.6 “Dorsey” (July 2024)
Improvements to Full Site Editing, better performance and refined block capabilities.
WordPress 6.7 “Rollins” (12 November 2024)
Introduced the Twenty Twenty-Five default theme, described as designed for “any blog, any scale”. It also brought proper font management into the editor and a Zoom Out view for working on a page at the macro level rather than block by block.
WordPress 6.8 “Cecil” (15 April 2025)
A quietly important release for anyone running a site in production. It added speculative loading, which prefetches the page a visitor is most likely to click next, and moved password hashing to bcrypt, a meaningful security upgrade. It also carried more than 100 accessibility improvements and brought the Style Book to classic themes.
WordPress 6.9 “Gene” (2 December 2025)
Added Notes, which brings block-level commenting to the editor so a draft can be reviewed in place rather than in a separate document. The Command Palette made dashboard navigation considerably faster, and the Abilities API laid the groundwork for the AI features that arrived in 7.0.
WordPress 7.x Series (2026 to Present)
WordPress 7.0 “Armstrong” (20 May 2026)
The first 7.x release, and the biggest single change to the WordPress admin in years. AI abilities are managed from a central hub inside the site rather than through scattered plugins, the dashboard received a new admin theme, and the block library and developer toolbox both expanded again. Point releases 7.0.1 and 7.0.2 followed in July 2026 with maintenance and security fixes.
Managed Hosting solutions for WordPress backed by Speed, Security and Scalability
Talk To Sales →Version Timeline
| WordPress Version | Release Date | Key Features and Milestones |
|---|---|---|
| WordPress 1.0 “Miles” | January 2004 | Introduced permalinks, multiple categories and migration tools |
| WordPress 1.2 “Mingus” | May 2004 | Plugin architecture introduced, extending functionality |
| WordPress 2.0 “Duke” | December 2005 | Added visual editor (TinyMCE) and Akismet anti-spam plugin |
| WordPress 2.7 “Coltrane” | December 2008 | New admin interface, introduced automatic updates |
| WordPress 3.0 “Thelonious” | June 2010 | Custom post types, multisite functionality, Twenty Ten theme |
| WordPress 4.0 “Benny” | September 2014 | Improved media library, embed previews in editor |
| WordPress 4.9 “Tipton” | November 2017 | Draft and schedule customizer changes |
| WordPress 5.0 “Bebo” | December 2018 | Introduced the Gutenberg block editor |
| WordPress 5.5 “Eckstine” | August 2020 | Auto-updates for themes and plugins, lazy-loading images |
| WordPress 6.0 “Arturo” | May 2022 | Block editing improvements, new block controls |
| WordPress 6.6 “Dorsey” | July 2024 | Full Site Editing improvements, block enhancements, performance optimisation |
| WordPress 6.7 “Rollins” | November 2024 | Twenty Twenty-Five theme, font management, Zoom Out view |
| WordPress 6.8 “Cecil” | April 2025 | Speculative loading, bcrypt password hashing, 100+ accessibility fixes |
| WordPress 6.9 “Gene” | December 2025 | Notes block-level commenting, Command Palette, Abilities API |
| WordPress 7.0 “Armstrong” | May 2026 | AI abilities hub, redesigned admin, new blocks and design tools |
The Evolution of WordPress Functionality
WordPress began as a simple blogging tool and grew into a powerful platform for building any kind of website.
From Blogging Platform to Full CMS
When WordPress launched in 2003 it was a straightforward blogging platform. Over time it grew into a full content management system supporting websites well beyond blogs. By the 3.0 release in 2010 it had become a robust solution for portfolios, business pages and eCommerce stores.
Introduction of Plugins and Themes
The introduction of plugins in version 1.2 (2004) revolutionised WordPress, letting users add functionality without touching core code. Themes followed in version 1.5 (2005), allowing easy design changes. Together, plugins and themes turned WordPress into a customisable tool for everyone.
Multisite and Custom Post Types
Version 3.0 (2010) was pivotal. WordPress added multisite, letting users create multiple sites on a single installation, and introduced custom post types so developers could create content beyond simple posts and pages.
Gutenberg Block Editor
In 2018, WordPress 5.0 introduced the Gutenberg block editor, transforming how users build and format content. Blocks let users insert, arrange and style multimedia elements within pages or posts without coding.
Full Site Editing
Starting with WordPress 5.9 (2022), Full Site Editing expanded the block concept to entire site layouts. Users can customise headers, footers and templates with blocks, turning WordPress into a comprehensive site builder with flexibility rivalling dedicated page builders like Elementor or Wix.
How Blocks Changed WordPress
If you learned WordPress before 2018, the platform you remember and the platform that exists now are different products. Almost everything that has changed since traces back to one decision: content stopped being a single field of HTML and became a tree of blocks.
What a block actually is
A block is a self-contained unit of content with its own settings, stored as structured data with the markup rather than as free-form HTML. A paragraph is a block. So is an image, a button, a query loop pulling in recent posts. Because each one carries its own attributes, the editor can offer controls for that block specifically, and the site can render it consistently anywhere it appears.
The practical consequence is that layout moved out of the theme and into the content. That is why a modern WordPress site needs far fewer page-builder plugins than one built in 2017, and it is a large part of why sites have got faster: every builder you remove is a stack of CSS and JavaScript you no longer load, and what is left is served from our global CDN. Our guide on what speed does to revenue covers why that matters commercially.
From the block editor to full site editing
Blocks arrived in the post editor with 5.0 in 2018. Full site editing extended the same idea to everything outside the post: headers, footers, sidebars, archive pages, the 404. In a block theme, those are templates made of blocks that you edit in the same interface, rather than PHP files you edit in a code editor.
That shift is the reason the 6.x series looks incremental from the outside while being substantial underneath. Most of those releases were making full site editing usable rather than merely possible. Testing each one before it reaches visitors is what staging environments are for, and every FastCow plan includes them.
Block themes versus classic themes
A classic theme uses PHP template files and, usually, the Customizer. A block theme uses HTML templates built from blocks plus a theme.json file that defines colours, spacing and typography in one place. Both still work. WordPress has not deprecated classic themes, and 6.8 specifically brought the Style Book to them.
The choice matters most when you are picking a theme rather than when you are migrating one. If you are shopping, our roundup of premium WordPress themes is a reasonable starting point, and it is worth checking whether a theme is block-based before committing, because switching later is closer to a rebuild than an update.
Where blocks are heading
The last two releases point the direction clearly. 6.9 added Notes, which puts comments on individual blocks so review happens in the editor rather than in a separate document, and it only works because content is already structured that way. 7.0 then added AI abilities operating on the same structure. Both build on the block model rather than sitting beside it, which is a reasonable signal about where the next few releases go.
WordPress Version Naming Tradition
WordPress versions are named after jazz musicians, a tradition that started with WordPress 1.0 “Miles”, named after Miles Davis. It reflects Matt Mullenweg’s love of jazz, and each version honours a renowned musician.
Why Jazz Musicians?
Mullenweg, a jazz enthusiast, wanted to celebrate the creativity and improvisation in jazz. This parallels the open-source spirit of WordPress, where users and developers can build and create freely.
How WordPress Versions Impact Users and Developers
User benefits: each release brings better user experiences. Interface upgrades make the platform more intuitive, performance boosts improve site speed, and design flexibility grows with each new feature, alongside better accessibility and smoother workflows.
Developer tools: developers benefit from new APIs and improvements to plugin and theme development. The block editor keeps evolving, offering more customization options and ways to extend WordPress without breaking the codebase.
Staying up to date: keeping WordPress updated is essential for security, compatibility and performance. Outdated versions can expose sites to security risks and may not support the latest plugins or themes.
How to upgrade: always back up the website first, use staging environments to test updates, and check plugin compatibility. It is best to update incrementally to avoid issues.
The Future of WordPress
Full Site Editing: the Gutenberg roadmap keeps focusing on Full Site Editing. Phase 3 will introduce collaboration tools so several people can work on a site together, and Phase 4 will add native multilingual support.
A complete site builder: WordPress aims to compete directly with Wix, Squarespace and Shopify without losing its open-source spirit. With FSE and block-based editing, it continues to grow into a full site builder while keeping open access at its core.
Conclusion
WordPress began as a simple blogging tool in 2003 and, over two decades, became a full-featured CMS. Every release added powerful features that changed how websites are built and managed, and today it powers a significant portion of the web, from blogs to eCommerce platforms. With its focus on Full Site Editing, multilingual support and collaboration tools, WordPress looks set to lead web development for years to come.