How Encapsulation Wraps Your Data

As data moves down a protocol stack to be sent, each layer adds its own control information. This process is called encapsulation. Like sealing a letter in one envelope, then a bigger one, then a mailbag, each layer wraps the data with a header meant for its peer on the other side. Encapsulation is how the layered model actually prepares data for the network.

The information each layer adds is mostly a header, a small block of control data placed in front of the payload. The header tells the matching layer on the receiving side how to handle the data: where it is going, which protocol it uses, and more. Some layers also add a trailer after the data. Headers are the instructions that make delivery work.

Encapsulation begins at the application layer, where your actual data, like a web request, is created. This data is handed down to the transport layer to begin its journey. At the start, the data is just the message itself with no networking headers. Each lower layer will add what it needs as the data descends the stack toward the wire.

At the transport layer, a header is added that includes port numbers and, for TCP, sequence and acknowledgment information. The data plus this header is now called a segment (TCP) or datagram (UDP). This header ensures the data will reach the right application and, with TCP, arrive reliably and in order on the far side.

Next, the internet layer adds an IP header containing the source and destination IP addresses. The result is called a packet. This header lets routers carry the data across networks to the correct device. The transport segment is now wrapped inside a packet, hidden as payload to the IP layer, which only reads its own header.

Finally, the link layer adds a header with MAC addresses and a trailer with an error check, producing a frame. The frame is what actually goes onto the cable or air as bits. With each layer having added its wrapper, the original data is now fully encapsulated and ready for transmission across the local medium.

Each stage has its own name for the wrapped data, collectively called protocol data units. The progression is data (application), segment (transport), packet (internet), and frame (link). Knowing these names tells you instantly which layer you are discussing. When someone says packet, they mean the internet layer; frame means the link layer.

At every layer, the data handed down from above becomes the payload, and the new header is added in front of it. A layer treats everything from above as opaque payload and cares only about its own header. This nesting, where each layer ignores the inner details, is what keeps the layers independent and the design clean.

On the receiving device the process reverses, called decapsulation. As data moves up the stack, each layer reads and removes its own header, then hands the payload to the layer above. The link layer strips the frame, the internet layer the IP header, and so on, until the original data reaches the application. Wrapping down, unwrapping up.

Encapsulation is what makes layered networking work in practice. It lets each layer do its job using only its own header, while carrying the layers above untouched. This is why you can change one layer without breaking others and why headers are where networking problems often hide. Reading headers at the right layer is a core troubleshooting skill.

Encapsulation adds a header (and sometimes a trailer) at each layer as data descends: data becomes a segment, then a packet, then a frame ready for the wire. On arrival, decapsulation strips each header in reverse on the way up. Each layer reads only its own header and treats the rest as payload, which is exactly what makes layered networking practical.

What is the correct order of data units as data is encapsulated from the top down?

Encapsulation wraps data with a header (and sometimes a trailer) at each layer as it descends the stack. The units progress from data (application) to segment (transport, adds ports), to packet (internet, adds IP addresses), to frame (link, adds MAC addresses and error check). On arrival, decapsulation strips each header on the way up. Each layer reads only its own header.