JavaScript Object Notation (.json)

RFC Standard

JavaScript Object Notation (JSON) is a lightweight, human-readable text format for data interchange, completely language-independent and universally used for web APIs.

Erfinder: Douglas CrockfordJahr: 2001MIME: application/json

Von JSON zu HTML konvertieren

Kostenloser Konverter von JSON zu HTML im Browser. Konvertieren Sie Dateien sofort auf Ihrem Gerät.

Konverter von JSON zu HTML →

JSON online komprimieren

100% private Komprimierung im Browser – Dateien verlassen Ihr Gerät nie

JSON komprimieren →

Untersuchen & Metadaten

Betriebssysteme und Dateianalysatoren identifizieren JSON-Dateien durch Untersuchung der führenden binären Byte-Sequenz:

Byte-basierte Headersignatur (Magic Bytes)

Betriebssysteme und Dateianalysatoren identifizieren JSON-Dateien durch Untersuchung der führenden binären Byte-Sequenz:

HEX-SIGNATUR (OFFSET 0):

7B or 5B

ASCII-DARSTELLUNG: { or [

Standardisierung: RFC 8259 / ECMA-404 / ISO/IEC 21778

Technische Daten

Container-Architektur	Lightweight, text-based, language-independent data interchange format
Kompression	Gzip / Brotli / Zstandard text compression (typically achieves 80%-90% ratio)
Byte-Endianness	UTF-8 encoded Unicode (no Byte Order Mark / BOM recommended)
Farbräume	Not applicable
Kanäle & Struktur	Six basic data types: object, array, string, number, boolean, null
Max. Abmessungen	Unbounded; limited only by parser memory and maximum string length
Transparenz	Not applicable
Streaming & Progressiv	NDJSON (Newline Delimited JSON) / JSON Lines enables progressive stream processing

Technischer Vergleich: JSON im Vergleich zu Wettbewerbern

Technisches Attribut	JSON (Aktuell)	YAML	XML	Protocol Buffers
Syntax Complexity	Minimal (6 types, strict syntax)	High (indentation-based, complex spec)	High (verbose closing tags, namespaces)	Schema-defined binary wire format
Parsing Performance	Extremely fast in all modern languages	Slow (complex indentation parsing)	Moderate to slow (heavy DOM construction)	Ultra-fast (zero-copy binary deserialization)
Comments Supported	No (deliberately excluded to prevent metadata creep)	Yes (# comments)	Yes (<!-- comments -->)	Yes in .proto files
Network Payload Size	Compact text (very high gzip ratio)	Compact text	Verbose text (heavy tag repetition)	Ultra-compact binary

Häufige Korruptionsarten & Hex-Wiederherstellungsleitfaden

⚠️ SyntaxError: Unexpected token , in JSON at position X.

Ursache: Trailing comma after the last item in an array or object, which is strictly illegal in RFC 8259 JSON.

Wiederherstellung: Remove trailing commas from object keys and array entries before passing to JSON.parse().

⚠️ SyntaxError: Unexpected token ' in JSON.

Ursache: Strings or keys enclosed in single quotes ('') instead of double quotes ("").

Wiederherstellung: Replace all single-quoted strings and keys with standard double-quoted strings.

Sicherheitsanalyse & Parser-Angriffsvektore

JSON is text-only and safe from direct code execution, but parsing untrusted JSON can lead to Prototype Pollution, ReDoS, or memory exhaustion.

Bekannte Angriffsvektore

Prototype Pollution: Keys named '__proto__' or 'constructor' modifying Object.prototype in JavaScript applications.
Stack overflow denial of service via deeply nested JSON structures (e.g. 10,000 opening brackets).
Loss of numeric precision: JavaScript numbers larger than 2^53 - 1 (9,007,199,254,740,991) silently lose precision.

Bewährte Sicherheitsverfahren: Never evaluate JSON with eval(). Use JSON.parse() and sanitize '__proto__' properties in recursive object merge functions.

Historische Ursprünge & Meilensteine

2017RFC 8259 standardizes UTF-8 as the sole mandatory character encoding for JSON.

2013ECMA-404 defines the universal JSON syntax standard.

2001Douglas Crockford specifies JSON to enable stateless browser-to-server data communication.

Hauptvorteile & Stärken

Human-readable, self-describing, and concise text structure.
Native parsing support built into JavaScript engines (JSON.parse) and every major programming language.
Strict specification prevents arbitrary code execution.

Technische Einschränkungen & Nachteile

No support for comments, trailing commas, or circular object references.
No native binary types (binary data must be base64-encoded, inflating size by 33%).
Inefficient serialization compared to binary formats like Protocol Buffers or MessagePack.

Interessante technische Wissenswertes

Douglas Crockford added the software license clause 'The Software shall be used for Good, not Evil' to the original JSMin JSON tools.
JSON is a strict subset of JavaScript syntax, but until ES2019, raw unescaped U+2028 and U+2029 characters were valid in JSON but invalid in JavaScript strings.

Häufig gestellte technische Fragen

Why doesn't JSON allow comments?

Douglas Crockford deliberately excluded comments from the JSON specification to prevent developers from putting parsing instructions or environment-dependent configuration pragmas into data feeds, preserving universal interoperability.

How do you store 64-bit integers in JSON without losing precision?

JavaScript's native Number type is an IEEE 754 double-precision float, which only supports integers up to 2^53 - 1 precisely. 64-bit integers (like database IDs or timestamps) must be serialized as strings (e.g. '1234567890123456789') in JSON.