What is JSON?
who is json
A screenshot went viral recently: someone using an AI coding tool, having just handed it full access to their machine, typed a single message “who is json” like they were asking about a coworker. The internet had a field day.
JSON isn’t a person. It’s not even close to a person. But the mix-up was funny enough that it briefly became one of the biggest jokes in tech.
Here’s the thing though if you’ve ever wondered the same thing (minus the full-access AI part), you’re not alone, and it’s a genuinely reasonable question. JSON sounds exactly like a name. It’s usually pronounced “Jason.” So let’s actually answer it properly.
Think about the last time you filled out a form maybe signing up for a gym membership. Name, age, phone number, a couple of checkboxes for your preferences. Simple, right? Someone (or something) could glance at that form and instantly understand exactly who you are and what you want.
Now imagine computers needing to do the same thing except instead of filling out a form once, they’re doing it millions of times a second, passing little bundles of information back and forth between apps, servers, and databases. They needed their own version of that form. That’s basically what JSON is.
So What Actually Is JSON?
JSON stands for JavaScript Object Notation. The name is a little misleading you don’t need to know JavaScript to use it, and almost every programming language today can read and write it.
At its core, JSON is just a way of organizing information using labels and values, kind of like that gym form. You say what something is (a “key”), and then what it equals (a “value”). Simple as that.
Get Dorine Writes’s stories in your inbox
Join Medium for free to get updates from this writer.
Here’s what it looks like in practice:
{
"name": "Maya",
"age": 27,
"city": "Nairobi",
"isMember": true
}That’s it. No complicated syntax, no confusing structure just clearly labeled information sitting inside curly brackets.
A Slightly Bigger Example
JSON gets more useful once you start nesting information inside other information which sounds complex, but really isn’t:
{
"user": {
"name": "Maya",
"hobbies": ["running", "cooking", "chess"]
}
}Here, “hobbies” is a list (called an array), and the whole thing is tucked inside a “user” object. You could keep nesting these forever a user with an address, which has a city, which has a zip code, and so on. It scales without getting messy.
Why Should You Actually Care?
You’ve almost certainly used JSON today without knowing it.
Check the weather on your phone? Your app asked a weather service for data, and that service replied in JSON. Log into a website? Your login details often travel as JSON behind the scenes. Order food, check your bank balance, save your settings in an app JSON is quietly doing the legwork in nearly all of it.
It’s become the internet’s go-to language for passing information around, mostly because it’s lightweight and doesn’t waste space with unnecessary formatting.
Why Developers Actually Like It
Developers love JSON because it maps naturally onto how most programming languages already think about data as labeled pairs of information. It’s also easy to convert into a format a program can use (and back again), which makes it fast and painless to work with. Compared to older formats like XML, JSON is shorter, cleaner, and far less annoying to read.
The Takeaway
JSON isn’t some intimidating technical concept reserved for engineers it’s really just a tidy, universal way of writing down information so that different systems can understand each other. Once you see it as a form with labels and answers, the whole thing clicks.
Next time you check the weather or log into an app, know that somewhere in the background, a little JSON message just made that possible.
And if anyone ever asks “who is json” again now you know exactly who to tell them it isn’t.
Have you spotted JSON in the wild before maybe poking around a website’s dev tools? What did it look like?
