Free tool · runs in your browser
MIME Type Lookup
Search by extension, type or subtype to find the Content-Type a server or client should use.
Type, subtype and parameters
A media type has the form type/subtype, optionally followed by parameters such as charset=utf-8. The type is the broad family — text, image, audio, video, application, multipart — and the subtype is the specific format. Registration lives in the IANA media type registry, though many real-world types are vendor extensions.
The Content-Type header is what matters on the wire. A file extension is only a hint; servers can and do send a different type, and the client must trust the header rather than the name.
Getting Content-Type right
Serving JSON as text/html invites content sniffing and can turn a data response into script execution in a browser. Send application/json and pair it with X-Content-Type-Options: nosniff so the browser does not second-guess you.
For text formats, declare the charset (text/html; charset=utf-8). For images, audio and video, the subtype selects the decoder; a wrong type usually produces a download prompt or a broken player rather than a visible error.
All media types, searchable
Every entry links to its full reference page. The search box above filters this list.
Frequently asked questions
Is a MIME type the same as a Content-Type?
In practice, yes. MIME type is the older name; Content-Type is the HTTP header that carries the media type and optional parameters.
What Content-Type should JSON use?
application/json. The older application/javascript and text/json are not correct for API responses.
Does the file extension decide the type?
No. The server sets Content-Type, and clients should use it. Extensions are a convenience for servers and users.