Content-Type lookup
The HTTP Content-Type header carries a MIME (media) type that tells clients how to interpret a response body — render it, parse it, or download it. This tool is the reverse of an extension lookup: search by format name, file extension, or top-level type and get the exact type/subtype string, the extensions it covers, and the parameters (like charset) you should include.
How it works
Each record pairs a canonical MIME type with its top-level type (text, image, audio, video, application, font), its matching file extensions, and any standard parameters. The search normalizes your query and matches it against the type string, the format name, and the extensions, so json, .json, and application all surface the relevant entry. Text formats include the recommended charset=utf-8 parameter; binary formats omit it.
Tips and example
Set the header with the parameter where appropriate:
Content-Type: text/html; charset=utf-8
Content-Type: application/json
Content-Type: image/png
Content-Type: application/octet-stream
- For downloads, pair
application/octet-streamwith aContent-Disposition: attachmentheader to force a save dialog. application/jsonis defined as UTF-8, so addingcharsetis redundant though harmless.- When a precise type is unknown,
application/octet-streamis the safe generic fallback.