Ir para o conteúdo principal

0 of 3 uses today · 3 remaining. Go Pro and remove the limit.

Upgrade

JSON Formatter

Validate · format · minify · repair — On-device processing.

Processado no seu navegador

Operation

Input

Output (formatted)

Formatted output appears here...
On-device processing. JSON parsed using the browser's native JSON.parse(). Nothing sent to server — safe for sensitive payloads, secrets, etc.
Sobre

What is a JSON formatter and validator?

Por Quorify EditorialAtualizado em

Quorify's JSON Formatter formats, validates, and indents any JSON string, helping developers inspect API payloads, configurations, and webhook responses with improved readability. The tool follows the official RFC 8259 (IETF) and ECMA-404 standards. Processing happens 100% in your browser — ideal when working with sensitive payloads and you prefer not to paste into online tools that send data to servers. Supports reverse minification, configurable indentation, and syntax error detection with position. Part of the Quorify dev toolkit: combine with Hash Generator to verify payload integrity, UUID Generator for identifiers, and Slug Generator to normalize strings in URLs.

Casos

When to use

  1. Inspect the response from a newly created REST endpoint and validate structure before integrating.

  2. Debug corrupted JSON from production logs, pinpointing the exact position of syntax errors.

  3. Format configuration files (package.json, tsconfig.json, manifest) that arrived minified.

  4. Validate webhook payloads before submitting to processing queue, preventing jobs from failing due to syntax issues.

  5. Compare two indented API responses side by side to identify subtle differences.

Método

How calculation works

The parser uses the browser's native JSON (JSON.parse), which follows RFC 8259. If the string is valid, the result is re-serialized with configurable indentation (2 or 4 spaces, or tab). In case of a syntax error, the browser returns a message with the approximate position of the problem — useful for locating missing commas, unclosed braces, or unquoted strings. The formatter also detects specific JSON types (string, number, boolean, null, array, object) and maintains the original payload key order. For reverse minification, all whitespace outside strings is removed.

FAQ

Frequently asked questions

Is JSON case-sensitive?
Yes. Keys and values differ based on case. true, false, and null are lowercase per specification; True/TRUE are syntax errors. Quotes must be double ("), not single ('). Comments (// or /* */) are not allowed in pure JSON — for that, use JSON5/JSONC.
Why does my JSON with a trailing comma error?
The JSON standard (RFC 8259) does not allow a comma after the last element in an array or object. Modern JavaScript accepts it, but JSON is strict. To support trailing commas, use JSON5 or JSONC — derived formats that are not strictly compatible with APIs expecting standard JSON.
How do I represent dates in JSON?
JSON has no native date type. The most common convention is ISO 8601 in a string: "2026-05-21T14:30:00Z". Other options: Unix timestamp (number in seconds or ms since epoch) or a structured object {year, month, day}. Combine ISO 8601 with our Epoch converter to work with timestamps.
Is there a size limit?
Browsers support JSON strings in the order of hundreds of megabytes in memory, but web formatters typically slow down above ~10 MB due to DOM rendering. For very large files, use CLI tools like jq.
What's the difference between JSON and JSON5?
JSON5 is an informal extension that adds human-friendly features: comments, trailing commas, unquoted keys, single-quoted strings, hexadecimal numbers. APIs and web libraries expect strict JSON; JSON5 is more common in configuration files that humans edit directly.
Why validate JSON before sending to an API?
Because strict APIs return 400 errors with vague messages when the payload is invalid. Validating beforehand saves debugging time, prevents mid-transaction aborts, and improves your own system's observability.
Fontes

Official sources

Tabelas, leis e referências consultadas para fundamentar esta ferramenta.

  1. International standardRFC 8259 (2017)IETF · Internet Engineering Task Force

    RFC 8259 — The JavaScript Object Notation (JSON) Data Interchange Format

    Official technical specification of the JSON format, including grammar, encoding, and interoperability rules. Foundation for any JSON formatter, parser, or validator.

    Consultar fonte oficial
  2. International standardECMA-404 (2nd ed.)Ecma International

    ECMA-404 — The JSON Data Interchange Syntax

    ECMA standard for JSON format, aligned with RFC 8259 and adopted by languages, APIs, and databases worldwide.

    Consultar fonte oficial

Metodologia — esta ferramenta consulta as tabelas e legislação vigentes nas fontes acima. As regras são atualizadas conforme novas instruções normativas são publicadas pelos órgãos competentes.

Última verificação editorial: junho de 2026.

SponsoredQuorify · free plan
Quorify Pro

Use Quorify without limits

100 uses/day across all 125 tools · ad-free · extended history

Starting at$4.08/mo
See plans
Compartilhe
SponsoredQuorify · free plan
Quorify Pro

Use Quorify without limits

100 uses/day across all 125 tools · ad-free · extended history

Starting at$4.08/mo
See plans

Related

Related tools

toolLayout.related_description

Pro

JSON to CSV

Export JSON data arrays perfectly into CSV spreadsheets.

Pro

JWT Decoder

Inspect and debug JSON Web Tokens payloads.

Free

CSS Minifier

Optimize CSS stylesheets for maximum speed.

Free

JS Minifier

Reduce vanilla Javascript payload size painlessly.

Free

HTML Minifier

Compress your HTML output removing dead space to save bandwith.

Free

Markdown Editor

Write and preview Github-flavored Markdown in real-time.