Skip to main content
MIME Types tells the web server what Content-Type header to send for files of a given extension. Browsers use that header to decide whether to render, download, or ignore the file.
MIME Types form with content-type and extensions fields

​
When you’d use it

The server already knows the right MIME type for .html, .css, .js, .png, .jpg, .pdf, and most modern formats. Reach for this tool only when you serve a file extension the server doesn’t know. Cases we still see:
  • .webmanifest: a PWA manifest. Some Apache configs don’t set the right type. Map to application/manifest+json.
  • .epub: ebook download. Map to application/epub+zip.
  • .wasm: WebAssembly binaries. Map to application/wasm.
If a browser is treating your file as plain text or downloading it instead of rendering, the MIME type is the usual culprit.

​
Add a MIME type

1

Type the content type

Examples: application/wasm, application/manifest+json, application/epub+zip. The full list is in the IANA registry.
2

Type the extensions

Space-separated, no dot. Example: wasm.
3

Click Add

cPanel writes an AddType line into ~/public_html/.htaccess. Effective immediately on the next request.

​
Common questions

The server doesn’t have .webmanifest mapped. Add a MIME type with Type: application/manifest+json and Extension: webmanifest. Browsers will then accept the manifest.
Either the MIME type is wrong, or the response includes Content-Disposition: attachment. Add the right MIME type here first; if downloads continue, check your application code (or .htaccess) for a Content-Disposition line.
No. The server defaults already cover them. Adding a duplicate entry is harmless but pointless. Only add types the server doesn’t recognize by default.

​
Need a hand?