In this article
What Is .htaccess?
The .htaccess (hypertext access) file is a directory-level configuration file for Apache web servers. It allows you to override server settings on a per-directory basis without editing the main server configuration. Common uses include URL redirects, access control, caching rules, and custom error pages.
The .htaccess file is read by Apache on every request to the directory it resides in, making changes take effect immediately without server restarts. This convenience makes it the standard way to configure Apache for shared hosting environments where you lack access to the main httpd.conf.
How .htaccess Configuration Works
Apache processes .htaccess directives using its module system, with mod_rewrite being the most commonly used module for URL manipulation.
- URL rewriting and redirects — mod_rewrite rules transform URLs using regular expressions, enabling clean URLs, HTTPS enforcement, and domain redirects
- Caching and compression — set browser caching headers with mod_expires and enable GZIP compression with mod_deflate to improve page load speed
- Access control — restrict access by IP address, require authentication with .htpasswd files, or block specific user agents and bots
Try it free — no signup required
Generate .htaccess Rules →When To Use an .htaccess Generator
Manually writing .htaccess rules requires knowledge of Apache directive syntax and regular expressions. A generator simplifies common configurations.
- HTTPS enforcement — redirect all HTTP traffic to HTTPS with a single rule, ensuring secure connections across your entire site
- Hotlink protection — prevent other sites from embedding your images and files by blocking requests with external referrer headers
- Custom error pages — define branded 404 and 500 error pages instead of Apache defaults, improving user experience during errors
Frequently Asked Questions
What is the difference between .htaccess and httpd.conf?
httpd.conf is the main Apache configuration file, loaded once at server startup. .htaccess files are read on every request and apply only to their directory. httpd.conf is faster because it avoids per-request file reads, but .htaccess is essential when you cannot modify server configuration directly, such as on shared hosting.
Does .htaccess affect server performance?
Yes, slightly. Apache must check for and read .htaccess files on every request in every directory in the URL path. For high-traffic sites with server access, moving directives to httpd.conf and disabling AllowOverride eliminates this overhead. For most sites, the impact is negligible.
What is the Nginx equivalent of .htaccess?
Nginx does not support .htaccess files. All configuration goes in the server block within nginx.conf or site-specific configuration files. Nginx reloads configuration only on explicit reload commands, which is more efficient but requires server access for every change.