Introduction to MIME types
MIME types enable browsers to recognize the filetype of a file which has been sent via HTTP by the webserver. As a result the browser is able to choose a suitable displaying method. Common MIME types are for example text/html for html-files or image/jpeg for jpeg-files.
original by Bob Clary
published Feb. 20, 2003
What are MIME types?
MIME (Multi-purpose Internet Mail Extensions) is an expansion of the original Internet e-mail protocol that exchanges different kinds of data files on the Internet: text, audio, video, images, application programs, and others. In 1991, the protocol was extended so that Internet clients and servers could recognize and handle various kinds of data, and new file types were added to the "mail" protocol as supported Internet Protocol file types.
Servers insert the MIME header at the beginning of any web transmission. Clients use this header to select an appropriate display, or "player", application for the type of data indicated by the header. Some of these players are built into the client, typically a browser (for example, all browsers come with GIF and JPEG image players, as well as the ability to handle HTML files); other players may need to be downloaded.
MIME types—also sometimes called Internet media types or Content-types—describe the media type of content either contained in email or served by web servers or web applications, and are intended to help guide a web browser to correctly process and display the content. Examples of MIME types are:
text/htmlfor normal web pages
text/plainfor plain text
application/octet-streammeaning "download this file"
application/x-java-appletfor Java™ applets
application/pdffor Adobe® PDF documents.
By default, many web servers are configured to report a MIME type of
application/octet-stream for unknown content types. As new content types are invented or added to web servers, web
administrators may fail to add the new MIME types to their web server's configuration. This is a major source of problems for
users of Gecko-based browsers, which respect the MIME types as reported by web servers and web applications.
MIME is currently defined in RFCs 2045, 2046, 2047, 2048, and 2049; registered values for MIME types are available in IANA/MIME Media Types. The HTTP specification defines a superset of MIME which is used to describe the media types used on the web.
Why are correct MIME types important?
If the web server or application reports an incorrect MIME type for content, a web browser has no way, according to the HTTP specification, of knowing that the author actually intended the content to be processed and displayed in a way different from that implied by the reported MIME type.
Some other web browsers, such as Internet Explorer, try to allow for misconfigured web servers and applications by guessing what the correct MIME type should be. This has sheltered many web administrators from their own errors as, using this method, Internet Explorer will continue to process content as expected even though the web server is misconfigured, e.g., it may correctly display an image that is reported to be plain text.
Serving content using the correct MIME type can also be important for security reasons; it's possible for malicious content to affect the user's computer by pretending to be a safe type of document when it is in fact not.
Why browsers should not guess MIME types
Apart from violating the HTTP specification, it is a bad strategy for browsers to guess MIME types for the following reasons.
Loss of control
If the browser ignores the reported MIME type, web administrators and authors no longer have control over how their content is to be processed.
For example, a website oriented for web developers might wish to send certain example HTML documents as either
text/plain in order to have the documents either processed and displayed as HTML or as
source code. If the browser guesses the MIME type, this option is no longer available to the author.
Some content types, such as executable programs, are inherently unsafe. For this reason, the actions a browser can take when given content of that type are usually restricted. For example, an executable program should not be executed on the user's computer, and at most should cause a dialog to appear asking the user if they wish to download the file.
MIME type guessing has led to security exploits in Internet Explorer based on malicious authors incorrectly reporting a MIME type of a dangerous file as a safe type. This deliberate misrepresentation bypassed the normal download dialog, resulting in Internet Explorer correctly guessing that the content was an executable program and then running it on the user's computer.
How to determine the MIME type sent by a server
According to the standards, a
meta tag that gives the MIME type such as
http-equiv="Content-Type" content="text/html"> should be ignored if there's a
Content-Type line in the header. Instead of looking for this line in the HTML source, use the above techniques to determine the MIME type sent by the
How to determine the correct MIME type for your content
There are several steps you can take to determine the correct MIME type value to be used for your content.
- If your content was created using a vendor's software application, read the vendor's documentation to see which MIME types should be reported for its media types.
- Look in the IANA/MIME Media Types registry, which contains all registered MIME types.
- Search for the file extension at FILExt or File extensions reference to see what MIME types are associated with that extension.
Common MIME Types
|MIME Type||File Type|
|application/xml||rss, atom, xml, rdf|
|audio/mp4||m4a, f4a, f4b|
|video/mp4||mp4, m4v, f4v, f4p|
- Incorrect MIME Type for CSS Files
- IANA/MIME Media Types
- Hypertext Transfer Protocol—HTTP/1.1
- Microsoft - 293336 - INFO: WebCast: MIME Type Handling in Microsoft Internet Explorer
- Microsoft - Appendix A: MIME Type Detection in Internet Explorer
- Microsoft - Security Update, March 29, 2001
- Microsoft - Security Update, December 13, 2001
This article contains content originally from external sources.
Portions of this content come from the Mozilla Developer Network : Article