Sobre os arquivos JSON
Dados JSON
Formato universal de dados estruturados (2001). Padrão de fato para APIs web, configurações de aplicativos, troca de dados estruturados.
Família
Documents & Text
Extensão
.json
Tipo MIME
application/json
Pode ser usado como
COMO NASCEU O
FORMATO JSON.
JSON — JavaScript Object Notation — was popularized by Douglas Crockford around 2001-2002 as a lightweight alternative to XML for browser-server data exchange. The syntax was lifted directly from the way JavaScript already defined object literals, which made parsing trivially cheap in the browser: eval(jsonString) worked (before anyone realized that was a security nightmare).
JSON went from a hack to a standard remarkably fast: ECMA-404 in 2013, RFC 8259 in 2017, and by then nearly every new REST API used it instead of XML. Crockford’s famous line was "I don’t want to maintain JSON" — he refused to version the format, arguing simplicity was its main virtue. Today JSON carries config files, API payloads, logs, database documents, build manifests, and an ever-growing chunk of the data plumbing of the internet.
CURIOSIDADES E
FATOS INTERESSANTES.
JSON is a subset of JavaScript, but not a strict one — some valid JSON (like leading zeros) is invalid JS, and vice versa.
Douglas Crockford intentionally refused to version the format: "JSON is done. It does not need a v2."
JSON does not permit trailing commas or comments — which is why JSONC (JSON with Comments) and JSON5 were invented.
The largest public JSON file is OpenStreetMap's planet dump — over 100 GB minified.
JSON's only allowed whitespace outside strings is tab, space, newline, and carriage return — nothing else.
VANTAGENS E
LIMITAÇÕES.
Vantagens
- Dead-simple — you can memorize the entire grammar on one page.
- Native parsers in every programming language.
- Human-readable and easy to debug.
- Compact — much smaller than equivalent XML.
- Frozen spec — a JSON parser written in 2010 still handles new JSON files from 2026.
Limitações
- No comments allowed — config files feel verbose.
- No trailing commas — a constant source of parse errors.
- No native date, decimal, or binary types — everything is strings or numbers.
- Easily bloated by repeated keys; large payloads compress poorly vs binary alternatives.
- Streaming is awkward — JSON wants to be parsed whole.
Tamanhos típicos de arquivo
Small config
< 1 KB
REST API payload
1-100 KB
Database export
10 MB - 100 GB
Especificações técnicas
- MIME type
- application/json
- Extension
- .json
- Standard
- ECMA-404, RFC 8259
- Encoding
- UTF-8, UTF-16, or UTF-32
- Allowed types
- object, array, string, number, boolean, null
CONVERTER A PARTIR DE
JSON
Casos de uso comuns
Web APIs, configuration files, data exchange, NoSQL databases
Formatos relacionados
Comparativos populares
JSON vs PDF
Diferenças, tamanho de arquivo e quando escolher cada formato.
JSON vs DOCX
Diferenças, tamanho de arquivo e quando escolher cada formato.
JSON vs ODT
Diferenças, tamanho de arquivo e quando escolher cada formato.
JSON vs TXT
Diferenças, tamanho de arquivo e quando escolher cada formato.
JSON vs MD
Diferenças, tamanho de arquivo e quando escolher cada formato.
JSON vs HTML
Diferenças, tamanho de arquivo e quando escolher cada formato.
Conversões populares de JSON
Os destinos mais procurados ao converter arquivos JSON.
Perguntas frequentes sobre JSON
Perguntas frequentes
JSON (JavaScript Object Notation) is a lightweight text formato para data exchange, popularized by Douglas Crockford around 2001. JSON represents nested objects, arrays, strings, numbers, booleans, e null values em um syntax derived de JavaScript. It is the default data formato para moderno web APIs.
JSON arquivos são plain text — abrir them in any text editor (Notepad, VS Code, Sublime Text, TextEdit). para formatoted reading, usar JSON-aware editors (VS Code auto-indents) ou online viewers like jsonformatter.org. Every web browser displays JSON directly if you abrir o arquivo locally.
Use KaijuConverter's JSON-to-CSV converter para nested data flattened em a tabular formato. para simples flat JSON (array of objects), command-line ferramentas like jq + csvkit give more control. Python's pandas e JavaScript's PapaParse also handle the conversion in one line of code.
JSON para machine-to-machine data exchange (APIs, config) — strict spec, fast parsers in every language. YAML para human-edited config arquivos — suporta comments, multi-line strings, e references. Kubernetes, Docker Compose, e GitHub Actions usar YAML; REST APIs overwhelmingly usar JSON.
JSON's strict specification disallows comments to keep parsers simples e unambiguous. Workarounds include JSONC (JSON com Comments, used by VS Code config), JSON5 (relaxed syntax com comments), ou a convention of adding a "comment" ou "_doc" field in your data.
JSON itself cannot execute code like JavaScript eval() can, making it safer than older exchange formatoos. Porém, deeply nested JSON can exhaust memory (a "billion laughs" variant) — usar streaming parsers e limit recursion depth when processing untrusted input.