Layer 6 — Presentation

What This Layer Does

Data that arrives correctly can still be useless. A file of raw bytes means nothing unless the receiving program knows what those bytes are meant to represent — letters, a photograph, a number, a sound.

The Presentation layer is about form rather than delivery. Its job is to put data into a shape the receiving application can understand, and to reverse that shaping at the other end. Three kinds of transformation live here, and beginners often confuse them, so it is worth separating them cleanly.

Encoding is agreeing what the bytes mean. Text is the clearest case. The letter "A" has to be stored as a number, and both sides must use the same table of numbers and letters or the message arrives as gibberish. UTF-8 is the encoding used for most text on the modern internet, and it can represent every character in every widely used writing system. Images, audio, and video are the same idea with more complicated rules: JPEG, PNG, and MP4 are all agreements about what a particular arrangement of bytes represents.

Compression is making data smaller. A compressed file contains the same information in fewer bytes, either by removing repetition without any loss, or by discarding detail the recipient is unlikely to notice, which is how photos and streaming video stay small enough to send.

Encryption is making data unreadable to anyone who does not hold the key. The sender scrambles the data before it travels; the receiver unscrambles it, which is called decryption. Anyone who intercepts it in between sees noise. This is what the padlock in your browser's address bar indicates.

Encoding, compression, and encryption are three different operations with three different purposes: meaning, size, and privacy. Data often gets all three.

A note on where encryption really sits. Web traffic is encrypted using TLS, which does not map onto exactly one OSI layer — different sources place it at Layer 6, at Layer 5, or spanning both alongside Layer 4. Encryption is discussed here because it is a presentation-style transformation, not because the industry has settled the question.

Common Examples

• UTF-8 text encoding
• Image formats such as JPEG and PNG
• Video and audio formats such as MP4
• Compression applied to web pages before they are sent
• TLS, the encryption behind HTTPS

Simple Real-World Example

You open a shopping site over HTTPS. The server compresses the page's text to reduce its size, then encrypts it before sending. The page travels across the internet as unreadable data.

Your browser decrypts it, decompresses it, and interprets the text using UTF-8 and the images using their own formats. Only then does anything appear on your screen. Every one of those steps is a Presentation-layer concern: not getting the data, but making it usable.

What Can Go Wrong?

• The two sides disagree on the encoding. Text appears as strange symbols, the classic sign of a mismatch.
• The receiver cannot handle the format. An unsupported image or video format shows as a broken placeholder even though the file arrived perfectly.
• Encryption fails to establish. The browser refuses to load the page and warns you, which is the system working as intended rather than breaking.
• Compressed data is corrupted. A small amount of damage can make a whole compressed file unreadable.

Remember This

Layer 6 formats, translates, compresses, or encrypts data.