JavaScript Object Notation (.json)
RFC EstándarJavaScript Object Notation (JSON) is a lightweight, human-readable text format for data interchange, completely language-independent and universally used for web APIs.
Convertir de JSON a HTML
Convertidor gratuito de JSON a HTML en el navegador. Convierte archivos al instante en tu dispositivo.
Comprimir JSON en línea
Compresión 100% privada en el navegador – los archivos nunca salen de tu dispositivo
Inspeccionar y metadatos
Los sistemas operativos y analizadores de archivos identifican los archivos de JSON inspeccionando la secuencia de bytes binarios inicial:
Firma de cabecera a nivel de bytes (Bytes mágicos)
Los sistemas operativos y analizadores de archivos identifican los archivos de JSON inspeccionando la secuencia de bytes binarios inicial:
FIRMA HEXADECIMAL (DESPLAZAMIENTO 0):
7B or 5BREPRESENTACIÓN ASCII: { or [
Estandarización: RFC 8259 / ECMA-404 / ISO/IEC 21778
Especificaciones técnicas
| Arquitectura del contenedor | Lightweight, text-based, language-independent data interchange format |
| Compresión | Gzip / Brotli / Zstandard text compression (typically achieves 80%-90% ratio) |
| Orden de bytes (Endianness) | UTF-8 encoded Unicode (no Byte Order Mark / BOM recommended) |
| Espacios de color | Not applicable |
| Canales y estructura | Six basic data types: object, array, string, number, boolean, null |
| Dimensiones máximas | Unbounded; limited only by parser memory and maximum string length |
| Transparencia | Not applicable |
| Streaming y progresivo | NDJSON (Newline Delimited JSON) / JSON Lines enables progressive stream processing |
Matriz de comparación técnica: JSON frente a la competencia
| Atributo técnico | JSON (Actual) | 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 |
Modos de corrupción comunes y guía de recuperación hexadecimal
⚠️ SyntaxError: Unexpected token , in JSON at position X.
Causa raíz: Trailing comma after the last item in an array or object, which is strictly illegal in RFC 8259 JSON.
Recuperación: Remove trailing commas from object keys and array entries before passing to JSON.parse().
⚠️ SyntaxError: Unexpected token ' in JSON.
Causa raíz: Strings or keys enclosed in single quotes ('') instead of double quotes ("").
Recuperación: Replace all single-quoted strings and keys with standard double-quoted strings.
Análisis de seguridad y vectores de ataque al analizador
JSON is text-only and safe from direct code execution, but parsing untrusted JSON can lead to Prototype Pollution, ReDoS, or memory exhaustion.
Vectores de ataque conocidos
- 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.
Mejores prácticas defensivas: Never evaluate JSON with eval(). Use JSON.parse() and sanitize '__proto__' properties in recursive object merge functions.
Orígenes históricos e hitos
Ventajas clave y pros
- 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.
Limitaciones técnicas y contras
- 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.
Curiosidades técnicas interesantes
- 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.
Preguntas técnicas frecuentes
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.
Pares de conversión de JSON relacionados
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).