Match the environment to your Joomla release
Joomla needs a web server, PHP and a supported database. The versions matter. A plan advertised as “PHP hosting” is not enough information: you need to know which PHP and database versions are available, and whether your chosen Joomla release supports them.
The table below summarises the Joomla 6.x supported baseline, rather than the lower absolute minimums that some database combinations may technically allow. Requirements can change, so consult the official technical requirements before a new deployment or upgrade.
| Component | Joomla 6.x supported baseline | What to check |
|---|---|---|
| PHP | 8.3.0 or newer | Choose a version supported by Joomla and your extensions |
| MySQL | 8.0.13 or newer | One supported database engine is required |
| MariaDB | 10.6 or newer | An alternative to MySQL |
| PostgreSQL | 14.0 or newer | Confirm extension compatibility before selecting it |
| PHP memory limit | At least 256 MB recommended | Heavier sites and extensions may need more |
You do not need all three databases. Choose one supported engine that also works with the extensions you intend to use. Joomla’s recommended versions can be higher than these baseline figures; review the live documentation when making the final choice.
PHP modules are part of compatibility
The PHP version is only one part of the environment. Joomla lists required modules including json, simplexml, dom, zlib and gd, as well as a suitable database driver such as mysqlnd, pdo_mysql or pdo_pgsql. It also recommends mbstring.
Ask your host which modules are enabled. If you administer a VPS, check the PHP runtime used by the website and the separate command-line runtime used by scheduled tasks. They can be configured differently.
The memory_limit setting is a PHP process limit, not the total memory of your server. The server also needs room for its operating system, database, web server and any concurrent PHP workers. A small memory setting should not be confused with a complete server-sizing recommendation.
Web servers and clean URLs
Joomla can run with Apache, Nginx or Microsoft IIS using a suitable configuration. Joomla’s documentation lists supported server versions. For Apache, mod_rewrite is relevant when enabling search-engine-friendly URLs. Nginx and IIS need their own rewrite configuration.
Test clean URLs on the new environment, including nested category pages and extension routes. A homepage that loads successfully does not prove that every route works.
Your extensions have a say too
Check the compatibility notes for templates, payment integrations, backup tools, image libraries and other extensions. Some require extra PHP modules, a different memory limit or a newer PHP version. Third-party code may also have narrower database support than Joomla itself.
For an upgrade, reproduce your site on a staging environment and test it against the target stack. Updating PHP on a live site without checking its extensions first can turn a routine hosting change into an application problem.
A host’s checklist
Before you buy or deploy, confirm:
- The Joomla release and each important extension support the proposed environment.
- The web and command-line PHP versions and modules are suitable.
- TLS certificates can be installed and renewed.
- You have secure file access and an appropriate way to manage the database.
- Scheduled tasks, outbound email and clean URLs can be configured.
- Files and databases can be backed up and restored together.
- Someone owns updates and security after launch.
On a self-managed provider such as Vultr, these are setup and maintenance decisions you make. See our Vultr planning guide for the next steps.
Source: Joomla! official technical requirements for 6.x. Always use the live documentation for your exact Joomla version.