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.
Formateur JSON
Mettez en forme du JSON avec l'indentation choisie — directement dans votre navigateur, sans inscription.
S'execute entierement dans votre navigateur. Votre JSON ne quitte jamais votre appareil.
Traitement — Formater…
Indent :
Entree
Vue virtualisee — saisie en lecture seule. Seules les lignes visibles sont rendues.
Sortie
Vue virtualisee — seules les lignes visibles sont rendues pour la performance.
Collez du JSON pour commencer
Stocke uniquement : choix de l'indentation (jt-indent).
Comment utiliser
Raccourcis clavier
- Collez votre JSON Tapez, collez ou glissez-deposez un fichier JSON dans l'editeur.
- Choisissez une action Basculez entre Formater, Valider, Minifier et Analyser via les onglets ci-dessus.
- Copiez le resultat Cliquez sur Copier ou appuyez sur Ctrl+Maj+C pour copier la sortie.
- Executer l'action active — Ctrl+Entree
- Formater — Ctrl+Maj+F
- Valider — Ctrl+Maj+V (focus editeur)
- Minifier — Ctrl+Maj+M
- Analyser — Ctrl+Maj+L
- Copier la sortie — Ctrl+Maj+C
- Effacer la saisie — Ctrl+Maj+K
Explications des regles 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 indentation should I use — 2 spaces, 4 spaces, or tab?
It depends on your team's style guide. 2 spaces is the most common default in JavaScript/TypeScript projects. 4 spaces is popular in Python and Java. Tabs let each developer set their own display width. This formatter remembers your last choice.
Does this formatter work offline?
Yes. Once this page is loaded, all formatting happens in your browser using JavaScript. You can disconnect from the internet and it will continue to work.
Can it sort keys alphabetically?
Sort keys is planned for v1.1. For now, the formatter preserves the original key order from your input.
What is the maximum file size?
The formatter handles files up to 50 MB. Files under 2 MB process instantly. Files between 2-10 MB show a working indicator. Files over 10 MB use a background worker with a cancel button to keep the page responsive.
Does it preserve number precision?
The formatter preserves all JSON values exactly as the browser's JSON parser reads them. For very large integers (beyond 2^53), standard JSON parsing may lose precision — this is a limitation of JavaScript, not the formatter.
How does it handle deeply nested JSON?
Deeply nested JSON is formatted normally with the selected indentation at every level. Very large deeply-nested payloads (>10 MB) use a background worker and virtualized rendering.