Paste JSON and view it: a practical workflow for API responses
How to paste JSON from the clipboard, fix the usual copy errors, and pick the right view (cards, table or tree) for the question you are trying to answer.
You have a response body in your clipboard. Maybe it came from the network tab, a curl command, a log aggregator or a message a teammate pasted into chat. You do not need a script or a local project to look at it. You need somewhere to drop the text, a quick answer to "is this even valid?", and a layout that suits what you are hunting for. This post walks through that routine and spends most of its time on the part that actually goes wrong: the text that arrives in your clipboard is often not the JSON you think it is.
The three-step routine
The routine is short. Paste the text into the editor, look at whether it parses, then switch to a view. In View My JSON the app lives at app.viewmyjson.com, you can paste straight into the editor or drop a .json file onto it, and the parsing happens in your browser, so a payload you would rather not send to a server stays on your machine. There is no account to create for the core tools.
The order matters because each step answers a different question. Parsing tells you whether the text is JSON at all. The view tells you what the data looks like. Skipping straight to a view on text that does not parse just shows you an error in a fancier frame, so I always settle the first question first.
Why valid-looking text fails to parse
Most failed pastes are not bad JSON from the server. They are bad copies. Browser consoles are the classic source: if you right-click a logged object and copy it, you may get a JavaScript object literal rather than JSON. That means single-quoted strings, unquoted keys, and sometimes values like undefined that JSON has no concept of.
RFC 8259, the JSON specification, is strict about this. Strings and object keys must use double quotes. There are only three literals, and they are lowercase: true, false and null. There is no undefined, no NaN, no Infinity. Numbers cannot have leading zeros or a leading plus sign, so 007 and +5 are both invalid. If your paste fails, compare it against that short list before assuming the API is broken.
// Copied from a browser console. This is a JavaScript object, not JSON.
{ id: 42, name: 'Ada', tags: ['admin', 'ops'], lastLogin: undefined }
// The JSON equivalent. Keys and strings are double-quoted; undefined is omitted.
{
"id": 42,
"name": "Ada",
"tags": ["admin", "ops"]
}Stray text around the payload
The second most common problem is extra material at the edges. A log line like 2026-03-14T09:12:55Z INFO response={...} puts a timestamp and a label in front of the braces. A curl -i command prints HTTP headers above the body. A chat client may wrap your snippet in smart quotes, which look like quotes but are different characters and will not parse.
The fix is mechanical: select from the first opening brace or bracket to the matching close, and nothing else. A JSON text must be a single value, so a second object pasted after the first, or a closing brace you missed at the bottom, will fail too. Trailing commas are another one. Developers write them in JavaScript all the time, but JSON does not allow a comma after the last item in an array or object.
One more edge case is worth knowing. The spec says JSON exchanged between systems must be encoded as UTF-8 and that generators must not add a byte order mark. Some Windows tools add one anyway. It is invisible in most editors, and some parsers reject it while others skip it. If the first character of an otherwise fine file seems to cause the error, a BOM is a real suspect.
Reading the first error, not the last
When a parser fails it reports a position, usually a line and column or a character offset. Believe the first one. Once a parser hits an unexpected character it cannot be sure what the rest means, so errors later in the output are often fallout from the first. Fix the earliest problem, re-parse, and repeat. Three rounds is typical for a hand-edited file.
Also remember the position points to where the parser gave up, not necessarily where you made the mistake. A missing closing quote on line 12 can surface as an error on line 13, because the parser treated everything up to the next quote as one long string. Look a line or two above the reported spot.
Picking a view for the question you have
Once the text parses, the right view depends on the shape of the data. If the top level is an array of similar objects, like a list of orders or users, a table is almost always the best choice. Columns line up, and you can scan one field down all rows. If the document is a single record with a handful of fields, cards read more naturally. If it is a deeply nested configuration, a tree lets you collapse the branches you do not care about and follow one path down to a leaf.
Cards, Table and Tree views, plus Format and Validate, are free in View My JSON. Charts, 3D, Compare and Rich view are part of Pro. For the everyday job of reading a response, the free views cover it.
[
{ "orderId": "A-1001", "status": "shipped", "total": 42.5, "items": 3 },
{ "orderId": "A-1002", "status": "pending", "total": 18.0, "items": 1 },
{ "orderId": "A-1003", "status": "shipped", "total": 7.25, "items": 2 }
]When the JSON is hiding inside a string
Sometimes a paste parses fine and still looks wrong: the whole document is one long string full of backslashes. That is double-encoded JSON. A service serialized an object, then put the resulting text inside a string field of another object, so every inner quote got escaped. It turns up in message queues, webhook envelopes and log pipelines.
The giveaway is a value that starts with a quote and a brace, like "{\"id\":1}". Take the string value, parse it again, and you get the real object. If you only look at the outer document, you will see one field containing what looks like noise. Spotting this early saves a lot of squinting at escape sequences.
{
"event": "order.created",
"payload": "{\"orderId\":\"A-1001\",\"total\":42.5}"
}A note on what stays on your machine
People paste real data into tools like this, including customer records and tokens that ended up in a response by mistake. The sensible habit is to check how any tool you use handles that. For View My JSON, the core viewing and editing runs in the browser and the text is parsed locally. Even so, redact secrets before pasting anything into any tool when you can, especially if you are sharing your screen afterward.