JavaScript Object Notation (.json)
RFC StandartinisJavaScript Object Notation (JSON) is a lightweight, human-readable text format for data interchange, completely language-independent and universally used for web APIs.
Konvertuoti JSON į HTML
Nemokamas JSON į HTML konverteris naršyklėje. Konvertuokite failus akimirksniu savo įrenginyje.
Glaudinkite JSON internetu
100% privatus glaudinimas naršyklėje – failai niekada nepalieka jūsų įrenginio
Tikrinti ir metaduomenys
Operacinės sistemos ir failų analizatoriai atpažįsta JSON failus tikrindami pradinę dvejetainę baitų seką:
Baitų lygio antraštės parašas (magiškieji baitai)
Operacinės sistemos ir failų analizatoriai atpažįsta JSON failus tikrindami pradinę dvejetainę baitų seką:
ŠEŠIOLIKTAINIS PARAŠAS (POSLINKIS 0):
7B or 5BASCII ATVAIZDAVIMAS: { or [
Standartizacija: RFC 8259 / ECMA-404 / ISO/IEC 21778
Techninės specifikacijos
| Konteinerio architektūra | Lightweight, text-based, language-independent data interchange format |
| Glaudinimas | Gzip / Brotli / Zstandard text compression (typically achieves 80%-90% ratio) |
| Baitų seka (Endianness) | UTF-8 encoded Unicode (no Byte Order Mark / BOM recommended) |
| Spalvų erdvės | Not applicable |
| Kanalai ir struktūra | Six basic data types: object, array, string, number, boolean, null |
| Maksimalūs matmenys | Unbounded; limited only by parser memory and maximum string length |
| Skaidrumas | Not applicable |
| Srautas ir progresyvusis įkėlimas | NDJSON (Newline Delimited JSON) / JSON Lines enables progressive stream processing |
Techninė palyginimo matrica: JSON vs konkurentai
| Techninis atributas | JSON (Dabartinis) | 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 |
Dažni sugadinimo režimai ir šešioliktainio atkūrimo vadovas
⚠️ SyntaxError: Unexpected token , in JSON at position X.
Pirminė priežastis: Trailing comma after the last item in an array or object, which is strictly illegal in RFC 8259 JSON.
Atkūrimas: Remove trailing commas from object keys and array entries before passing to JSON.parse().
⚠️ SyntaxError: Unexpected token ' in JSON.
Pirminė priežastis: Strings or keys enclosed in single quotes ('') instead of double quotes ("").
Atkūrimas: Replace all single-quoted strings and keys with standard double-quoted strings.
Saugumo analizė ir analizatoriaus atakos vektoriai
JSON is text-only and safe from direct code execution, but parsing untrusted JSON can lead to Prototype Pollution, ReDoS, or memory exhaustion.
Žinomi atakos vektoriai
- 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.
Geriausia apsaugos praktika: Never evaluate JSON with eval(). Use JSON.parse() and sanitize '__proto__' properties in recursive object merge functions.
Istorinė kilmė ir svarbiausi etapai
Pagrindiniai privalumai
- 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.
Techniniai apribojimai ir trūkumai
- 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.
Įdomūs techniniai faktai
- 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.
Dažniausiai užduodami techniniai klausimai
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.
Susijusios JSON konvertavimo poros
Render structured JSON payloads into styled, human-readable HTML tables.
Parse and extract tabular structured data from HTML pages into JSON objects.
Parse SQL schema and insert queries to extract structured relational database rows into clean JSON objects.
Ingest structured JSON object arrays into relational SQLite database tables with typed columns.
Extract Adobe Swatch Exchange binary color palettes into structured JSON color design tokens.
Compile JSON design token color swatches into binary Adobe ASE files for Photoshop and Illustrator.
Parse GIMP/Inkscape GPL text color palettes into web-ready JSON color arrays.
Convert JSON design tokens and color palettes into standard CSS Custom Properties (:root variables).