How to Rename htaccess.txt to .htaccess for Joomla

On Apache-compatible hosting, Joomla's htaccess.txt contains the distributed rewrite and security rules intended to be activated as .htaccess. Rename it carefully: an existing .htaccess may already contain important hosting, security, caching, or redirect directives.

Confirm .htaccess applies to your server

Use this procedure for Apache or a compatible server that honors per-directory .htaccess files. Nginx does not use .htaccess; changing the filename there will not configure URL rewriting.

If you are unsure which server handles the site, check the hosting control panel or ask the hosting provider before changing server files.

Back up any existing .htaccess

  1. Open the Joomla root—the directory containing index.php, configuration.php, and administrator/.
  2. Enable display of hidden files in the file manager or SFTP client.
  3. If .htaccess already exists, download or copy it before making changes.
  4. Compare it with Joomla's current htaccess.txt rather than overwriting it blindly.

Existing directives may control HTTPS redirects, security headers, access restrictions, caching, or another application.

Rename htaccess.txt

  1. Locate htaccess.txt in the Joomla root.
  2. Rename it exactly to .htaccess.
  3. Keep it in the same directory.
  4. Reload the site before changing anything else.

On Unix-like systems, the leading dot makes the file hidden. If it seems to disappear, enable hidden-file display.

Test before enabling URL Rewriting

Confirm the frontend and Administrator still load after the rename. If the server immediately returns a 500 error, restore the previous file and inspect the server error log; the host may disallow a directive or override.

Only after the active file works should you enable Use URL Rewriting under System → Global Configuration → Site.

Review RewriteBase only if needed

Joomla's supplied file includes guidance for RewriteBase. Some subdirectory installations need an appropriate value, but many installations do not. Test the default first and change the base only when the deployment path requires it.

Keep custom rules maintainable

When Joomla later ships an updated htaccess.txt, compare relevant changes with the active .htaccess. Do not replace site-specific redirects or hosting directives without review. Document intentional custom rules so future maintenance does not erase them accidentally.


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