What Is Art-Net? A 2026 Explainer for Lighting Engineers

What Is Art-Net?

Art-Net is an Ethernet-based protocol, invented and maintained by Artistic Licence, that carries DMX512 lighting data over standard UDP networking. It lets you push hundreds of universes of lighting control over a single Ethernet cable — vastly more than the one universe (512 channels) of traditional DMX over XLR.

Art-Net became the dominant Ethernet lighting protocol for two reasons: it was free to license, and it shipped early. When network-based lighting took off in the early 2000s, Artistic Licence's permissive approach meant every console and node manufacturer could implement it without a royalty cost, so support spread fast. GrandMA, Avolites, Hog, Chamsys, and virtually every modern lighting console speaks Art-Net natively today.

How Art-Net Works

The mental model is straightforward: take DMX512's 512-channel-per-universe structure, wrap each universe in a UDP packet, and broadcast it on the network. Everything listening on UDP port 6454 picks up the packets and translates them into DMX for downstream fixtures.

Packet Structure

An Art-Net DMX packet contains:

• Header: magic bytes "Art-Net\0" (null-terminated)
• OpCode: identifies the packet type (OpDmx for lighting data)
• Protocol version: 14 (current)
• Sequence number: optional, for detecting dropped packets
• Physical port and universe address: where this data is destined
• Data length and DMX payload: 512 bytes of channel data

A node receiving the packet strips the header and outputs the 512-byte payload as standard DMX on the configured physical XLR port.

Addressing: Net / Sub-Net / Universe

Art-Net's universe address space is organized hierarchically:

• Net: 7 bits (0-127)
• Sub-Net: 4 bits (0-15)
• Universe: 4 bits (0-15)

Total: 15 bits = 32,768 universes. Art-Net 1-3 only used the sub-net + universe fields for 256 universes total, so older nodes may not understand the Net field. Modern Art-Net 4 hardware handles the full range.

Transport: Broadcast and Unicast

Originally Art-Net broadcast every DMX packet to the entire subnet, which works fine for small rigs but creates noise on larger networks. Art-Net 3 introduced unicast, where nodes register their universes via poll/reply messages and the controller only sends packets to devices that care. Most current hardware uses unicast automatically.

CueSync's Art-Net implementation defaults to unicast with broadcast fallback when discovery fails.

Art-Net 4 Features

The current version (Art-Net 4, published 2016) adds:

• 32,768 universes (up from 256 in earlier versions)
• RDM over Art-Net (ANSI E1.20 Remote Device Management) — lets you configure fixture parameters over the network
• Improved discovery protocol with richer node metadata
• Time code support via Art-Net Timecode packets
• Art-Net Trigger for triggering nodes based on external events

Most mid-2020s lighting hardware supports Art-Net 4. Legacy gear from before 2016 may only understand Art-Net 3, which is compatible but limited to the old 256-universe space.

Art-Net vs sACN

Art-Net's closest alternative is sACN (E1.31), an ANSI-standard protocol developed by ESTA. The practical differences:

For DJ and small-club rigs, Art-Net is the safer default — it's what everything speaks and requires no switch configuration. For festival-scale rigs and multi-controller setups with priority merging, sACN's built-in priority field is worth the slightly more complex network setup. The full comparison covers when to use each.

Network Requirements

Art-Net runs over any standard Ethernet network:

• Switch: any gigabit switch works for small rigs; managed switches with IGMP snooping help at scale
• Cabling: Cat5e or better; Cat6 recommended for long runs
• Topology: star topology with a central switch is the standard
• Subnet: Art-Net traditionally uses the 2.0.0.0/8 range (Artistic Licence's assigned space), but modern networks use standard private IPs without issue

Typical Small Rig

1 Mac running CueSync → 1 gigabit switch → 1 Art-Net node (e.g., ENTTEC ODE) → DMX-in to your fixture chain. That's the full rig for a 1-universe setup, and it handles 32 8-channel fixtures (256 channels, half a universe).

Typical Festival Rig

Multiple CueSync instances or consoles → managed switch with VLANs → multiple Art-Net nodes per stage → dozens of universes. sACN often gets used alongside Art-Net here for its multicast efficiency.

Using Art-Net with CueSync

CueSync supports Art-Net output in every edition:

• DJ Edition: up to 4 universes of Art-Net or sACN
• Theatre Edition (coming soon): unlimited universes, plus timecode generation (LTC, MTC, Art-Net, sACN, TCNet) and full CueStack sequencing
• Ultimate Edition (coming soon): everything in Theatre plus Coordination Bus for multi-instance deployments, Predictive Preview, and Connection Analytics

Configuration lives in Settings → Protocols → Art-Net. Add your node by IP address, assign universes, and CueSync's routing engine starts outputting DMX immediately. The GrandMA3 automation guide walks through a complete Art-Net setup step by step.

Common Gotchas

Wi-Fi: don't. Art-Net over Wi-Fi is theoretically possible but unreliable. Wired Ethernet is mandatory for live use.

Firewall interference. macOS Firewall can block UDP port 6454. Allow CueSync through the firewall on first run, or disable firewall on your show network.

Switch loops. Spanning Tree kicks in on consumer switches and can freeze Art-Net traffic for several seconds during topology changes. Run a simple star topology or use a managed switch with STP tuned for lighting.

Universe conflicts. Two devices outputting to the same Art-Net universe cause flickering at best and complete failure at worst. Use sACN with priority merging if you need multi-source control, or use a physical merger.

Subnet mismatches. Art-Net traditionally uses 2.0.0.0/8 but modern networks often use 10.0.0.0/8 or 192.168.0.0/16. Make sure your Mac and nodes are on the same subnet.

Try It

Art-Net is the easiest way to get CueSync talking to your rig. Download CueSync, add a node in Settings → Protocols, and you're outputting DMX over Ethernet in under five minutes. The integrations page has full setup guides for popular node hardware.