Paste something

Broken JSON, CSVs, log files. It reads what your editor won’t, fixes what’s broken with your say-so, and keeps your text where you put it. It runs in your browser, it opens 8 formats, and it treats all of them the same way — which is the part most viewers get wrong.

Paste something

There is no import step and no new-document dialog. Paste into the app, drop a file onto the window, or paste onto the landing page and keep going from there. What you pasted is scored by every adapter and read by the one most confident it is theirs; when two are close enough that guessing would be a coin flip, the app asks instead of picking.

A document that will not parse is still opened. Broken input is the case this product was built for, not an error state it falls into. What you pasted stays on the left, editable, for the whole session; the tree is added beside it when you ask for it.

What it opens

Each row is a registered adapter. The repair column is the number of steps that adapter actually runs — 40 across all of them, plus the record-by-record path the log-shaped formats use instead.

What it does

Every format collapses to one of two shapes — a document with one root value, or records with many rows — and each verb is implemented once per shape. That is why a CSV gets the same fixing, comparing and searching as a webhook payload. The right-hand column is the only place the two shapes differ.

Where it runs

In the tab you have open. Parsing, fixing, comparing, searching and converting make no network request at all — the editor is bundled into the build rather than fetched from a CDN, and share links carry their data in the URL fragment, which browsers never transmit. What is stored, and where, is listed in the privacy note.

What changed

Every release that changed how the app behaves, in plain words, is in the changelog. No “various bug fixes and improvements”: an entry there is a behaviour the shipped app already has.