How to Use the MIME Type Lookup
- Type a file extension (with or without the dot, e.g. "woff2") or a MIME type (e.g. "application/pdf") into the search box.
- The list filters instantly with fuzzy matching, showing each format’s extensions, MIME type and a short description.
- Click any row to copy the value, or use the nginx/Apache snippet buttons to copy server configuration you can paste directly into your config file.
What Is MIME Type Lookup?
A MIME type (officially a media type) is the two-part identifier — type/subtype, such as text/html, image/png or application/json — that servers send in the HTTP Content-Type header to tell browsers what kind of bytes they are receiving. Browsers decide how to render or download a resource largely from this header, not from the file extension.
MIME types are maintained in the IANA media type registry. Common examples include text/css for stylesheets, application/javascript for scripts, image/avif and image/webp for modern images, font/woff2 for fonts, and application/pdf for documents. Extensions map to MIME types through server configuration: nginx uses a types block mapping extensions to types, while Apache uses AddType directives or mime.types.
Wrong MIME types cause real bugs: CSS served as text/plain is blocked by strict MIME checking ("X-Content-Type-Options: nosniff"), JavaScript served as text/plain will not execute, fonts with the wrong type can fail CORS preflight checks, and downloads may render in the browser instead of downloading. That is why verifying Content-Type is a standard step when wiring up static hosting or a CDN.
When you add a new file format to a site — say .avif images or .wasm modules — you must ensure the server maps the extension to the correct MIME type (image/avif, application/wasm). This lookup gives you the correct value plus the exact config line for nginx or Apache, removing the guesswork.
Common Use Cases
- Fixing wrong Content-Type headers. Diagnose resources browsers refuse to parse because the server sends text/plain or application/octet-stream.
- Configuring nginx or Apache. Copy types-block or AddType snippets for new formats like AVIF, Wasm, WOFF2 or Markdown straight into your server config.
- CDN and object storage setup. Look up the correct Content-Type to set when uploading files to S3, Cloudflare R2 or another object store.
- Backend upload handling. Validate uploaded files by comparing the declared MIME type against expected extensions in server-side code.
- Writing download endpoints. Choose the right type for Content-Type and Content-Disposition headers when forcing file downloads.
Frequently Asked Questions
What is a MIME type used for?
The MIME type travels in the HTTP Content-Type header and tells the browser (or API client) what format the response body is — HTML, JSON, PNG, PDF and so on. Clients use it to decide how to parse, render or download the resource.
How do I add a MIME type in nginx?
Inside an http or server block, add entries to the types mapping — for example "image/avif avif;" — or use "default_type application/octet-stream;" for a location. The tool generates copy-ready snippets for each result.
How do I add a MIME type in Apache?
Use AddType in your config or .htaccess, e.g. "AddType application/wasm .wasm". Make sure mod_mime is enabled (it is by default). The Apache snippet button produces these lines for you.
Can one MIME type have several extensions?
Yes. For example image/jpeg maps to .jpg, .jpeg and .jpe, and application/json is associated with .json and .map. The lookup lists every registered extension for each type.
Does the lookup work offline?
Yes. The MIME database ships with the page and searching is pure client-side JavaScript. No query is sent to a server, and there is no login or tracking.