Formats

JSON

The format everything else is compared against, and the one people paste broken most often.

How it opens

JSON parses into the document shape — one root value, browsed as a tree.

Nothing is chosen by file extension alone: every adapter scores the text itself and the highest confidence wins. When two are close enough that guessing would be a coin flip, the app asks instead of picking.

extensions · .json, .json5, .jsonc, .har, .geojson
media type · application/json
shape · document
extra diagnostics · this adapter lints beyond what parsing reports

Fixing

A broken JSON document gets a verdict — “Not valid JSON yet · N fixable” — and a list: every problem on its line, with the fix’s name, before anything changes. Fix all rewrites only the lines it names and leaves every other byte as pasted; ⌘Z puts the original back exactly. Typing a fix yourself counts the verdict down with no click.

A fix that could say something your document did not — a judgment call — is reported and never applied unless you ask.

Nesting

A JSON value can hold another system's output — a stringified body, an escaped document. Unpack opens it in place, names the parser that opened it, and repeats until nothing parses. Pack restores the original text byte for byte rather than re-serializing from the tree.

A sample

The document below is the fixture this adapter ships and its own tests parse — not an illustration written for this page.

clean-order-example.json

{
  "order_id": "ord_8f3aa19c4d",
  "status": "fulfilled",
  "customer": { "id": "cus_4129", "verified": true },
  "items": [
    { "sku": "BRD-OAK-002", "qty": 1, "unit_price": 124.00 },
    { "sku": "OIL-MNRL-008", "qty": 2, "unit_price": 12.50 }
  ]
…