Max Walter · July 16, 2026

In short: Art-Net and sACN (ANSI E1.31) are the two most widely used Ethernet protocols for sending DMX lighting data over an IP network to LED and DMX controllers. Art-Net is the older, vendor-driven de facto standard; sACN is the newer, officially ESTA-standardized successor with multicast transmission and priorities. Both carry classic DMX512 universes — only the path through the network differs.

What is Art-Net?

Art-Net is a protocol developed in 1998 by Artistic Licence that transmits DMX512 over UDP/IP. By default it sends lighting data via broadcast (optionally unicast) on port 6454. The current version, Art-Net 4, can address up to 32,768 universes. Thanks to its long history, Art-Net is supported by practically every node, interface, and software package — it’s the most compatible common denominator.

What is sACN (E1.31)?

sACN stands for “Streaming ACN” and is defined in ESTA’s ANSI E1.31 standard. It also transmits DMX data over UDP, but by default uses multicast on port 5568: each universe gets its own multicast group, so devices only receive the data they actually need. sACN also supports priorities (0–200 per universe) — multiple sources can feed the same universe, and the receiver uses the highest priority.

Art-Net vs. sACN: The Key Differences

FeatureArt-NetsACN (E1.31)
StandardizationVendor-specific (Artistic Licence), de factoANSI E1.31 (ESTA), official
TransportUDP – broadcast or unicastUDP – multicast (or unicast)
Port64545568
Max. universesup to 32,768 (Art-Net 4)up to 63,999
PriorityNot natively supportedYes – 0 to 200 per universe
Network loadHigher (broadcast to all)Lower (targeted multicast)
Device discoveryArtPoll / ArtPollReplyUniverse Discovery
Typical useMaximum compatibility, mixed hardwareLarge, professional installations

Which Protocol Should You Use?

As a rule of thumb: Use sACN (E1.31) if you’re running a large or professional installation with many universes and your network handles multicast cleanly (managed switch with IGMP snooping). Multicast and priorities keep network load low and allow clean backup scenarios. Go with Art-Net if you need maximum compatibility with older nodes and mixed hardware, or if you’re using a simple, unmanaged network. Many setups run both protocols in parallel — for different devices on the same network.

PixDrive Studio speaks both protocols — Art-Net and sACN (E1.31), plus TPM2.NET, DDP, and WARLS. You can choose per universe which protocol goes to which controller, without compromises.

Frequently Asked Questions

Can I use Art-Net and sACN at the same time?
Yes. Both run in parallel on the same network without issues, as long as universes and ports are assigned correctly. PixDrive Studio can decide per output which protocol to use.

Do I need a managed switch?
For sACN multicast in larger networks, yes — a switch with IGMP snooping prevents multicast traffic from flooding all ports. For small setups or Art-Net broadcast, a simple switch is often enough.

How many universes do the protocols support?
Art-Net 4 addresses up to 32,768 universes, sACN up to 63,999. In practice, controllers, bandwidth, and frame rate limit the number more than the protocol does.

Does PixDrive Studio support both?
Yes — Art-Net and sACN (E1.31) are fully integrated, including additional protocols like TPM2.NET, DDP, and WARLS.

→ Try PixDrive Studio for free