Packets & routing
Your message doesn't travel across the internet as one big lump. It gets chopped into small chunks called packets, each one labelled with the destination address. The packets are sent off separately, hop along through machines called routers, and get put back together at the other end. This is how everything — a photo, a video, a chat message — actually crosses the network.
A message is cut into packets
Imagine mailing a long book, but the post office only accepts postcards. So you copy the book onto a stack of postcards, number them (page 1, page 2, page 3…), write the same destination address on every one, and drop them in the mailbox. The internet does exactly this. Before your message leaves, it's sliced into small packets. Each packet carries a piece of the data, the destination address, and its number in line. Sending small postcards instead of one giant parcel keeps the network fair (nobody hogs the wire with one huge file) and tough (if one postcard gets lost, you only re-send that one, not the whole book).
Routers are the signposts that pass packets along
No single wire runs from your house straight to a far-away server. Instead the internet is a giant web of connection points called routers. A router is like a signpost at a crossroads: a packet arrives, the router reads the destination address on it, decides which road points more or less toward that address, and sends it down that road. Then the next router does the same. Hop by hop, the packet gets closer until it reaches the machine with that address. No router knows the whole path — each one only knows 'for an address like this, the next step is that way.' That's enough. Like asking for directions town by town, you reach a faraway place without anyone needing the entire route in their head.
Packets travel independently — and can arrive out of order
Here's the surprising part: the packets of one message don't have to travel together or take the same path. One postcard might go through one set of routers, the next might take a slightly different route (maybe one road got busy). They race across separately. That means they can arrive out of order, or one might be slower than another. So the receiver uses the numbers on the packets to sort them back into the right order, and notices if any number is missing so it can ask for that one again. Putting packets back in order and re-asking for lost ones is a job handled by something called TCP — that's the next topic.
Questions you might have
▸If packets take different paths, how does the message not get scrambled?
Because every packet is numbered, like the postcards page 1, page 2, page 3. No matter what order they arrive in, the receiver sorts them by their numbers before reading. The paths can differ; the numbering keeps the message correct.
▸Does a router know the whole way to the destination?
No, and it doesn't need to. A router only knows 'for an address like this, send it that direction — one hop closer.' The next router figures out the next hop. The full path emerges from many routers each making one small, local decision.
▸What happens if a packet gets lost on the way?
The receiver notices a number is missing (say it got packets 1, 2, and 4 but not 3) and asks the sender to send that one again. Only the missing packet is re-sent, not the whole message. Spotting and re-asking for lost packets is TCP's job, coming up next.
▸Why bother cutting it into packets at all — why not send the whole thing?
Small packets share the wires fairly so one giant download can't freeze everyone else, they can take whatever route is least busy, and a hiccup only loses a tiny piece instead of the entire message. Chopping things up is what makes the internet fair and resilient.
Best read after: IP addresses