JavaScript Object Notation (.json)

RFC 표준

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

발명자: Douglas Crockford연도: 2001MIME: application/json

JSON을(를) HTML(으)로 변환

무료 브라우저 내 JSON-HTML 변환기. 기기에서 파일을 즉시 변환하세요.

JSON에서 HTML로 변환기 →

JSON 온라인 압축

브라우저 내 100% 안전한 압축 — 파일이 기기 외부로 전송되지 않습니다

JSON 압축 →

검사 및 메타데이터

운영 체제와 파일 분석기는 파일 선두의 바이너리 바이트 시퀀스를 검사하여 JSON 파일을 식별합니다:

바이트 단위 헤더 시그니처 (매직 바이트)

운영 체제와 파일 분석기는 파일 선두의 바이너리 바이트 시퀀스를 검사하여 JSON 파일을 식별합니다:

16진수 시그니처 (오프셋 0):

7B or 5B

ASCII 표현: { or [

표준화: RFC 8259 / ECMA-404 / ISO/IEC 21778

기술 사양

컨테이너 아키텍처	Lightweight, text-based, language-independent data interchange format
압축	Gzip / Brotli / Zstandard text compression (typically achieves 80%-90% ratio)
바이트 엔디안	UTF-8 encoded Unicode (no Byte Order Mark / BOM recommended)
색 공간	Not applicable
채널 및 구조	Six basic data types: object, array, string, number, boolean, null
최대 크기	Unbounded; limited only by parser memory and maximum string length
투명도	Not applicable
스트리밍 및 프로그레시브	NDJSON (Newline Delimited JSON) / JSON Lines enables progressive stream processing

기술 비교 매트릭스: JSON 대 경쟁사

기술적 속성	JSON (현재)	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

일반적인 손상 모드 및 헥스 복구 가이드

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

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

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

⚠️ SyntaxError: Unexpected token ' in JSON.

근본 원인: Strings or keys enclosed in single quotes ('') instead of double quotes ("").

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

보안 분석 및 파서 공격 벡터

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

알려진 공격 벡터

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.

방어적 모범 사례: Never evaluate JSON with eval(). Use JSON.parse() and sanitize '__proto__' properties in recursive object merge functions.

역사적 배경 및 주요 이력

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.

주요 장점

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.

기술적 제한 사항 및 단점

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.

흥미로운 기술적 상식

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.

자주 묻는 기술 질문

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.