handyman
Hazuu Tools

JSON Parser

Parse JSON strings and escaped data into clean, structured output.

Input JSON
Parsed Output
Parsed output will appear here...
info

About JSON Parser

JSON Parser is a free online tool that converts a raw JSON string into a structured, pretty-printed result. Unlike a JSON formatter that only adds indentation or a JSON viewer that browses an already-parsed tree, this tool focuses on the parse step itself — specifically on input that is not yet a clean JSON literal, such as a minified single-line blob, a JSON-encoded string from a REST API wrapper, or a value that has been stringified multiple times.

Its standout capability is recursive double-encoded JSON unwrapping. When an API embeds a JSON object inside a quoted string — producing something like "{"name":"Alice","score":42}" — one call to JSON.parse returns another string, not an object. This tool detects that pattern and keeps parsing until it reaches a real value, then reports exactly how many parse passes were needed. The stats bar also shows the root type (object, array, string, number, boolean, or null), the number of top-level keys or array items, and the maximum nesting depth, so you understand the shape of your data at a glance.

Every parse runs entirely in your browser using the native JSON.parse function — nothing is uploaded, logged, or sent to a server. You can paste text directly, upload a .json or .txt file, or load the built-in sample to see double-encoded unwrapping in action. The tool is completely free with no rate limits and no account required.

star

Key Features

check_circle

Recursive double-encoded unwrapping

When JSON has been stringified more than once, the parser keeps calling JSON.parse until a non-string value is reached. The stats bar shows the number of passes so you know exactly how many layers were nested.

check_circle

Structural metadata at a glance

After parsing, a stats bar reports the root type, the count of top-level keys (for objects) or items (for arrays), and the maximum nesting depth — no manual inspection required.

check_circle

File upload support

Beyond pasting text, you can upload a .json or .txt file directly. The contents load into the input pane and are parsed without leaving the page.

check_circle

100% client-side — no data upload

All parsing uses the browser-native JSON.parse API. Your JSON strings never leave your machine, making the tool safe for API tokens, credentials, or internal config payloads.

check_circle

Clear syntax error reporting

If the input cannot be parsed, the error bar shows the exact SyntaxError message from the JavaScript engine so you can pinpoint and fix the malformed token quickly.

check_circle

One-click copy of parsed output

Once the JSON is parsed and pretty-printed, a single button copies the full formatted result to your clipboard, ready to paste into your editor, ticket, or diff tool.

help

How to Use

01

Paste or Upload JSON

Paste your raw or double-encoded JSON string into the input pane, or upload a .json file.

02

Click Parse

Hit the "Parse" button. The tool recursively parses the input until it reaches a structured result.

03

Review the Output

View the pretty-printed result, check type and depth info in the stats bar, and copy the parsed output.

code_blocks

Example

A double-encoded JSON string (an object serialized inside a quoted string) is recursively unwrapped in two parse passes, producing a clean pretty-printed object. The stats bar reports type: object, 4 keys, depth 2, and 2 parse passes.

Double-encoded JSON input
"{\"name\": \"Hazuu Tools\", \"version\": 2, \"features\": [\"fast\", \"secure\", \"free\"], \"config\": {\"theme\": \"dark\", \"lang\": \"en\"}}"
Parsed output
{
  "name": "Hazuu Tools",
  "version": 2,
  "features": [
    "fast",
    "secure",
    "free"
  ],
  "config": {
    "theme": "dark",
    "lang": "en"
  }
}
lightbulb

Common Use Cases

  • arrow_circle_right

    Unwrapping double-encoded API responses

    Some REST APIs — especially those that proxy or serialize their payloads — return a JSON object embedded inside a quoted string. Paste the raw response body here and the parser strips every layer automatically, unlike a formatter that would just indent the outer string.

  • arrow_circle_right

    Decoding log file JSON strings

    Application logs often store structured data as an escaped JSON string inside a larger JSON document. The parser recursively resolves nested stringification so you can read the actual event payload without writing a one-off script.

  • arrow_circle_right

    Inspecting unknown API payload structure

    When you receive an unfamiliar JSON blob, the stats bar — root type, key count, and nesting depth — gives an instant structural summary before you dig into the content. A JSON viewer requires you to have already parsed the data.

  • arrow_circle_right

    Pre-validating JSON before committing config files

    Paste a draft configuration or feature-flag payload to confirm it parses cleanly and has the expected structure. The syntax error bar pinpoints the offending token, which is more actionable than a generic "invalid" message from a JSON validator.

  • arrow_circle_right

    Recovering parseable data from stringified payloads in webhooks

    Webhook senders sometimes double-stringify their body. Dropping the raw webhook payload here immediately reveals the real event object without needing to write a quick Node.js snippet or reach for the DevTools console.

quiz

Frequently Asked Questions

What is a JSON Parser? expand_more
A JSON parser takes a raw JSON string and converts it into a structured JavaScript value (object, array, string, number, boolean, or null). It validates the syntax and makes the data readable and navigable.
How does it handle double-encoded JSON? expand_more
When JSON is stringified multiple times (e.g., an API wraps a JSON object inside a string), our parser detects this and recursively calls JSON.parse until the result is no longer a string. The stats bar shows how many parse passes were needed.
Is my data safe? expand_more
Yes. All parsing happens locally in your browser using the native JSON.parse function. No data is sent to any server, so your JSON stays completely private.
What types of input are supported? expand_more
The parser handles objects, arrays, strings, numbers, booleans, null, and any combination of these — including edge cases like escaped/double-encoded strings and raw primitives like "42" or "true".
How is JSON Parser different from JSON Formatter? expand_more
JSON Formatter assumes you already have a valid JSON value and adds indentation and line breaks for readability. JSON Parser focuses on the parse step: it accepts raw strings (including double-encoded ones), converts them to a structured value, and reports metadata like type, depth, and parse iterations. Use the formatter when your JSON is already valid but messy; use the parser when you need to decode or inspect what a string actually contains.
How is JSON Parser different from JSON Validator? expand_more
JSON Validator checks whether a piece of text is syntactically valid JSON and reports errors if not. JSON Parser goes further: it parses the input into a real value, recursively unwraps double-encoded strings, and shows structural metadata. Both catch syntax errors, but the parser is the right choice when you also need to see the resulting structure.
What does the nesting depth number mean? expand_more
Depth counts how many levels of objects or arrays are nested inside each other. A flat object like {"a": 1} has depth 1. An object containing another object — {"a": {"b": 2}} — has depth 2. This helps you quickly spot unexpectedly deep structures that might cause issues in your code.
Can I parse a plain JSON number or boolean? expand_more
Yes. The parser handles any valid JSON value at the root level, including raw numbers like 42, booleans like true or false, and null. The stats bar will show the appropriate type label for each.