We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
A quick reference tool for MIME types and file extensions used in web development.
This is a locally maintained static reference table, not a live official directory, current policy or complete collection. Records without a named source and update date remain unverified.
50 selected media-type/extension examples; extensions do not establish file contents. Original English descriptions are retained, not a complete or live IANA registry. Reference
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This reference table contains 50 preset rows with a media type, one or more filename extensions, and a short description. Media type is the modern standards term often called a MIME type. In HTTP, a Content-Type header tells the recipient the media type of the message representation. A value such as application/pdf has a type and subtype separated by a slash; optional parameters may follow in a header, for example a character set.
Search the table for a full value such as application/pdf, an extension such as pdf, or a description keyword. The supplied rows cover selected office documents, archives, images, text, audio, video, and application formats. This is a curated quick-reference subset rather than a full registry or a file inspection service.
An extension is part of a filename; a media type labels data in a protocol message. A table can associate common extensions with media types, but the extension alone does not prove a file’s contents. Likewise, a server’s declared type is metadata for a recipient and is not a file-integrity or safety check.
Some extensions have more than one listed row. For example, js appears with both application/x-javascript and text/javascript in this dataset. Check the application and server requirements before choosing between alternatives.
IANA maintains the registry of registered media types. RFC 9110 defines the HTTP Content-Type field and describes the media type’s role in indicating representation format and intended processing. The table helps locate familiar values; use the registry and applicable specification when you need registration status or protocol details.
Content-Type field and media types in HTTP; published June 2022, checked 2026-09-28.Guide
Follow the workflow and verify inputs and outputs with practical examples.
Choose a term: a complete type such as image/jpeg, an extension such as jpg, or a word from the row description.
Enter it in the table search field and review the matching rows. Extensions are listed without a leading dot, so start with pdf rather than .pdf.
Compare the full media type and all extensions when several rows match. Copy the complete value only after checking the requirements of the receiving software or server.
Use cases
See how the tool fits into real work and everyday tasks.
A developer preparing a response for a PDF or image can find a familiar type string, then confirm it against the actual file and server behavior.
A team maintaining an upload form can compare extension and type labels while separately defining server-side checks for permitted content.
When a browser handles a response unexpectedly, a developer can look up the declared type and then inspect the response configuration and actual payload.
Q&A
Find concise answers to common questions and confusing cases.
This table lists text/plain for txt. Confirm any charset or application-specific requirement separately.
Mappings can reflect different conventions or historical values. Choose based on the data and the receiving application rather than assuming each extension has one universal type.
No. The table neither reads the file nor verifies that its content matches its extension or declared type.
Notes
Review scope, result limitations, and important precautions before use.
The preset list is not a live mirror of every IANA entry and may omit uncommon, vendor-specific, legacy, or newly registered types. Consult the official registry and relevant format documentation for authoritative current status.
For untrusted uploads, do not rely on a filename extension or a client-supplied Content-Type as proof of content. Validate files with appropriate server-side controls for your application. This reference does not inspect, upload, or certify files.
Related
Discover related tools, collections, and available API capabilities.