How to Rename htaccess.txt to .htaccess for Joomla
Confirm that the site is using Apache-compatible .htaccess rules
Joomla ships a preconfigured htaccess.txt for Apache-style per-directory configuration. Before renaming it, confirm that the web server supports .htaccess and that the hosting configuration allows overrides. Nginx does not use .htaccess, so renaming the file on an Nginx-only site will not enable rewriting.
Back up an existing .htaccess file first
Look in the Joomla root for an existing .htaccess. Hosting platforms, security tools, redirects, caching systems, and administrators may already have added important directives. Do not overwrite that file blindly. Save a copy and compare or merge required rules with Joomla's current htaccess.txt when an existing file is already active.
Rename the file in the Joomla root
Using the hosting file manager, SFTP, or SSH, rename htaccess.txt to .htaccess in the same directory as Joomla's main index.php. On Unix-like systems a leading dot makes the filename hidden, so configure the file manager to show hidden files if .htaccess seems to disappear after the rename.
Review RewriteBase only when the environment requires it
Joomla's supplied rules include a commented RewriteBase directive. Joomla documentation notes that some installations may need it, particularly when Joomla runs in a subdirectory. Do not uncomment or change RewriteBase automatically; first test the default file and follow the host's Apache configuration when a base-path problem is demonstrated.
Enable URL Rewriting only after the file is ready
Open System → Global Configuration → Site and enable Use URL Rewriting after Search Engine Friendly URLs is working. Save, then test the frontend. Renaming htaccess.txt alone does not toggle Joomla's URL Rewriting setting, and enabling the Joomla setting without functioning server rules can cause clean URLs to return errors.
Watch for immediate 403, 404, or 500 errors
If the site fails immediately after activating .htaccess or URL Rewriting, revert the last change and inspect the web-server error log. An unsupported directive can cause a 500 response, denied overrides can prevent the rules from being used, and incorrect rewrite handling can produce 404 responses. Do not keep adding random directives.
Keep Joomla's distributed file as your baseline
When Joomla updates its supplied htaccess.txt, compare relevant changes with your active .htaccess rather than replacing custom server rules without review. Document intentional redirects, security directives, and RewriteBase changes so a future administrator can distinguish Joomla's baseline from site-specific configuration.
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.