did you know the internet sends your photo in little pieces?

a photo usually does not cross the internet as one uninterrupted object. its bytes travel inside packets, each with addressing information that helps network equipment forward it towards the destination.

small packets let many conversations share a link. a huge download does not need exclusive use of the whole network until its final byte arrives. routers can take turns forwarding different users' data.

packets move through a sequence of network links and routers. they can be delayed, lost, duplicated, or arrive out of order. their route can change, although packets in one flow often follow the same path.

protocols above IP handle the behaviour an application needs. TCP, for example, uses sequence numbers and acknowledgements to deliver an ordered byte stream, retransmitting missing data when necessary.

with an illustrative payload of 1,400 bytes per packet, a 2,800,000-byte photo needs 2,000 payload chunks. headers and protocol details add traffic beyond the photo's own size.

chunks = round up(file bytes / payload bytes); 2,800,000 / 1,400 = 2,000

• for live media, a packet that arrives much too late may be less useful than moving on. applications balance completeness against delay.
• packet sizes vary with the network and protocol. 1,400 bytes is a worked example, not a universal internet parcel size.