What Is Unicast? Definition, Examples, and How It Works

Unicast: The Backbone of Almost Every Internet Connection

Unicast is a one-to-one network transmission method where data travels from a single source to a single destination. When you load a web page, download a file, or make a video call, you are using unicast. Every packet you send carries a specific destination IP address, and only the device holding that address receives and processes it — every other device on the network ignores it.

The term comes from the Latin prefix uni- (meaning one) and cast (meaning to transmit or send). Unicast literally means send to one — contrasting with multicast (send to a group) and broadcast (send to all devices on a subnet).

Unicast dominates internet traffic because the overwhelming majority of communication is personalized: your browser requests your page, your email goes to your inbox, your file transfer goes to your storage. The internet was designed around unicast addressing, and every routing protocol from BGP to OSPF is built to forward unicast packets efficiently across the global network.

How Unicast Transmission Works Step by Step

Every unicast transmission follows the same path through the network stack:

1. Address assignment: Your device has a unicast IP address — assigned by DHCP, static configuration, or auto-configuration. This address is unique on the network segment and identifies only your device.
2. Packet construction: When your application sends data, the OS wraps it in IP packets with your IP as the source address and the destination IP (the server) as the destination address.
3. Local forwarding decision: Your device checks whether the destination IP is on the same local subnet. If yes, it sends the packet directly using ARP to resolve the destination MAC address. If no, it sends the packet to the default gateway.
4. Router forwarding: Routers along the path examine the destination IP in each packet and forward it toward the destination using their routing tables. This happens hop by hop — each router only needs to know the next hop, not the full path.
5. Delivery: The final router on the path delivers the packet to the destination device. That device processes it, and any response travels back to your IP address using the same unicast mechanism in reverse.

Each TCP connection or UDP stream is a unicast flow identified by the 5-tuple: source IP, source port, destination IP, destination port, and transport protocol. These five values together uniquely identify a flow and allow firewalls, NAT devices, and load balancers to track it.

IPv4 Unicast Address Ranges

In IPv4, most of the address space is unicast. The key ranges:

• Public unicast: All routable addresses not reserved for special use — used by servers and devices on the public internet. Assigned by IANA and regional registries.
• Private unicast: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 — used inside home and corporate networks. These addresses are not routed on the public internet.
• Loopback: 127.0.0.0/8 — unicast addresses for communicating with the local device itself. 127.0.0.1 is the standard loopback address, known as localhost.
• Link-local: 169.254.0.0/16 — automatically assigned when no DHCP server is available. Not routed beyond the local link.

Multicast occupies 224.0.0.0/4 (224.0.0.0 through 239.255.255.255). The limited broadcast address is 255.255.255.255. Everything else in the IPv4 space is unicast.

IPv6 Unicast Addressing

IPv6 expanded unicast addressing significantly while eliminating broadcast entirely:

• Global unicast (2000::/3): Equivalent to public IPv4 addresses — routable on the internet. All currently assigned global unicast addresses start with 2001:, 2600:, 2a00:, and similar prefixes.
• Link-local unicast (fe80::/10): Automatically configured on every IPv6-capable interface. Used for neighbor discovery and router discovery on the local link. Not routable.
• Unique local (fc00::/7): Equivalent to IPv4 private addresses — intended for use within private networks and not routed on the internet.
• Loopback (::1): The IPv6 equivalent of 127.0.0.1.

In IPv6, there is no broadcast. Functions that used broadcast in IPv4 — like ARP for address resolution — are replaced by ICMPv6 Neighbor Discovery, which uses multicast. This eliminates the broadcast overhead that limited IPv4 scalability in large subnets.

Unicast vs Multicast vs Broadcast vs Anycast

Real-World Unicast Examples

Virtually every named internet service is unicast. Specific examples:

• Web browsing: Your browser opens a TCP connection to the web server's IP on port 443. The server sends the page content back to your IP. Every request and response is a unicast exchange.
• On-demand video streaming: Netflix, YouTube, Spotify — each viewer or listener gets their own individual stream. If a million people watch the same video simultaneously, that is a million separate unicast streams from Netflix's CDN to each viewer's IP.
• Email (SMTP, IMAP, POP3): Every email delivery is a unicast TCP connection between mail servers, and every email retrieval by a client is a unicast session.
• File transfers (FTP, SCP, SFTP, rsync): All unicast TCP sessions from source to destination.
• VPN tunnels: WireGuard, OpenVPN, and IPSec tunnels are unicast sessions between the client and VPN server, carrying encrypted traffic.
• DNS queries: Each DNS query is a unicast UDP packet to a specific DNS server IP. The response is a unicast UDP packet back to the querying device.

When Unicast Is the Wrong Choice

Unicast's bandwidth consumption scales linearly with recipients. Send the same video stream to 1,000 viewers via unicast and you generate 1,000 streams from your server. The same content sent via multicast uses one stream regardless of audience size — the network replication happens at routers rather than at the source.

For live video distribution within an enterprise campus or IPTV delivery over an ISP's managed network, multicast dramatically reduces bandwidth requirements. A single multicast stream of a live event to thousands of recipients uses the same bandwidth as sending it to one recipient. Each router that has subscribers in its downstream network receives one copy of the stream and replicates it only to the interfaces where subscribers have joined the multicast group.

The practical limitation of multicast is that internet-wide multicast routing (via Multicast BGP) is not widely deployed. Most ISPs do not carry multicast routes. This is why live internet video — YouTube Live, Twitch, live sports streaming — is delivered as many individual unicast streams rather than one multicast stream, at enormous bandwidth cost.

Common Misconceptions

Misconception 1: All TCP is unicast but unicast is not all TCP

Every TCP connection is unicast — TCP requires a two-way exchange between exactly two endpoints, which is the definition of unicast. But unicast also includes UDP. DNS queries are unicast UDP. QUIC (the protocol under HTTP/3) is unicast UDP. Unicast is the addressing model; TCP and UDP are the transport protocols that operate on top of it.

Misconception 2: Private IP addresses are not real unicast

Private address ranges (10.x.x.x, 172.16.x.x, 192.168.x.x) are fully functional unicast addresses within the networks where they are used. They are not routed on the public internet, but within a home network or corporate LAN, they behave identically to public unicast addresses. Your router uses NAT to translate private addresses to your public IP for internet communication.

Misconception 3: Unicast means the data only travels one path

Unicast addresses one destination, but the packets can take different paths through the network. Equal-cost multi-path routing (ECMP) allows packets of the same flow to travel over multiple physical links simultaneously. BGP may route packets across different international paths depending on policy. The destination is singular; the network path is determined by routing decisions hop by hop and can vary.

Misconception 4: Anycast and unicast are the same

Anycast uses addresses formatted identically to unicast addresses, but the same address is announced from multiple physical locations. When you query 1.1.1.1 (Cloudflare's DNS), your packet is routed to the geographically nearest Cloudflare data center — not a specific single server. Unicast always goes to one specific physical device; anycast routes to the nearest of many. From the router's perspective, anycast looks like unicast routing — the distinction is in the address management, not the packet format.

Pro Tips for Working With Unicast in Practice

• Understand your 5-tuple for troubleshooting. When diagnosing a connectivity issue, identify the full 5-tuple: source IP, source port, destination IP, destination port, protocol. Every firewall rule, NAT entry, and load balancer session is keyed on this tuple. If a connection fails, verifying each element of the tuple systematically finds the problem faster than guessing.
• Use per-flow hashing in ECMP configurations. When configuring equal-cost multipath routing, ensure your hash is based on the full 5-tuple rather than just source IP. IP-only hashing can create significant imbalance when a few source IPs generate most traffic.
• Remember that IPv6 link-local addresses are mandatory. Every IPv6-capable interface has a link-local address (fe80::/10) automatically, regardless of whether global unicast is configured. This is used for Neighbor Discovery and router solicitation. Firewalls blocking all IPv6 traffic need to explicitly allow ICMPv6 for link-local communication to function correctly.
• Account for asymmetric routing in stateful firewalls. Stateful firewalls track unicast flows by their 5-tuple. In networks with asymmetric routing (where outbound and inbound packets follow different paths), a stateful firewall may see only one direction of the flow and drop it. Design routing to be symmetric when stateful firewalls are in the path.
• For multicast-like behavior on the internet, use a CDN. Since multicast is not universally available on the internet, content delivery networks replicate popular content to edge nodes globally. Each user gets a unicast connection to a nearby CDN node, which is functionally similar to multicast in terms of reducing origin bandwidth.

Look up your current unicast IP address and see what information is associated with it.