Free Online JSON Key and Value Extractor
List every key a JSON document uses with how often each appears, pull out every value of one key wherever it occurs, or pick several keys and get a flat list of records ready for a spreadsheet. A key that is present but null is reported separately from a key that is absent, because those are different answers.
Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.
How to Use JSON Key and Value Extractor
Step by step, start to finish.
Any shape. The sample has keys at several depths and one key that appears twice in different places.
The list of keys is for understanding an unfamiliar response. The other two modes are for getting data out of a familiar one.
Keys found in the document are suggested as you type. A dot reaches one level down, as customer.name.
CSV opens straight in a spreadsheet. Several files each produce their own result, downloadable as one zip.
Key Features
What this tool does, and what it does not do.
The fastest way to understand a response you have never seen, including how deep each key sits.
Every value of a key at any depth, optionally with the full path of each one.
Name several keys and get one row per record, which is what a spreadsheet actually needs.
Missing keys and null values are counted separately, because they mean different things.
Three output shapes, with distinct values and counts as switches rather than separate tools.
Everything is read in this tab, so a response full of customer records never leaves it.
About JSON Key and Value Extractor
There are two completely different reasons to pull things out of a JSON document, and they want different tools. The first is understanding: you have been handed a response from an API nobody documented and you need to know what is in it. A list of every key, with how often each appears and how deep it sits, answers that in a few seconds, and it is much faster than scrolling through a formatted tree.
The second is extraction: you know the document and you want some of its data somewhere else, usually a spreadsheet. This is where most tools stop being useful, because the data you want is nested and a spreadsheet is flat. Getting every sku out of a nested order document is easy enough to describe and surprisingly annoying to do by hand, and getting four particular fields out as a table with one row per record is the thing people actually need and almost never have a button for.
The distinction the tool is careful about is absent against null. A record that has no note field and a record whose note is null are different facts about your data, and squashing them together into "empty" sends people to look for the wrong bug. So both are counted, separately, and you can see at a glance whether a field is sometimes missing, sometimes empty, or both.
The last decision is that distinct values are compared as values rather than as text. The number 5 and the string "5" look the same when printed and are not the same thing, and a tool that merges them helps hide exactly the kind of inconsistency you would want to find. Keeping them apart occasionally looks like a longer list than you expected, and that longer list is the answer.
Frequently Asked Questions
Common questions about this tool.