Network Basics: The OSI Model Explained in Plain Language

Ever tried to figure out why a website will not load? Or why two devices on the same network refuse to talk? You were troubleshooting across the layers of the OSI model, whether you knew it or not. Is the cable plugged in? Does the device have an IP address? Is the right port open? Each question targets a different layer.

The OSI model is not software, a protocol, or something you install. It is a mental map. It gives network engineers, security analysts, developers, and help-desk technicians one shared vocabulary. Every IT certification tests it. Every vendor’s documentation references it. Once you understand it, troubleshooting becomes systematic instead of random.

This guide walks through all seven layers in plain language. Each layer gets a real-world analogy, its key protocols and devices, and links to related tools on this site.

What Is the OSI Model?

The OSI model is a seven-layer framework, published by ISO as ISO/IEC 7498-1, that standardizes how network communication is described. It is a reference model, not a protocol. Engineers use it to classify protocols, hardware, and troubleshooting steps by layer.

OSI stands for Open Systems Interconnection. The International Organization for Standardization (ISO) published the model in 1984. Its goal was simple. Give the entire networking industry one common reference so products from different vendors could interoperate.

Before the OSI model, every vendor had its own proprietary networking stack. IBM had SNA. Novell had IPX/SPX. Apple had AppleTalk. Engineers trained on one system could not easily reason about another. The OSI model solved this by defining seven abstract layers. Each layer owns a specific slice of the communication process. The model standardized how we talk about networking, even though no real protocol suite maps to it perfectly.

Here is the critical distinction. The OSI model is a reference model, not a protocol. You will never install “OSI” on a server or configure an “OSI interface” on a router. Instead, you use the model to classify the protocols and hardware you already work with. HTTP operates at Layer 7. TCP operates at Layer 4. Ethernet operates at Layer 2.

The 7 Layers of the OSI Model

The seven layers, from bottom to top, are Physical, Data Link, Network, Transport, Session, Presentation, and Application. The mnemonic Please Do Not Throw Sausage Pizza Away keeps them in order. Each layer handles one specific slice of the communication process.

The layers are numbered from the bottom up. Layer 1 sits closest to the physical wire or radio wave. Layer 7 sits closest to the user. Let’s walk through each one, starting from the top.

How Data Flows Through the OSI Model Layers

Data moves down the seven layers on the sending device and up the layers on the receiver. Each layer adds a header on the way down (encapsulation) and strips it on the way up (decapsulation). The wrapped unit at each layer is called its Protocol Data Unit.

Understanding individual layers matters. Seeing how they work together is where the model earns its keep. When you load a web page, your request passes through all seven layers in a process called encapsulation.

Encapsulation (Sending Side)

On the sending device, data starts at Layer 7 and moves downward. Each layer wraps the data in a new header, and sometimes a trailer, carrying that layer’s control information. The wrapped unit at each stage has a formal name. That name is its Protocol Data Unit (PDU).

Decapsulation (Receiving Side)

At the receiving device, the process reverses. The Physical layer receives raw bits and passes them up. Each layer strips its header, reads the control information, and hands the payload to the layer above. By Layer 7, the data is back in its original form and ready for the application.

This layered design is what makes modern networking modular. You can swap the Physical layer, copper to fiber or wired to wireless, without touching Layer 4. You can move from IPv4 to IPv6 at Layer 3 without rewriting your web application at Layer 7. Each layer does its job and trusts the others to do theirs.

OSI Model vs TCP/IP Model

The OSI model has seven layers and serves as the teaching and troubleshooting reference. The TCP/IP model has four layers and reflects how the internet actually works. TCP/IP merges OSI Layers 5 through 7 into one Application layer and Layers 1 and 2 into Network Access.

If the OSI model is the theory, the TCP/IP model is the practice. The internet runs on TCP/IP, not OSI. The U.S. Department of Defense developed the TCP/IP suite in the 1970s, a full decade before the OSI model was published. Its model consolidates the seven OSI layers into four.

Which one should you learn? Both. The TCP/IP model reflects how protocols are actually implemented. The OSI model offers finer granularity, which pays off in troubleshooting and on certification exams. When someone says “that is a Layer 2 issue,” they are speaking OSI.

The practical difference comes down to lumping versus splitting. TCP/IP merges Layers 5, 6, and 7 into one Application layer. It also merges Layers 1 and 2 into Network Access. TCP/IP does not care whether your problem is session management (Layer 5) or encryption (Layer 6). The OSI model does. That extra specificity helps when you are narrowing a root cause.

Why the OSI Model Still Matters

The OSI model survives because it is a shared vocabulary. It structures troubleshooting, anchors certification exams like CompTIA Network+ (N10-009) and Cisco CCNA (200-301), and appears throughout vendor documentation. Layer numbers give technical teams instant shorthand for locating problems.

Fair question: if the internet runs on TCP/IP, why learn a 40-year-old reference model? Because the OSI model became something more useful than a protocol specification. It became a common language.

• Troubleshooting. Thinking in layers lets you isolate problems systematically. Start at Layer 1 and work up, or start at Layer 7 and work down. Rule out each layer until you find the culprit. Our network troubleshooting guide uses this exact approach.
• Certification exams. CompTIA Network+ (N10-009), CompTIA Security+, and Cisco CCNA (200-301) all test the OSI model. It is foundational material, not optional.
• Vendor documentation. Firewall vendors, switch manufacturers, and cloud providers all reference OSI layers. A firewall admin guide might say “this feature operates at Layers 3 through 7.” Without the model, that sentence is meaningless.
• Cross-discipline communication. A developer, a network engineer, and a security analyst can all use layer numbers as shorthand. “The problem is at Layer 4” instantly narrows the conversation to ports and TCP handshakes.

Layer 8: The Human Layer

Spend time around network engineers and you will hear someone blame “a Layer 8 issue.” The OSI model officially stops at seven. Layer 8 is an in-joke for the user sitting at the keyboard.

It is the polite way to say the problem was human error. A mistyped password or an unplugged cable the user swears they never touched. Related shorthand includes PEBKAC, “problem exists between keyboard and chair.”

The joke extends upward too. Some teams call Layer 9 the organization or politics, and Layer 10 government or legal compliance. Security writer Bruce Schneier popularized that framing. There is a serious point underneath. The user layer is the favorite target of social engineering, phishing, and pretexting attacks. No firewall rule patches a person who clicks the wrong link.

Troubleshooting with the OSI Model

Work from Layer 1 upward. Check the cable and link lights first. Then verify MAC and ARP, then IP addressing and the gateway. Finish with port connectivity, then DNS and the application. Each layer depends on the layers below it, so the order matters.

Let’s put the model to work. A user reports: “I cannot load a website.” Here is the systematic bottom-up walkthrough.

The bottom-up approach is efficient because each layer depends on the ones below it. There is no point checking DNS if the device has no IP address. There is no point checking the IP if the cable is unplugged. For the complete walkthrough, see how to troubleshoot network connectivity.

Quick Reference: OSI Layers and Common Troubleshooting Commands

Related Tools & Resources

NetworkCheckr pairs this guide with free tools at nearly every layer. Use the Subnet Calculator and My IP Address tool for Layer 3. Reach for the Port Number Reference at Layer 4 and the DNS Lookup at Layer 7. All run in your browser.

• Subnet Calculator — work out masks, ranges, and host counts at Layer 3.
• My IP Address — see your public IP and connection details instantly.
• MAC Address Lookup — identify the vendor behind any Layer 2 address.
• Port Number Reference — the Layer 4 port catalog, searchable.
• DNS Lookup — query any record type at Layer 7.
• DNS Records Explained — the companion guide to every common record type.
• How to Troubleshoot Network Connectivity — the layer-by-layer method in full.
• All NetworkCheckr Tools — the complete collection of free utilities.

Frequently Asked Questions

Six questions cover the essentials. What the OSI model is used for. How many layers it has. How it differs from the TCP/IP model. Which layers routers and switches operate at. And whether you actually need to memorize it for your career.