Best Free Joomla Templates : 10 Picks Reviewed [2026]
Cassiopeia plus a child template is genuinely the right answer for many sites. That is the bar every free template has to clear.
You want a free Joomla template that looks decent, works on the Joomla line you run, and does not turn into a maintenance problem in eighteen months. The difficulty is that “free Joomla template” describes at least four quite different things, only two of which are safe to build a real site on.
This review covers the free template landscape for the supported Joomla lines as it stands in 2026 — Joomla 6 has been current since October 2025, with Joomla 5 still supported alongside it, and template selection works identically on both — what free actually means, how to evaluate a candidate before you commit, and which categories are worth your time. It starts where every honest version of this article has to start: with Cassiopeia, the template Joomla already installed for you.
Methodology
Free templates were assessed against the criteria below. We have not ranked named products by star rating, because ratings on abandoned templates are the most misleading signal in this category — a template with excellent reviews from 2021 is still a template with no releases for a current line.
| Criterion | What we checked | Fails if |
|---|---|---|
| Current-line support | A release published for the line you run (5.x or 6.x), not a J3 template with a compatibility note | No release for a current line — automatic disqualification |
| Update history | Releases across at least the last twelve months | Nothing shipped in two years |
| Override friendliness | Standard html/ override structure, child template support |
Layouts generated in PHP you cannot override |
| Accessibility of shipped markup | Heading order, focus visibility, colour contrast, landmark regions | Keyboard navigation broken out of the box |
| Asset weight | CSS and JS shipped on a default page, and how much is unavoidable | Multi-megabyte payload for a brochure page |
| Upgrade path | What happens when you outgrow it or the vendor stops | Content locked into proprietary shortcodes or builder data |
We name templates and frameworks only where we are confident about what they are and who maintains them. The free template market has a high churn rate and a long tail of one-person projects; naming a specific free template as a recommendation in an article that will be read in two years is how readers end up installing abandonware. The evaluation criteria below will outlive any list.
Start with Cassiopeia, and be honest about it
Cassiopeia is the front-end template bundled with Joomla 4 and Joomla 5. It is maintained by the Joomla project itself, ships with every release, is tested against every core change, and is the template every core layout is developed against.
The common criticism is that it looks plain. That is accurate and it is the point — it is a starting template, not a finished design. What it gives you is consistently undervalued:
- It cannot be abandoned. Its maintenance is the project’s maintenance. There is no vendor to go quiet.
- It is accessible out of the box in a way most commercial templates are not, because core accessibility work happens here first.
- It ships almost nothing. A default Cassiopeia page loads a modest CSS payload and essentially no JavaScript framework, which means your performance budget is spent on your content rather than on the template.
- Every Joomla tutorial applies to it. When you search for how to do something, the answer will be written against core markup.
- It supports child templates natively, which is the correct way to customise any modern Joomla template.
For a brochure site, a club, a small publisher, a charity or a professional services firm, Cassiopeia plus a child template plus a few hours of CSS is genuinely the right answer, and it is free in a way no commercial free edition is. That sets the bar: any other free template must beat it to be worth the risk it carries.
Building a Cassiopeia child template
Joomla 4.1 introduced child templates and Joomla 5 and 6 kept them. A child inherits everything from its parent and overrides only what you change, so the parent can be updated by core without destroying your work. This is the most important technique in this article.
Create the child from the admin
Go to System → Site Templates, tick Cassiopeia, and click Create Child Template. Joomla generates a new template directory containing a manifest and a minimal structure that inherits from the parent.
Do this before writing a line of CSS. Editing Cassiopeia directly works right up until the next Joomla update overwrites it, at which point you lose everything with no record of what you changed.
Add your own stylesheet
Create media/templates/site/cassiopeia_child/css/user.css. Since Joomla 4.1 a template’s CSS, JavaScript and images live under media/templates/site/ rather than in the template folder itself, and that is still where they live in Joomla 5 and 6. Cassiopeia loads a user.css automatically if present, so no manifest edit is needed. Put your overrides there.
Work with Cassiopeia’s CSS custom properties rather than fighting its rules. Redefining the colour and spacing tokens gets you most of a visual identity in a few dozen lines:
:root {
--cassiopeia-color-primary: #14532d;
--cassiopeia-color-link: #14532d;
--cassiopeia-color-hover: #166534;
--cassiopeia-font-family-body: "Inter", system-ui, sans-serif;
--cassiopeia-font-family-headings: "Inter", system-ui, sans-serif;
}Overrides: how you customise without forking
Override layouts in the child, never in core
To change the markup of an article, a module chrome or a core layout, copy the relevant file into templates/cassiopeia_child/html/, preserving the path structure. Note the split: PHP layout overrides stay in the template folder under html/, while CSS and other media assets live under media/templates/site/. An article layout override lives at html/com_content/article/default.php; a module chrome at html/layouts/chromes/.
Overrides in a child template survive both Joomla core updates and any parent template update. This is the whole architecture, and it is why building on core is a low-risk position rather than a compromise.
What “free” actually means
Four distinct things are sold as free Joomla templates, and the risk profile differs enormously between them.
| Category | What it is | Real cost | Risk |
|---|---|---|---|
| Core bundled | Cassiopeia — shipped and maintained by the project | None | Very low |
| Framework free tier | A starter template on a commercial framework, e.g. a base template on Gantry or Astroid | Learning the framework; upgrade pressure | Low to moderate — depends on the vendor’s health |
| Limited edition of a commercial template | The paid template with features removed and often a credit link | Feature ceiling, branding, upsell friction | Moderate — you are being funnelled towards a purchase |
| Independent free release | A one-off template from a developer or an agency’s portfolio piece | Nothing, until it stops being updated | High — most abandonment happens here |
| Abandoned | Anything with no release for a currently supported line | A rebuild, at the worst possible time | Do not install |
The framework free tier is the most interesting category professionally. Astroid and Gantry both offer a usable free starting point with a real layout system, a settings UI and an override architecture, and both stay maintained because the framework is a commercial product. Helix Ultimate follows the same pattern. You accept some vendor dependency in exchange for capability you would otherwise build yourself.
The eight places free templates actually come from
Rather than a ranked list of products that will be stale before you read it, here are the eight sources free Joomla templates come from, ordered by how safe each is to build on. The source tells you more about a template’s future than any screenshot does.
- Joomla core. Cassiopeia for the front end, Atum for the administrator. Maintained by the project, tested against every release.
- Framework vendor free tiers. A starter template on an actively developed commercial framework — Gantry and Astroid both operate this way. Maintained because the framework is the product.
- Free templates built on a maintained framework. Helix Ultimate is the well-known example: a free template whose underlying framework is commercially supported.
- Free editions of commercial templates. Feature-capped versions from established template clubs. Usually well built and deliberately limited.
- Agency portfolio releases. A studio publishes a template as marketing. Quality is often high; maintenance depends entirely on whether they still care next year.
- Community contributions on the Joomla Extensions Directory. Variable. The JED listing itself is not a quality signal — check the vendor’s own site for release dates.
- Starter and boilerplate templates from developers. Minimal, unstyled, intended as a foundation. Excellent if you write CSS; useless if you were hoping for a design.
- Nulled download sites. Paid templates distributed illegally, routinely backdoored. Never.
Sources one to four are where a professional should be looking. Five and six are viable if the evaluation checks pass. Seven suits developers who write their own CSS. Eight is not a source but an incident waiting to be logged.
How to evaluate a free template in fifteen minutes
Do this before you install anything on a site you care about. It is faster than recovering from a bad choice.
Check the release history first, not the demo
Find the vendor’s download or changelog page and look at dates. You want at least one release for the line you run and evidence of activity within the last twelve months. A template whose latest release predates your line has not been tested against it, whatever the compatibility badge says.
If you cannot find a changelog at all, that is your answer. A vendor who does not publish release notes is not running a maintained product.
Install it on a throwaway site, not your real one
Spin up a local or subdomain install on your line, apply the template, and load a page with real Joomla content — an article with an intro image, a category blog, a contact form, a search results page. Template demos are built from curated content; the failure modes appear on ordinary core output.
Pay attention to the pages the demo does not show: search results, the login form, an error page and a multi-level menu.
Run the three checks that matter
Open devtools’ Network tab on a plain article page and note the transferred size and request count. A brochure template shipping several megabytes before your images is spending your performance budget on itself.
Then unplug the mouse and Tab through the page: you must reach and operate the menu including dropdowns, see a visible focus ring at every stop, and never get trapped.
Finally, look for an html/ folder in the template directory. Its presence tells you the template overrides core layouts, and reading those files shows how far it has diverged from standard markup.
Many free templates are distributed with a “quickstart” package that installs Joomla plus the template plus demo content in one go. Never use a quickstart on an existing site — it installs a complete Joomla instance and will overwrite what is there. And on a new site, a quickstart bakes in the vendor’s extension choices, their sample articles and their module configuration, all of which you will then spend a day removing. Install the template on its own and build your own content.
Warning signs: templates that will trap you
These are the characteristics that turn a free template from a saving into a liability. Any one of them should make you look elsewhere; two together are disqualifying.
| Warning sign | Why it traps you |
|---|---|
| No release for a currently supported line | Untested against current core; a security patch may never come |
| Content stored in proprietary shortcodes | Switching templates leaves your articles full of unrendered [tags] |
| Requires the vendor’s own page builder for layout | Your page structure lives in the builder’s data, not in Joomla |
| Ships bundled third-party libraries at fixed versions | You inherit their patch schedule for code you did not choose |
No html/ override directory and hardcoded output |
You cannot correct their markup without editing the template |
| A required credit link in the footer | Removing it may breach the licence; keeping it is a permanent outbound link you did not choose |
| Positions named non-standardly with no documentation | Every module placement becomes trial and error |
| Support forum with unanswered threads months old | The vendor has moved on, whatever the download page says |
The shortcode point is the most expensive one. If a template introduces its own markup syntax into your article bodies, your content stops being portable, and changing template later means editing every article by hand or writing a migration script. A template is presentation; the moment it stores structure inside your content it has overstepped, and that is a hard no. Keep the boundary clean from day one — content in Joomla, presentation in the template — and every future decision stays cheap.
Performance: what a template costs you before your content loads
Template choice is one of the largest levers on page weight and it is decided before any content exists. The payload is fixed overhead paid on every page view. Rough expectations for a plain article page, before any of your own assets:
| Template type | Typical CSS + JS payload | What drives it |
|---|---|---|
| Cassiopeia, default | Small — tens of kilobytes | Core CSS only, essentially no JS framework |
| Minimal starter template | Small | Whatever you add |
| Framework free tier | Moderate — often several hundred kilobytes | Framework runtime, layout engine, icon set |
| Feature-rich commercial free edition | Moderate to large | Bundled slider, animation library, icon fonts, sometimes jQuery |
| Template with a bundled page builder | Large | Builder runtime loaded on the front end whether used or not |
Those bands are indicative rather than measured and vary by configuration, but the ordering is reliable. The practical point is that heavier templates load their weight unconditionally — a slider library ships on a contact page with no slider on it. Optimisation extensions such as JCH Optimize can combine and compress those assets and genuinely help, but combining CSS you never needed is worse than not shipping it. Check instead whether the template lets you switch off features you do not use; well-built ones expose that in template settings.
Accessibility: what to check on any free template
Joomla core has had sustained accessibility work and Cassiopeia benefits directly. Third-party templates vary from good to actively hostile, and the defects are consistent enough to check in a few minutes.
- Focus visibility. Many templates remove the browser’s focus outline for aesthetic reasons and replace it with nothing. Tab through the page — if you lose track of where you are, the template is unusable by keyboard.
- Dropdown menus that require hover. A submenu reachable only by mouse hover is unreachable by keyboard and by touch. Check that Tab and Enter open it.
- Heading order. Templates that style headings by size rather than by level produce pages that jump from
h1toh4. Screen reader users navigate by heading; a broken order breaks navigation. - Colour contrast in the shipped palette. Light grey body text on white is the most common failure, followed by low-contrast link colours and placeholder text.
- Landmark regions. Real
<header>,<nav>,<main>and<footer>elements rather than a page of nested<div>s, plus a skip link to main content.
None of these are hard to get right, which is why finding several together tells you something about how the template was built generally. A free template with good accessibility is usually well engineered in other respects too.
Free versus commercial: the honest comparison
Commercial Joomla templates typically run around €30–80 for a single site, with club subscriptions higher. There are cases where that is obviously correct spending, and cases where it buys you nothing.
| Your situation | Free is fine | Pay for it |
|---|---|---|
| Brochure site, under 30 pages, one person maintaining it | Yes — Cassiopeia child | No |
| You need a specific complex layout and cannot write CSS | No | Yes — a framework template with a layout builder |
| Agency building many similar client sites | Only if you standardise on one free framework tier | Usually yes — a developer licence pays for itself in hours saved |
| You need vendor support with a response commitment | No | Yes — support is most of what you are buying |
| Site must meet a formal accessibility standard | Cassiopeia child, audited | Only if the vendor publishes an accessibility statement |
| Long-lived site, low change rate, small budget | Yes | No — the subscription outlasts the need |
What you buy with a commercial template is threefold: support from someone obliged to answer, a layout system that saves you writing CSS, and a maintenance commitment. If you do not need all three, the case weakens considerably. Note that none of the three is design — a free template plus a designer’s afternoon usually beats a commercial template used as shipped.
Templates are extensions. They can contain PHP, they execute on every page load, and an abandoned one is unpatched code in your web root. Beyond that: never install a “free” copy of a commercial template from a nulled-download site. Those packages routinely carry injected backdoors, and the injection is usually in a template PHP file where nobody looks. Downloading a paid template for free is the most reliable way to have your site used for something you did not intend.
Frequently asked questions
Is Cassiopeia good enough for a real business site?
Yes, for the large majority of business sites. With a child template, some CSS custom property overrides and a decent typographic scale, it produces a clean, fast, accessible site that will not need rebuilding when the vendor loses interest — because there is no vendor. Where it falls short is complex marketing layouts, which is what a framework or a designer is for.
How do I know if a free template supports my Joomla version?
Check the vendor’s changelog for a release dated within your line — 5.x or 6.x — and check the template’s templateDetails.xml manifest for its declared Joomla version. A directory listing claiming compatibility is not evidence; a dated release note is. If there is no changelog at all, treat the template as unmaintained.
Can I edit Cassiopeia directly instead of making a child template?
You can, and the next Joomla update will overwrite your changes without warning. Child templates exist precisely to prevent this and take about thirty seconds to create from System → Site Templates. There is no scenario in which editing the parent is the better choice.
What does a free template’s credit link in the footer actually oblige me to do?
It depends on the licence, and you need to read it rather than assume. Joomla extensions are distributed under the GPL, which does not permit a vendor to forbid you from removing a link in code you have received — but vendors sometimes attach separate terms to support or to artwork. If the link matters to you, ask the vendor before installing rather than after.
Are template quickstart packages safe to use?
They are safe on a genuinely empty domain and destructive anywhere else, because a quickstart installs an entire Joomla instance rather than just a template. Even on an empty site they bring the vendor’s extension choices and demo content, which you then have to unpick. Installing the template alone onto a clean Joomla is nearly always the better route.
Why does my free template look nothing like the demo?
Because the demo is built from prepared content, specific module configurations and often extensions not included in the free download. This is normal across the whole category rather than dishonesty by one vendor, but it is why you should evaluate a template against your own content before committing. Ask the vendor which extensions the demo uses, and whether they are in the free package.
A template I like has not been updated in two years. Is that really a problem?
Yes. It has not been tested against a current Joomla line, it will not receive a fix if a vulnerability is found in it, and PHP itself moves under it — code written for PHP 7 throws deprecation warnings on 8.2 and errors on later versions. The template may load today and break on a routine PHP upgrade your host performs without asking you.