kno.wled.ge

WLED runs on ESP8266 and ESP32 boards and drives addressable LED strips built on the NeoPixel family (WS2812B, WS2811, SK6812), SPI chipsets such as WS2801 and APA102, and HUB75 video wall panels. If your strip uses one of those chipsets and your controller is an ESP8266 or ESP32, it is compatible in principle. The practical limits are the number of LED outputs per board and whether you need RGBW or a 2D panel.

Compatible LED strips and chipsets

WLED's own documentation groups supported LEDs into two families:

RGBW strips are explicitly supported, which matters if you want a dedicated white channel rather than mixing white from RGB. The docs also list "Multi-strip Support" and "Mixed 2D and 1D Bus" as features, so a single controller can drive more than one strip type in one setup.

Compatible controllers

WLED is an ESP32/ESP8266 webserver implementation, so the controller must be one of those two chip families. The documentation's "Compatible hardware" section covers controllers, and the compatibility pages split into LED strips, controllers, and other hardware.

Output capacity differs by chip:

• ESP8266: up to 3 LED outputs per instance
• ESP32: up to 10 LED outputs per instance

That is the number of independent data outputs, not the number of LEDs. Total LED count is limited by your power supply, injection, and the data protocol rather than by a single published ceiling in this material.

How to check your own hardware

1. Identify the chip printed on your strip (for example WS2812B or SK6812) or the driver IC on an SPI strip (WS2801, APA102).
2. Confirm your board's microcontroller is an ESP8266 or ESP32 — not a Raspberry Pi, Arduino Uno, or similar.
3. Count how many separate outputs you need. Three or fewer fits an ESP8266; up to ten fits an ESP32.
4. If you need a dedicated white channel, check that your strip is an RGBW variant.
5. If you are building a video wall rather than a strip run, confirm the panel is HUB75.

Common mismatches

• Non-addressable strips (plain 12V or 24V RGB with a single color for the whole run) are not what WLED drives; it expects individually addressable pixels.
• Analog-only or proprietary controllers cannot be reflashed to run WLED unless they contain an ESP8266 or ESP32.
• Assuming output count equals LED count. Adding a second output means another data line and another injection point, not just more LEDs on the same wire.

The WLED documentation's "Compatibility" section and its "LED strips," "Controllers," and "Other Hardware" pages are the place to confirm a specific part before buying. If your strip's chipset appears in the table above and your board is an ESP32 or ESP8266, you can proceed to the Quick Start and wiring guides.

WLED exposes a broad set of control interfaces that fall into three groups: network protocols for real-time lighting data (E1.31/Art-Net, DDP, UDP realtime, tpm2.net), application-level APIs for automation (HTTP Request API, JSON API, MQTT, Websocket), and hardware or ecosystem integrations (DMX input/output, Philips Hue, ESPNow remotes, UDP sync between WLED devices). The right choice depends on what is sending the data: a lighting console, a home automation hub, a media server, or another WLED node.

Network protocols for real-time light data

These interfaces stream pixel data to WLED over the network, so they suit media servers, lighting desks, and visualizers rather than simple on/off automation.

DMX also works in both directions: WLED can output DMX and accept DMX input, so it can act as a bridge between a DMX chain and addressable LEDs.

Application APIs and home automation

If you are triggering effects, presets, or colors from software rather than streaming frames, these are the relevant interfaces:

• HTTP Request API — send commands over HTTP; the documentation notes presets can be used to automatically execute API calls.
• JSON API — structured state and control, the usual target for scripts and dashboards.
• MQTT — publish/subscribe control, the common path for home automation systems.
• Websocket — persistent connection for live state updates and control.
• Remote Control — grouped in the docs alongside the API options above.

For broader automation, WLED documents a Home Automation section and Remote Access / IFTTT, which covers reaching a device from outside the local network. There is also an OTA Lock option and an "Accessing WLED over Internet" topic, so remote reachability is a documented configuration rather than an assumed default.

Ecosystem and hardware integrations

• Philips Hue — listed as a supported interface, for integrating WLED into a Hue-centric setup.
• ESPNow Remotes — low-latency remote control between ESP devices without Wi-Fi infrastructure.
• Relay Control — switch a relay alongside the LEDs.
• Audio Reactive WLED — drive effects from sound input.
• Ethernet (LAN) — wired networking as an alternative to Wi-Fi.

How to choose

• Streaming frames from a PC or console → E1.31/Art-Net, DDP, or UDP Realtime.
• Triggering presets from a smart home hub → MQTT or the JSON/HTTP API.
• Keeping several WLED strips identical → UDP Sync.
• Mixing WLED into an existing Hue or DMX installation → Philips Hue integration or DMX input/output.

The project's own documentation organizes all of this under an Interfaces section, with setup details in the Quick Start and Getting Started pages.

WLED is a fast, feature-rich firmware for ESP32 and ESP8266 boards that controls addressable LEDs such as WS2812B, WS2811, and SK6812, plus SPI chipsets like WS2801 and APA102 and HUB75 video wall panels. To get started you need three things: a compatible ESP board, a compatible LED strip, and a way to flash the WLED binary onto the board. After flashing, the board creates its own Wi-Fi access point so you can open the web UI in a browser and configure everything from there — no coding required.

What you need before you start

• A controller board. WLED runs on ESP32 and ESP8266 hardware. The project notes support for up to 3 LED outputs per ESP8266 instance and up to 10 LED outputs per ESP32 instance.
• A compatible LED strip. NeoPixel-style strips (WS2812B, WS2811, SK6812) work, as do SPI-based chipsets (WS2801, APA102) and HUB75 panels. RGBW strips are supported.
• A power supply matched to your strip, and a way to connect the board to your computer (usually USB).
• A browser on a phone, tablet, or computer to reach the WLED web UI.

Step 1: Install the WLED firmware

The documentation lists several installation routes. Pick the one that matches your setup:

The exact menus and buttons depend on the tool you choose, so follow the linked page for your method rather than guessing at screen layouts. The expected result is the same in every case: the board reboots running WLED and starts broadcasting its own Wi-Fi network.

Step 2: Connect to the WLED access point

On first boot, WLED runs in Access Point mode with an automatic failsafe AP. Join that network from your phone or computer, then open the web UI in a browser. This is the same interface you'll use for all later configuration.

Step 3: Configure Wi-Fi and LED output

In the web UI:

1. Open the Settings page — the documentation describes it as network-based configuration.
2. Enter your home Wi-Fi credentials so the board can switch to station mode and join your normal network. Access Point and station mode are both supported, so you can fall back to the AP if the credentials are wrong.
3. Set your LED output: strip type, length, color order, and which GPIO pin drives the data line. Wiring details are covered in the project's wiring guides.
4. Save and reboot if prompted.

Once the board is on your network, you can reach the web UI from any device on the same network instead of joining the AP each time.

Step 4: Start using effects, palettes, and presets

The web UI gives you color, effect, and segment controls. Key things you can do right away:

• Effects and palettes. WLED integrates the WS2812FX library for over 100 special effects, plus FastLED noise effects and 50 palettes.
• Segments. Split your strip into parts and give each segment its own effect and color.
• Presets. Save and load colors and effects — up to 250 user presets, with support for cycling through them. Presets can also trigger API calls automatically.
• Nightlight. Gradually dims the strip down, useful for bedtime lighting.

Wiring and hardware notes

The documentation includes dedicated wiring guides and a "Top 5 mistakes" page — read both before powering anything up. Two practical points from the project's own documentation:

• Long data lines are covered under wiring protips; if your strip is far from the controller, check that section before assuming a fault.
• Multi-strip support and relay control are built in, so you can drive more than one strip or switch a power relay from the same board.

Common mistakes to avoid

The project maintains a "Top 5 mistakes" page for a reason. The recurring themes in WLED setups are:

• Powering a long strip from the board's regulator instead of a separate supply sized for the current draw.
• Wrong color order — colors look swapped until you correct the RGB/RGBW order in settings.
• Data line and ground issues — a missing common ground between controller and strip causes flicker or no output.
• Flashing the wrong binary for your chip family (ESP32 vs ESP8266).
• Losing the AP after entering bad Wi-Fi credentials — the failsafe AP exists so you can recover, but you need to know it's there.

Where to go next

Beyond the basics, the documentation covers DMX output and input, E1.31/Art-Net, the JSON and HTTP request APIs, MQTT, Philips Hue integration, UDP sync and realtime modes, audio-reactive effects, home automation, and remote access. If you hit a problem, the FAQ and the recovery pages (including ESP32 recovery and boot-loop detection) are the first places to check.

WLED is an open-source firmware for ESP32 and ESP8266 boards that turns them into network-connected LED controllers. You flash it onto a supported microcontroller, wire up an LED strip or panel, and then control it from a web browser over Wi-Fi. It fits anyone who wants addressable LED lighting they can drive from a phone, browser, or home automation system without writing firmware from scratch.

What WLED actually is

WLED is a fast, feature-rich implementation of an ESP32 webserver built to control addressable LEDs. According to the project's own documentation, it drives:

• NeoPixel chipsets such as WS2812B, WS2811, and SK6812
• SPI-based chipsets such as WS2801 and APA102
• HUB75 video wall panels

The firmware runs on the ESP board itself. The ESP creates its own Wi-Fi access point on first boot (an automatic failsafe AP), and you configure it from there. Once connected to your network, everything is managed through a browser-based interface.

What you can do with it

Lighting effects and control

WLED integrates the WS2812FX library, giving you over 100 special effects, plus FastLED noise effects and 50 palettes. You get a modern UI with color, effect, and segment controls.

Segments are one of the more useful features: they let you assign different effects and colors to different parts of the same LED strip. A single strip can run a rainbow chase on one section and a solid warm white on another.

Presets and automation

You can save and load up to 250 user presets for colors and effects, and cycle through them. Presets can also trigger automatic API calls, which is how most people wire WLED into scheduled or event-driven routines.

Interfaces and integrations

The documentation lists a wide range of control interfaces, including:

There is also a dedicated Home Automation section and Remote Access / IFTTT support in the advanced documentation.

Hardware capacity

• Up to 3 LED outputs per ESP8266 instance
• Up to 10 LED outputs per ESP32 instance
• Support for RGBW strips
• Relay control and multi-strip support

Other built-in functions

• Nightlight — gradually dims the lights down
• Full OTA software updates over HTTP, with optional password protection
• Configurable analog clock, plus support for the Cronixie kit
• Audio reactive effects (covered in the advanced section)
• Ethernet (LAN) compatibility
• Pixel art tools — a Pixel Art Converter, PixelForge for images and GIFs, and custom fonts

Who it's for

WLED suits you if you want:

• Smart LED strips — desk, shelf, or room accent lighting controlled from a browser or phone
• Ambient and decorative lighting — effects, palettes, and segments for scenes
• DIY lighting projects — matrix panels, HUB75 video walls, or multi-strip builds
• Home automation integration — MQTT, JSON API, and IFTTT hooks into a larger smart home
• Synchronized multi-controller setups — UDP sync and realtime protocols across several boards

It is less suited to someone who wants a plug-and-play consumer product with no wiring or flashing. WLED requires a compatible ESP board, a supported LED strip or panel, and a power supply sized for your LEDs.

Getting started

The documentation's quick start path is:

1. Check compatibility — confirm your LED strip and controller board are supported (see the Compatibility section for LED strips, controllers, and other hardware).
2. Install the firmware — options include installing the WLED binary, using the ESP GUI, or the WLED ESP Flasher.
3. Wire it up — follow the Wiring Guides.
4. Configure over the network — connect to the WLED access point, then set up station mode so it joins your Wi-Fi.
5. Control it — use the Web UI for colors, effects, segments, and presets.

The project also maintains a Top 5 mistakes page and a FAQ, both worth reading before your first build — the wiring and power pitfalls are the ones that most commonly trip up new users.

Where to look next

The documentation is organized into Basics, Compatibility, Software Installation, Features, Interfaces, Advanced, Wiring, Compiling, Community Usermods, and About sections. If you are deciding whether WLED fits your project, the Features and Compatible Hardware pages answer most of it. If you have already decided, start with Getting Started and the Wiring Guides.

WLED is a fast, feature-rich firmware implementation of an ESP32 (and ESP8266) webserver for controlling addressable LEDs. It supports NeoPixel chipsets like WS2812B, WS2811, and SK6812, SPI-based chipsets like WS2801 and APA102, and HUB75 video wall panels. If you want a single firmware that handles effects, color control, network integrations, and over-the-air updates without writing your own code, WLED covers that scope.

Effects and color control

• WS2812FX library integration — provides over 100 special effects out of the box.
• FastLED noise effects — adds organic, noise-driven animations on top of the standard effect set.
• 50 palettes — predefined color gradients you can apply across effects.
• Modern UI — color, effect, and segment controls are exposed through a web interface rather than requiring code changes.
• RGBW strip support — works with four-channel strips, not just RGB.

Segments, presets, and macros

• Segments let you assign different effects and colors to different parts of a single LED strip, so one physical strip can behave like multiple independent zones.
• Up to 250 user presets save and load colors and effects easily, and you can cycle through them.
• Presets can trigger API calls automatically, which turns them into lightweight macros for automation.
• Macros are a documented feature area for chaining actions.

Hardware and output capacity

This matters if you're planning a multi-strip build: an ESP32 gives you substantially more independent output channels than an ESP8266.

Network, control interfaces, and integrations

WLED exposes a broad set of control paths, which is often the deciding factor for whether it fits a project:

• Web UI — the primary interface for configuration and control.
• JSON API, HTTP Request API, and WebSocket — for programmatic control.
• MQTT — for home automation message buses.
• E1.31 (sACN) / Art-Net and DMX input/output — for lighting-industry protocols.
• UDP sync, UDP Realtime / tpm2.net, DDP Realtime, ESPNow — for multi-device synchronization and real-time streaming.
• Philips Hue — integration with an existing Hue setup.
• Home Automation and Remote Access / IFTTT — documented integration paths.
• Audio Reactive — effects that respond to sound.

Setup, updates, and reliability features

• Access Point and station mode with automatic failsafe AP — if the device can't join your network, it falls back to its own access point so you can still reach it.
• Settings page — full configuration over the network, no reflashing needed.
• Full OTA software updatability over HTTP, which can be password protected.
• Nightlight function — gradually dims the LEDs down instead of cutting them off abruptly.
• Configurable analog clock, plus support for the Cronixie kit by Dia.

Other capabilities worth knowing

The documentation also covers multi-strip support, relay control, Ethernet (LAN) compatibility, white handling (relevant for RGBW), a Pixel Art Converter and PixelForge image/GIF tool, custom fonts, a particle system, and HUB75 mapping including mixed 2D and 1D bus configurations.

How to decide if WLED fits your project

• Choose WLED if you want addressable LED control with a ready-made web UI, a large built-in effect library, and one of the widest protocol/integration sets available in this space — especially if you need MQTT, E1.31/Art-Net, or multi-device sync.
• Pay attention to output count if you're driving many independent strips: ESP8266 caps at 3 outputs, ESP32 at 10.
• Check the compatibility pages for your specific LED strip and controller before buying, since supported chipsets are listed explicitly (NeoPixel WS2812B/WS2811/SK6812, SPI WS2801/APA102, and HUB75 panels).

For installation paths, the documentation lists installing the WLED binary, using ESP GUI, or using WLED ESP Flasher, alongside a Quick Start guide and a "Top 5 mistakes" page that's worth reading before your first flash.