The latest version of WordPress is 7.1.4, a security release published October 28, 2026 on the 7.1 “Mary Lou” branch (7.1 itself shipped August 19, 2026). The next major release, WordPress 7.2, is scheduled for December 8, 2026 and is in beta now. Since 0.7 in May 2003, WordPress has shipped 55 major versions, almost all named after jazz musicians.
The table below lists every one of them with its codename, release date, minimum PHP version and headline feature, linked to our full write-up where one exists. After the table, each era gets a short section on what changed and why it mattered. The releases come from the open source project rather than any one company, which is worth knowing if you have ever wondered who actually owns WordPress.
You can also run almost every version on this page. Since August 2026, WordPress Playground boots releases back to 0.7 in a browser tab. Tick “Include older versions” in its settings and it picks the matching PHP version for you (PHP 5.2 for 0.7 through 4.9, PHP 7.4 for 5.0 through 6.2). It is the quickest way to see what an old admin screen looked like or to reproduce a bug on one release.
- WordPress has shipped 55 major releases since 2003, each since 1.0 named after a jazz musician.
- The latest version is 7.1.4 (October 28, 2026). The latest major release is WordPress 7.1, released August 19, 2026, and WordPress 7.2 is scheduled for December 8, 2026.
- Minor releases (like 7.1.3 and 7.1.4) install automatically by default and are mostly security and bug fixes.
- WordPress 7.0 and 7.1 need PHP 7.4 or newer. Always run the latest version: WordPress.org flags every older 7.x build except 7.0.8 as insecure.
Quick reference: current and upcoming versions
- Latest version: 7.1.4, a security release from October 28, 2026. The current major line is WordPress 7.1 “Mary Lou”, released August 19, 2026.
- Next major release: WordPress 7.2, scheduled for December 8, 2026. Beta 4 shipped November 3, and RC1 is planned for November 17. Matt Mullenweg leads it, and a new default theme ships alongside.
- Other supported 7.x build: 7.0.8 (also October 28). The WordPress.org stable-check API marks 7.0.8 as outdated and every other 7.0.x and 7.1.x build as insecure.
- Minimum PHP: 7.4 since WordPress 7.0. The 6.6 to 6.9 releases need 7.2.24.
- Oldest branch still getting security fixes: 4.7 (4.7.39 shipped with the October 28 release). The 4.6 branch last updated with 4.6.30 in July 2025.
- Cadence: two or three major releases a year (three in 2024, two in 2025, three in 2026 if 7.2 lands on schedule).
To find out which version you’re running, see how to check your WordPress version.
WordPress version history table
Every major release in one place, newest first. Release 2.4 never existed: the project skipped from 2.3 straight to 2.5.
| Version | Codename (musician) | Released | Min. PHP | Headline feature |
|---|---|---|---|---|
| 7.2 | Not announced yet | December 8, 2026 (scheduled) | 7.4 | In beta; new default theme planned |
| 7.1 | Mary Lou (Mary Lou Williams) | August 19, 2026 | 7.4 | Responsive styles, hover and focus states, Playlist and Tabs blocks |
| 7.0 | Armstrong (Louis Armstrong) | May 20, 2026 | 7.4 | AI Client and Abilities API in core; real-time collaboration pulled |
| 6.9 | Gene (Gene Harris) | December 2, 2025 | 7.2.24 | Notes on blocks, Abilities API, dashboard-wide Command Palette |
| 6.8 | Cecil (Cecil Taylor) | April 15, 2025 | 7.2.24 | Speculative loading, bcrypt password hashing |
| 6.7 | Rollins (Sonny Rollins) | November 12, 2024 | 7.2.24 | Twenty Twenty-Five, Zoom Out, HEIC uploads |
| 6.6 | Dorsey (Tommy Dorsey) | July 16, 2024 | 7.2.24 | Automatic rollbacks for failed plugin auto-updates |
| 6.5 | Regina (Regina Carter) | April 2, 2024 | 7.0 | Font Library, Block Bindings API, Interactivity API |
| 6.4 | Shirley (Shirley Horn) | November 7, 2023 | 7.0 | Twenty Twenty-Four, Block Hooks, image lightbox |
| 6.3 | Lionel (Lionel Hampton) | August 8, 2023 | 7.0 | Command palette, Footnotes block |
| 6.2 | Dolphy (Eric Dolphy) | March 29, 2023 | 5.6.20 | Site Editor out of beta |
| 6.1 | Misha (Mikhail Alperin) | November 1, 2022 | 5.6.20 | Fluid typography |
| 6.0 | Arturo (Arturo O’Farrill) | May 24, 2022 | 5.6.20 | Style variations, block locking |
| 5.9 | Joséphine (Joséphine Baker) | January 25, 2022 | 5.6.20 | Full Site Editing, first default block theme |
| 5.8 | Tatum (Art Tatum) | July 20, 2021 | 5.6.20 | Block widgets, theme.json, WebP |
| 5.7 | Esperanza (Esperanza Spalding) | March 9, 2021 | 5.6.20 | One-click HTTPS switch, Robots API |
| 5.6 | Simone (Nina Simone) | December 8, 2020 | 5.6.20 | Application passwords, Twenty Twenty-One |
| 5.5 | Eckstine (Billy Eckstine) | August 11, 2020 | 5.6.20 | Plugin and theme auto-updates, XML sitemaps, lazy-loading |
| 5.4 | Adderley (Nat Adderley) | March 31, 2020 | 5.6.20 | Social Icons and Buttons blocks |
| 5.3 | Kirk (Rahsaan Roland Kirk) | November 12, 2019 | 5.6.20 | Twenty Twenty, editor polish |
| 5.2 | Jaco (Jaco Pastorius) | May 7, 2019 | 5.6.20 | Site Health screens, fatal error protection |
| 5.1 | Betty (Betty Carter) | February 21, 2019 | 5.2.4 | Outdated-PHP warnings |
| 5.0 | Bebo (Bebo Valdés) | December 6, 2018 | 5.2.4 | Block editor (Gutenberg) |
| 4.9 | Tipton (Billy Tipton) | November 16, 2017 | 5.2.4 | Customizer drafts, code error checking |
| 4.8 | Evans (Bill Evans) | June 8, 2017 | 5.2.4 | Image, audio and video widgets |
| 4.7 | Vaughan (Sarah Vaughan) | December 6, 2016 | 5.2.4 | REST API content endpoints, Twenty Seventeen |
| 4.6 | Pepper (Pepper Adams) | August 16, 2016 | 5.2.4 | Updates without page reloads, system fonts |
| 4.5 | Coleman (Coleman Hawkins) | April 12, 2016 | 5.2.4 | Inline link editing, custom logos |
| 4.4 | Clifford (Clifford Brown) | December 8, 2015 | 5.2.4 | Responsive images, REST API infrastructure |
| 4.3 | Billie (Billie Holiday) | August 18, 2015 | 5.2.4 | Site icons, formatting shortcuts |
| 4.2 | Powell (Bud Powell) | April 23, 2015 | 5.2.4 | Emoji support, utf8mb4 |
| 4.1 | Dinah (Dinah Washington) | December 18, 2014 | 5.2.4 | Distraction-free writing, Twenty Fifteen |
| 4.0 | Benny (Benny Goodman) | September 4, 2014 | 5.2.4 | Media library grid view |
| 3.9 | Smith (Jimmy Smith) | April 16, 2014 | 5.2.4 | Live widget and header previews |
| 3.8 | Parker (Charlie Parker) | December 12, 2013 | 5.2.4 | Admin redesign (MP6), Twenty Fourteen |
| 3.7 | Basie (Count Basie) | October 24, 2013 | 5.2.4 | Automatic background updates |
| 3.6 | Oscar (Oscar Peterson) | August 1, 2013 | 5.2.4 | Revisions screen, post locking |
| 3.5 | Elvin (Elvin Jones) | December 11, 2012 | 5.2.4 | New media manager, Twenty Twelve |
| 3.4 | Green (Grant Green) | June 13, 2012 | 5.2.4 | Theme Customizer |
| 3.3 | Sonny (Sonny Stitt) | December 12, 2011 | 5.2.4 | Drag-and-drop uploader |
| 3.2 | Gershwin (George Gershwin) | July 4, 2011 | 5.2.4 | Dropped PHP 4, Twenty Eleven |
| 3.1 | Reinhardt (Django Reinhardt) | February 23, 2011 | 4.3 | Admin Bar, post formats |
| 3.0 | Thelonious (Thelonious Monk) | June 17, 2010 | 4.3 | Custom post types, Multisite merge |
| 2.9 | Carmen (Carmen McRae) | December 18, 2009 | 4.3 | Trash, image editor, oEmbed |
| 2.8 | Baker (Chet Baker) | June 11, 2009 | Not set | Theme installer, new Widget API |
| 2.7 | Coltrane (John Coltrane) | December 10, 2008 | Not set | Admin redesign, one-click upgrades |
| 2.6 | Tyner (McCoy Tyner) | July 15, 2008 | Not set | Post revisions, Press This |
| 2.5 | Brecker (Michael Brecker) | March 29, 2008 | Not set | Dashboard widgets, shortcode API |
| 2.3 | Dexter (Dexter Gordon) | September 25, 2007 | Not set | Native tags and the taxonomy system |
| 2.2 | Getz (Stan Getz) | May 16, 2007 | Not set | Widgets in core |
| 2.1 | Ella (Ella Fitzgerald) | January 22, 2007 | Not set | Autosave, spell check |
| 2.0 | Duke (Duke Ellington) | December 31, 2005 | Not set | WYSIWYG editor, user roles |
| 1.5 | Strayhorn (Billy Strayhorn) | February 17, 2005 | Not set | Themes and static pages |
| 1.2 | Mingus (Charles Mingus) | May 22, 2004 | Not set | Plugins |
| 1.0 | Davis (Miles Davis) | January 3, 2004 | Not set | Search-friendly permalinks, multiple categories |
| 0.7 | None | May 27, 2003 | Not set | First release, forked from b2/cafelog |
$required_php_version value in core; releases before 2.9 did not set one. Linked versions have a full SmartWP write-up.WordPress 7.x (the next chapter)

WordPress 7.2 (scheduled for December 8, 2026)
The last major release of 2026 is in beta: Beta 4 shipped November 3, with RC1 planned for November 17 and the final release on December 8. Matt Mullenweg is release lead, and a new default theme ships alongside it. The codename has not been announced. Dev notes so far cover SVG icons in the admin bar and menu and the NO_BACKSLASH_ESCAPES SQL mode being turned off by default. We will publish a full 7.2 breakdown when it ships.
WordPress 7.1 “Mary Lou” (released August 19, 2026)
Released: August 19, 2026, on the final day of WordCamp US, exactly on the date announced at the start of the cycle. Codename “Mary Lou,” honouring the pianist, arranger and composer Mary Lou Williams, who turned her Harlem apartment into the workshop where Thelonious Monk and Dizzy Gillespie worked out bebop. Release lead: Anne McCarthy. More than 800 contributors, over 170 of them contributing for the first time, shipping 1,500+ enhancements and fixes.
Where 7.0 added an AI framework, 7.1 mostly finished things. The headline is styling: responsive styles and interactive states (hover, focus, active) became editor controls, removing two of the most common reasons people still wrote custom CSS. Media got the deepest rework, with image processing moving into the browser rather than the server, a dedicated crop and rotate modal, and support for the formats phones actually produce. Two new blocks shipped, Playlist and Tabs, and the admin bar finally followed users into every editor.
For developers the consequential change was the enforced iframed editor, which requires blocks still on Block API version 2 or lower to be updated. Real-time collaboration was absent for a second consecutive release. Full detail in our WordPress 7.1 breakdown, and the official 7.1 “Mary Lou” announcement.
WordPress 7.0 “Armstrong” (released May 20, 2026)
Released: May 20, 2026 (delayed from the original April 9 target). The first major version under the 7.x series. Codename “Armstrong,” honoring jazz trumpeter Louis Armstrong. Real-time collaboration was originally planned as the headline feature, but Matt Mullenweg pulled it from 7.0 on May 8, 2026, citing surface area, race conditions, server load, memory efficiency, and bugs surfaced through fuzz testing. The feature is not shelved; the team plans broader testing and continued iteration toward a future release. The actual marquee features that shipped on May 20 (AI Client + Abilities API in Core, modernized dashboard with Command Palette, four new blocks, block-level Custom CSS) are covered in our WordPress 7.0 deep dive. Full breakdown of the RTC removal.
The cycle was paused in late March 2026 after RC1 testing feedback on real-time collaboration, and the later release candidates were treated as betas, which is unusual for WordPress. 7.0 shipped as a stability-focused release led by Matias Ventura. See The Path Forward for WordPress 7.0 for the reasoning.
WordPress 6.x (block editor matures)

The 6.x series picked up where 5.x left off, building out Full Site Editing into a real Site Editor, expanding block patterns, and pushing performance improvements like speculative loading. By the end of 6.x, WordPress could edit every piece of a theme through the block interface.
WordPress 6.9 “Gene”
Released: December 2, 2025. Introduced Notes (block-level comments for editorial review), extended the Command Palette across the whole dashboard, added a Fit text option that sizes text to fill its container, and shipped the Abilities API that 7.0 later built its AI features on.
Notes are the most distinctive addition. Editors can leave feedback on individual blocks, which suits teams reviewing posts before they go live. Full breakdown: WordPress 6.9 “Gene”.
WordPress 6.8 “Cecil”
Released: April 15, 2025. Editor performance improvements, speculative loading (preloads the next page on hover for faster perceived navigation), and bcrypt security upgrades to user password hashing.
Speculative loading is the under-the-radar headline. When a visitor hovers over an internal link, WordPress preloads the target page in the background, which makes navigation feel near-instant once they click through. Full breakdown: WordPress 6.8 “Cecil”. See also the official 6.8 announcement.
WordPress 6.7 “Rollins”
Released: November 12, 2024. Shipped the “Twenty Twenty-Five” default theme, added Zoom Out preview mode for designing at the page level instead of block by block, and introduced HEIC image support for media uploads.
Zoom Out is the Site Editor mode that lets you design at the page level instead of zooming into individual blocks. For long-form layouts and complex template work, it is a noticeable productivity gain. HEIC support also matters for iPhone users uploading photos straight from their camera roll without converting first. Full breakdown: WordPress 6.7 “Rollins”.
WordPress 6.6 “Dorsey”
Released: July 16, 2024. Added color and font sets that multiply design combinations per theme, a side-by-side page preview layout in the Site Editor, and automatic rollbacks for failed plugin auto-updates.
Automatic rollbacks are the most consequential change. If a plugin auto-update causes a fatal error, WordPress restores the previous version on its own, which makes leaving auto-updates on much less risky. Full breakdown: WordPress 6.6 “Dorsey”.
WordPress 6.5 “Regina”
Released: April 2, 2024. Introduced the Font Library (manage custom fonts directly in the Site Editor without uploading via FTP), Data Views for managing posts and templates, and the Block Bindings API for connecting block content to dynamic data sources like custom fields.
Block Bindings was the under-celebrated headline of 6.5. It lets a block (paragraph, heading, image, button) bind its content to a dynamic source (a custom field, a query parameter, a post property) without writing custom blocks. For developers building dynamic sites, Block Bindings is what moved the block editor from “static content composition” to “templating system.” Combined with the Font Library and the maturing Data Views, 6.5 set up the trajectory the rest of the 6.x series and 7.0 are building on. Full breakdown: WordPress 6.5 “Regina”. See also the official 6.5 announcement.
WordPress 6.4 “Shirley”
Released: November 7, 2023. Shipped the “Twenty Twenty-Four” default theme (designed to work across blogs, business sites, and portfolios), introduced Block Hooks for plugins to inject blocks into themes, and added a built-in image lightbox.
Block Hooks let plugins inject blocks into specific positions in a theme without modifying theme files (e.g., add a related-posts block after every single-post template). Together with the built-in image lightbox, 6.4 closed two long-standing “why does this need a plugin” gaps in core.
WordPress 6.3 “Lionel”
Released: August 8, 2023. Brought full content management into the Site Editor (you could now edit every template, template part, and pattern in one place), added the Footnotes block, and introduced a command palette for jumping around the editor with the keyboard.
The command palette (open with Cmd-K or Ctrl-K) lets you jump to any template, post, or editor action without clicking through menus. Once you are used to it, it is faster than navigating the wp-admin sidebar. The Footnotes block was a small addition with disproportionate impact for academic and reference-heavy writers.
WordPress 6.2 “Dolphy”
Released: March 29, 2023. Reimagined the Site Editor and took it out of beta, improved the Navigation block, and added a sticky toolbar to the writing flow. For a full account of everything that changed in 6.2, see what’s new in WordPress 6.2.
6.2 was the version that made Full Site Editing feel mainstream rather than experimental. Taking the Site Editor out of beta meant theme developers and agency builders could rely on it for client work without the “this is still beta” caveat that had hung over earlier 5.9 and 6.0/6.1 work.
WordPress 6.1 “Misha”
Released: November 1, 2022. Refined design tools across blocks, cleaner default layouts, and fluid typography that scales with viewport size automatically. Continued the Full Site Editing trajectory from 5.9 and 6.0.
Fluid typography (introduced in 6.1) lets a theme define a font size that scales smoothly between mobile and desktop without media queries. It fixed responsive typography for thousands of themes without requiring custom CSS work, and it became the recommended pattern in modern theme.json files.
WordPress 6.0 “Arturo”
Released: May 24, 2022. Major writing improvements in Gutenberg, style variations (switch a theme’s color palette and typography in one click), and block locking so editors can’t accidentally remove or move structural blocks.
WordPress 5.x (the block editor era)

WordPress 5.0 introduced the Block Editor (Gutenberg) and changed how millions of people wrote on WordPress. The rest of the 5.x series cleaned up the rough edges, added auto-updates, introduced Site Health, and finally arrived at Full Site Editing in 5.9.
WordPress 5.9 “Joséphine”
Released: January 25, 2022. Shipped the “Twenty Twenty-Two” theme, the first default block theme. Introduced the Site Editor and Full Site Editing for block themes, the start of replacing the customizer with block-based theme editing.
Full Site Editing (FSE) extended the block editor to every part of a theme: headers, footers, sidebars, archive pages, the 404 page, single post and page templates. Themes that opted into the block-theme model declared their structure through theme.json and template files made of blocks, which meant users could edit any visual element of their site through the same block interface they used for posts.
This started a long migration: classic themes (the kind built with PHP template files and the customizer) are still fully supported, but block themes are now the recommended path for new themes. The Site Editor matured significantly over the rest of the 6.x series. See WordPress 5.9 Joséphine and the Site Editor documentation.
WordPress 5.8 “Tatum”
Released: July 20, 2021. Introduced block widgets (the widget admin became block-based), early block theme support, the List View panel for navigating complex page structures, and WebP image support.
theme.json arrived in 5.8, the configuration file modern block themes use to declare their colors, fonts, layout settings, and spacing scale. Every block theme since 5.9 ships a theme.json. WebP support meant WordPress could finally serve modern image formats natively.
WordPress 5.7 “Esperanza”
Released: March 9, 2021. A refreshed admin color palette, one-click HTTP to HTTPS switching, and the Robots API for controlling the robots meta tag (with max-image-preview:large on by default).
The HTTPS switch was the most user-visible change. Once an SSL certificate was in place, one click updated the database URLs to https://, which used to mean a search-and-replace job.
WordPress 5.6 “Simone”
Released: December 8, 2020. Shipped the “Twenty Twenty-One” default theme. Major Gutenberg enhancements, application passwords for REST API authentication, and continued block editor work. (Bcrypt password hashing came later, in 6.8.)
Application Passwords became one of the most-used features in 5.6. They let scripts, mobile apps, and integrations authenticate against the WordPress REST API without using the user’s main login password, the pattern most automation workflows still rely on today.
WordPress 5.5 “Eckstine”
Released: August 11, 2020. Native lazy-loading for images (added loading="lazy" attributes automatically), built-in XML sitemaps, and auto-updates for plugins and themes.
Plugin and theme auto-updates were the under-the-radar headline. Site owners could opt individual plugins and themes into background updates from Plugins → Installed Plugins, and most managed-WordPress hosts started enabling this by default for their customers. The result: a meaningful chunk of WordPress’s install base started staying patched on plugin security releases without anyone manually clicking Update. Combined with the core auto-updates from 3.7 (Basie), this is most of why WordPress runs without constant maintenance for the average site. See WordPress 5.5 Eckstine.
WordPress 5.4 “Adderley”
Released: March 31, 2020. Social icons and buttons blocks landed in core (no plugin needed), custom field support for menu items, and continued Gutenberg performance work.
WordPress 5.3 “Kirk”
Released: November 12, 2019. Polished interactions across the editor, shipped the “Twenty Twenty” default theme (designed for the block editor from the start), and continued accessibility and admin UI improvements.
WordPress 5.2 “Jaco”
Released: May 7, 2019. Added Site Health status and info screens and fatal error protection (a recovery-mode email when a plugin or theme crashes the site). The Block Directory for installing blocks from the editor came later, in 5.5.
Site Health Check was the standout feature. It is a built-in diagnostic that surfaces PHP version warnings, plugin conflicts, file permission issues, and configuration problems before they become user-facing bugs. PHP error protection (now part of WordPress’s built-in debug and Recover Mode flow) saved a lot of sites from white-screen-of-death scenarios when a plugin update went wrong.
WordPress 5.1 “Betty”
Released: February 21, 2019. Added PHP version upgrade nudges (warning users on outdated PHP versions), block editor performance improvements, and reduced memory usage on common operations.
PHP version upgrade nudges were the under-discussed shift. WordPress started showing prominent warnings on sites running PHP 5.x, which accelerated the broader WordPress ecosystem’s PHP modernization. By 2021, the WordPress PHP version distribution had shifted dramatically toward PHP 7+.
WordPress 5.0 “Bebo”
Released: December 6, 2018. The release that introduced Gutenberg, the new block-based editor that replaced the Classic Editor as the default writing experience. Also shipped the “Twenty Nineteen” theme. The biggest UX shift in WordPress’s history; the platform divided into “block editor” and “Classic Editor + plugin” camps for years afterward.
Gutenberg replaced TinyMCE (the WYSIWYG editor that had been WordPress’s default since 2.0 in 2005) with a JavaScript-based interface where every piece of content (paragraphs, images, headings, embeds, custom layouts) is a self-contained “block.” The user experience shifted from “type into a single text area” to “build a page from components.” For modern websites that needed flexible layouts, this was a massive productivity unlock. For users who wanted the simple text editor, it was a regression.
The Classic Editor plugin (officially supported as a fallback) still has more than 8 million active installs. The block editor side, meanwhile, became the foundation for everything that followed: block themes (5.8+), the Site Editor and Full Site Editing (5.9), and the Block Bindings API (6.5). See the launch announcement at WordPress 5.0 Bebo and the official block-editor documentation at developer.wordpress.org/block-editor/.
WordPress 4.x (the customizer era)

The 4.x series finished modernizing the WordPress admin, brought the REST API into core, kept iterating on the customizer, and laid the foundation for what would become Gutenberg.
WordPress 4.9 “Tipton”
Released: November 16, 2017. Customizer scheduling and design locking, gallery widgets, and code error checking in the theme/plugin editor (so you couldn’t accidentally save a syntax error that broke the site).
The code error checking was a small but lifesaving addition. Before 4.9, you could save a syntax error from the wp-admin file editor and instantly take your site offline. After 4.9, WordPress refused to save broken PHP and gave you a useful error message instead.
WordPress 4.8 “Evans”
Released: June 8, 2017. Media widgets (image, audio, video) replaced the previous text-only widget defaults, plus an upgraded text widget with WYSIWYG editing.
WordPress 4.7 “Vaughan”
Released: December 6, 2016. Brought the REST API content endpoints into core (the foundation for headless WordPress), shipped the “Twenty Seventeen” default theme, video header support, and PDF preview thumbnails in the media library.
The REST API content endpoints (posts, pages, media, comments, taxonomies, users) were what unlocked headless WordPress. Once any client (a headless Next.js front-end, a React Native app, a static site generator, an e-ink dashboard) could read and write WordPress data through standard JSON, WordPress stopped being just a theme-rendered website and became a content service. Frameworks like Frontity and Gatsby’s WordPress plugins were direct downstream effects. The endpoints are documented at the REST API endpoint reference. See the original announcement at WordPress 4.7 Vaughan.
WordPress 4.6 “Pepper”
Released: August 16, 2016. Streamlined plugin and theme updates (no full-page reloads anymore), native system fonts in the admin, and content recovery in the editor.
WordPress 4.5 “Coleman”
Released: April 12, 2016. Inline link editing, formatting shortcuts in the editor (Markdown-like), and live responsive previews in the customizer for desktop, tablet, and mobile breakpoints.
WordPress 4.4 “Clifford”
Released: December 8, 2015. Shipped the “Twenty Sixteen” default theme, responsive images via srcset, embeds for any oEmbed-compatible content, and the start of the REST API infrastructure (endpoints came in 4.7).
The REST API infrastructure was the bigger long-term story. 4.4 didn’t expose the post and comment endpoints yet (that came in 4.7), but it shipped the routing layer, authentication scaffolding, and request/response handling that the later endpoints plugged into. For a deep dive, see the official REST API handbook. Responsive images via srcset arriving as a core feature was also significant: it meant millions of WordPress sites started serving the right image size to each device automatically, without needing a plugin or custom theme work.
WordPress 4.3 “Billie”
Released: August 18, 2015. Mobile experience improvements, stronger password recommendations on user creation, and customizer additions for site icons.
WordPress 4.2 “Powell”
Released: April 23, 2015. Press This received a big update for sharing content from anywhere on the web, native emoji support arrived, and the customizer gained menu management.
WordPress 4.1 “Dinah”
Released: December 18, 2014. Shipped the “Twenty Fifteen” default theme and added distraction-free writing mode (the editor faded surrounding UI when typing).
WordPress 4.0 “Benny”
Released: September 4, 2014. Improved media management (grid view in the library), inline embeds in the post editor, and a tighter writing interface. The 4.0 number was a marketing milestone, not a major rewrite.
WordPress 3.x (multisite and custom post types)

The 3.x series transformed WordPress from a blogging platform into a full content management system. Multisite, custom post types, custom menus, the customizer, and automatic background updates all landed in this era.
WordPress 3.9 “Smith”
Released: April 16, 2014. Media editor improvements, live widget previews in the customizer, and live header image previews while editing.
WordPress 3.8 “Parker”
Released: December 12, 2013. Major admin redesign (the MP6 project), the first fully responsive admin, and the “Twenty Fourteen” theme. The dark sidebar and modern admin chrome that lasted nearly a decade started here.
MP6 was the biggest cosmetic shift in WordPress’s history at the time. The new admin design (dark sidebar, modern flat icons, responsive layout for tablets) replaced the older, more cluttered admin from the 2.7-3.7 era. The structural decisions in MP6 carried forward through every subsequent admin update.
WordPress 3.7 “Basie”
Released: October 24, 2013. Automatic background updates for security and minor releases (the reason most WordPress sites stay patched without anyone touching them) and stronger password recommendations.
Automatic background updates were the headline. Until 3.7, WordPress required manual confirmation in the admin for every minor and security update. After 3.7, security and maintenance releases (5.6.1, 6.4.2, etc.) installed themselves on most sites with no human intervention. This is most of why a typical WordPress site stays patched without anyone touching it. See WordPress 3.7 Basie.
WordPress 3.6 “Oscar”
Released: August 1, 2013. The “Twenty Thirteen” theme, a new revision system, autosave for posts, and post locking (so two editors couldn’t overwrite each other on the same post).
WordPress 3.5 “Elvin”
Released: December 11, 2012. Retina display support, a color picker for the admin, and the “Twenty Twelve” theme. The new media manager replaced the old upload flow and is essentially the modern media library you still use today.
WordPress 3.4 “Green”
Released: June 13, 2012. Theme customization improvements (the customizer landed here as a precursor to what 4.x and 5.x built out), and Twitter embeds.
WordPress 3.3 “Sonny”
Released: December 12, 2011. Friendlier onboarding for new users, drag-and-drop media uploading, and tablet support for the admin.
WordPress 3.2 “Gershwin”
Released: July 4, 2011. Performance and speed improvements across the admin and front-end. This was also the first version to drop support for PHP 4 and MySQL 4.
Dropping PHP 4 and MySQL 4 support was the consequential decision. PHP 4 had reached end of life years earlier; ending official compatibility freed core developers from supporting features no modern host shipped, and accelerated the broader WordPress ecosystem’s PHP modernization.
WordPress 3.1 “Reinhardt”
Released: February 23, 2011. The Admin Bar (now the Toolbar) appeared on the front-end for logged-in users, post formats arrived for theme support, and internal linking shortcuts came to the editor.
The Admin Bar (renamed to Toolbar in later versions) introduced the floating bar at the top of front-end pages for logged-in users, the gateway to the admin from any page on the site. Post formats (gallery, video, link, status, etc.) were a theme-developer-facing feature that never quite caught on but lived in core for years.
WordPress 3.0 “Thelonious”
Released: June 17, 2010. One of the most consequential releases ever. Custom post types and custom taxonomies turned WordPress into a real CMS. Custom menus replaced the old theme-bound nav. WordPress MU merged into core, giving every install Multisite capability. New theme APIs unlocked theme features as opt-in declarations. The “Twenty Ten” theme launched the annual default-theme tradition.
Custom post types are why WordPress can run e-commerce stores, real estate listings, podcast networks, and learning platforms. Without them (see our custom post types guide), every non-blog use case would have required a fork of WordPress or a hack on the post table. WooCommerce (7 million+ active installs) is built entirely on custom post types and taxonomies introduced in 3.0. So is Advanced Custom Fields, every major LMS plugin, every major event-management plugin, and a long tail of niche ecosystem tools.
The Multisite merge had a different kind of impact: it gave hosts and agencies a single-codebase way to run thousands of sites, which fueled the WaaS (WordPress-as-a-service) market that grew through the 2010s. See the original announcement at WordPress 3.0 Thelonious.
WordPress 2.x (the rich editor era)

The 2.x series turned WordPress from a blogging tool with rough edges into a polished publishing platform. Rich-text editing, plugins, themes, taxonomies, image editing, and the redesigned admin all came in this era.
WordPress 2.9 “Carmen”
Released: December 18, 2009. Global undo (a “trash” for posts and comments instead of permanent deletion), a built-in image editor, and batch plugin updates.
The Trash for posts and comments (instead of permanent deletion) was a long-overdue safety net. Accidental deletions stopped being permanent without a database rollback. The built-in image editor let you crop, rotate, and resize images in the media library without leaving WordPress, which had previously required offline tools.
WordPress 2.8 “Baker”
Released: June 11, 2009. Performance improvements, automatic theme installation from the wp.org directory, and the CodePress syntax-highlighting editor for theme files.
WordPress 2.7 “Coltrane”
Released: December 10, 2008. A complete admin interface redesign that defined how WordPress looked for the next five years. Automatic plugin and core upgrades from the dashboard (the predecessor to background auto-updates in 3.7).
The 2.7 admin (with its left-side navigation menu and dashboard widget grid) became the template every WordPress admin since has iterated on. Even after MP6 in 3.8 modernized the look, the structural decisions Jane Wells and the design team made in 2.7 carried forward. See the original announcement at WordPress 2.7 Coltrane.
WordPress 2.6 “Tyner”
Released: July 15, 2008. Post and page revision tracking, change tracking in the editor, and remote posting via Press This and email.
WordPress 2.5 “Brecker”
Released: March 29, 2008. Dashboard redesign (a precursor to the bigger 2.7 redesign), multi-file media uploads, and an improved plugin management interface. Note: there was no 2.4 release; the version jumped directly from 2.3 to 2.5.
Multi-file media uploads via Flash-based uploaders meant you could finally drag a folder of images into WordPress without uploading them one at a time. The version jump from 2.3 to 2.5 was a planning decision; some intended 2.4 features got rolled into 2.5 instead of shipping a smaller release.
WordPress 2.3 “Dexter”
Released: September 25, 2007. Native tags landed in core (previously a plugin), the new taxonomy system (the same one that powers categories and tags today), and update notifications when new versions of plugins were available.
Native tags in core was a milestone. Until 2.3, you needed a plugin to add tags to posts. The new taxonomy system (which still powers categories, tags, and every custom taxonomy used by WooCommerce, ACF, and others) is one of the most-used parts of WordPress today, and 2.3 is where it landed.
WordPress 2.2 “Getz”
Released: May 16, 2007. Widget support landed in core (sidebar widgets had been a plugin until then), the Atom 1.0 feed, and speed optimizations.
Widget support landing in core was a watershed moment for theme design. Until 2.2, sidebars were hardcoded in theme template files. After 2.2, themes could declare widget areas, and users could drag widgets in and out of them through the admin, the foundation of every modern WordPress sidebar.
WordPress 2.1 “Ella”
Released: January 22, 2007. Security fixes, a redesigned editing interface, and improved tools for writing and managing content.
About six weeks after 2.1, in March 2007, the project had its most embarrassing security moment: a cracker modified the 2.1.1 download on the wordpress.org server to include a backdoor. It was caught quickly and fixed in 2.1.2, and the lesson about build-server security stuck.
WordPress 2.0 “Duke”
Released: December 31, 2005. Rich-text editing arrived (TinyMCE replaced the old plain HTML textarea), image uploading from the post editor, faster posting workflows, and an improved import system. This was the version that made WordPress feel like a real publishing tool instead of a code project.
TinyMCE replaced the plain HTML textarea, giving WordPress a real WYSIWYG editor for the first time. Image uploading directly from the post editor (instead of a separate uploads area) was the second big quality-of-life improvement. 2.0 is the version where WordPress started competing with Movable Type and TypePad on user experience, not just on price and openness.
WordPress 1.x (themes and the foundation)

The 1.x series put down the architectural foundations: themes, plugins, comment moderation, multi-author support, and pages as a separate concept from posts. By the end of 1.5, you could recognize WordPress as the same platform we use today.
WordPress 1.5 “Strayhorn”
Released: February 17, 2005. Static pages (a separate concept from blog posts), the theme/template system that’s still in use today, comment moderation tools, and a new default template (“Kubrick”) that lasted for years.
The static pages concept (separate from blog posts) was the moment WordPress started moving beyond pure blogging. Without 1.5, WordPress could not have become the CMS it grew into during the 3.0+ era. Kubrick was the most recognizable WordPress design for years and influenced thousands of derivative themes.
WordPress 1.2 “Mingus”
Released: May 22, 2004. Plugin support landed in core. Plugins are a big part of why WordPress runs 39.4% of all websites today; that ecosystem started here.
The plugin API in 1.2 was deceptively small but architecturally enormous. Hook-based extension (actions and filters) is what every WordPress plugin since has been built on. The wp.org plugin directory lists more than 70,000 plugins today; all of them trace back to the API hooks introduced in this release.
WordPress 1.0 “Davis”
Released: January 3, 2004. The first numbered release. Search-engine-friendly permalinks, support for assigning multiple categories to a post, comment moderation, and Atom feed support. Codenamed “Davis” after Miles Davis, kicking off the jazz musician naming tradition that’s continued for every release since.
1.0 also marked the point where WordPress started feeling less like a fork of b2/cafelog and more like its own thing. The interface stayed minimal but the underlying data model (posts, users, comments, the admin scaffolding) had been rewritten. The release also coincided with a wave of users leaving Movable Type after a controversial pricing change later that year, which is what really put WordPress on the map.
WordPress 0.7 (the very first release)

Released: May 27, 2003. The first WordPress release, forked from b2/cafelog by Matt Mullenweg and Mike Little. It used the same file structure as its predecessor and added the foundational improvements that would set the project apart over the next two years. No codename (those started at 1.0).
How WordPress started: from b2/cafelog to 0.7
WordPress wasn’t built from scratch. Before WordPress existed, a small blogging tool called b2/cafelog (often just “b2”) was used by about 2,000 sites. In early 2003, b2’s lead developer slowed down on the project, and one of its users, Matt Mullenweg, posted that he was forking it. Another developer, Mike Little, replied with interest, and the two started building.
The name “WordPress” was suggested by Christine Selleck Tremoulet, a friend of Mullenweg. The first release, 0.7, shipped on May 27, 2003. WordPress’s growth accelerated in 2004 when Movable Type, the dominant blogging platform at the time, changed its licensing terms. Many users migrated to WordPress, and the platform never looked back.
The jazz musician naming convention
Starting with WordPress 1.0 (“Davis,” for Miles Davis), every major release has been named after a jazz musician the lead developer of that release admires. The tradition isn’t a strict rule (5.6 was named for Nina Simone, who’s more associated with soul, and 5.9 for Joséphine Baker, a singer-dancer in the jazz heritage), but it’s run continuously for more than two decades. The most recent is 7.1 “Mary Lou,” for Mary Lou Williams.
The codename is revealed in the release announcement on WordPress.org News and recorded in the official WordPress history. Upcoming releases stay unnamed until launch day, which is why 7.2 has no codename yet.
Release cadence and how updates work
WordPress ships two or three major releases a year: three in 2024 (6.5, 6.6, 6.7), two in 2025 (6.8, 6.9) and three planned for 2026 (7.0, 7.1 and 7.2). Each major version is followed by maintenance and security releases (7.1.1, 7.1.2 and so on), which WordPress installs automatically by default.
Security fixes are also backported to older branches for years. The October 28, 2026 security release patched every branch back to 4.7 (4.7.39). The 4.6 branch stopped at 4.6.30 in July 2025, so anything older than 4.7 no longer gets fixes.
If you want to take more control over which versions auto-install, the WP_AUTO_UPDATE_CORE constant in wp-config.php controls the policy: true for all updates, 'minor' for security/maintenance only (the default), or false to disable core auto-updates entirely.
Which version are you running?
The quickest answer on your own site is the footer of any wp-admin screen, which shows the version on every page. To check a site you do not have access to, or to see whether a version is current, use our free WordPress version checker. It reports the version, the active theme, and how far behind the latest release a site is, and the same guide covers all seven manual methods including WP-CLI and the RSS feed.
Frequently asked questions
What is the latest version of WordPress?
The latest version of WordPress is 7.1.4. As of November 2026 that is 7.1.4, a security release from October 28, 2026 on the 7.1 “Mary Lou” branch, which first shipped August 19, 2026. If you are on any earlier 7.x build other than 7.0.8, WordPress.org flags it as insecure, so update. Our WordPress version checker shows what a site is running.
When is WordPress 7.2 coming out?
WordPress 7.2 is scheduled for December 8, 2026. It reached Beta 4 on November 3, with RC1 planned for November 17. It will be the last major release of 2026 and ships with a new default theme.
How often is WordPress updated?
Major versions arrive two or three times a year. Maintenance and security releases ship in between as needed, often every few weeks, and install automatically on most sites. In 2026 that meant 7.0 in May, 7.1 in August and four 7.1.x updates by the end of October.
What PHP version does WordPress need?
WordPress 7.0 and 7.1 require PHP 7.4 or newer, and 7.2 keeps that minimum. Versions 6.6 to 6.9 need PHP 7.2.24, 6.3 to 6.5 need PHP 7.0, and 5.2 to 6.2 need PHP 5.6.20. The minimum is a floor, not a recommendation: run a PHP version that still gets security support.
How long are old WordPress versions supported?
There is no fixed window, but security fixes reach a long way back. The October 2026 security release covered every branch from 4.7 to 7.1. The 4.6 branch got its last fix in July 2025. Only the newest branch is fully supported, though, so the safe answer is to run the latest version.
What was the most important WordPress release ever?
Three versions stand out. WordPress 3.0 (June 2010) added custom post types and merged WordPress MU into core, turning WordPress from a blogging platform into a real CMS. WordPress 5.0 (December 2018) introduced the Gutenberg block editor, the biggest UX shift in WordPress history. WordPress 5.9 (January 2022) shipped the first block theme and Full Site Editing, the start of the post-classic-theme era. Each one fundamentally changed how people use the platform.
Wrap-up
WordPress has gone from a small b2 fork in 2003 to 55 major releases, and most people only care about two of them: the one they are running and the next one. Right now those should be 7.1.4 and 7.2, due December 8, 2026. Bookmark the table above and check back when 7.2 ships.


