WordPress 7.0 - Louis Armstrong
The current major branch as of June 8, 2026. This release marks the next generation of WordPress core after the long 6.x cycle.
WordPress has changed from a small blogging script into the operating system for a large part of the web. This timeline tracks the releases that actually changed how people build, edit, secure, and maintain WordPress sites.
Use this page as a practical release reference for checking the current WordPress version, reviewing recent maintenance updates, and understanding which milestones changed everyday WordPress site work.
The latest major WordPress version checked for this page is WordPress 7.0 "Louis Armstrong", released on May 20, 2026. The first public WordPress release was WordPress 0.70 on May 27, 2003.
Major releases are the milestones, but maintenance and security releases are what keep real sites stable. These recent updates are the ones site owners are most likely to see in dashboards today.
The timeline below lists every major WordPress release from the first public build to WordPress 7.0. Version names follow the WordPress tradition of honoring jazz musicians, starting with WordPress 1.0.
The current major branch as of June 8, 2026. This release marks the next generation of WordPress core after the long 6.x cycle.
A late-2025 major release followed by 6.9.1, 6.9.2, 6.9.3, and 6.9.4 maintenance updates in early 2026.
Focused on steady editor, security, and performance refinement for modern WordPress sites.
Introduced the Twenty Twenty-Five default theme and continued work on the site editing experience.
Improved design tooling, pattern management, style variations, and Data Views in the admin experience.
Brought the Font Library, Interactivity API, and Block Bindings API into everyday WordPress workflows.
Shipped Twenty Twenty-Four and pushed block patterns deeper into the editing workflow.
Made the Site Editor feel more complete, with better navigation, patterns, and the command palette.
Removed the beta label from the Site Editor and made block themes more practical for production sites.
Expanded style variations and shipped Twenty Twenty-Three as a flexible block theme foundation.
Polished full site editing, patterns, writing flow, and block theme controls after the 5.9 jump.
Introduced full site editing to mainstream WordPress and shipped the first default block theme, Twenty Twenty-Two.
Moved widgets into blocks, added early template editing, and expanded WebP support.
Added an HTTP-to-HTTPS migration tool and continued the block editor cleanup work.
Introduced application passwords, Twenty Twenty-One, and more automatic update control.
Added native XML sitemaps, lazy loading for images, and built-in plugin/theme auto-updates.
Improved block editor performance, navigation, embeds, and social blocks.
Shipped Twenty Twenty, refined large-image handling, and folded in many block editor improvements.
Made Site Health visible to everyday site owners and added fatal error protection.
Improved performance after 5.0 and laid more groundwork for Site Health checks.
Replaced the classic editor as the default writing experience with the block editor, then known widely as Gutenberg.
Improved Customizer workflows, scheduled design changes, and code-editing safeguards.
Added image, video, audio, and rich text widgets for a more flexible dashboard experience.
Shipped Twenty Seventeen, custom CSS in the Customizer, and REST API endpoints for posts, users, comments, terms, and settings.
Used native system fonts in the admin, improved updates, and made editor recovery smoother.
Added inline links, responsive preview controls, and faster image generation.
Introduced responsive images and the REST API infrastructure that later made headless WordPress common.
Moved menus into the Customizer, added site icons, and pushed stronger password behavior.
Improved character support, including emoji, and cleaned up plugin installation.
Added Twenty Fifteen and a cleaner writing mode for long-form publishing.
Brought a stronger media grid, better embed previews, and smoother plugin discovery.
Improved the visual editor, media handling, galleries, and widget previews.
Gave the WordPress admin its modern responsive design and introduced Twenty Fourteen.
Added automatic background updates for maintenance and security releases.
Improved revisions, autosaves, post locking, and native audio/video support.
Introduced the media manager and the Twenty Twelve default theme.
Made theme previews and the early Customizer part of normal WordPress management.
Improved the uploader, navigation, admin pointers, and tablet support.
Made the admin faster, introduced distraction-free writing, and raised old browser/server expectations.
Added the admin bar, post formats, internal linking, and archive improvements.
A landmark release: custom post types, custom menus, multisite merge, and the Twenty Ten theme.
Added image editing, post trash, easier embeds, and batch plugin updates.
Improved widgets, theme and plugin browsing, and admin speed for site owners.
Introduced the modern left-side admin navigation, automatic core upgrades, threaded comments, and quick editing.
Added post revisions, Press This, theme previews, and better publishing control.
Redesigned the dashboard, improved media handling, and renamed Blogroll to Links in the admin.
Added native tags, update notifications, and database changes that made upgrading important for site owners.
Moved widgets into core and improved Atom feed support.
Added autosave, privacy options, spell checking, and a cleaner editing workflow.
Brought a redesigned admin, user roles, rich editing, and image uploading into the core experience.
Introduced themes, pages, and template improvements that shaped WordPress as a full website platform.
Added plugin architecture, turning WordPress into a platform that site owners could extend.
The first named major release, with friendlier permalinks, multiple categories, and installation improvements.
The public starting point of WordPress, forked from b2/cafelog and built around simple publishing.
Some versions matter more because they changed daily WordPress work. Use these notes to understand why an older site may behave differently after a major jump.
If you manage the site, the safest place to check is inside WordPress itself. Publicly exposing the exact version is not a security strategy; keeping the site patched is.
wp core version.A WordPress update should be routine, not dramatic. The sites that run into trouble usually skip backups, staging checks, or plugin compatibility review.
Use it when planning upgrades, checking compatibility notes, or explaining why an older WordPress site behaves differently from a current install.
If a site is several major versions behind, read the releases in order and test the jump on staging before updating production.