← Back to MIME types
MIME Type
application/jwt
APIMIME type for JSON Web Token data represented as a standalone media type.
MIME type reference, HTTP example, browser usage, common mistakes, and related content.
What is the application/jwt MIME type?
The MIME type application/jwt is used to tell browsers, APIs, and servers how a file or response body should be interpreted.
MIME stands for Multipurpose Internet Mail Extensions, and MIME types are now a standard part of HTTP responses and web content delivery.
When a browser or client receives a response with application/jwt, it uses that information to decide how the content should be processed, rendered, downloaded, or executed.
Example
Content-Type: application/jwt
HTTP example
HTTP/1.1 200 OK Content-Type: application/jwt Content-Length: 1256
Common use cases
- Returning a JWT as a standalone response body
- Token issuance endpoints
- Explicit JWT content signaling
Common mistakes
- Using the wrong MIME type for the file being served
- Returning text/plain instead of application/jwt
- Forgetting required parameters like charset when relevant
- Using a deprecated MIME type in older server configurations
- Serving assets with a mismatched Content-Type header, causing browser parsing issues
How browsers use it
Browsers use the Content-Type response header to decide how a response should be handled. For example, HTML is rendered as a page, CSS is parsed as styles, JavaScript is executed as script, and images are displayed visually. If the MIME type is incorrect, the browser may refuse to load the file correctly or may treat it as plain text or a download instead.
Practical developer insight
application/jwt is technically defined in RFC 7519, but in practice JWTs are almost always transmitted in HTTP headers (Authorization: Bearer) or inside JSON response bodies rather than as a standalone response with this MIME type. Include it for completeness, but do not expect to encounter it frequently in real-world APIs.