A JSON Web Token is a small, signed, base64-encoded payload. The server can issue one, the client can carry it on every request, and the server can verify it without consulting a session store.
In plain language
In security, this is one of the pieces a system uses to keep the wrong people out and the right people in. A JSON Web Token is a small, signed, base64-encoded payload. The server can issue one, the client can carry it on every request, and the server can verify it without consulting a session store. If you are new to the field, the simplest mental model is this: a signed token that carries claims as json. Read it once with that frame in mind, then come back and read it again — that is usually enough for the rest of the entry to make sense.
An everyday picture
Think of JWT as a lock on a door. Boring when it works, suddenly the loudest thing in the room when it doesn't. The goal is for it to stay boring.
Where it shows up
JWT runs in the background of any product that handles login, payment, or private data. It is most visible the moment it fails — someone gets in who shouldn't, or someone is locked out who shouldn't be.
A small example
Imagine the scene above. The role JWT plays is the one its blurb describes — A signed token that carries claims as JSON. When you log in to a bank without anyone in a café reading your password, ideas like this are doing the protective work.
Common misunderstanding
One line to take with you
JWT is a quiet promise. Keep the promise small, write it down, and check it works.