What this tool does
MIME Type Explorer maps common file extensions to Content-Type values, categories, browser behavior notes, and typical uses.
← All Tools
🧾 MIME Type Explorer
Search common MIME types and file extensions, then copy safe Content-Type values for uploads, APIs, static hosting, and attachment handling.
Search by extension, MIME type, category, or common use. The reference is local and intentionally conservative.
Lookup notes
Browsers, servers, and operating systems may disagree on obscure or legacy types. Use this as a practical reference, then confirm final production behavior with your target server, CDN, and upload validator.
Why it is useful
It helps developers choose correct HTTP headers, upload allowlists, attachment metadata, and static asset configuration without hunting through scattered references.
How it works
The page filters a local reference table by extension, MIME type, category, and common use. Selecting an entry produces a copyable JSON summary.
Best input
Search for an extension such as .json, a MIME type such as image/svg+xml, or a category such as font.
Header tip
For HTTP responses, send the exact Content-Type value and pair executable or downloadable content with safe cache, disposition, and sniffing controls.
Privacy note
Search and filtering run locally in your browser from static reference data.
Important limitation
MIME mappings are not security policy by themselves. Validate uploads by content and extension, disable sniffing where appropriate, and verify CDN/server header behavior.
Quick answers
Is a MIME type the same as a file extension?
No. Extensions are filename hints; MIME types are content labels used by HTTP, email, browsers, and upload systems.
Can I rely on browser sniffing?
No. Set explicit Content-Type headers and use X-Content-Type-Options: nosniff when serving risky content.
Common Use Cases
Configure static asset headers
Look up correct Content-Type values for SVG, WebP, WASM, CSS, JavaScript, and font files.
Build upload allowlists
Compare file extensions and expected MIME labels before writing validation rules for PDFs, images, or archives.
Debug API attachments
Check whether a response should use application/json, text/csv, application/pdf, or a binary download type.
HTTP Developer Workbench workflow
Move between curl conversion, webhook testing, status-code reference, typed HTTP security diagnostics, redirect-chain analysis, status samples, MIME lookups, and user-agent parsing while keeping network behavior explicit.