Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 37 ยท Getting Started

Joomla Versions and Requirements

Understand Joomla's version numbers, long-term support, upgrades and server requirements for PHP, database and extensions, with a runnable requirements checker.

Before you install Joomla you need to know two things: which version to choose, and whether your server can run it. Joomla publishes clear version rules and system requirements, but the exact numbers change with each major release, so this lesson teaches the system and shows you where to confirm the current figures. The runnable example is a stand-in requirements checker whose table you can edit to match the official requirements page.

The numbers in this lesson are a snapshot meant for learning. Always confirm the minimum PHP and database versions for the release you install on the official Joomla requirements page, because they rise over time.

How Joomla numbers its versions

Joomla uses three numbers, such as 5.2.3:

  • Major (5): large changes. Extensions and templates built for an older major version may not work and need an update. Major versions are released every couple of years.
  • Minor (5.2): new features, released several times a year within a major line.
  • Patch (5.2.3): bug and security fixes only.

Updating patch and minor releases within the same major line is normally straightforward. Moving to a new major version is a project: check that every extension and your template support it, test on a copy of the site, then upgrade.

Support and long-term releases

Each major line is supported for a limited period: first with regular bug and feature releases, then with security fixes only, and then it ends (end of life). An unsupported version gets no security fixes, which makes it a risk for any public site. When you start a site, choose the newest stable major release that your key extensions support, and note its end-of-life date in your project plan.

flowchart LR
    A["Active development<br/>features and fixes"] --> B["Security fixes only"]
    B --> C["End of life<br/>no more updates"]

Every major line moves through these phases. Plan your upgrade before the last one.

Some history helps you read old tutorials: Joomla 3 was the long-running line with a Bootstrap 2/3 look; Joomla 4 (2021) brought a new administrator, Bootstrap 5 and the Cassiopeia template; Joomla 5 (2023) cleaned up deprecated code and raised requirements; Joomla 6 followed in late 2025. Old articles that mention "JFactory" screens or the Protostar template describe version 3, and instructions often differ slightly.

Server requirements

Joomla needs three layers on the server.

  1. A web server: Apache, Nginx or Microsoft IIS. Apache with mod_rewrite is the most common choice and works with the supplied htaccess.txt.
  2. PHP: a supported version, with required extensions. Joomla 5 requires at least PHP 8.1; newer majors raise the minimum, so use a current PHP.
  3. A database: MySQL (8.0 or newer), MariaDB (10.4 or newer) or PostgreSQL (12 or newer) for Joomla 5; check the page for your release.

Required PHP extensions typically include json, simplexml, dom, zlib (for downloads and updates), mbstring, gd (image handling), fileinfo, pdo with a database driver such as mysqli or pdo_mysql, and intl is recommended. Joomla's installer shows a pre-installation check that lists what is missing and which values should be raised, such as memory_limit, upload_max_filesize and post_max_size.

What a Joomla server needs

Web server Apache, Nginx or IIS
PHP A supported version plus extensions
Database MySQL, MariaDB or PostgreSQL
HTTPS A certificate for the live site

Check the official page for exact versions

1 / 2

Check a server before you install

When you talk to a hosting provider, you want clear yes/no answers. The checker below takes a description of a server and compares it with a requirements table. Edit the table to match the official numbers.

JS Stand-in: a requirements checker

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Host A passes. Host B fails on several counts; the output lists every problem in one go, which is how you would want an installer's pre-check to behave. The key detail is the atLeast function: version numbers must be compared number by number, because as plain strings "10.4" would sort before "8.0".

JS Stand-in: why string comparison fails

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Practical choices

  • Hosting: pick a host that advertises Joomla support, lets you choose the PHP version, and offers daily backups.
  • PHP version: use the newest one that Joomla and your extensions support; old PHP versions stop getting security fixes too.
  • Staging: keep a copy of the site for testing updates. Local development is covered in the next chapter.
  • Extensions first: before choosing a version, list the third-party extensions you need and verify each has a release for it.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. In the version number 5.2.3, what does the last number stand for?

    Patch numbers contain fixes only. Major numbers mark big changes and minor numbers add features.
  2. 2. Why is it risky to run an end-of-life Joomla version on a public site?

    Without security updates, known vulnerabilities stay open for attackers.
  3. 3. What should you do before upgrading to a new major version?

    Major releases can break extensions and templates, so verify compatibility and test on a staging copy.
  4. 4. Which check compares versions correctly?

    Part-by-part numeric comparison treats 10.10 as larger than 10.9, unlike text sorting.

Summary

  • Joomla versions are major.minor.patch; major upgrades need compatibility checks and testing.
  • Each major line has an active phase, a security-only phase and an end of life; never run unsupported versions publicly.
  • A server needs a web server, a supported PHP with the required extensions, and a supported database.
  • Always confirm exact minimums on the official requirements page for your release.
  • Compare versions numerically, part by part, never as plain text.

Next: Set Up a Local Environment for Joomla