MIME Type Finder

A MIME type, also called a media type or content type, tells software what kind of data a file holds, for example image/png or application/json. A web server sends it in the Content-Type header so the browser knows how to handle the response.

It looks for a forward slash. Any query containing a slash, like text/css, is treated as a MIME type and searched in reverse. Anything without a slash, like css, is treated as an extension. The hint line under the input tells you which mode it chose.

No. For extensions the finder lowercases the query and strips one leading dot, so png, .png, .PNG and PNG all resolve the same way. MIME type matching is also case-insensitive.

Several extensions can share a type. A reverse search on image/jpeg returns jpe, jpeg and jpg, and application/yaml returns yaml and yml. The results are sorted alphabetically so the order is stable.

The finder only knows the extensions in its built-in table, so an obscure or made-up extension returns no match. Likewise a MIME type not in the table returns no extensions. Truly unknown binary data is conventionally served as application/octet-stream.

The table spans common formats across images, documents, text and code, audio, video, archives and fonts. It is a curated list of everyday types rather than the full IANA registry, so rare or vendor-specific types may be missing.

No. This is a name-based lookup keyed on the extension or the type string you enter. It does not read file bytes or magic numbers, so a mislabelled file will still return the type its extension implies.

The values follow common web conventions and are a good default for static files. For text formats you may still want to add a charset, such as text/html; charset=utf-8, which this lookup does not append.

No. The lookup uses the built-in table and runs entirely in your browser, so nothing you type is sent to a server.