Shader fills
Formo team · 10 July 2026
Hello,
Solid colour, gradient, image. This week the list of things a fill can be gets a new, much longer entry.
A fill that is a tiny program
In 2020 we showed a prototype where a rectangle swapped its flat colour for moving water. That was the idea: a shader, a few lines of code that the graphics card runs for every pixel, instead of a picture. This week it is a real fill type in the editor, next to Solid, Gradient and Image: you draw a shape and say "this is glass".
That is what Shader fills are. Pick a shape, open its fill, and choose Shader instead of Solid or Gradient. The shape is now painted by a small program, live, and it keeps moving when you play the animation.
One is ready to use: Glass, which bends and tints whatever sits behind the shape. It comes with settings you can change right in the panel: a colour picker for the tint, sliders for how strongly it bends the picture.
A rectangle becomes glass, and you tune it with sliders.
A shelf of shaders, with previews
The hard part was never the power, it was choosing: names in a list tell you nothing.
Open the paint popup, switch to Shader, and you get a picker of tiles with live previews, so you choose the way you choose a paint chip. A button creates a new shader of your own. Built-in shaders stay linked to the library until you edit them, so improvements to the original reach your project, and the moment you change one it becomes yours. Shader parameters accept formulas, so a value can follow another property, and the canvas handles lock while a formula is bound to them.
Choose by looking, not by name.
One colour popup for solid, gradient and shader
Changing a fill from a flat colour to a gradient used to mean starting over: pick the new type, then pick the colours again. It felt like swapping a paintbrush and finding the paint pot empty.
The paint popup now remembers. Switch between Solid, Gradient and Shader and your colours carry over: the popup tries to reuse the colours you already have. In the gradient view there is a header for the stops with an Add button, and you can drag a swatch to scrub a stop through colours while watching the canvas. The popup follows undo and redo, so stepping back updates what it shows.
Solid to gradient without losing your blue.
Write your own
If you can write a little GLSL, you can make your own. Start a new shader with the + in the fill's paint dialog; open an existing one for editing from the Library. The shader editor shows the program next to a live preview. Every setting your program declares (a colour, a number, a point, an angle, an image) turns into a proper control in the panel, so the people who use your shader never have to read the code.
You can save it as a preset and reuse it across the project. Presets and the built-in shaders can be published, so a good fill is not stuck in one file.
Change a line, see the result, get a new control for free.
Step through your shader
Writing a shader is like cooking with a closed oven door: you change a line, run it, and look at the result to guess what happened. When it goes wrong, you rarely know why.
The Debugger in the shader code editor lets you open the door. Put breakpoints in the code and walk through it with the step buttons (into, over and out), watching values change, and use zoom lenses to look at the pixels close up. You can also pick another pixel at the current step and see the values of all the variables for that pixel.
Pause on a line and see what a pixel is doing.
A breakpoint can also wait for a condition. Shaders that move do so over time, so "stop when this value goes above 0.9" is often the question you actually have: press Run and the debugger plays time forward until the picked pixel meets the condition, then stops on that line with every variable showing why.
Let the debugger find the moment for you.
Pick a shape, set its fill to Glass, and put it over a photo.
As always, let us know what you think on our Discord.