;colony/science  / Computers, Visually  / How does the internet send a message?
Computers, Visually

How does the internet send a message?

Your message doesn't travel as one piece down one wire. It's shredded into numbered packets that scatter across the network by different routes and reassemble at the far end.

Plate 57 — A message in pieces packet switching · hop-by-hop routing
Cut a cable and watch the next packets reroute around the damage.
Predict firstBefore you cut a cable: will the message stop, or just find another route?
sender receivera message cut into pieces — each finds its own way · click a line to cut it
PLATE 57 · A MESSAGE IN PIECES
The network 0 cut
Click any line in the map to cut that cable, then watch the next batch reroute around it.
Packets
0/ 6 in
Cut cables
0ok
Your message doesn't travel as one long letter. It's chopped into little numbered packets, and each packet is set loose to find its own way across a web of routers — like mailing a book one page at a time, each page free to take a different road. If a road is blocked, the very next packet just steers around it. At the other end the receiver lines the pages back up in order. No single road, no single boss.
Try with the plate
  • Cut a cable and watch the packets detour around the gap.
  • Drop one packet and watch the far end ask for just that piece.

The internet sends a message by shredding it into small numbered packets, each tagged with its source, destination and sequence number. The packets scatter across a mesh of routers by different routes, each forwarded hop by hop, and are reassembled in order at the far end.

The short answer

When you send a message, the internet chops it into little numbered pieces called packets, like tearing a letter into postcards. Each postcard finds its own way across a web of routers to the destination, possibly by totally different routes, and they're put back in order at the other end. Cut one cable and the packets just go around it — which is exactly what the internet was built to do.

The common mix-up

Most people picture a message travelling as one stream down one wire. In fact it is shredded into numbered packets that each find their own route across a mesh of routers and reassemble in order at the far end.

What's actually happening

When you picture sending a message across the internet, you probably imagine it travelling as a single stream down a single connection. That's not how it works, and the real design is far cleverer. Your message (an email, a photo, a video frame) is first chopped into small chunks called packets. Each packet is wrapped in a header that says where it came from, where it's going, and which numbered piece of the whole it is, like postcards labelled "3 of 12".

Those packets are then released into a mesh of routers, and here is the key idea: each packet finds its own way. There is no reserved wire, no fixed path booked in advance. Every router that receives a packet simply looks at its destination and forwards it one hop closer, choosing whatever route looks best at that instant. Two packets from the same message might take completely different paths across the world and arrive out of order — which is fine, because their sequence numbers let the receiving computer reassemble them correctly, and ask for any that went missing. This is "packet switching", and the simulator shows it: watch six packets fan out across the router grid and converge on the destination.

This design wasn't an accident — it was the whole point. The early internet (ARPANET) was built to keep working even if parts of it were destroyed, so it deliberately avoided any single fixed route that could be cut. Snip a cable in the simulator and the very next packets simply detour around the gap, because every router is constantly free to pick a new path. That resilience is why the internet shrugs off outages, why a video call survives one network hiccup by resending a few lost packets, and why no central switchboard can fail and take everything down. The message was never in one place to begin with.

Remember this

Packet switching was built so no single cut can sever the whole — the message was never in one place to begin with, which is why the internet shrugs off outages.

Try it at home Be a router
  1. 1Write a sentence, then cut it into single words on separate scraps, numbering each (1, 2, 3…).
  2. 2Shuffle them and hand them to a friend in random order — that's packets arriving by different routes.
  3. 3They use the numbers to reassemble your sentence perfectly. Now hide one scrap: they notice number 4 is missing and can ask you to resend just that one, not the whole message.

Common questions

Why split a message into packets at all?

There is no reserved wire. Each router forwards each packet toward its destination independently, choosing the best route at that instant — which makes the network efficient and resilient, with no single fixed path to fail.

Why was the internet designed this way?

The early internet (ARPANET) was built to keep working even if parts were destroyed, so it deliberately avoided any single route that could be cut. Snip a cable and the next packets simply detour around the gap.

What if packets arrive out of order or go missing?

Sequence numbers let the receiving computer reorder them, and it can ask for any that went missing to be resent — which is why a video call survives a brief network hiccup.

Built & checked by Nilesh Singh · how this is made · last updated June 2026