Getting Started with WLED: Light Sequences in 5 Minutes, No Coding
Light sequences like this used to take me hundreds of lines of code. Now it takes about 5 minutes. The difference is an open source firmware called WLED. It runs from its own app, so there’s no coding involved. Even if you know nothing about microcontrollers, you can be up and running in minutes.
What you’ll need
- A microcontroller that can run WLED. An ESP32 or ESP8266 is the common choice, but nothing fancy is required. Even a tiny ESP01 does the job for a basic strip.
- An addressable LED strip. I’m using WS2812B, sometimes called NeoPixel, which is what most WLED setups use.
- A separate power supply if you’re running more than a handful of LEDs. The microcontroller alone can’t supply enough current.
Wiring is simple. Data goes to one GPIO pin, and power and ground connect to your supply.
Flashing WLED onto the board
Go to install.wled.me in Chrome or Edge, plug the board in, and hit install.
ESP01
I use a programming jig for the ESP01, which makes flashing painless because you don’t have to hand wire the boot mode pins every time.
Important: choose advanced mode and set the flash size to 1 MB. If you skip this, the installer will still run through and look like it worked, but the ESP01 won’t boot afterward. Get that one setting right and you’re flashed and ready to go.
ESP32
The flash size step isn’t necessary. I’d recommend clicking erase memory first to wipe anything already on the board, then hitting install. It takes a few minutes.
When it’s done, a new Wi-Fi network will appear nearby. That’s the board itself. Connect to it to continue.
The two settings that matter
Before anything lights up, you need to get two settings right in the WLED interface: LED count and LED pin.
LED count is how many individual LEDs are on your strip. If you’re not sure, check the packaging or count them. Get it wrong and you’ll either lose LEDs at the end of the strip or see garbled colors past the end.
LED pin is where people new to microcontrollers get tripped up. Every board has GPIO pins (general purpose input/output), the little metal legs or holes you connect wires to. Each has a number, and that number is what WLED wants, not the physical position on the board. If your data wire is on the pin labeled GPIO2, enter 2, not “the third pin from the left.”
Same process on a different chip
To show this isn’t tied to one board, I switched to an ESP32-S3 Mini. Same firmware, same setup process, just a different physical layout. The only thing that changes is which GPIO number you enter.
This controller has 5V and ground broken out on their own pins, so I used those to power the strip directly. For larger runs of LEDs, connect to your power supply directly instead of going through the board, since the board can only handle so much current.
I used GPIO7 for the data line. Back in WLED, I updated the LED count and pin number to match and hit save. If everything is wired correctly, the strip glows yellow. That’s WLED’s way of saying it’s connected and ready.

Make it your own
From here you can play with colors and animations in the app. There’s no real limit to the combinations when you mix base colors and themes. Find one you really like and save it as a preset. It goes into preset 1 and becomes the default animation when the unit boots, instead of the solid yellow.
Top 5 troubleshooting tips
If you’ve made it this far but can’t get it working, check these, counting down from five:
- You’re trying to use an Arduino. Arduinos and ESPs can look similar, but WLED only works on ESP devices because of its architecture.
- Your first pixel is dead. This can happen if you connect the data pin to an Arduino without a resistor, which quickly kills the pixel. You can cut it off or solder to the next pixel along to test.
- You wired to data out instead of data in. LED strips have a direction, shown by a small arrow. Check that you’ve soldered onto the correct pad.
- A bad ground connection. Weirdly, the pixels can still light with no ground connected, which can have you running in circles for a while.
- The wrong IO pin. This is easy to mix up, so double-check the one you’ve configured. Some pins have special functions, and if something is connected to them they can stop the ESP from booting. These are called strapping pins, and a quick search will tell you which ones apply to your board.
Wrap-up
That’s everything you need to get WLED running on a strip. I’ll go into more detail in upcoming videos, so subscribe if you want to follow along.
No related posts.
You May Also Like
DIY NeoPixel Frisbee with Accelerometer and Bluetooth: A Fun Project for Summer Nights
13 November 2024WLED Matrix Displays and Sound Reactive Effects: Setup in a Few Minutes
9 October 2026