Minificador JSON

Elimina los espacios de JSON para obtener la salida mas compacta — ahorro de bytes inmediato.

Se ejecuta totalmente en tu navegador. Tu JSON no sale de tu dispositivo.
Procesando — Minificar…
Entrada
Vista virtualizada — entrada de solo lectura. Solo se renderizan las lineas visibles.
Pega JSON aqui, o arrastra y suelta un archivo...Max 50 MB
Salida
Vista virtualizada — solo se renderizan las lineas visibles para rendimiento.
Pega JSON para empezar

Como usar

Atajos de teclado
  1. Pega tu JSON Escribe, pega o arrastra y suelta un archivo JSON en el editor.
  2. Elige una accion Cambia entre Formatear, Validar, Minificar y Analizar con las pestanas.
  3. 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
Errores comunes

Explicaciones de reglas 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.

Se ejecuta totalmente en tu navegador. Tu JSON no sale de tu dispositivo. Ultima actualizacion: 2026-05-03 Acerca de ToolMatic

Preguntas frecuentes

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.