Content-Type Lookup

Find the right MIME content-type by format name, extension, or type tree.

Reverse-lookup MIME content-type strings by format name, file extension, or top-level type. See the canonical type/subtype, matching extensions, and common parameters like charset so you can set HTTP Content-Type headers correctly.

What is a Content-Type header?

The HTTP Content-Type header tells the client what kind of data the response body contains, such as text/html; charset=utf-8. Browsers and APIs rely on it to parse, render, or download the payload correctly.

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-stream with a Content-Disposition: attachment header to force a save dialog.
  • application/json is defined as UTF-8, so adding charset is redundant though harmless.
  • When a precise type is unknown, application/octet-stream is the safe generic fallback.