How to Find Joomla Template Files

Identify the template before browsing files

In Administrator, open System → Templates and determine whether you need a Site Template or Administrator Template. Select the template name to open Templates: Customise. Joomla provides separate template areas for the frontend and Administrator, so confirming the package first prevents edits to the wrong application.

Use Templates: Customise to inspect the file tree

The Editor tab in Templates: Customise displays the files and folders Joomla makes available for that template. Current Joomla help describes this screen as the place to inspect and edit template source code. Use it to understand the template structure before making any filesystem changes.

Know the normal filesystem locations

Site templates are installed below the Joomla /templates directory, while Administrator templates are below /administrator/templates. Modern templates may also place assets below /media/templates/site or /media/templates/administrator. The exact files present depend on the template package rather than on one universal folder list.

Find overrides under the template's html folder

Joomla template overrides normally live beneath the active template's /html directory. Component, module, plugin, and layout override paths mirror the Joomla output they replace. For example, Joomla documentation shows module overrides such as /templates/cassiopeia/html/mod_login/default.php.

Do not edit distributed template files casually

Joomla documentation warns that files supplied as part of a template can be overwritten by an update. For small Cassiopeia CSS or JavaScript customizations, Joomla documentation recommends adding user.css or user.js rather than modifying distributed assets. For extension output changes, use template overrides.

Use the hosting filesystem when Administrator is insufficient

A hosting file manager, SFTP, or SSH can show the complete installed template tree, including files not convenient to inspect through Joomla. Confirm the Joomla document root first and take a backup before changing code. File ownership and permissions should follow the hosting environment's secure configuration.

Document which files are custom

Keep a record of user-created CSS, JavaScript, overrides, child-template files, and other intentional customizations. That makes Joomla and template upgrades easier to review and helps distinguish local work from vendor files when troubleshooting an unexpected frontend change.


Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.

Open a Support Ticket