MIME Type Lookup
Look up MIME types, file extensions, and content types.
About this tool
Look up MIME types, file extensions, and content types. Turn opaque strings from network traces, devtools, or SEO audits into structured output you can act on.
Search by file extension (json, png) or MIME string (application/json). Confirm the Content-Type you should send or expect. Example — JSON content type: try `json` and expect something like `.json → application/json`.
Lookup table is curated — brand-new or proprietary types may be missing. See also: HTML Entity Lookup, and HTTP Header Parser. Runs in your browser — nothing you paste gets uploaded.
How to use
- Search by file extension (json, png) or MIME string (application/json).
- Confirm the Content-Type you should send or expect.
- Copy the MIME type into headers, nginx maps, or upload validators.
- Cross-check vendor-specific types when dealing with Office or CAD files.
Example
JSON content type
Input
json
Output
.json → application/json
Limitations
- Lookup table is curated — brand-new or proprietary types may be missing.
- Does not sniff file bytes; extension mismatches will not be detected.
- Charset parameters (charset=utf-8) are not attached automatically.
Related guides
1Related tools
2Frequently asked questions
What does the MIME Type Lookup do?
Look up MIME types, file extensions, and content types. Runs in your browser — no install, no account.
How do I use the MIME Type Lookup?
Search by file extension (json, png) or MIME string (application/json). Confirm the Content-Type you should send or expect. Copy the MIME type into headers, nginx maps, or upload validators. Cross-check vendor-specific types when dealing with Office or CAD files.
Is the MIME Type Lookup free?
Yes. No signup, no usage limits, no paywall.
Does the MIME Type Lookup upload my data?
No. Processing happens locally in JavaScript. Your input is not uploaded, stored, or logged.
What are the limitations of the MIME Type Lookup?
Lookup table is curated — brand-new or proprietary types may be missing. Does not sniff file bytes; extension mismatches will not be detected. Charset parameters (charset=utf-8) are not attached automatically.