What a TOL file actually is
Think of a TOL file the way a cook thinks about a written recipe. The dish is the light effect running on your strip. The recipe is the instruction sheet that tells the controller which pixel lights up, in what colour, and at what moment. Once the recipe is written down, anyone can produce the same dish again — next week, next city, on a different fixture.
That is a TOL file. It stores one effect: a chase, a fade, a wave, a colour wipe. It is not the whole show. A complete show with several effects arranged one after another is an SWF file, and that is a different job. Most technicians only ever need TOL files, because on site you rarely want more than a handful of good effects that you can drop in and adjust.
The reason it is worth learning to build your own is simple. Downloaded effect files are made for someone else's fixture. A file built for a 100-pixel strip looks wrong on a 400-pixel toran — the movement crawls, or the pattern repeats in a way the customer notices. When you build the file yourself, it fits the fixture in front of you.
LED Edit has been released in several builds, and menu wording shifts slightly between them. The workflow below is the same in every version, but if a menu on your copy is named a little differently, look for the option that does the same job rather than the exact word.
What to prepare before you start
Five minutes of preparation here saves an hour of rework later. Before you open the software, write down four numbers:
| What you need | Why it matters | Example |
|---|---|---|
| Total pixel count | The effect is drawn across this number. Guess it wrong and the pattern will not reach the end of the strip. | 360 pixels |
| IC type | Decides the data timing. Wrong IC means flickering or dead pixels. | WS2811 |
| Controller model | Sets the port count and the export format. | T1000S |
| Physical layout | Straight line, zig-zag, or a matrix. This decides how movement travels. | Single line, left to right |
The pixel count is the one people get wrong most often. Count the actual pixels on the fixture, not the metres of strip. On a 12V WS2811 strip, three physical LEDs usually make up one pixel — so a strip with 180 LEDs may only be 60 pixels. If you are unsure which type you have, our WS2811 vs WS2812B guide explains how to tell them apart.
Building the file, step by step
Set up the hardware first
Open the hardware or setup screen and select your controller model, your IC type, and your total pixel count. Do this before anything else. If you build an effect and then change the pixel count afterwards, the timing you carefully adjusted will no longer match, and you will be starting over.
Draw your pixel layout
This is the step most beginners skip, and it is the reason their effect runs backwards on the fixture. The software has no idea how your strip is physically wired. If the strip goes left to right on the top row and then right to left on the row below — a zig-zag, or serpentine layout — you have to draw it that way.
Get this right and a wave effect will sweep smoothly across the whole fixture. Get it wrong and the wave will jump back to the start on every second row.
Add one effect to the timeline
Open the effect editor and place a single effect on the timeline. Start with something simple — a straight chase or a colour fade. Do not stack four effects on your first attempt. One effect, adjusted properly, is worth more than four effects fighting each other.
Set the colours
Pick your colours in the effect properties. For wedding and event work, two or three colours usually look better than a full rainbow — a rainbow across a long toran tends to read as a muddy blur from a distance. Save the rainbow for short fixtures where the customer will be standing close.
Preview and correct
Run the preview window and watch the effect the whole way through, at least twice. You are looking for three things: does the movement reach the end of the fixture, does the loop restart cleanly, and does the speed suit the fixture length. Correcting this on screen takes seconds. Correcting it on a ladder at a venue takes half an hour.
Save the file
Save the effect as a TOL file with a name that tells you what it is. Chase_Blue_360px_Fast.tol is a useful name. effect1.tol is not — in six months you will have forty files called effect1 through effect40 and no idea which is which.
Put the pixel count in the filename. When you arrive at a job with a 360-pixel fixture, you can pull up every file you have already tuned for 360 pixels instead of guessing which one will fit.
The three settings that decide how good it looks
Speed
Speed is relative to fixture length, not an absolute number. A chase that looks lively across 100 pixels looks slow and lazy across 500 pixels, because it has five times the distance to cover. As a rule of thumb, when you double the pixel count, increase the speed to keep the same visual pace. Always judge it in the preview at the real pixel count — never trust a speed value copied from another job.
Brightness
Full brightness is rarely the right answer. There are two reasons. First, at maximum brightness every pixel draws its full current, and a long run will show visible dimming towards the far end unless you have injected power correctly — our wiring and power injection guide covers this. Second, at close range a fully bright white pixel washes out the colour either side of it. Around eighty percent usually looks cleaner and puts less load on the supply.
Loop length
Watch where your effect ends and where it starts again. If the last frame does not flow into the first frame, the audience sees a jump every few seconds. Nobody can say what is wrong, but the display looks cheap. Adjust the end of the timeline until the restart is invisible.
An effect that looks impressive on a laptop screen can look completely different on a fixture twenty feet up. Whenever you can, test on a short sample strip and step back before you commit the file to a job.
Reusing the file on other jobs
This is where the effort pays back. A TOL file is a small file, and it copies like any other. Keep a folder on your laptop organised by pixel count, and back it up — a pen drive, a cloud folder, anything. Technicians lose years of tuned effect files to a single failed hard disk, and there is no way to get them back.
When you reuse a file on a fixture with a different pixel count, load it, change the pixel count in the hardware settings, then re-check the speed and the loop. It usually needs a small adjustment rather than a rebuild. That adjustment takes two minutes, which is the whole point of building your own library.
Five mistakes that waste an afternoon
- Changing the pixel count after building the effect. Set the hardware first, always.
- Skipping the layout step. Your effect will run backwards or break at every row on a zig-zag fixture.
- Copying speed values from another job. Speed only means something relative to fixture length.
- Not previewing the full loop. The restart jump only shows up if you watch it twice.
- Saving everything to the desktop. One reinstall and the library is gone.
Questions we get asked
Can I open a TOL file made by someone else and edit it?
Yes. Load it into the timeline and adjust it like any effect you built yourself. This is often the fastest way to learn — take a file that looks good, open it, and see how the layers were put together.
Why does my effect look different on the fixture than in the preview?
Almost always one of two things: the pixel layout in the software does not match the physical wiring, or the RGB signal order is wrong so the colours are swapped. Check the layout first, then the signal order.
How many effects should I keep in my library?
Ten well-tuned effects beat two hundred downloaded ones. Most working technicians rely on five or six files for the majority of their jobs and adjust them per fixture.
Does the TOL file store my controller settings too?
The effect file holds the effect. Controller and pixel settings live in the project configuration, which is why you re-check the hardware settings whenever you load a file on a different fixture.
Tell us and we will correct it. Menu wording differs between LED Edit builds, and reports from the field are how this guide stays accurate. Use the contact page.
Rajkumar
Six years in the pixel LED industry, running a manufacturing and supply business for event decorators and tent professionals across India, and teaching controller programming to working technicians on YouTube.