Art-Net vs DMX vs sACN vs SPI: Which Protocol Actually Works for Pixel LEDs? #
Choosing a lighting protocol for a pixel LED installation is one of those decisions that looks straightforward until your installation has 10,000 pixels and the network is dropping frames. Art-Net, DMX512, sACN, and SPI all get mentioned in the same conversations, but they solve different problems at different layers. This guide cuts through the confusion and tells you exactly what each protocol does, where it breaks down, and which one professional installers reach for — and why.
What Are These Protocols Actually Doing? #
Before comparing them, it helps to understand that these protocols don’t all live at the same level. DMX512 and SPI are physical-layer serial protocols — they run over dedicated wires directly between a controller and a fixture or LED chip. Art-Net and sACN are network protocols — they carry DMX-style channel data inside standard Ethernet packets over your existing network infrastructure. The LEC3 protocol from LED Strip Studio is something different again: a modern, compressed, encrypted protocol built from scratch specifically for pixel LED control over Ethernet.
Mixing these up is the source of a lot of confusion. SPI is what talks to the IC chip inside your WS2815 LED strip or APA102 LED strip. Art-Net is what carries the data from your computer or media server to the Art-Net LED controller, which then converts it to SPI. They work together, not against each other.
Protocol Comparison Table #
| Protocol | Cable | Wireless? | Built for Pixels? | Max Pixels / Run | Key Strengths |
|---|---|---|---|---|---|
| Art-Net | Ethernet Cat5e/6 | Yes (Wi-Fi) | No | 170 RGB per universe | Universal compatibility — works with grandMA, Resolume, Madrix, MadMapper |
| DMX512 | 3-pin or 5-pin XLR | No | No | 170 RGB per cable | Rock-solid reliability; triggers SD card animations on standalone controllers |
| sACN | Ethernet Cat5e/6 | Yes (Wi-Fi) | Partial | 170 RGB per universe | Multicast support; built-in source priority for merging |
| SPI | 2–4 wires | No | Yes | IC-dependent | Direct chip language; zero latency; used inside every pixel controller |
| LEC3 (LSS) | Ethernet | Yes (compressed) | Yes | 100,000+ pixels | Real-time compression, TCP delivery, encryption, pixel-native addressing |
Art-Net: The Industry Standard That Wasn’t Built for Pixels #
Art-Net is by far the most widely supported lighting network protocol. Every major lighting console — grandMA, ChamSys, Avolites — outputs Art-Net. Every serious media server — Resolume Arena, MadMapper, LED Strip Studio software — outputs Art-Net. If you need an Art-Net pixel controller that works with gear from multiple manufacturers, Art-Net is the obvious choice.
The problem is that Art-Net was designed in 1998 to carry DMX512 data over Ethernet. DMX was designed for intelligent fixtures — moving heads, dimmers, fog machines — not for thousands of individually addressed pixels. So Art-Net inherits the 512-channel universe limit of DMX, which works out to just 170 RGB pixels per universe. Drive 5,000 pixels and you’re managing nearly 30 universes of uncompressed UDP data. On a wired Gigabit switch this is fine. On Wi-Fi, it’s a recipe for dropped frames and flickering.
Art-Net also uses UDP, which means it’s “fire and forget” — if a packet gets lost, that frame is simply skipped. In a dark nightclub with strobes going, you might never notice. In a live TV studio broadcast, a single dropped frame shows up on camera.
DMX512: Still Useful, But Not the Way You’d Expect #
DMX512 is the original standard of professional stage lighting. It’s been around since 1986, it runs on simple balanced RS-485 cable, and it works. For controlling a handful of intelligent fixtures or a DMX dimmer rack, it’s still perfectly valid.
For DMX pixel controller use with large addressable LED strip installations, though, DMX is basically impractical. Each cable carries one universe — 170 RGB pixels. Running 10,000 pixels over DMX requires 59 separate RS-485 cable runs. Nobody does that.
Where DMX still earns its place in a modern LED pixel installation is as a trigger signal. Many professional standalone LED controllers with SD card playback support a DMX input specifically for this: a lighting desk sends a single DMX channel value, and the controller switches to the corresponding stored animation. This keeps the pixel data off the DMX cable entirely and just uses DMX for what it’s still genuinely good at — reliable, simple, low-bandwidth control commands.
sACN (E1.31): The Better Ethernet Protocol for Large-Scale Work #
sACN — Streaming ACN, standardized as E1.31 — is the ESTA’s modern answer to Art-Net. It also carries DMX universes over Ethernet UDP, but it adds two features that matter enormously at scale.
The first is multicast, which means an sACN LED controller subscribes to only the universes it needs, and the network switch only sends it those universes. In a large installation with dozens of controllers, this prevents the network flooding that happens when every controller receives every Art-Net universe broadcast. For stadium-scale or LED video wall installation projects with complex data routing, sACN’s multicast architecture is significantly cleaner.
The second is a priority system (values 1–200) that lets multiple sources send to the same universe and defines which one wins. This makes it possible to run a backup media server alongside the primary, or to allow a local controller to override a remote one — without needing a hardware merger. For TV studio LED lighting or permanent architectural installations where redundancy matters, that’s a real advantage.
sACN is still 170 pixels per universe like Art-Net, and it’s still UDP, so it has the same packet-loss limitations. But it’s generally the better choice for large-scale, multi-controller commercial LED installation work.
SPI: The Language Every Pixel Chip Actually Speaks #
SPI (Serial Peripheral Interface) isn’t really a competing protocol — it’s what happens at the last mile. Every addressable LED strip IC — WS2811, WS2812B, WS2815, SK6812, APA102, TM1803, MBI6024 — receives its color data as SPI pulses directly from a controller output pin.
When you use an Art-Net to SPI converter, the controller receives Art-Net universe data over Ethernet and translates it in real time to the SPI timing required by your specific IC family. Different chips use different SPI protocols — APA102 uses a clock and data line, WS2812B uses a single-wire timed pulse — so the SPI LED controller needs to know exactly which IC it’s talking to.
The main limitation of SPI is distance. TTL SPI signals from a standard controller output start degrading after about 3–5 meters of cable. For large installations, you need an SPI signal extender or SPI signal splitter — a differential buffer that boosts the signal for long cable runs. Professional controllers like the LEC3 build this into their output architecture so you can push SPI data reliably over tens of meters without external hardware.
Why Art-Net and sACN Were Never Really Meant for Pixel LEDs #
Here’s the thing that rarely gets said plainly: Art-Net and sACN were designed to control intelligent lighting fixtures, not pixel LEDs. The 512-channel universe model made perfect sense in 1998 when a fixture used 3–20 channels for pan, tilt, color, gobo, and strobe. It became awkward when a single meter of WS2812B LED strip running at 60 LEDs/m burns through 180 channels.
The entire workflow of dividing a pixel installation into 170-pixel groups, assigning universe numbers, patching output ports — all of that overhead exists because the protocol wasn’t designed for this use case. It works, and the industry has built enormous ecosystems on top of it, but it’s fundamentally a workaround.
Every time someone asks “how many pixels per Art-Net universe?” they’re dealing with a consequence of this mismatch. The answer — 170 RGB, 128 RGBW — is a number that only exists because of a 40-year-old channel count limit for stage dimmers.
The LEC3 Protocol: Built for Pixels From the Ground Up #
The LED Strip Studio protocol used in the LEC3 LED controller approaches the problem differently. Instead of wrapping DMX channels in Ethernet packets, it works natively in pixels. You address pixels directly — no universe math, no 170-pixel grouping. The software knows there are 50,000 pixels in your installation, and it sends 50,000 pixels worth of data, period.
Three technical decisions separate it from Art-Net and sACN in ways that matter for professional use.
Real-time compression. The LEC3 protocol compresses video data on the fly, reducing network usage by approximately 80% compared to uncompressed Art-Net. This is what makes high-resolution pixel content viable over Wi-Fi — not because Wi-Fi is great (it isn’t), but because the data load is small enough that the network doesn’t get overwhelmed. For a wireless Art-Net controller scenario, uncompressed Art-Net saturates a standard 2.4GHz Wi-Fi network almost immediately at large pixel counts. The LEC3 protocol doesn’t.
TCP delivery. Art-Net and sACN use UDP — fast, but lossy. The LEC3 protocol uses TCP, which guarantees every data packet arrives and is acknowledged. In a TV studio LED lighting scenario where a single dropped frame could go out live on broadcast, or in a LED building facade lighting installation running 24/7, that guarantee matters.
Encryption. Art-Net is unencrypted. Anyone on the same network can send Art-Net packets to your controllers. The LEC3 protocol includes data encryption, which is increasingly important for permanent public installations — outdoor LED pixel installations, architectural LED lighting on commercial buildings, LED billboard advertising displays — where the controller is connected to a shared or public network.
Which Protocol Should You Actually Use? #
For most installations that use third-party software — Resolume, MadMapper, a lighting console — you’ll be using Art-Net because that’s what those tools output. Choose a professional Art-Net pixel controller with enough universes for your pixel count, wire it on a dedicated Ethernet switch, and keep Wi-Fi for monitoring only.
For large-scale stadium or multi-venue work where bandwidth management and source redundancy matter, sACN is worth the extra setup complexity.
For a plug and play LED system running autonomously in a bar, hotel lobby, or restaurant that never needs to talk to a third-party console, use an SD card LED controller like the REACTIVO on the LEC3 protocol and skip the Art-Net overhead entirely.
For the highest-demand scenarios — permanent TV studio LED lighting, LED facade lighting on major buildings, large LED pixel curtain or LED pixel wall installations that need guaranteed delivery and secure control — the LEC3 is the right tool.
How many pixels can I fit in one Art-Net universe?
One Art-Net universe carries 512 DMX channels. RGB pixels use 3 channels each, so you get 170 RGB pixels per universe. RGBW pixels — like SK6812 RGBW strips — use 4 channels each, giving you 128 pixels per universe. This limit is a fundamental property of the protocol and cannot be changed. For large installations you simply use multiple universes — a 5,000-pixel installation needs about 30 universes of Art-Net.
What is the difference between Art-Net and sACN for pixel LED installations?
Both Art-Net and sACN carry DMX universe data over standard Ethernet and support the same 170 RGB pixels per universe. The key differences are: sACN uses multicast, so network switches only send each controller the universes it needs — this prevents network flooding on large installations. sACN also has a built-in source priority system (1–200) for merging multiple control sources without hardware. For most pixel installations Art-Net works fine; for complex multi-controller setups or stadium-scale work, sACN’s architecture is cleaner.
Can I control addressable LED strips over Wi-Fi using Art-Net?
Yes, but with significant limitations at scale. Art-Net sends uncompressed DMX data as UDP packets, and a large pixel installation generates a lot of network traffic — a 10,000-pixel setup pushes nearly 30 Art-Net universes simultaneously. A standard 2.4GHz Wi-Fi network saturates quickly under that load, causing frame drops and flickering. The LEC3 protocol from LED Strip Studio solves this with real-time compression that cuts bandwidth by about 80%, making wireless pixel control genuinely stable even at high pixel counts.
What is SPI and how does it relate to Art-Net in a pixel LED setup?
SPI (Serial Peripheral Interface) is the low-level signal that actually drives the IC chips inside your addressable LED strips — WS2812B, WS2815, APA102, SK6812, and all others. Art-Net carries the color data over Ethernet from your computer or media server to the controller. The controller then converts that data in real time to SPI pulses that the LED chips understand. An Art-Net to SPI converter is what bridges these two worlds. SPI itself is a direct wire protocol with no network stack — it only works over short distances (3–5m) without a signal buffer.
Why does DMX only support 170 pixels and how do professionals work around it?
DMX512 was designed in 1986 for stage lighting fixtures like dimmers and moving heads, not for pixel LEDs. Each DMX universe carries 512 channels, and an RGB pixel needs 3 channels, so you get exactly 170 pixels per universe. In professional pixel LED installations, this limit is bypassed by using Art-Net or sACN — which can carry thousands of universes over a single Ethernet cable — or by using a native pixel protocol like the LEC3 that doesn’t use DMX universe addressing at all. Modern professionals use DMX primarily as a simple trigger signal to start animations stored on an SD card controller, not for carrying actual pixel color data.
What makes the LEC3 protocol better than Art-Net for large TV studio or facade installations?
Three things. First, real-time compression: the LEC3 protocol reduces bandwidth by roughly 80% compared to uncompressed Art-Net, which matters enormously for wireless stability and network headroom on large installations. Second, TCP delivery: unlike Art-Net’s UDP (which drops lost packets), the LEC3 protocol guarantees every frame arrives — critical for live broadcast TV studio LED lighting where a dropped frame goes out on camera. Third, pixel-native addressing: there’s no universe math, no 170-pixel grouping, no patching overhead. You work directly in pixels, and the system scales cleanly to 100,000+ pixels without the administrative complexity that Art-Net universe management creates at scale.