LINT_DUPLICATE_KEY
Two properties in the same object use the same key. Most parsers keep the later value, which can hide bugs in copied API payloads and config files.
JSON Lint
Analiza el JSON en busca de problemas comunes — claves duplicadas, comas finales, comentarios, comillas simples.
Se ejecuta totalmente en tu navegador. Tu JSON no sale de tu dispositivo.
Procesando — Analizar…
Entrada
Vista virtualizada — entrada de solo lectura. Solo se renderizan las lineas visibles.
Salida
Vista virtualizada — solo se renderizan las lineas visibles para rendimiento.
Pega JSON para empezar
Solo se guarda: la indentacion (jt-indent).
Como usar
Atajos de teclado
- Pega tu JSON Escribe, pega o arrastra y suelta un archivo JSON en el editor.
- Elige una accion Cambia entre Formatear, Validar, Minificar y Analizar con las pestanas.
- Copia el resultado Pulsa Copiar o usa Ctrl+Mayus+C para copiar la salida.
- Ejecutar la accion activa — Ctrl+Intro
- Formatear — Ctrl+Mayus+F
- Validar — Ctrl+Mayus+V (foco en el editor)
- Minificar — Ctrl+Mayus+M
- Analizar — Ctrl+Mayus+L
- Copiar salida — Ctrl+Mayus+C
- Limpiar entrada — Ctrl+Mayus+K
Explicaciones de reglas de lint
LINT_TRAILING_COMMA
Trailing commas are common in JavaScript and JSON5, but strict JSON rejects them. Remove the comma before the closing brace or bracket.
LINT_LINE_COMMENT
JSON does not support // comments. If you need comments, switch to a JSONC or JSON5-compatible parser instead of strict JSON.
LINT_BLOCK_COMMENT
Block comments are not valid JSON. Remove them or convert the file to a format that explicitly supports comments.
LINT_SINGLE_QUOTED_STRING
Strict JSON requires double-quoted strings and keys. Single-quoted strings usually mean the input is JSON5 or a JavaScript object literal.
LINT_UNQUOTED_KEY
Object keys must be quoted in JSON. Unquoted keys are allowed in JavaScript object literals and JSON5, but not in RFC 8259 JSON.
LINT_BOM
A byte-order mark at the start of the file can confuse downstream tools. Removing it is a safe normalization step.
LINT_CONTROL_CHAR_IN_STRING
Unescaped control characters inside strings can break parsing and transport. Escape them explicitly or remove them.
LINT_EMPTY_INPUT
Empty input does not contain JSON to check. Paste a payload, config, or response body before running lint.
LINT_LOOKS_LIKE_JSON5
This advisory groups comment, quote, and trailing-comma patterns that suggest the input is JSON5-like rather than strict JSON.
What rules does JSON Lint check?
Duplicate keys, trailing commas, line comments (//), block comments (/* */), single-quoted strings, unquoted keys, byte-order mark (BOM), unescaped control characters, and empty input. It also detects JSON5-like patterns and offers to convert to strict JSON.
What does LINT_DUPLICATE_KEY mean?
Two or more properties in the same object have the same key name. JSON parsers silently pick one (usually the last), which often masks bugs. The linter shows the locations of all occurrences.
Are trailing commas allowed in JSON?
No. Strict JSON (RFC 8259) does not allow trailing commas. JSON5 does. If your input has trailing commas, JSON Lint will flag them and offer to remove them via "Convert to strict JSON."
Are comments allowed in JSON?
No. Strict JSON does not support // or /* */ comments. They are allowed in JSON5, JSONC (used by VS Code), and JavaScript object literals. JSON Lint flags them and can strip them.
What is JSON5?
JSON5 is a superset of JSON that allows comments, trailing commas, single-quoted strings, unquoted keys, and more. It is not supported by standard JSON parsers. JSON Lint detects JSON5 patterns and offers a one-click conversion to strict JSON.
"Convert to strict JSON" — what does it change?
It produces a copy with: BOM stripped, comments removed, trailing commas removed, single-quoted strings re-quoted with double quotes, unquoted keys quoted, and the result re-run through Lint to confirm zero residual findings. Your original input is never modified — the converted copy appears in the output pane.