JSON Path Editor

-

How to use it

1. Paste a JSON document into the left panel.
2. Type a path into Path. Plain keys use dots, array indexes use brackets, and keys that are not plain identifiers use quoted brackets: data.items[2].id, data["full name"]. A $. prefix is accepted and ignored.
3. Click Read to see the value and its type. When the path does not exist, the message tells you exactly which segment broke and what the container actually holds.
4. Pick a New type, fill in New value, then click Apply change. Choosing delete removes the key or the array element.
5. The right panel holds the complete modified document. Copy it, or download it as a file.

Common use cases

• Patching a config file - flip one flag deep inside a nested object without touching the rest of the file.
• Fixing one bad record - change a single field in an array of hundreds of entries and export the whole array again.
• Removing a stale key - delete a deprecated field and check the resulting document before you commit it.
• Confirming a path before scripting - resolve the path here first, then put the same path into your own code with confidence.

Why it stays private

The document is parsed, edited and serialized inside your browser. Nothing is uploaded, so configuration with credentials, customer payloads and internal exports stay on your device.

FAQ

Q: What path syntax is supported? A: Keys separated by dots, array indexes in brackets, and quoted brackets for keys with spaces or other special characters. A $. prefix is optional. Bracket segments accept negative indexes, which count from the end of the array.

Q: What happens when the path does not exist? A: You get an explicit error that names the segment where resolution stopped, plus what was actually there, for example an array instead of an object. Nothing is silently created and nothing is silently ignored.

Q: Does editing reformat my whole document? A: Yes. The result is serialized with two-space indentation, so key order is preserved but whitespace is normalized. If you need byte-identical output, edit the file directly instead.