Drop any file to identify it
No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.
Drop it!
Let go to identify this file.
Couldn't identify this file
Need to convert it? fwip it →
An .htaccess file is a directory-level Apache configuration file. Drop one into a folder on an Apache web server and it overrides the global config for that folder and everything beneath it. The single most common use is URL rewriting via mod_rewrite: pretty URLs like `/blog/my-post` getting silently mapped to `/index.php?post=my-post`. Almost every WordPress install has an .htaccess file at its root doing exactly this.
Beyond rewrites, .htaccess can password-protect directories (with .htpasswd), set custom error pages, redirect URLs, gzip-compress responses, set caching headers, block specific IP addresses, and force HTTPS. The syntax is Apache directives — `RewriteRule`, `Redirect`, `Header`, `AuthType` — one per line. Comments start with `#`. A misplaced character will return a 500 Internal Server Error for the entire directory, so test changes carefully and keep a backup.
The critical caveat: .htaccess is Apache-only. Nginx, Caddy, and IIS don't read it — those servers configure routing in their own central config files. Apache itself recommends putting directives in the main config (`httpd.conf`) when possible, because .htaccess is checked on every request and slightly slows things down. .htaccess exists primarily because shared hosting lets users configure their site without root access to the main config. If you control the server, the central config is faster.