Content-Type Parser

The Content-Type header tells a client what kind of data a response body contains. It is one of the most important HTTP headers because it drives how a browser, API client, or server decides to interpret the bytes it receives: render as HTML, parse as JSON, treat as an image, or download as a file.

A Content-Type value has two parts: a media type written astype/subtype (for example text/html or application/json) and an optional list of parameters separated by semicolons (for example charset=utf-8 or a multipart boundary). This tool splits any Content-Type value into those pieces so you can read and copy each part. It runs entirely in your browser.

1. 1

   Paste the header value

   Drop the raw Content-Type value into the input field, for example multipart/form-data; boundary=----Abc123.
2. 2

   Read the breakdown

   The tool shows the base media type, splits it into type and subtype, and lists every parameter as a name and value pair.
3. 3

   Copy what you need

   Use the copy button next to the media type or any parameter value to grab just that piece for your code or config.

Take text/html; charset=utf-8. The media type is text/html, where text is the top-level type and html is the subtype. After the semicolon comes the parameter charset=utf-8, which tells the client the text is encoded as UTF-8.

Quoted parameter values

Parameter values can be wrapped in double quotes, which is common when the value contains spaces or special characters. A boundary might look like boundary="my boundary". This tool strips the surrounding quotes so you see the real value, not the quoting syntax around it.

Structured suffixes

Some subtypes carry a suffix after a plus sign, like application/ld+json or image/svg+xml. The suffix (+json, +xml) signals the underlying structure so generic parsers can still handle the payload. The parser surfaces the suffix when one is present.

• Always send a charset for text types. text/html; charset=utf-8 avoids encoding ambiguity.
• Media types are case-insensitive, so application/JSON and application/json are equivalent.
• The boundary parameter in multipart bodies is required and must match the delimiter in the body.
• Use application/json, not text/json, which is not a registered media type.
• Parameters you do not recognize are usually safe to ignore, but never strip charset.

What is the difference between type and subtype?

The type is the broad category (text, image, application) and the subtype is the specific format within it (html, png, json). Together they form the media type, which used to be called the MIME type.

Why are some values in quotes?

Quotes let a parameter value contain spaces, semicolons, or other characters that would otherwise be treated as syntax. The actual value is whatever sits between the quotes, which is what this tool shows.

Is charset always required?

Not technically, but for text-based types it is strongly recommended. Without an explicit charset, clients may guess the encoding and get it wrong, leading to garbled characters. UTF-8 is the modern default.

Does this tool send my data anywhere?

No. Parsing happens locally in your browser using plain string operations. The header value you paste never leaves your device.