JSON tools
Locate a value, inspect address tokens or generate an address with explicit encoding rules.
Copy and download contain the complete primary result: selected JSON value, token array, generated Pointer or transformed token. The reference details below are not included.
Inputs stay in browser memory and are not uploaded or saved.
Plain: empty input selects the root; / selects an empty key. Fragment: include # and use UTF-8 percent encoding. Spaces and line endings are significant; inputs are not trimmed.
Run again to refresh the result. Copy and download are disabled while it is out of date.
Use JSON Pointer to check the exact location named in an API response, schema error or patch path. A syntactically valid address may still point to a missing member. This workbench separates parsing an address from resolving it against a document, so these failures stay distinct.
A JSON Pointer tester helps distinguish the root, an empty property name and an array index. The JSON Pointer generator accepts explicit string tokens; the JSON Pointer resolver reads one value without editing its source. JSON Pointer escape and JSON Pointer unescape operate on a single token, keeping address syntax separate from JSON string escaping.
JSON Pointer uses an empty string for the entire document and / for a property whose name is empty. A token such as 0 becomes an array index only when the current value is an array. The same token can also be an ordinary object key.
JSON Pointer first escapes each token, then joins tokens with slash separators. URI fragment output adds a separate UTF-8 percent-encoding layer. The decoded token list shows why one escaped slash belongs to a key while a path separator moves to another level.
Parse needs only Pointer text and a representation. Locate value also requires a strict JSON document. Choose plain or URI fragment explicitly; the tool does not infer the format from #. Press Ctrl/Cmd+Enter or Run to process the current inputs.
Generate takes a JSON array of strings: [] addresses the root and [""] addresses an empty key. A number such as [0] is rejected. Escape and Unescape take one raw or encoded token; they ignore the representation setting and do not use the JSON document.
The primary result is selected JSON, a decoded token array, a generated address or transformed token. Copy and download export this full result, excluding the reference details. Example and Clear preview their replacement before applying it; Undo restores inputs, settings and the previous result.
Parse checks syntax without requiring the target document. Locate value walks the actual document. Generate joins explicit string tokens, while Escape and Unescape transform one token. Unrelated source text is ignored outside Locate value.
Plain text preserves %, +, dots, backslashes, spaces and line endings literally. A fragment starts with # and requires valid UTF-8 percent bytes for spaces and non-ASCII characters. Percent decoding happens once before splitting the path; token decoding happens once afterward.
The selected subtree keeps JSON types, original object key order and numeric spellings, including large integers, precise decimals, large exponents and -0. Missing members produce errors; a successfully selected null, false, zero or empty string remains a real value.
JSON Pointer results include decoded tokens and plain and fragment reference forms when available. JSON string display makes empty text and control characters visible. Those display quotes are not part of the raw address. Each detail preview is limited to 5,000 characters.
Within one key, encode a slash as ~1. The token a/b therefore becomes a~1b, and its plain address is /a~1b. Passing /a/b instead selects a field b inside a. Use Escape for the token alone, or Generate with ["a/b"].
Encode a literal tilde as ~0. A key m~n becomes /m~0n. Unescape performs one decoding pass, so ~01 becomes the literal text ~1. Repeating that pass would change the key and is deliberately avoided.
Empty plain input selects the entire JSON document; fragment # has the same meaning. A slash is different: / selects an empty object key. Generate uses [] for the root and [""] for that empty key. A document whose root is null can also be selected successfully.
Array indexes must be canonical nonnegative decimal integers within the array bounds. Values such as 01, -1, +1 and 1.0 are rejected. The - token has no existing value to read. These array rules do not prevent an object from having a literal key named 01 or -.
No. This tool checks addresses, generates them and reads existing values. It does not apply JSON Patch operations or create missing nodes. You can inspect a patch path here, but any actual modification must take place in a separate patch workflow.
Found an address that behaves unexpectedly?
Try JSON Pointer with the example, compare the root and empty-key tokens, then copy the complete selected value or generate your own address.