Art-Net vs sACN: what's the difference?
Art-Net and sACN (ANSI E1.31) are the two main protocols for sending DMX lighting control over a network. Both carry 512-channel universes over UDP/IP. The core differences: sACN is an ESTA standard that uses multicast and a built-in per-source priority for merging, while Art-Net is a widely-supported vendor protocol that historically uses broadcast and leaves merging to the receiving device.
Art-Net vs sACN at a glance
| Art-Net | sACN (E1.31) | |
|---|---|---|
| Standard / owner | Artistic Licence (open, vendor-maintained) | ANSI E1.31, published by ESTA (industry standard) |
| Transport | UDP, historically broadcast; modern versions also unicast | UDP, multicast by default (one group per universe), also unicast |
| Default network | Typically a dedicated 2.x or 10.x lighting network | Runs on a normal production LAN with multicast |
| Addressing | Net / sub-net / universe (Art-Net 4: up to 32,768 universes) | Universe number 1-63,999 → a fixed multicast group |
| Priority & merging | No standardized priority; merging is done by the node/controller (usually HTP) | Native per-source priority 0-200 (default 100); higher wins, HTP among equals |
| Source identification | Node short/long name via ArtPoll discovery | Source name + CID (UUID) + sequence numbers in every packet |
| Network efficiency at scale | Broadcast can flood large flat networks | Multicast + IGMP snooping delivers only subscribed universes |
When to use each
Use sACN on larger or multi-console networks where you want efficient multicast and native priority merging (for example, a main and backup console where the backup sits at a lower priority). Use Art-Net when your nodes or fixtures support it best. It is ubiquitous across budget nodes and Artistic Licence hardware. In practice many rigs run both, and a router sits in the middle to translate and merge.
Bridging and merging Art-Net and sACN
Because both protocols just carry universes over IP, a router can ingest one and emit the other, remap universes, and merge several sources. DMXhub is a free macOS app that does exactly this: take in Art-Net and sACN, merge with Priority / HTP / LTP / switch, apply failover, and route or mirror the result back out as Art-Net and/or sACN, all on a visual canvas. Read the docs.
FAQ
Is Art-Net or sACN better?+
Neither is universally better. They solve the same job differently. sACN (E1.31) is an ANSI standard with built-in per-source priority and efficient multicast, which suits large installs and multi-console setups. Art-Net is extremely widely supported, especially by Artistic Licence gear and budget nodes. Most modern consoles and nodes speak both, so the choice often comes down to what your hardware supports and how you want to merge sources.
Can you convert Art-Net to sACN (or sACN to Art-Net)?+
Yes. A protocol router or bridge can take one protocol in and send the other out, universe by universe. DMXhub does this on a Mac: ingest Art-Net or sACN, remap the universes, and output either protocol, so you can bridge an Art-Net console to sACN nodes, or vice versa, for free.
Does sACN have priority and Art-Net doesn't?+
sACN carries a per-source priority value (0-200, default 100) in every packet, and receivers merge by priority then HTP. Art-Net has no standardized priority field, so merging two Art-Net sources is handled by the receiving node or a router, typically using HTP or LTP. A merger like DMXhub lets you set Priority, HTP, LTP, or single-source switching per route regardless of protocol.
Can I run a backup console with Art-Net or sACN?+
Yes, with a router that supports failover. DMXhub gives each route a TTL on signal loss and an on-loss behavior (hold last look, snap to zero, fade to black, or go to a snapshot), plus auto-return and a manual flip between a primary and backup source, for either protocol.
Last updated June 2026 · by CUE++