Reference

MIME types, explained

A media type (also called a MIME type or content type) tells a client how to interpret a body. The entries below cover the types you meet most often, with the registry name, extensions and the practical differences that matter when a file will not open or an API rejects a payload.

How to read a media type

The form is type/subtype, optionally followed by parameters such as charset=utf-8 or boundary=.... The type names the family (text, image, audio, video, application, multipart) and the subtype names the format. Media types are registered with IANA; the registry is the authority when two servers disagree.

In HTTP the value travels in the Content-Type header for requests and responses. In HTML it appears in <script type>, <link type> and file inputs. A wrong type can make a browser download a file instead of rendering it, or make an API parser read bytes with the wrong grammar.

Where these definitions come from

Names and registrations follow the IANA media type registry, RFC 9110 for HTTP semantics, and the format-specific standards cited in each entry. Descriptions of browser behavior are practical observations, not part of the registration.

All entries

New tools, straight to your inbox

One short email when we add tools worth using. No spam, unsubscribe anytime.