What is the correct JSON content type?

Created 25.01.2009 15:25
Viewed 3.12M times
10687 votes

I've been messing around with JSON for some time, just pushing it out as text and it hasn't hurt anybody (that I know of), but I'd like to start doing things properly.

I have seen so many purported "standards" for the JSON content type:


But which one is correct, or best? I gather that there are security and browser support issues varying between them.

I know there's a similar question, What MIME type if JSON is being returned by a REST API?, but I'd like a slightly more targeted answer.

Answers 36

For JSON text:


The MIME media type for JSON text is application/json. The default encoding is UTF-8. (Source: RFC 4627).

For JSONP (runnable JavaScript) with callback:


Here are some blog posts that were mentioned in the relevant comments:

25.01.2009 15:27
Complete list of MIME types by Eugen Mihailescu, 04.04.2017 05:08
does it really matter what mime type it has? it's text that gets parsed into an object. wouldn't it be more natural to pass it as text/plain if you want it to be openable in browser without force download, and application/octet-stream if you want it to be automatically downloaded(useful if you're generating it on a webpage intended to be saved locally). Is there really that many people that will need to know the mime type so the downloader can view it with a special json viewer? What am I missing that warrants it a special mime type? by Dmitry, 23.08.2017 12:00
Using "text/plain" is a bad practice in general. There are, for instance, attacks in the web platform that would allow cross-origin data theft if you fail to send an appropriate MIME type value. by EricLaw, 21.11.2017 21:27
Internet Explorer sometimes has issues with application/json - blog is offline by kudlatiger, 04.06.2018 03:59
Imagine I have a document written by somebody which contains plain text. Now that plain text just happens to be valid JSON as well. Would I then be wrong to use text/plain as its mime-type? JSON is a SUB-TYPE of text. So I think both should be allowed. The question is which works better in practice. According to comment by codetoshare IE has problems with application/json. But no browser should have problems with text/plain. If text/plain is unsafe then how can I serve text-files from my web-site? by Panu Logic, 01.09.2018 16:08
@EugenMihailescu The title of that page is "Incomplete list of MIME types" by Omegastick, 30.08.2019 06:30
Note that RFC4627 was obsoleted by RFC7159, itself replaced by RFC8259. The information provided here still holds. by Oliver Sieweke, 09.11.2020 19:43
@Omegastick True, however that page does have a link to the IANA list of "all" types linked in the answer. by mbomb007, 20.11.2020 15:55
Which are now called Media Types by the IANA. by Ludovic Kuty, 19.03.2021 12:28
Show remaining 4 comments

IANA has registered the official MIME Type for JSON as application/json.

When asked about why not text/json, Crockford seems to have said JSON is not really JavaScript nor text and also IANA was more likely to hand out application/* than text/*.

More resources:

07.04.2010 04:32
A lot of stuff got put into the text/* section in the early days that would probably be put into the application/* section these days. by TRiG, 05.07.2011 20:47
@Rohmer - You "can" open anything in a text editor, but a binary format like JPEG or a Windows .exe or a .zip will contain non-printable characters which can actually break many text editors or cause undesired behavior. Try running cat file.jpg for example. Whereas any xml or json file is 100% printable. So I think Stijn de Witt's point is a valid one, despite the fact that yes, it's too late to change now. by XP84, 16.01.2018 20:59
@XP84 You can open any binary with a text editor in HEX form. And all the different characters (the 16 of them) are 100% printable. So, by that logic... are all binaries text? Json is not text. Json is (warning: informal loose definition ahead) a text representation of an object (or array of objects) by xDaizu, 05.04.2018 11:55
There is no meaning to the phrase "a text editor in HEX form". A Hex editor shows each byte as its hexadecimal value, for example, the byte 1111000 as "78". While there may be some text editors which also happen to have a hex editing mode, this is neither common nor useful for anything but the most technical users doing the most technical tasks. Text, by comparison, means ASCII or Unicode, and in text, the byte 1111000 means lower-case x character. Not 78. JSON is text in exactly the same way as HTML (text/html). It contains only readable text characters, with structured meaning in them. by XP84, 21.05.2018 21:53
I tend to agree with Stijn de Witt. JSON is meant to be viewed and edited with a text-editor. by Panu Logic, 01.09.2018 15:59


Content-Type: application/json


Content-Type: application/javascript
20.06.2012 03:10
JSONP is not really JSON though, it's a technique for passing a JavaScript object literal by Benjamin Gruenbaum, 08.09.2013 06:44

Of course, the correct MIME media type for JSON is application/json, but it's necessary to realize what type of data is expected in your application.

For example, I use Ext GWT and the server response must go as text/html but contains JSON data.

Client side, Ext GWT form listener

uploadForm.getForm().addListener(new FormListenerAdapter()
    public void onActionFailed(Form form, int httpStatus, String responseText) 

    public void onActionComplete(Form form, int httpStatus, String responseText) 

In case of using application/json response type, the browser suggests me to save the file.

Server side source code snippet using Spring MVC

return new AbstractUrlBasedView() 
    protected void renderMergedOutputModel(Map model, HttpServletRequest request,
                                           HttpServletResponse response) throws Exception 
07.10.2009 14:35
server response must go as text/html. This is true for the ExtJS variant as well. by gbegley, 30.10.2012 21:10


Response is dynamically generated data, according to the query parameters passed in the URL.


{ "Name": "Foo", "Id": 1234, "Rank": 7 }

Content-Type: application/json


JSON with padding. Response is JSON data, with a function call wrapped around it.


functionCall({"Name": "Foo", "Id": 1234, "Rank": 7});

Content-Type: application/javascript

28.03.2013 07:54
The definition of JSON is wrong. It does not need to be dynamically generated or respect query parameters. You can serve a static JSON file. Also, the most upvoted answer has a link to the RFC. by styfle, 29.01.2014 01:37
Also JSONP can be json data assigned to a var. by Jimmy Kane, 30.01.2014 13:16

If you are using Ubuntu or Debian and you serve .json files through Apache, you might want to serve the files with the correct content type. I am doing this primarily because I want to use the Firefox extension JSONView

The Apache module mod_mime will help to do this easily. However, with Ubuntu you need to edit the file /etc/mime.types and add the line

application/json json

Then restart Apache:

sudo service apache2 restart
16.11.2010 22:58
usually a reload is enough (faster than restart). Also, note that you can now do "sudo service apache2 reload". by noamtm, 19.01.2011 17:37
Ubuntu 12.04 has this by default by Prizoff, 25.05.2012 17:52

If you're calling ASP.NET Web Services from the client-side you have to use application/json for it to work. I believe this is the same for the jQuery and Ext frameworks.

25.01.2009 15:31
jQuery seems to work with at least 'application/json' and 'text/plain'... I haven't tried all the others though. by Nathan, 18.03.2010 19:30
jQuery is capable of working with content-Type: text/plain, content-Type: application/json, content-Type: application/json; charset=UTF-8, contentType: "application/x-www-form-urlencoded; charset=UTF-8" by Ashraf.Shk786, 27.07.2017 11:13

The right content type for JSON is application/json UNLESS you're using JSONP, also known as JSON with Padding, which is actually JavaScript and so the right content type would be application/javascript.

12.04.2012 04:00

There is no doubt that application/json is the best MIME type for a JSON response.

But I had some experience where I had to use application/x-javascript because of some compression issues. My hosting environment is shared hosting with GoDaddy. They do not allow me to change server configurations. I had added the following code to my web.config file for compressing responses.

    <scheme name="gzip" dll="%Windir%\system32\inetsrv\gzip.dll"/>
        <add mimeType="text/*" enabled="true"/>
        <add mimeType="message/*" enabled="true"/>
        <add mimeType="application/javascript" enabled="true"/>
        <add mimeType="*/*" enabled="false"/>
        <add mimeType="text/*" enabled="true"/>
        <add mimeType="message/*" enabled="true"/>
        <add mimeType="application/javascript" enabled="true"/>
        <add mimeType="*/*" enabled="false"/>
<urlCompression doStaticCompression="true" doDynamicCompression="true"/>

By using this, the .aspx pages was compressed with g-zip but JSON responses were not. I added

<add mimeType="application/json" enabled="true"/>

in the static and dynamic types sections. But this does not compress JSON responses at all.

After that I removed this newly added type and added

<add mimeType="application/x-javascript" enabled="true"/>

in both the static and dynamic types sections, and changed the response type in

.ashx (asynchronous handler) to


And now I found that my JSON responses were compressed with g-zip. So I personally recommend to use


only if you want to compress your JSON responses on a shared hosting environment. Because in shared hosting, they do not allow you to change IIS configurations.

18.04.2012 08:22
"So I personally recommending to use application/x-javascript" is where this answer becomes misleading. GoDaddy does allow compression of application/json, I leverage it on my shared hosting and I wouldn't suggest using a different content type to enable compression anyway, it's simply wrong. It can be done, but it will still be wrong. Using different content types for browser support is one thing, using different content types for server-side compression is another. by User, 11.12.2014 16:20

Only when using application/json as the MIME type I have the following (as of November 2011 with the most recent versions of Chrome, Firefox with Firebug):

  • No more warnings from Chrome when the JSON is loaded from the server.
  • Firebug will add a tab to the response showing you the JSON data formatted. If the MIME type is different, it will just show up as 'Response content'.
30.11.2011 06:42

Not everything works for content type application/json.

If you are using Ext JS form submit to upload file, be aware that the server response is parsed by the browser to create the document for the <iframe>.

If the server is using JSON to send the return object, then the Content-Type header must be set to text/html in order to tell the browser to insert the text unchanged into the document body.

See the Ext JS 3.4.0 API documentation.

07.09.2011 02:41
Tools that don't adhere to standards should be avoided whenever possible; use application/json per spec. by one.beat.consumer, 16.02.2012 02:05
@one.beat.consumer while that is true, it's not specific to ExtJs per se. It's a browser limitation (or rather, perhaps, a "security measure"). by Hendy Irawan, 24.02.2012 15:54
Surely it would be better to use text/plain so it doesn't apply any HTML semantics to non-HTML content? Or don't browsers let you extract a frame's content if it's got no DOM? by Synchro, 10.08.2012 12:34
To add further confusion: I'm just debugging a similar case on Samsung Galaxy Beam (Android 2.3) with default browser, and the iframe seems to fire load event for application/javascript, application/x-javascript, text/javascript, text/plain, but NOT firing it for application/json nor text/html. As of today, Android <=2.3 is About 50% of the Android market share. by jakub.g, 05.07.2013 12:41

JSON is a domain-specific language (DSL) and a data format independent of JavaScript, and as such has its own MIME type, application/json. Respect for MIME types is of course client driven, so text/plain may do for transfer of bytes, but then you would be pushing up interpretation to the vendor application domain unnecessarily - application/json. Would you transfer XML via text/plain?

But honestly, your choice of MIME type is advice to the client as to how to interpret the data- text/plain or text/HTML (when it's not HTML) is like type erasure- it's as uninformative as making all your objects of type Object in a typed language.

No browser runtime I know of will take a JSON document and automatically make it available to the runtime as a JavaScript accessible object without intervention, but if you are working with a crippled client, that's an entirely different matter. But that's not the whole story- RESTful JSON services often don't have JavaScript runtimes, but it doesn't stop them using JSON as a viable data interchange format. If clients are that crippled... then I would consider perhaps HTML injection via an Ajax templating service instead.


14.05.2012 22:19

If you're in a client-side environment, investigating about the cross-browser support is mandatory for a well supported web application.

The right HTTP Content-Type would be application/json, as others already highlighted too, but some clients do not handle it very well, that's why jQuery recommends the default text/html.

27.04.2012 16:27

The correct answer is:

Content-Type: application/json
31.12.2012 06:29

As many others have mentioned, application/json is the correct answer.

But what haven't been explained yet is what the other options you proposed mean.

  • application/x-javascript: Experimental MIME type for JavaScript before application/javascript was made standard.

  • text/javascript: Now obsolete. You should use application/javascript when using javascript.

  • text/x-javascript: Experimental MIME type for the above situation.

  • text/x-json: Experimental MIME type for JSON before application/json got officially registered.

All in all, whenever you have any doubts about content types, you should check this link

02.04.2013 11:10
When did text/javascript become obsolete? I'm still filling up HTML documents with <script type="text/javascript" ... tags. by Oli, 02.04.2013 12:23
It makes no difference for browsers, really. It's just obsolete for RFC standards: rfc-editor.org/rfc/rfc4329.txt by fcm, 02.04.2013 12:34
@Oli you can safely drop type="text/javascript" and just do <script>...</script> at least according to HTML5. by TCB13, 27.06.2013 21:41

In JSP, you can use this in page directive:

<%@ page language="java" contentType="application/json; charset=UTF-8"

The correct MIME media type for JSON is application/json. JSP will use it for sending a response to the client.

19.01.2013 08:22

application/json” is the correct JSON content type.

def ajaxFindSystems = {
  def result = Systems.list()
  render(contentType:'application/json') {
    results {
        system(id:sys.id, name:sys.name)
    resultset (rows:result.size())
26.02.2013 11:55

The IANA registration for application/json says

Applications that use this media type: JSON has been used to exchange data between applications written in all of these programming languages: ActionScript, C, C#, Clojure, ColdFusion, Common Lisp, E, Erlang, Go, Java, JavaScript, Lua, Objective CAML, Perl, PHP, Python, Rebol, Ruby, Scala, and Scheme.

You'll notice that IANA.org doesn't list any of these other media types, in fact even application/javascript is now obsolete. So application/json is really the only possible correct answer.

Browser support is another thing.

The most widely supported non-standard media types are text/json or text/javascript. But some big names even use text/plain.

Even more strange is the Content-Type header sent by Flickr, who returns JSON as text/xml. Google uses text/javascript for some of it's ajax apis.


curl -I "https://ajax.googleapis.com/ajax/services/search/video?v=1.0&q=jsonexample"

Output: Content-Type: text/javascript

curl -I "https://www.flickr.com/services/rest/?method=flickr.test.echo&format=json&api_key=f82254c1491d894f1204d8408f645a93"

Output: Content-Type: text/xml

12.02.2014 16:12

The right MIME type is application/json


I experienced many situations where the browser type or the framework user needed:


03.05.2013 16:00
Example of such a situation? by Mark Amery, 04.06.2014 19:29

I use the below

contentType: 'application/json',
data: JSON.stringify(SendData),
16.05.2013 12:43

The Content-Type header should be set to 'application/json' when posting. Server listening for the request should include "Accept=application/json". In Spring MVC you can do it like this:

@RequestMapping(value="location", method = RequestMethod.POST, headers = "Accept=application/json")

Add headers to the response:

HttpHeaders headers = new HttpHeaders();
headers.add("Content-Type", "application/json");
09.08.2013 10:49
stackoverflow.com/a/65430096/4307338 by Hoque MD Zahidul, 23.12.2020 19:46

The application/json works great in PHP to store an array or object data.

I use this code to put data in JSON on Google Cloud Storage (GCS) which is set publically viewable:

$context = stream_context_create([
    'gs' => [
        'Content-Type' => 'application/json',

    json_encode((object) $array), 

To get back the data is straight forward:

$data = json_decode(file_get_contents("gs://BUCKETNAME/FILENAME.json"));
01.04.2015 16:13

In Spring you have a defined type: MediaType.APPLICATION_JSON_VALUE which is equivalent to application/json.

29.06.2013 08:34
That's Java EE too :: javax.ws.rs.core.MediaType by Edward J Beckett, 28.02.2014 03:01

If the JSON is with padding then it will be application/jsonp. If the JSON is without padding then it will be application/json.

To deal with both, it is a good practice to use: 'application/javascript' without bothering whether it is with padding or without padding.

21.06.2013 15:22
The first part of your answer is wrong. "application/jsonp" is not a valid MIME type. The response body of a JSONP is just JavaScript, so one of the MIME-types for JavaScript has to be used. by Rob W, 30.08.2013 16:14

For JSON, I am using:

 Content-Type: application/json

This is described in the IETF's JSON Data Interchange Format 7158 proposal, Section 1.2: Specifications of JSON.

06.02.2015 12:01

PHP developers use this:

    header("Content-type: application/json");

    // Do something here...
29.03.2014 05:43

Extending the accepted responses, when you are using JSON in a REST context...

There is a strong argument about using application/x-resource+json and application/x-collection+json when you are representing REST resources and collections.

And if you decide to follow the jsonapi specification, you should use of application/vnd.api+json, as it is documented.

Altough there is not an universal standard, it is clear that the added semantic to the resources being transfered justify a more explicit Content-Type than just application/json.

Following this reasoning, other contexts could justify a more specific Content-Type.

09.06.2015 19:12
application/vnd.api+json seems to be specifically for apis using json:api, a very narrow specification with its own expectations and format, I don't understand it to be for any API that returns json. Please correct me if I'm wrong by Hilikus, 25.07.2016 22:49

If you get data from REST API in JSON so you have to use content-type

For JSON data: Content-Type:application/json
For HTML data: Content-Type:text/html,
For XHTML data: Content-Type:application/xhtml+xml,
For XML data: Content-Type:text/xml, application/xml
11.04.2016 09:15

Content-Type: application/json - json
Content-Type: application/javascript - json-P
Content-Type: application/x-javascript - javascript
Content-Type: text/javascript - javascript BUT obsolete, older IE versions used to use as html attribute.
Content-Type: text/x-javascript - JavaScript Media Types BUT obsolete
Content-Type: text/x-json - json before application/json got officially registered.

08.08.2017 03:49
For JSON text: application/json Content-Type: application/json by Vikash Chauhan, 03.09.2019 14:40

JSON (JavaScript Object Notation) and JSONP ("JSON with padding") formats seems to be very similar and therefore it might be very confusing which MIME type they should be using. Even though the formats are similar, there are some subtle differences between them.

So whenever in any doubts, I have a very simple approach (which works perfectly fine in most cases), namely, go and check corresponding RFC document.

JSON RFC 4627 (The application/json Media Type for JavaScript Object Notation (JSON)) is a specifications of JSON format. It says in section 6, that the MIME media type for JSON text is


JSONP JSONP ("JSON with padding") is handled different way than JSON, in a browser. JSONP is treated as a regular JavaScript script and therefore it should use application/javascript, the current official MIME type for JavaScript. In many cases, however, text/javascript MIME type will work fine too.

Note that text/javascript has been marked as obsolete by RFC 4329 (Scripting Media Types) document and it is recommended to use application/javascript type instead. However, due to legacy reasons, text/javascript is still widely used and it has cross-browser support (which is not always a case with application/javascript MIME type, especially with older browsers).

15.02.2016 03:20

For specifying the interesting JSON result, you add "application/json" in your request header like below:

"Accept:application/json" is a desired response format.

"Content-Type:application/json" specifies the content format of your request, but sometimes you specify both application/json and application/xml, but the quality of these might be different. Which server will send back the different response formats, look at the example:


This will return XML, because XML has higher quality.

04.09.2016 10:21
If I may start an argument here: The accept header in the request does not make the server reply in that format. As you said, it's the desired format. The q qualifier is a wieghtage. The server app can go ahead and reply in whatever format it desires if it doesn't do as the request says. Along the same vein, if the server app only supports xml, specifying json won't do any auto-convert; you'll get an xml response. by Hussain Akbar, 29.11.2019 05:26

To complement the rest of the answers, the MIME type for JSON linked data (JSON-LD) according to W3C is:


Type name: application

Subtype name: ld+json

Additionally, from the same source:

File extension(s):


03.01.2017 22:15

The proper current standard is application/json. While the default encoding is UTF-8, it is worth mentioning that it could also be UTF-16 or utf-32. When JSON is written in UTF-16 or UTF-32, binary content-transfer-encoding must be used.

There is more information about json here: https://tools.ietf.org/html/rfc4627

more information on binary transfer encoding here: https://www.w3.org/Protocols/rfc1341/5_Content-Transfer-Encoding.html

17.10.2016 21:40

Always try to remember these three content types even though there are many content types. as you may have to use these more frequently.

  • Content-Type: application/json
  • Content-Type: application/xml
  • Content-Type: text/html
08.04.2019 20:37
Don't forget text/plain by jpaugh, 20.08.2019 15:44

A part of your question is relevant to me as I just came across it.

A third-party provider is providing a REST service that is used by multiple clients. It's a straight-forward REST called with query parameters that returns a well-formed JSON. I have tested it with PHP and Java where it worked as expected.

My client uses Oracle Service Bus as a gateway between his application server and the Internet. When I made the OSB service, it crashed with an Invalid message format error. Turned out that the content-type being returned was text/html. OSB treats responses as per this header; converting between text, XML and JSON. In this case, the response was JSON but the header didn't say so. Contacting the provider, I got the reply: "We're not going to change it as it doesn't effect anyone else".

The Content-Type header specifies what the content should be, not what it actually is. That is to say, in your consuming program, it's up to you to check or ignore it and process the content in any manner. Another example, you can return GIF data but specify the content type as JSON, then go ahead and ignore the header and read the image data. This won't hurt your program, but may hurt others.

Moral of the story: Play nice.

29.11.2019 05:17

As some research,

Most commonly MIME type is


Let's see a example to differentiate with json and javascript.

  • application/json

It is used when it is not known how this data will be used. When the information is to be just extracted from the server in JSON format, it may be through a link or from any file, in that case, it is used.

For example-

$directory =[ 

    ['Id'=> 1, 'Name' => 'this' ], 

    ['Id'=> 2, 'Name' => 'is'], 

    ['Id'=> 3, 'Name' => 'stackoverflow'], 


// Showing the json data 

echo json_encode($directory);     


Output is,

[{"Id":1, "Name":"this"}, {"Id":2, "Name":"is"}, {"Id":3, "Name":"stackoverflow"}]

  • application/javascript

it is used when the use of the data is predefined. It is used by applications in which there are calls by the client-side ajax applications. It is used when the data is of type JSON-P or JSONP. 

For example



$dir =[ 

    ['Id'=> 1, 'Name' => 'this' ], 

    ['Id'=> 2, 'Name' => 'is'], 

    ['Id'=> 3, 'Name' => 'stackoverflow'], 


echo "Function_call(".json_encode($dir).");"; 



Output is,

Function_call([{"Id":1, "Name":"this"}, {"Id":2, "Name":"is"}, {"Id":3, "Name":"stackoverflow"}])

And for other MIME Types see full detail here,


13.12.2020 07:50