Developer Tools

HTTP 415 Unsupported Media Type

4xx Client Error. The server refuses the request because the payload format (Content-Type) isn't supported.

Runs in your browser. Your files and text never leave your device - nothing is uploaded.

4xx Client Error

What it means

The server refuses the request because the payload format (Content-Type) isn't supported.

PropertyDetail
Status class4xx Client Error
Defined inRFC 9110, Section 15.5.16
Cacheable by defaultOnly with explicit caching headers: a cache stores it when the response carries Cache-Control (max-age, s-maxage or public) or Expires.
Who needs to actThe client, which has to send a supported format.

What does HTTP 415 Unsupported Media Type mean?

HTTP 415 Unsupported Media Type means the server refuses the request because the body is in a format it does not support for that method and URL. The usual cause is a missing or wrong Content-Type header, such as JSON labelled as text/plain. It can also mean the body uses a Content-Encoding the server cannot decode.

How 415 Unsupported Media Type works

The server can decide the format is unsupported from the Content-Type header, from the Content-Encoding header, or by inspecting the data itself. RFC 9110 suggests helping the client: if the media type was the problem, the response can carry an Accept header listing the types the server would take, and if a content coding such as gzip was the problem, an Accept-Encoding header can list the codings it accepts. A 415 differs from 400 and 422 in timing: the server rejects the format before it attempts to parse the content.

Example 415 request and response

POST /api/users HTTP/1.1
Host: api.example.com
Content-Type: text/plain;charset=UTF-8

HTTP/1.1 415 Unsupported Media Type
Accept: application/json

The JSON body was labelled as plain text, so the server refused it and listed the type it accepts.

What causes a 415 Unsupported Media Type

  • Calling fetch() with a JSON string body but no Content-Type header, so it is sent as text/plain.
  • Posting multipart/form-data or URL-encoded form data to an endpoint that only accepts application/json.
  • Uploading a file type the endpoint does not allow, such as HEIC to an image API that wants JPEG or PNG.
  • Compressing the request body with an encoding the server cannot decode.

How to fix a 415 Unsupported Media Type

If you sent the request

  • Set Content-Type to what the API documents, usually application/json, and make sure the body really is in that format.
  • In fetch(), pass headers: { 'Content-Type': 'application/json' } alongside JSON.stringify(body).
  • Convert files to a supported format before uploading.

If you build the API

  • Return Accept or Accept-Encoding headers listing what you support.
  • Reject unsupported types before parsing, and document the accepted formats.

Related status codes

  • 400 Bad Request: The format is accepted, but the body is malformed.
  • 422 Unprocessable Entity: The format and syntax are fine, but the content fails validation.
  • 406 Not Acceptable: The reverse direction: the server cannot produce a response in a format the client accepts.

Tools that help

Frequently asked questions

Sources

Link to or cite this page

Free to link from documentation, README files, answers and articles. Copy the form you need:

Plain text

"HTTP 415 Unsupported Media Type", The Tools Kit, https://www.thetoolskit.co/http-status-codes/415

Markdown (README, GitHub, Reddit)

[HTTP 415 Unsupported Media Type](https://www.thetoolskit.co/http-status-codes/415)

HTML

<a href="https://www.thetoolskit.co/http-status-codes/415">HTTP 415 Unsupported Media Type</a>

Other HTTP status codes

Reviewed by Raja Jahangir · Last reviewed: October 7, 2026