JSON Key Extractor
List JSON member names, escaped paths, value types, and array-aware structure.
Arrays are shown with [] placeholders by default, so repeated item shapes collapse into one readable path.
What to include
Output view
Extracted Structure
JSON paths and key details will appear here.
users[].name and escaped dot paths are readable conventions, not JSON Pointer or JSONPath. For a standardized pointer syntax, see RFC 6901.A field list should describe shape without pretending arrays are objects
API payloads often repeat the same object shape inside arrays. Writing users.name hides that boundary, while printing every index creates hundreds of near-identical paths. The default users[].name form keeps the array visible and collapses repeated item structure.
Turn on exact indexes when position matters during debugging. Then the same data becomes users[0].name, users[1].name, and so on.
Keys containing dots or brackets need escaping
A real JSON member may be named profile.name. Without escaping, that looks identical to a nested profile object containing name. Property-name dots, brackets, and backslashes are therefore escaped in the displayed path.
{"profile.name":"editor"}→$.profile\.name“Unique key names” answers a different question from “paths”
A member called id may appear under users, orders, and teams. The unique-key view lists id once; the path view keeps each location. Detailed output adds the observed value type and depth, including union-like type summaries when an index-free array path holds mixed value types.
Empty objects and arrays remain visible as terminal fields. That matters in schema reconnaissance because an empty container is still a real value, not the same thing as a missing member.
JSON defines the data model; pointer syntaxes are separate layers
RFC 8259 defines JSON objects, arrays, member names, values, and interoperability rules. It does not define dot notation. RFC 6901 defines JSON Pointer when a standards-based address for a specific JSON value is required.
Boundaries to keep in mind with generated field inventories
- Observed types describe the pasted sample, not every value an API may return later.
- Duplicate object member names are resolved by the browser's JSON parser before extraction; interoperable JSON should use unique names.
- Index-free array paths intentionally merge repeated shapes and may show more than one observed type for the same path.
- Traversal stops beyond 25,000 visited values or 120 nested levels so an unusually large payload cannot lock the page indefinitely.