Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is WordPress LTS? A Plain Explanation

Short answer

WordPress LTS does not exist, because WordPress has no long-term support version. Only the latest major release is actively supported, and security fixes reach older branches only as a courtesy, with no promise or fixed date. To stay supported, update to each new major release and keep PHP and your database on versions that still receive fixes.

Key takeaways

  • WordPress has no LTS version: only the latest major release is actively supported as of November 2026.
  • Security fixes may reach older WordPress branches as a courtesy, but WordPress gives no promise or date for them.
  • WordPress stopped security updates for versions 4.1 through 4.6 in July 2025, after they had run for 9 or more years.
  • PHP does have dated support: PHP 8.2 ends on 31 December 2026, while PHP 8.5 runs until 31 December 2029.
  • MySQL 8.4 LTS and MariaDB 10.11 LTS give your database a fixed support window, unlike WordPress core.

What is WordPress LTS?

WordPress LTS does not exist, because WordPress has no long-term support version.

LTS stands for long-term support. It means one version gets security fixes for a fixed, stated period, often several years, while newer versions keep coming out.

Many people search for WordPress LTS because other software works that way. Ubuntu, PHP, MySQL and MariaDB all publish LTS or dated support windows. WordPress core does not follow that model.

Does WordPress have an LTS version?

No, WordPress has no LTS version as of November 2026.

WordPress.org states this in plain terms on its Supported Versions page. It says there is no fixed period of support and no Long Term Support version such as Ubuntu's.

The same page says the only current officially supported version is the last major release of WordPress. A major release is the first two numbers, such as 7.1, while a minor release adds a third number, such as 7.1.4.

That rule is simple to apply. If your site runs the latest major release, it is supported. If it runs an older major release, it is not actively supported, even if it still works.

What does LTS mean in software?

LTS means a version receives security fixes for a set number of years, with no new features added.

An LTS release is a promise about time. The vendor states a start date and an end date, and it fixes security faults in that version until the end date.

MySQL explains this model in its MySQL Releases manual. An LTS series gets only necessary fixes, keeps the same data format, and follows the Oracle Lifetime Support Policy, with 5 years of premier support and 3 years of extended support.

LTS suits teams that want few changes. They pick one version, plan one upgrade every few years, and avoid new features in between. WordPress takes the opposite path: it ships new major releases often and asks site owners to move with them.

How does WordPress support older versions instead?

WordPress backports some security fixes to older branches as a courtesy, with no guarantee and no timeframe.

That sentence comes from WordPress.org's Supported Versions page. A backport is a fix from a newer release applied to older code.

The courtesy has limits. WordPress stopped security updates for versions 4.1 through 4.6 in July 2025, as announced on WordPress News. Those versions were first released 9 or more years ago, and over 99% of WordPress installations ran a more recent version.

The same announcement repeats the core rule: the only actively supported version of WordPress is the most recent one. Backports may help for a while, but they can stop at any time.

WordPress branchSupport status as of November 2026What it means for you
Latest major releaseActively supportedYou get new features, bug fixes and security fixes
Older branches, 4.7 and laterCourtesy backports onlySome security fixes may arrive, with no promise
Versions 4.1 through 4.6No security updates since July 2025No new fixes from the WordPress Security Team
Beta and nightly buildsNot supportedUse them only for testing, not for a live site

The release cycle behind this model is covered in our guide to what a WordPress release cycle is.

How do PHP, MySQL and MariaDB LTS versions fit in?

PHP, MySQL and MariaDB do have LTS or dated support, so your server stack can have a fixed support window even though WordPress core does not.

WordPress runs on PHP and a database, so those two layers matter as much as WordPress itself. A site can run current WordPress on an old PHP version and still be at risk.

WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support, as of November 2026, on its Requirements page. It also notes that WordPress still works with PHP 7.4 and MySQL 5.5.5, but those versions have reached end of life and may expose a site to security risks.

The Make WordPress Hosting team recommends PHP 8.4 or later for production, in its Server Environment handbook. It notes that PHP 8.4 is fully supported by WordPress 6.7 and later, and PHP 8.5 is fully supported by WordPress 6.9 and later.

PHP versionSecurity fixes untilStatus as of November 2026
PHP 8.231 December 2026Security fixes only, ending soon
PHP 8.331 December 2027Security fixes only
PHP 8.431 December 2028Active support
PHP 8.531 December 2029Active support

These dates come from the PHP Supported Versions page. Each PHP branch gets about 2 years of active support, then about 2 years of security fixes only.

The database side has its own LTS dates. MySQL 8.4 LTS follows 5 years of premier support plus 3 years of extended support, according to the MySQL Releases manual. MySQL 8.0 reached end of life in April 2026, so 8.4 LTS is the safer pick for a new site.

MariaDB lists 4 maintained LTS series as of November 2026. MariaDB 10.11 runs until 16 February 2028, and MariaDB 11.8 runs until 4 June 2028.

MariaDB 11.4 runs until 29 May 2029, and MariaDB 12.3 runs until 12 June 2029, according to the Make WordPress Hosting Server Environment handbook. MariaDB 10.6 reached end of life on 6 July 2026.

Our guide on how to choose WordPress hosting explains how to check these versions before you pick a plan.

How do you check which version your site runs?

Log in to your WordPress dashboard and look at the version shown at the bottom of the At a Glance box.

WordPress.org gives this exact check in its announcement about versions 4.1 through 4.6. An out-of-date version shows an update notice in the dashboard.

To check PHP and the database, go to Tools, then Site Health, then the Info tab. That screen lists your PHP version and your database version.

Compare the numbers you see with the tables above. If WordPress is not the latest major release, or PHP ends within a few months, plan an update.

  1. Open your dashboard and note the WordPress version.
  2. Open Tools, then Site Health, then Info, and note the PHP and database versions.
  3. Compare all 3 numbers with the current supported versions.
  4. Make a full backup before you change any of them.

What should you do if your site runs an old WordPress version?

Update to the latest major release after a backup, and test the update first if your site uses many plugins or a custom theme.

Start with a backup, because an update can clash with an old plugin or theme. Our guide to how to back up WordPress walks through the steps.

Then update WordPress itself, then update your plugins and theme. If a plugin has not been updated for a long time, check it with our guide to how to find abandoned WordPress plugins.

If your host still runs PHP 8.2, ask about moving to PHP 8.4 or 8.5. PHP 8.2 stops getting security fixes on 31 December 2026, so a move before that date removes a known deadline.

WordPress 7.1 was released on 19 August 2026, according to the Make WordPress Hosting WordPress 7.1 Server Compatibility post. WordPress 7.1 requires PHP 7.4 or later and is fully compatible with PHP 7.4, 8.0, 8.1, 8.2, 8.3, 8.4 and 8.5, so the PHP move and the WordPress move can be planned together.

What mistakes should you avoid?

Do not treat an old WordPress version as safe just because the site still loads.

A site can look fine while it misses security fixes. The absence of a visible error is not proof that the version is supported.

  • Staying on a branch that lost security updates, such as 4.1 through 4.6 after July 2025.
  • Updating WordPress but leaving PHP 8.2 or an old database in place.
  • Picking a host plan without checking its PHP and database versions first.
  • Skipping the backup before a major update.
  • Assuming a plugin will keep working on old WordPress versions: authors drop old versions over time, as explained in our guide to what happens when a plugin is closed on WordPress.org.

The safe habit is short and repeatable. Run the latest major WordPress release, run PHP and a database that still receive fixes, and check the numbers after each major release.

Frequently asked questions

Is there a WordPress LTS version I can install?

No. WordPress has no LTS version, and no version is sold or labelled as a long-term support release. Only the latest major release is actively supported. If you want a fixed support window, you can get one from PHP, MySQL or MariaDB, but WordPress core itself still needs regular major updates.

How long does WordPress support each major release?

There is no fixed period. Support ends in practice when the next major release ships, because only the latest major release is actively supported. Security fixes may be backported to older branches as a courtesy, but WordPress gives no promise and no date for those backports.

Is it safe to stay on an old WordPress version if my site still works?

No, it is not safe to treat a working site as a supported site. An old version may miss security fixes, and plugin and theme authors drop old versions over time. Check your version in the dashboard, make a backup, and update to the latest major release.

Which PHP version should I use with WordPress in November 2026?

Use PHP 8.4 or 8.5 if your plugins and theme support them. WordPress recommends PHP 8.3 or greater, and the hosting team recommends PHP 8.4 or later for production. Avoid PHP 8.2, which stops getting security fixes on 31 December 2026, and avoid PHP 7.4, which is long past end of life.

Do plugins and themes have LTS versions?

Most do not. Plugin and theme authors set a minimum WordPress version and drop older versions when they stop testing them. Check the last update date and the tested-up-to version on each plugin page, and replace any plugin that has not been updated for a long time.

Sources

  1. Supported Versions WordPress.org
  2. Dropping security updates for WordPress versions 4.1 through 4.6 WordPress News
  3. Requirements WordPress.org
  4. Server Environment Make WordPress Hosting
  5. Supported Versions PHP
  6. MySQL Releases: Innovation and LTS MySQL Documentation
  7. MariaDB Server 10.6 Reaches End of Life on July 6th MariaDB.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test