Guide
Art-Net Made Simple: IP Addresses, Subnets, Universes & Troubleshooting
Learn how Art-Net really works: IP addressing, subnets, universes, and the most common mistakes that break Art-Net lighting networks.
What Art-Net Is (and What It Is Not)
Art-Net is a UDP-based lighting protocol that transports DMX universes over standard Ethernet networks.
It does not replace DMX — it replaces long DMX cable runs by moving data over IP.
Art-Net is:
Fast
Simple
Very permissive
That permissiveness is both its strength and its biggest weakness.
For a broader comparison, see Art-Net vs sACN vs ALPINE
The Mental Model You Need
Think in layers:
Layer | Role |
|---|---|
DMX | Channel data model |
Art-Net | Transport |
Ethernet | Physical/network layer |
IP | Addressing |
If any layer is misconfigured, nothing works.
Art-Net IP Addressing (The #1 Failure Point)
Default Art-Net IP range
2.0.0.0 – 2.255.255.255Subnet mask: 255.0.0.0
Most Art-Net nodes expect:
Static IPs
Same subnet
No routing
Common working examples
Controller: 2.0.0.10Node: 2.0.0.20
Common failure patterns
Controller on
192.168.x.x, node on
2.x.x.xDHCP assigning random IPs
Mixed Wi-Fi and Ethernet subnets
If you don’t understand IP basics, stop here and read: DMX Universe Explained
Universes in Art-Net (Not the Same Everywhere)
Art-Net universe numbering is historically messy.
Depending on the device:
Universe may start at 0 or 1
Net / Subnet / Universe may be split
Some UIs flatten everything into a single number
Safe rule
Match exactly what the receiver expects — never assume.
If you’re unsure how many universes you actually need, see: How many DMX Universes do you actually need
Broadcast vs Unicast (Why “It Works Until It Doesn’t”)
Broadcast
Packets sent to all devices
Simple
Scales poorly
Common in small rigs
Unicast
Packets sent directly to nodes
More efficient
Requires correct IP mapping
Art-Net defaults to broadcast, which is why:
It works instantly
Then breaks when networks grow
For timing side effects, see: DMX Latency and Jitter - Why your lighting feels "off"
Switches, Wi-Fi, and Why Art-Net Gets Fragile
Art-Net assumes:
Flat networks
No filtering
No managed switch features
Problems appear when:
Wi-Fi drops UDP packets
Switches prioritize other traffic
IGMP or storm control interferes
If reliability matters, Art-Net should be:
Wired
Isolated
Limited in scope
Art-Net Troubleshooting Checklist
Check in this order:
Same IP subnet on all devices
Static IPs (disable DHCP)
Universe numbers match exactly
Broadcast vs unicast configured intentionally
No Wi-Fi unless unavoidable
Test with one universe first
If Art-Net still feels fragile, you’re not wrong — see the sACN guide next.
When Art-Net Is the Right Choice
Art-Net is ideal for:
Small to medium rigs
Temporary setups
DJ and mobile rigs
Simple Ethernet layouts
It becomes risky when:
Networks grow
Switches become “smart”
Timing consistency matters
Summary
Art-Net works best when:
Networks are simple
IPs are controlled
Universes are few
Expectations are realistic
It’s fast and flexible — but not defensive.