Skip to content We're live on Product Hunt today Upvote
install

tool · one of 34 free, no counter

JSON

How do I read this API response without a formatter site?

A raw JSON response in a browser tab is one long line, and the usual next step is pasting it into a formatter site - which is a stranger’s server receiving whatever was in it. This opens the same body in a window of its own as a folded tree you can search, with a lint pass over it, and nothing crosses the network.

Reach it Press + K on any tab and type json. Ctrl + K on Windows and Linux

Reads a JSON response as a tree, beside the page it came from
reads the tab’s body, when it is JSON
writes nothing
sends nothing
surface a window of its own
search substring, never fuzzy
lint duplicate keys, suspicious numbers, tokens
plan free
section#about

What this actually is

On any endpoint you have opened in a tab, and as a scratch editor for a payload from somewhere else. The window is separate from the panel because a nested response is not readable in a 340px column.

section#asked

Asked about this tool

What happens on a page that is not JSON?

It opens as an empty editor, so it is still the fastest way to read a payload you have on your clipboard. It never guesses at half-JSON inside an HTML document.

Is anything sent to be formatted?

No. The parse, the tree and the search all run in the window. That is the whole argument for having it here rather than using a site.

Why is it a separate window rather than a panel tab?

Because a nested response is thousands of lines wide and a 340px column is not where one is read. The switcher gets you between it and the other windows without going back to the panel.

Does it re-read when I switch tabs?

It reads when it opens, from the tab it was opened on. A viewer that silently re-read on focus would show you a body from a page you had navigated away from.

how to use json

  1. Open the endpoint in a tab, then open JSON - it reads that tab's body.
  2. The tree opens in a window of its own, because a nested response is unreadable in a 340px column.
  3. Search by substring to find the key. Hits are marked in place.
  4. Read the lint pass for duplicate keys, suspicious numbers and tokens.