Skip to content
yutils
Example

Input (minified JSON)

{"name":"yutils","version":"0.1.0","private":true,"tools":55}

Output (2-space indent, sorted keys)

{
  "name": "yutils",
  "private": true,
  "tools": 55,
  "version": "0.1.0"
}

Note

Enable sort-keys to make two JSON values visually diff-friendly. The tree view shows the same data as an expandable hierarchy you can collapse by depth. Double-encoded JSON (Redis · Kafka, etc.) is auto-detected and a one-click unwrap hint appears. MongoDB Extended JSON (`$oid`, `$date`, etc.) is also recognized in the tree view. The Sample button cycles through three cases.

Usage / FAQ

When to use

  • Format minified API JSON responses with proper indentation
  • Quickly spot missing commas, quotes, or other syntax errors
  • Minify indented JSON to a single line for sharing
  • Use sort-keys to diff two JSON values visually
  • Tree view to navigate deeply nested JSON structures
  • MongoDB Extended JSON (DataGrip exports) auto-recognized in tree view

FAQ

Q.Does data leave my browser?
A.No. Everything runs client-side. JWT tokens or secrets inside JSON never reach any server.
Q.My JSON has comments and it errors out.
A.Standard JSON disallows comments. Use JSONC/JSON5 variants, or consider YAML (yaml-json tool converts both ways).
Q.Why are tree values colored differently?
A.Type-based — string=emerald, number=blue, boolean=amber, null=gray. EJSON wrappers get extra colors (ObjectId=violet, Date=orange, etc.).
Fun facts

  • Douglas Crockford has repeatedly said he didn't "invent" JSON. His own words: "I just discovered it in JavaScript object literals; I didn't create it." What he did in 2001 was give the format a name (JSON), build json.org, and buy the domain. Standardization was a side effect, not a goal.

    Crockford

  • JSON's lack of comments is a deliberate decision by Crockford, not an oversight. He noticed people were starting to abuse comments as parsing directives (like `// utf-8` headers), so he removed them on purpose. "Removing comments saved us from a fragmentation disaster."

    Crockford on G+ (2012)

  • JSON has been standardized six times — RFC 4627 (2006), ECMA-404 (2013), RFC 7159 (2014), ECMA-404 2nd ed (2017), RFC 8259 (2017). "Six standards" is another way of saying "nobody got it exactly right the first time". Current authority: RFC 8259 + ECMA-404 2nd edition.

    RFC 8259

Related guides

Related tools

See all in this category →