Skip to main content
Apache Handlers is a niche tool for telling Apache to process files of a given extension with a specific handler module. The form writes an AddHandler line to your .htaccess.
Apache Handlers form with handler and extension fields

​
What it does

By default, Apache and LiteSpeed know how to handle every common file type: .html, .php, .css, .js, images. This tool exists for the rare case where you need an unusual extension treated as a known handler. A made-up example: you want .tpl files to be parsed as PHP. You’d add a handler with Handler: application/x-httpd-php and Extension: tpl. In practice, almost no modern stack needs this. Frameworks include their own routing.

​
Add a handler

1

Type the handler name

Common values: application/x-httpd-php (parse as PHP), cgi-script (run as CGI), server-parsed (parse Server-Side Includes).
2

Type the extensions

Space-separated, no dot. Example: tpl tmpl.
3

Click Add Handler

cPanel writes an AddHandler line to ~/public_html/.htaccess. Effect is immediate.

​
Common questions

Either the .htaccess line was overridden by something deeper in the directory tree, or the handler name is wrong. Open ~/public_html/.htaccess directly and check the AddHandler line is there. Test with a simple file (e.g., test.tpl containing <?php phpinfo(); ?>).
Honestly, almost never. The case we still see occasionally: legacy applications shipping templates with unusual extensions that need PHP parsing. If you’re on a modern stack (WordPress, Laravel, Drupal, Magento), you don’t need this. If you’re not sure whether you need it, you don’t.

​
Need a hand?