application/ld+json

All MIME types
Application · Standards tree · W3C JSON-LD 1.1.jsonld

Media type / application

application/ld+json

JSON-LD: linked data expressed as JSON, and the format search engines read for structured-data markup.

Served inline: Browsers have no renderer for this, so it downloads even without a Content-Disposition header. That makes it the quiet default for anything you do not want opened in place.

Browser behaviour

Downloads

Charset

charset ignored

Compression

Compress in transit

Send it like this

Content-Type: application/ld+json

The format defines its own encoding, so no charset parameter is registered for this type. Sending one is harmless, but receivers are required to ignore it — it is not doing what people think it does.

Handling verdict

InlineDownloads

Browsers have no renderer for this, so it downloads even without a Content-Disposition header. That makes it the quiet default for anything you do not want opened in place.

Charsetcharset ignored

The format defines its own encoding, so no charset parameter is registered for this type. Sending one is harmless, but receivers are required to ignore it — it is not doing what people think it does.

CompressionCompress in transit

The payload is text-like or otherwise repetitive, so gzip or Brotli removes real bytes. Enable it at the server or CDN.

NameStandards tree

Registered with IANA through a public review process, so the name is stable and every implementation can rely on it meaning the same thing.

Anatomy of the name

RFC 6838

Top-level type

application

Application

Subtype

ld+json

Registered in the standards tree.

Structured syntax

+json

Any client that can parse JSON can read the payload, even without understanding this specific type.

Parameters

profile

Defined for this type in addition to any charset rule above.

What trips people up

1 note
  • In a page this appears inside <script type="application/ld+json">, never as a response type.

Response headers

Content-Type: application/ld+json
X-Content-Type-Options: nosniff
Content-Disposition: attachment; filename="example.jsonld"
Vary: Accept-Encoding

nosniff stops the browser second-guessing the type you declared, which is what makes the rest of this reliable. Content-Disposition: attachment names the saved file and removes any doubt about rendering.

Server configuration

extension mapping

nginx

types {
    application/ld+json  jsonld;
}

Apache

AddType application/ld+json .jsonld

Caddy

@type path *.jsonld
header @type Content-Type "application/ld+json"

Extensions and other spellings

declared

File extensions

.jsonld

File signature

No fixed signature — this format has no reliable magic number, so identify it by parsing rather than by the first few bytes.

Related media types

8
Familyapplication
Treestandards
Suffix+json
Inlinedownload