Dante Network Requirements: A Practical Planning Guide
By VJ Ries · Published 2026-07-12 · Updated 2026-08-01 · 10 min read
A Dante network needs every switch in the path configured consistently (a managed switch makes that far easier); quality-of-service to prioritize audio; one clock leader that nobody fights; and ideally its own VLAN so other traffic cannot crowd it. This is a planning guide for the network around Dante. Audinate owns the exact switch settings, the clocking behavior and the channel limits, so plan the shape here and confirm every specific figure against current Dante documentation.
What Dante actually needs from a network
Dante rides on standard Ethernet. That is exactly why it trips people up: it looks like ordinary networking, so people treat it like ordinary networking. It is not tolerant of a network that drops or delays its packets. The good news? The requirements are a short, well-understood list, and none of them are exotic.
- A managed switch is strongly preferred: it lets you disable Energy Efficient Ethernet and control IGMP snooping. A small dedicated Dante-only network can run on an unmanaged gigabit switch, provided that switch does not force EEE on.
- Consistent configuration across every switch in the path, so a well-set switch does not feed into a misconfigured one.
- QoS so audio and clock traffic get priority when the link is busy.
- One clock leader, with the rest of the system following it.
- Headroom: enough switch and uplink capacity for your channel count, with room to spare.
The switch: managed, consistent, and QoS-enabled
One inconsistent or unmanaged switch in the path is the single most common Dante problem. So plan for managed switches. Ones you control end to end. Two settings dominate the planning conversation. Both should be confirmed against Audinate's guidance for your gear:
- QoS: prioritize the traffic classes Dante uses so a busy uplink never delays clock or audio. The specific markings to use are published by Audinate; apply their recommended values rather than inventing your own.
- Energy Efficient Ethernet (EEE / green Ethernet): commonly advised to be turned off for Dante because its power-saving behavior can add latency. Confirm the current recommendation for your switch.
Unicast vs. multicast (and why it affects capacity)
Dante can distribute audio as unicast (one stream per receiver) or multicast (one stream many receivers subscribe to). The trade-off is a capacity question. Sending the same audio to many destinations can be more efficient as multicast; multicast, though, needs the switch to contain it (see IGMP snooping) or it floods the network. Which flows are unicast vs. multicast affects how much bandwidth you consume and how many channels a link can carry. So it belongs in your plan, with the exact behavior and limits checked against Dante documentation.
In practice, keep multicast contained on its segment. Size links for your real channel counts rather than assuming the network is infinite. Multicast that is not contained is one of the classic ways a Dante network gets swamped. The same IGMP snooping hygiene that keeps NDI tidy applies here.
Give Dante its own lane
Dante works best when other traffic cannot crowd it. On a small dedicated audio network that happens for free. On a converged network, the equivalent is a dedicated Dante VLAN: control, video and guest traffic live elsewhere. Standard AV segmentation, in other words, covered in VLAN planning for AV systems. A media VLAN for Dante, separate from control and management.
Segmentation also makes the system legible. When Dante has its own VLAN and its own address range, an engineer can look at the IP schedule and know instantly what is audio and what is not.
| Plan item | Why it matters | Confirm in |
|---|---|---|
| Managed switch + saved config | Inconsistent switches are the #1 failure | Audinate switch guidance |
| QoS markings | Keeps clock and audio prioritized on busy links | Audinate QoS documentation |
| EEE off (commonly) | Power-saving can add latency | Audinate / switch datasheet |
| One clock leader | Competing external clock sources cause dropouts | Dante Controller docs |
| Dante VLAN + IP range | Isolates audio, makes the network legible | Your VLAN + IP schedule |
| Uplink headroom for channel count | Prevents swamping at peak | Dante channel-count docs |
Clocking: one leader, and do not fight it
Dante devices share a clock so audio stays sample-accurate across the system. The planning rule is simple even though the mechanism is not: there is one clock leader and everything else follows, and since Dante elects that leader itself and always lands on exactly one, problems appear elsewhere: devices synced to different external clock sources, or a poor-quality source chosen as leader. Decide the intended leader in advance. Record it. Then let Dante Controller manage the rest. The exact clocking behavior, preferred-leader settings, and how the system elects a leader are Audinate's to define, so confirm them there.
Planning a Dante network, step by step
- List every Dante device and its channel counts, straight off the signal-flow diagram.
- Decide dedicated audio network vs. Dante VLAN on a converged network, and segment accordingly.
- Pick one managed switch model and one saved config; plan QoS from Audinate's recommended markings; plan to disable EEE unless current guidance says otherwise.
- Size uplinks for your real channel count with headroom; contain multicast with IGMP snooping.
- Choose the intended clock leader and record it.
- Assign addresses on the Dante VLAN and write the IP schedule.
- Document the whole thing on the diagram so the next engineer inherits a plan, not a mystery.
In WireFlow the Dante devices live on the same diagram as the rest of the system, carrying their VLAN, IP assignments and switch ports, so the audio network is documented alongside the signal flow instead of in a separate spreadsheet nobody updates.
Frequently asked questions
- Do I need a special switch for Dante?
- A managed switch you can configure consistently is strongly preferred, for QoS support and the ability to turn EEE off. A small dedicated Dante-only network can run on an unmanaged gigabit switch, as long as that switch does not force EEE on. Expensive or exotic is not the requirement. Consistency is: every switch in the Dante path must be set up the same way. Confirm the specific feature requirements against Audinate's switch guidance for your channel counts.
- Can Dante share a network with video and control?
- Yes, on a properly segmented network. Put Dante on its own VLAN so control, video and guest traffic cannot crowd it. Apply QoS and contain multicast. On smaller systems a fully dedicated audio network is simpler. Either way, plan the segmentation deliberately.
- Why does everyone say to turn off EEE for Dante?
- Energy Efficient Ethernet lets a switch port drop into a low-power state, and that behavior can introduce latency that Dante does not tolerate well. It is commonly recommended to disable it on Dante ports. Confirm the current recommendation for your specific switch against Audinate's documentation.
- What causes random Dante dropouts?
- Usual suspects: an inconsistent or unmanaged switch in the path, missing QoS, multicast that is not contained, EEE left on, or devices synced to different external clock sources. Work down that list. Verify each setting against Dante documentation rather than guessing.
Document your AV network in WireFlow
VLANs, IPs, PoE, and switch ports live on the same diagram as your signal flow, one source of truth for the whole system.