MIME Types
A media-type reference by file extension, with a filter and a note on parameters such as text/plain; charset=utf-8.
The media type behind a file extension
A server labels every response with a media type, formerly called a MIME type, so the browser knows whether to render it, play it or download it. The label comes from the extension in most configurations, which is why a table of extension to media type is useful when you are writing that configuration.
Reading the table
Each row is one extension, the registered media type and a short family label. Filter by extension, by type or by family: image narrows the list to the image formats, and font/ narrows it to the two font types. The family column is a convenience for scanning, not a registered part of the type.
Parameters
A media type may carry parameters after a semicolon. The common one is the character set: a plain-text response is normally served as text/plain; charset=utf-8, which tells the browser how to decode the bytes. Parameters describe the representation; they are not part of the registered name, which is why this table lists text/plain and explains the suffix separately.
What it does not do
It does not inspect a file. The page cannot tell you what type a particular file really is, because that would require reading its bytes; it answers what type the extension conventionally maps to. If two servers disagree about an extension, this table gives the registered spelling, and your server's own configuration remains the authority.
A server labels every response with a media type so a browser knows whether to render, play or download it. This page is a filterable table of file extensions and the registered media type each conventionally maps to, with a short family label for scanning.
The filter matches the extension, the type or the family, so image narrows the list to image formats and font/ to the font types. The family column is a convenience rather than part of the registered name.
It does not inspect a file. The page cannot tell you what type a particular file really is, because that would mean reading its bytes; it answers what the extension conventionally means.
Reading and filtering the table
Each row is one extension, its media type and a family. The count below the table reports the whole list until a filter is typed, then how many rows match and how many exist in total, so an empty result is distinguishable from a short list.
Two servers can disagree about an obscure extension. The table gives the registered spelling, and a server's own configuration remains the authority for what it actually sends.
- Extension, media type and family per row
- Filter by any of the three
- A live match count
Parameters are not part of the name
A media type can carry parameters after a semicolon. The common one is the character set: a text response is normally served as text/plain with charset=utf-8 so the browser decodes the bytes correctly.
Parameters describe the representation rather than renaming it, which is why the table lists text/plain and explains the suffix separately. Copy the type, then add the parameter your response needs.
How to use the filter
Type the extension, media type or family into the filter box; image narrows the table to image formats and font/ to the font types. The count under the table reports how many rows match and how many exist in total, so an empty result reads as no match rather than a short list.
Copy the registered spelling from the Media types column into the server configuration, then append the charset parameter a text response needs. Check an obscure extension against what the server actually sends, since the table records convention rather than that server's behaviour.
What to Expect
Best for
- Looking up the type to configure for an extension
- Checking the registered spelling of a media type
- Teaching the difference between a type and its parameters
Not ideal for
- Identifying what a particular file actually contains
- Discovering what a specific server sends
- A type that is not in the table
What this tool keeps
- The registered spelling of each media type
- The family label as a scanning aid
- The filter text and the live match count
What may need cleanup
- The charset parameter, which must be added to the response
- A server that sends a different type for the same extension
- An extension the table does not list
Common errors
- Reading the family label as part of the media type
- Expecting the page to sniff a file's bytes
- Forgetting the charset parameter on a text response
Example use cases
- Writing a web server's type map
- Checking a Content-Type header
- Teaching MIME types to a new developer
Sample input
The filter image typed into the table's filter field.
Sample output
Only the image-family rows remain, and the count reports how many of the full list matched.
Who this is for
- Web developers configuring a server
- Support engineers reading a header
- Students learning media types
Frequently asked questions
What does the MIME type table list?
File extensions and the registered media type each conventionally maps to, with a short family label and a live filter.
Does it identify what a particular file contains?
No. It maps extensions to conventional types; the actual bytes of a file are not inspected.
Why does a server send a different type for the same extension?
A server can be configured differently, and a parameter such as charset must be added to the response separately.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.