Try Joomla without XAMPP (or any local server)

You do not need XAMPP to run Joomla, and for Joomla 6 a stock XAMPP will not work at all. The newest XAMPP release, from 19 November 2023, ships PHP 8.2.12. Joomla 6 sets a floor of PHP 8.3.0, so the pre-installation check stops you before you start. An online sandbox opens a clean Joomla install in your browser instead, with nothing to download.

XAMPP is only one way to run a web server, PHP, and a database on your own machine. Plenty of guides treat it as the only door into Joomla. It is not. This guide is updated for September 2026 with the current XAMPP, PHP, and Joomla version numbers. It covers why the local route costs more than people expect, and the faster way to get a working free Joomla test site. Want to skip ahead? You can open one right now and read the rest after.

Can you try Joomla without XAMPP?

Yes. Joomla needs a web server, PHP, and a MySQL, MariaDB, or PostgreSQL database, per the 2026 technical requirements in the Joomla Programmers Documentation. XAMPP is only a convenient way to bundle those parts on your own computer. Any environment that meets those requirements runs Joomla, including managed hosting, a Docker container, or an online sandbox that hosts the site for you. XAMPP is never strictly required.

The reason people reach for XAMPP anyway is habit. For years the standard advice for trying Joomla locally has been to install XAMPP or MAMP first, then Joomla on top. That works, but it front-loads ten minutes of plumbing onto a job that might take you two minutes once you are actually inside the Administrator. If your goal is to vet an extension, preview a template, or reproduce a bug, the stack is pure overhead.

Why will a default XAMPP not run Joomla 6?

The short answer is version drift: XAMPP has not shipped a new release since 19 November 2023, and Joomla moved on. As of September 2026 the newest packages on the Apache Friends download page are XAMPP 8.2.12 for Windows and Linux (Apache Friends, XAMPP downloads, 2026). They carry PHP 8.2.12, MariaDB 10.4.32, and Apache 2.4.58. Joomla 6.1 sets PHP 8.3.0 as its supported minimum, with MariaDB 10.4 or MySQL 8.0.13 as the database floor (Joomla Programmers Documentation, Technical Requirements, 2026). XAMPP’s MariaDB clears that absolute floor, though it sits below the MariaDB 10.6 that Joomla officially supports, and every current XAMPP download misses the PHP bar.

The macOS packages sit further back still, at PHP 8.2.4 and MariaDB 10.4.28 from the April 2023 build. So the answer is not “pick the right XAMPP”. There is no XAMPP package in 2026 that installs Joomla 6 out of the box. You would download it, then watch the pre-installation check refuse to go green. Fixing that means replacing XAMPP’s PHP and database with newer builds by hand, which is exactly the yak-shaving a test environment is supposed to save you.

Is PHP 8.2 still supported?

Only just, and not for much longer. PHP 8.2 left active support on 31 December 2024 and its security support ends on 31 December 2026 (The PHP Group, Supported Versions, 2026). Testing next year’s Joomla on a PHP branch that stops getting fixes this year is not a realistic test run of your live site.

The same numbers, laid out component by component:

Does XAMPP still work for Joomla 5?

Yes. Joomla 5 asks for PHP 8.1.0 as its minimum, with MariaDB 10.4.0, MySQL 8.0.13, or PostgreSQL 12.0 (joomla/Manual, Joomla 5.1 Technical Requirements, 2026). XAMPP 8.2.12 clears every one of those with PHP 8.2.12 and MariaDB 10.4.32, so a stock XAMPP will install Joomla 5 today. The version gap only bites on Joomla 6.

The problem is that Joomla 5 is on its way out. Regular bugfix support for the 5.x series ends on 13 October 2026, with security-only fixes running to 12 October 2027. Joomla 6.2 is scheduled for that same October 2026 date (Joomla Project, Roadmap, 2026). Standing up a local stack that can only reach the outgoing series is a short-lived win. If you want to compare the two, we walk through Joomla 5 vs Joomla 6 and which one to test on.

How do you try Joomla without XAMPP or any local server?

You use an online sandbox, which hosts the Joomla for you. JInstant creates a clean, isolated Joomla install on a real server and emails a one-click link that signs you straight into the Administrator as a Super User. There is no XAMPP, no MAMP, no PHP to configure, and no database to create. You go from click to a working back end without touching a local stack. Here is the whole flow:

1. Pick your Joomla and PHP version. Choose Joomla 6.1 or 5.4 and a PHP version it supports. There is no stack to download and nothing to configure first.
2. Let the sandbox create the install. A clean, isolated Joomla spins up on a real server with the database and configuration already handled. No XAMPP, no MAMP, no MySQL setup.
3. Log in with one click. A private link arrives by email and opens the Joomla Administrator signed in as a Super User. It only needs your email, so there is no long signup form.

It is a real Joomla install, not a locked-down demo, and it runs a current release. The Joomla Project shipped 6.1.3 and 5.4.8 on 18 August 2026 (Joomla Project, Release News, 2026), and a fresh sandbox gives you the current point release of whichever series you pick. You get the actual Super User login and full control of the back end, so you can upload any extension, template, or package, change whatever you like, and deliberately break things. Each site runs in its own isolated container, so your testing never touches anyone else. You can open a Joomla 6.1 or Joomla 5.4 site directly.

What about MAMP, WAMP, or Docker instead?

MAMP, WAMP, and Docker are good tools, and they carry the same setup tax as XAMPP: you still stand up and tear down the environment yourself. MAMP, WAMP, and Docker each ask you to install software, configure PHP and a database, run the Joomla installer, and clean up afterwards. For a long-lived local project that control is worth paying for. For a quick, throwaway test it is the part you are trying to avoid.

They hit the same version wall, too. A 2024 Joomla community thread opened with the claim that MAMP PRO on the Mac was dead (templaza/astroid-framework discussion #654, April 2024). The replies corrected that, and MAMP PRO 7 arrived in July 2024. The real complaint in the thread survived the correction, though: MAMP PRO 6 bundled MySQL 5.7, well under the MySQL 8.0.13 that Joomla 5 requires. Bundled stacks lag the CMS, and you are the one who has to notice. A hosted sandbox that always runs a current Joomla on a supported PHP and database is one less thing to check.

For a fuller comparison of every route, see our guide to spinning up a free Joomla test site.

The official trial at launch.joomla.org

Joomla runs its own free hosted trial, but it is built for a longer evaluation rather than a quick throwaway. launch.joomla.org gives you a genuine hosted Joomla 6.1 or 5.4 maintained by the project, on a subdomain with 500MB of disk space. Paid upgrades that lift those limits start at $5 per month (launch.joomla.org, the official Joomla trial, 2026). The signup asks for first name, last name, email, password, country, and a phone number for TXT message verification.

The site is persistent rather than disposable, which sounds like an advantage until you read the terms. You keep it only as long as you log in and click a renew button once every 30 days. That model suits someone sizing Joomla up over weeks. It is heavier than you want when the job is “open a clean install, try this one extension, throw it away.” An email-only, auto-disposing sandbox fits that job better, which is the gap JInstant fills. We compare them side by side in our launch.joomla.org alternative write-up.

What can you do once you are in?

Anything you would never risk on a live site. You get a real Super User login on a clean install, in an isolated container, and the back end is fully yours for the four hours before the site deletes itself. The common jobs are exactly the ones the XAMPP setup used to gate:

• Vet an extension or template before it touches production. You can safely test a Joomla extension on a throwaway install, and our walkthrough on how to test a Joomla extension covers it step by step.
• Test an update or a major upgrade and see what breaks before you touch the real site, the way our guide to testing a Joomla update before going live lays out.
• Compare two versions side by side, say a fresh Joomla 5.4 next to a clean Joomla 6.1.
• Reproduce a client bug on a clean install to learn whether it is the extension, the template, or the config.
• Learn the Joomla Administrator, or demo it to someone, without a site that matters on the line.

Joomla still powers 1.1% of all websites and 1.7% of those whose CMS is known, measured on 1 September 2026 (W3Techs, Usage statistics and market share of Joomla). That is a lot of people who need a safe place to experiment without standing up a server first.

How does this compare to WordPress Playground?

WordPress users have had instant, no-setup sandboxes for years, and Joomla has not. WordPress Playground runs WordPress in the browser with no install using WebAssembly (WordPress Playground documentation, 2026), and hosted options like TasteWP and InstaWP spin up a throwaway site in seconds. The Joomla community asked out loud for the same thing in a GitHub discussion opened on 4 July 2024, requesting “something like wp-playground but for Joomla” (joomla/joomla-cms discussion #43744).

The mechanics differ. WordPress Playground runs in your browser tab. JInstant runs each Joomla on a real, isolated server and hands you a one-click admin link, so the site behaves like hosting rather than a simulation. The experience is the one Joomla was missing: pick a version, click once, and you are in a clean install with no XAMPP in sight. If you want the wider picture, our online Joomla sandbox guide covers what the term means and which tools qualify.

Where a sandbox is the wrong tool

A disposable sandbox is not a replacement for hosting or for a proper staging server. A JInstant site lasts four hours and then deletes itself with no backup. It runs on a subdomain you do not own, and it starts from a clean install rather than a copy of your live database. It is built for a fast, throwaway experiment, not for a live site.

So if you need to test against your own content, restore a backup of production onto a Joomla staging site instead. If you need the site to still be there next week, use hosting. And if you are doing week-long development work with your own editor and version control, a local stack still earns its keep. The sandbox wins on the short jobs: the extension you want to vet in ten minutes, the upgrade you want to watch fail somewhere harmless, the bug you want to reproduce on a clean install.

Conclusion

XAMPP is a habit, not a requirement, and in September 2026 it is a habit that no longer reaches Joomla 6 at all. Its newest release is nearly three years old, and its PHP is a branch that stops getting security fixes in December 2026. It also makes you stand up and tear down a whole local stack for a job that is often two minutes of real work. When you just need a clean install to test an extension, test an upgrade, or chase a bug, an online sandbox is faster and leaves nothing behind. Next time, skip the stack: open a clean Joomla test site, do your thing, and walk away.

Frequently asked questions