A MIME type, also called a media type, labels data so that software can decide how to handle it. Web servers commonly send a Content-Type header with a response; a browser may use that value to display, download, or pass content to another handler. This reference lets you search a bundled mapping of common filename extensions and MIME strings. It is a quick lookup aid for developers configuring a response, checking an upload rule, or documenting a known file format—not a detector that inspects the actual bytes inside a file.
Type an extension such as “.pdf” or a search term into the single input field. The page filters the reference list as you type, matching either the extension text or the MIME value without regard to case. If the typed value resolves to a known extension, a highlighted “MIME Type” result appears above the filtered list. The listing is scrollable and capped in height so that many results do not stretch the entire page. Clear the search to browse the bundled entries again.
A checked example: entering “.pdf” shows application/pdf as the lookup and filters the list to the matching extension row. Searching “image/” filters rows whose MIME strings contain that text, helping you browse image entries without knowing a particular suffix. For a file named report.pdf, the lookup helper uses the filename’s final suffix and lowercases it before searching the mapping. An unlisted suffix falls back to application/octet-stream, which means generic binary data rather than a confident identification of the file’s true content.
The mapping includes common web, document, image, audio, video, archive, font, and programming file extensions. Examples include .html as text/html, .json as application/json, .png as image/png, and .woff2 as font/woff2. The list is embedded in the application rather than fetched from an up-to-date registry. MIME names and extension conventions can vary across platforms and deployments, so use the tool as a practical reference and confirm any value that is part of a protocol contract or security policy.
Common use cases include choosing a Content-Type for a static download, reviewing an upload allowlist, checking a MIME value in an API response, and learning the relationship between familiar suffixes and media types. It can help a developer quickly find a likely value without consulting a large standards document. For a secure upload pipeline, however, do not trust a filename extension or the client-supplied Content-Type alone. Validate file content and enforce an allowlist server-side according to the application’s threat model.
This is a dictionary lookup, not file analysis. The page does not upload a file, read bytes, inspect magic numbers, test whether a document is valid, or confirm that a browser can render it. A misleading extension can therefore return a plausible mapping for content of a completely different type. Multi-dot filenames resolve using the final extension. A bare unknown term can yield the generic fallback in the result area while the visible list is filtered to no matches; distinguish that fallback from a verified standard mapping.
When configuring a server, check the destination behavior as well as the label: content sniffing, download disposition, caching, and security headers are separate concerns. Use the canonical spelling and case conventions expected by the receiving system, and test with the actual deployment. If a format is missing from this built-in table, consult the relevant IANA media type registry or authoritative format documentation rather than assuming the tool’s generic fallback is suitable for every application.
The interface only searches a static in-memory mapping and does not accept a file or send a lookup request. No user-provided document is needed to use it. This describes the component’s lookup logic and should not be expanded into a guarantee about unrelated site operations. For security-sensitive upload handling, perform validation on the server and keep the browser’s submitted filename and MIME header untrusted. A known MIME label is metadata, not proof of authenticity or safe content.
A subtle extension detail is that the helper resolves the final suffix after the last period. A name such as archive.tar.gz is therefore checked as .gz, not as the compound suffix .tar.gz. This is appropriate for the included mapping but may not match the way every application interprets compound extensions. When setting a web server rule, confirm the extension matching behavior in that server and add explicit handling for any compound format used by your project.
The static list is useful for a fast reference but is not a substitute for testing the response that your application actually serves. Inspect the network response headers in a development environment, then test downloads and browser behavior for representative clients. Some formats have more than one historical media type, and software ecosystems may accept aliases. Prefer the type required by the protocol or receiving system rather than choosing an entry solely because it appears in this local table.
Search results are not ranked by standardization status or security. A search term may match several extensions that share a MIME value, so scan both columns and select the suffix relevant to your use. The list is limited to common entries and cannot tell you whether a file is safe to open. For upload validation, separate the convenience of a MIME reference from malware scanning, content validation, and server-side authorization checks.
If a result is absent, consult an authoritative registry rather than inferring a type from a similar extension.