Skip to content
uencoder
TASK

Format minified JSON so it can be read (and diffed)

Turn a one-line API response into indented JSON, with precise error locations when the input is not valid JSON at all.

  1. 1
    JSON Formatter →

    Paste the minified JSON. Choose indent size in the options (2 spaces is the ecosystem default). The output is safe to paste into a diff or PR review.

  2. 2

    If formatting fails, the input is not valid JSON — the tool reports the exact line and column (common culprits: trailing commas, unquoted keys, single quotes, NaN/undefined values). Fix the source, not the formatter: JSON.stringify-level strictness is what every consumer will apply.

  3. 3
    JSON Validator →

    Validation-only pass when you just need a yes/no with the error position, without producing formatted output.

  4. 4

    For large responses, remember everything runs locally in this tab — there is no size ceiling from an upload limit, only your browser's memory. Minified payloads of several megabytes format in well under a second.

Frequently asked questions

Does pretty-printing change the data?
No. Formatting only changes whitespace between tokens. The parsed values are identical, and re-minifying restores the semantics exactly (key order is preserved too, per JSON object semantics).
Can I sort the keys instead?
Key sorting is a different transformation (useful for stable diffs). This formatter preserves original key order by design — sorting silently changes what a diff means.

Workflows that solve this

Convert naming case and validate as JSON
Convert identifiers to a target naming convention, then validate the output as JSON to confirm structure.
PIPELINE
Compare two YAML configs via JSON
Convert YAML configs to JSON for diff-friendly comparison of structured values.
PIPELINE
Encode a JSON payload for URL transport
Prepare a JSON document for a URL parameter: pretty-print, Base64-encode, then percent-encode — the exact inverse of the nested-parameter decode chain.
PIPELINE
HJSON to JSON Format
Format HJSON then convert to standard JSON.
PIPELINE
JS Format and JSON Validate
Format JS code then validate as JSON.
PIPELINE
Format JSON and compute integrity checksum
Pretty-print a JSON document and compute a CRC32 checksum to detect any subsequent modifications.
PIPELINE
Minify and validate JSON
Format JSON for inspection and validate it is syntactically correct in one pass.
PIPELINE
Generate JSON Schema and Validate
Generate a JSON schema from sample data then validate against it.
PIPELINE
Format JSON and generate TypeScript interface
Format a JSON document then infer a TypeScript interface definition in one chain.
PIPELINE
Validate, format, then convert JSON to YAML
Convert a (possibly minified) JSON config to YAML, catching syntax errors at the first node instead of producing subtly wrong YAML.
PIPELINE
JSON5 to JSON Format
Format JSON5 then convert to standard JSON.
PIPELINE
JSONC to JSON Format
Format JSONC (JSON with comments) then convert to standard JSON.
PIPELINE
Decode and format a JWT payload
Parse a JWT token, extract its payload, and format the JSON for inspection.
PIPELINE
Parse Query String and Format JSON
Parse query string into key-value pairs then format as JSON.
PIPELINE
Convert TOML to JSON
Parse a TOML configuration file into JSON for tools and APIs that expect JSON input.
PIPELINE
Convert TOML to YAML via JSON
Transform a TOML configuration file into YAML format, using JSON as an intermediate representation.
PIPELINE
Decode nested URL parameter (Base64 JSON)
Unwrap a URL parameter that carries URL-encoded Base64 JSON into readable, formatted JSON.
PIPELINE
Generate TypeScript interfaces from YAML
Convert a YAML document to TypeScript interface definitions, using JSON as an intermediate format.
PIPELINE
Validate and format YAML
Convert YAML to JSON to validate its structure, then confirm the JSON is well-formed.
PIPELINE

Learn more

Want to understand why?

Related tools