Minificateur JSON

Supprimez les espaces du JSON pour obtenir la sortie la plus compacte — economie en octets immediate.

S'execute entierement dans votre navigateur. Votre JSON ne quitte jamais votre appareil.
Traitement — Minifier…
Entree
Vue virtualisee — saisie en lecture seule. Seules les lignes visibles sont rendues.
Collez du JSON ici, ou glissez-deposez un fichier...Max 50 Mo
Sortie
Vue virtualisee — seules les lignes visibles sont rendues pour la performance.
Collez du JSON pour commencer

Comment utiliser

Raccourcis clavier
  1. Collez votre JSON Tapez, collez ou glissez-deposez un fichier JSON dans l'editeur.
  2. Choisissez une action Basculez entre Formater, Valider, Minifier et Analyser via les onglets ci-dessus.
  3. 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
Erreurs courantes

Explications des regles de lint

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.

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.

S'execute entierement dans votre navigateur. Votre JSON ne quitte jamais votre appareil. Mis a jour: 2026-05-03 A propos de ToolMatic

Questions frequentes

How much smaller does JSON typically get when minified?

It depends on how much whitespace the input has. Pretty-printed JSON with 2-space indentation typically shrinks 30-60%. Already compact JSON may shrink only 0-5%.

Is minified JSON still valid?

Yes. Minification only removes insignificant whitespace (spaces, tabs, newlines between tokens). The data and structure are identical.

Should I also gzip my JSON?

For network transfer, yes — gzip or brotli compression on top of minification typically achieves 80-95% total reduction. Minification helps even with compression because it removes redundant patterns.

Can it handle large files?

Yes, 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.

Does it preserve key order?

Yes. Minification preserves the order of keys exactly as they appear in the original JSON.

Can it strip duplicate keys?

No — the Minifier preserves all data as-is. To detect duplicate keys, switch to the Lint tab.