Corrupt a JSON File Online
Corrupt a .json file online for free. Breaks bracket structure and injects invalid UTF-8 so every JSON parser rejects the file.
- Nessun caricamento
- Nessun limite di dimensione
- Nessuna registrazione
Corrompi il tuo file JSON
Calibrato per .json, .jsonl, .geojson, e funziona altrettanto bene con qualsiasi altro formato.
Perché i file JSON sono difficili da corrompere per bene
JSON has no header and no index. It is validated purely by grammar. That makes it easy to break and hard to break convincingly: replacing characters at random often produces something a lenient parser still accepts, or something so obviously mangled it reads as a text edit rather than corruption.
Cosa distrugge questo strumento
- Structural characters. Braces, brackets, commas and quotes are overwritten, so the document can no longer be balanced.
- Invalid UTF-8. Byte sequences that are not valid UTF-8 are injected, which fails at the decoding stage before parsing even begins.
- The opening bytes. The start of the document is destroyed, so streaming parsers fail on the very first token.
- The tail. The closing bytes are replaced, leaving the document permanently unterminated.
Cosa vedrai dopo
| Applicazione | Comportamento |
|---|---|
JSON.parse() | Throws SyntaxError: Unexpected token immediately. |
Python json.load() | Raises JSONDecodeError or UnicodeDecodeError. |
| jq | "parse error: Invalid numeric literal" and a non-zero exit code. |
| Postman / API clients | Reject the body as malformed before sending. |
Motivi comuni per farlo
- Testing that an API rejects a malformed request body with a clean 400 rather than a 500.
- Verifying a config loader fails fast instead of running with partial settings.
- Building malformed fixtures for a parser fuzzing corpus.
- Checking that a data import job reports the failing file rather than dropping records silently.
Come corrompere un file JSON
- Trascina il tuo file .json nel riquadro qui sopra, oppure fai clic per sfogliare.
- Lascia il livello su Standard, a meno che tu non voglia un danno parziale (Light) o debba sconfiggere un software di recupero (Heavy).
- Premi Corrompi file. L'elaborazione avviene sul tuo dispositivo, quindi termina quasi subito.
- Scarica il risultato. Per impostazione predefinita mantiene il nome file e la lunghezza in byte originali.
Domande frequenti su JSON
Why not just delete a closing brace?
Because that is a hand edit, not corruption. It is trivially spotted and trivially fixed. Injecting invalid UTF-8 alongside structural damage makes the file fail at the byte level, the way a truncated transfer actually fails.
Will a lenient parser still read it?
No. At Standard level the file is not valid UTF-8, so even parsers that tolerate trailing commas or comments fail before they reach the grammar.
Does it work on JSON Lines and NDJSON?
Yes. Line-delimited formats use the same text profile, and the injected bytes break individual records as well as the file as a whole.
Can I get a file that is only slightly broken?
Yes. Light level touches roughly 0.5% of the payload, which usually produces a file that fails at one specific offset rather than everywhere.