A Collision Domain Is About Shared Wire
In the original Ethernet design, every device hung off the same shared cable. Only one device could transmit at a time; if two transmitted simultaneously, their signals overlapped and corrupted each other — a collision. The protocol that managed this, CSMA/CD, had devices listen before sending and back off for a random interval after a collision before retrying.
A collision domain is simply the set of devices whose transmissions can collide with one another — everyone sharing that one electrical segment. The more devices in a single collision domain, the more they contend for the wire, and the more time is wasted on collisions and back-offs. Throughput collapses as the domain grows, which is exactly the scaling problem early Ethernet ran into.
A hub made this worse. A hub is electrically dumb: a signal arriving on one port is repeated out every other port, so a hub joins all its ports into a single large collision domain. Plugging more devices into a hub just crowds the same shared medium.
A Broadcast Domain Is About Who Hears "Everyone"
A broadcast frame is addressed to every device on the local network at once (the destination MAC address is all ones, FF:FF:FF:FF:FF:FF). Protocols rely on this: ARP broadcasts "who has this IP address?", and DHCP clients broadcast to find a server.
A broadcast domain is the set of devices that will all receive such a frame. Broadcasts are useful but not free — every device in the domain must process every broadcast, even if it is irrelevant to them. As the domain grows, "broadcast traffic" becomes background noise that consumes bandwidth and CPU on every host. A network with thousands of devices in one broadcast domain can be crippled by broadcast storms.
Which Device Breaks Which Domain
The whole topic comes down to one table. Each device operates at a different layer and so affects the two domain types differently:
| Device | Collision domains | Broadcast domains |
|---|---|---|
| Hub (Layer 1) | One — all ports share it | One — repeats everything |
| Switch (Layer 2) | One per port — each is isolated | One — floods broadcasts to all ports |
| Router (Layer 3) | One per interface | One per interface — does not forward broadcasts |
The two pivotal facts are:
- A switch breaks up collision domains. Each switch port is its own collision domain, and with full-duplex links there is a dedicated send and receive path, so collisions simply cannot happen. This is why a switch dramatically outperforms a hub.
- A router breaks up broadcast domains. A router does not forward broadcast frames between interfaces, so each side is a separate broadcast domain. This is what stops broadcast noise from spreading across an entire organisation.
Put simply: switches solve the collision problem; routers (and VLANs) solve the broadcast problem.
Why Collisions Mostly Vanished — and Broadcasts Didn't
On a modern switched network, every device has its own port and runs in full duplex. Each collision domain contains exactly one device and its switch port, so collisions are a non-issue — the term survives mostly as a teaching concept and a reason hubs disappeared. CSMA/CD is effectively retired on wired LANs.
Broadcast domains, by contrast, are alive and central to network design. A switch, for all its intelligence, still floods broadcasts out every port by default, so a flat switched network of any size is one big broadcast domain. That is why large networks are deliberately segmented.
VLANs: Splitting Broadcast Domains Without More Routers
Buying a router interface for every group of devices does not scale. The elegant solution is the VLAN (Virtual LAN), which lets a single switch carve its ports into multiple independent broadcast domains. Ports assigned to VLAN 10 form one broadcast domain; ports in VLAN 20 form another; a broadcast in one never reaches the other, even though they share the same physical switch.
This is how an office puts staff, guest Wi-Fi, IP phones, and security cameras on separate logical networks using shared hardware — each VLAN is its own broadcast domain, with a router (or a Layer 3 switch) handling traffic that must cross between them. The mechanics of tagging and carrying VLANs between switches are covered in VLANs and trunking, and the way these segments map onto IP ranges in network topologies.
Frequently Asked Questions
What is the difference between a collision domain and a broadcast domain?
A collision domain is the set of devices whose signals can collide on shared media. A broadcast domain is the set of devices that all receive a broadcast frame. Switches split collision domains (one per port) but forward broadcasts; routers split broadcast domains.
Does a switch separate collision domains or broadcast domains?
Collision domains. Every switch port is its own collision domain. A switch does not separate broadcast domains by default — it floods broadcasts to all ports, making the whole switch one broadcast domain unless VLANs divide it.
How do you break up a broadcast domain?
With a router or with VLANs. A router does not forward broadcast frames, so each interface is a separate broadcast domain; VLANs achieve the same split logically inside one switch.
Are collisions still a problem on modern networks?
Rarely. Full-duplex switched Ethernet eliminates collisions because each device has a dedicated link with separate send and receive paths. Collisions only occur on shared half-duplex media like old hubs. Broadcast domains still matter on every network.