2026
The OSI Model: A Practical Guide to the Seven Layers
What the seven layers actually mean, how data moves through them and why the model still matters when something on your network stops working.
The first time someone mentions the OSI model, it usually comes with a mnemonic you are supposed to memorise. Seven layers. A neat little acronym. Move on. What nobody explains is why the model exists in the first place, which makes it very easy to learn the names of the layers without ever understanding what they are actually for.
The OSI model is a conceptual framework. It does not describe the exact way modern networks are built. What it does is give everyone a shared vocabulary for talking about where in the communication process something happens. When an engineer says a problem is at layer 3, or that a switch operates at layer 2, they are pointing at a specific slice of responsibility. That is the whole point.
The model was published by the International Organization for Standardization in 1984. Networking at the time was fragmented. Different vendors had different proprietary systems that could not talk to each other. The OSI model was an attempt to define a universal blueprint for how network communication should be structured. The internet ultimately settled on the simpler TCP/IP model in practice, but the OSI model stuck around as the standard reference for understanding what different parts of the stack are responsible for.
The seven layers
The model is typically shown from top to bottom, starting at the application layer where users interact with software, down to the physical layer where signals travel over cables. Data travels down the stack on the sending side. It travels back up on the receiving side.
Application
What you actually interact with
This is where your software lives. HTTP, DNS, FTP, SMTP — these protocols all live at layer 7. When your browser sends a request to load a webpage, it is speaking at the application layer. It does not care how the data gets there. That is someone else's problem.
e.g. Your browser making an HTTP GET request
Presentation
Format, encode, encrypt
This layer is responsible for translating data into a format the application can understand. Encryption happens here. So does character encoding. When a server sends you data over TLS, layer 6 is where the encryption and decryption take place before handing it off up or down the stack.
e.g. TLS encryption, JPEG compression, UTF-8 encoding
Session
Opening and closing conversations
Layer 5 manages the lifecycle of a communication session. It sets up the connection, keeps it alive while data is being exchanged and tears it down cleanly when the work is done. Think of it as the layer that says hello, manages the conversation and then says goodbye.
e.g. Authentication sessions, NetBIOS, RPC
Transport
Reliable delivery between two points
This is where TCP and UDP live. Layer 4 takes the data from the layers above and breaks it into segments. TCP adds sequencing and acknowledgements so that data arrives in order and nothing gets lost. UDP skips that overhead entirely when speed matters more than guarantees.
e.g. TCP port 443 for HTTPS, UDP port 53 for DNS queries
Network
Finding a route across different networks
Layer 3 is responsible for logical addressing and routing. IP addresses live here. A router is a layer 3 device. When a packet needs to travel from one network to another, it is the network layer that figures out the path it should take to get there.
e.g. IP addresses, routers, ICMP (ping)
Data Link
Sending frames between devices on the same network
Layer 2 deals with physical addressing on a local network. MAC addresses live here. A switch is a layer 2 device. It is responsible for taking the raw bits from layer 1 and organising them into frames that can be addressed to a specific device on the same network segment.
e.g. MAC addresses, Ethernet frames, network switches
Physical
The actual signal going through a wire
This is the lowest level. Layer 1 is voltage on a copper cable, light pulses in a fibre optic line, radio waves coming out of a wireless antenna. It does not know anything about addresses or protocols. Its only job is to move raw bits from one end to the other.
e.g. Ethernet cables, Wi-Fi radio signals, fibre optics
How data actually moves through the stack
Each layer wraps the data from the layer above it in its own header before passing it down. This process is called encapsulation. By the time data reaches the physical layer, it carries headers from every layer above it, each one containing the information that layer needs to do its job.
On the receiving end, each layer strips its own header off and passes the remainder up. The application at the top never sees any of those headers. It just gets the original data, as if none of that complexity existed.
DataSegmentPacketFrameBitsWhat actually happens when you visit a website
Walk through loading a webpage in your browser and the layers become much more concrete.
Your browser constructs an HTTP request.
That is layer 7. The application layer. The protocol you are using is HTTP or HTTPS.
If it is HTTPS, the data is encrypted before leaving.
Layer 6 handles that. TLS encrypts the payload so only the server can read it.
TCP opens a connection to port 443 on the server.
Layer 4. TCP handles the handshake, sequencing and retransmission if packets are dropped.
The packet gets stamped with your IP address and the server's IP address.
Layer 3. Routers along the path read these addresses to figure out where to send the packet next.
Your router wraps it in an Ethernet frame addressed to the next hop.
Layer 2. MAC addresses here. The frame changes at every hop because MAC addresses are local.
Your network card converts the whole thing into electrical or radio signals.
Layer 1. From here it travels over a cable or through the air.
Devices and the layers they operate at
Network devices are often described by the layer they work at because that tells you what information they can see. A device at layer 1 is blind to everything except raw signals. A device at layer 4 can see ports. A device at layer 7 can inspect the actual content of requests.
HubSwitchRouterFirewallLoad BalancerOSI versus TCP/IP
Real internet traffic does not follow the OSI model exactly. The TCP/IP model, which is what the internet actually runs on, collapses the seven layers into four. Sessions, presentation and application all merge into a single application layer. Physical and data link merge into a network access layer.
OSI Model
The reference model
7 Application
6 Presentation
5 Session
4 Transport
3 Network
2 Data Link
1 Physical
TCP/IP Model
What the internet actually uses
Application
Transport
Internet
Network Access
The OSI model is still the one you will see in documentation, job descriptions and conversations about troubleshooting. Knowing which layer something belongs to narrows down where a problem is and what tools are relevant to diagnosing it.
Why it is worth knowing
You do not need to memorise all seven layers before you can do anything useful in networking. What matters is the idea behind the model: that network communication is broken into distinct responsibilities, each layer concerned with one job. When something is not working, that separation of concerns tells you where to start looking.
A packet that never arrives could be a physical problem at layer 1, a routing issue at layer 3 or a firewall rule at layer 4. Each possibility has different tools and a different fix. The OSI model is the map you use to figure out which one you are dealing with.