Shaders WebGPU effects are now free in any project, even commercial ones: as of October 6, 2026, its engine and components are MIT. Shader Effects Inc. released under MIT license the rendering engine, all effects components, and bindings for React, Vue, Svelte, Solid, and plain JavaScript, and also made code export free from its visual editor.
What was once a paid creative tool is now a library you install with npm install and take to production. Animated gradients, glass, chrome, neon, distortions, halftone and ASCII styling, and effects that react to the cursor: all as components you compose just like any other piece of your UI.
What is a shader and what is Shaders?
A shader is a small program that runs on the GPU and calculates the color of each pixel; Shaders is a library that gives you hundreds of them already made, as components. It also includes a design editor to build effects visually. Effects render live in the browser over WebGPU and, according to its documentation, you don’t need to know WGSL, GLSL, or graphics programming: if you know how to lay out a page with CSS or stack layers in Figma, you already have the mental model.
An effect is a <Shader> component with layers inside, which are drawn in order from bottom to top. It doesn’t matter how many layers you stack: a <Shader> renders in a single <canvas>. The documentation speaks of nearly 200 components among textures, shape effects, distortions, styling, interactive effects, adjustments, blurs, and transitions; the manufacturer’s own pages don’t agree on the exact number.
What is free and what remains paid in Shaders?
The engine and components are MIT; the editor and curated library are not. The complete breakdown, as of October 8, 2026:
| Free | Open source (MIT) | |
|---|---|---|
| Rendering engine | ||
| All effects components | ||
| Bindings for React, Vue, Svelte, Solid, and JS | ||
| Design editor, including code export | ||
| CLI and MCP server (the tools themselves) | ||
| Pro presets and pre-designed sections | ||
| Video and image rendering without watermark | ||
| Install presets and sections via CLI or MCP |
The announcement is explicit: commercial work for clients, SaaS products, and internal tools don’t need a license. They also made public defineShader, the language the team uses to build their own components, so you can write your own and submit them as a pull request. The documentation marks the underlying primitives as experimental and subject to change between versions.
How to add a WebGPU effect to a React app?
Install a single package and import from its React entry:
npm install shaders
This is the example from the official quickstart: a gradient from dark to purple with a trail that follows the cursor.
import { Shader, LinearGradient, CursorTrail } from 'shaders/react'
export default function Hero() {
return (
<Shader className="w-full h-64">
<LinearGradient colorA="#0f172a" colorB="#7c3aed" />
<CursorTrail />
</Shader>
)
}
The canvas has no size of its own: it takes the one you give to <Shader> via className or style. Apply styles to the <Shader>, not to the internal <canvas>, whose markup may change between versions. Props work like any React prop and accept state; according to the documentation, changing a value like the angle of a gradient updates it on the GPU in the next frame, without recompiling the effect.
Does it work with Next.js and server-side rendering?
Yes, but only on the client. Shaders needs a browser with GPU, so it can’t be server-rendered. In Next.js’s App Router, add 'use client' at the start of any file that renders a <Shader>. The official SSR guide also covers the Pages Router and other setups.
What about Vue, Svelte, Solid, or plain JavaScript?
It’s the same package with a different entry: shaders/vue, shaders/svelte, shaders/solid, or shaders/js. The component tree is identical across frameworks, and each has its own quickstart in the documentation.
Shaders or React Three Fiber?
It depends on whether you want 2D effects over your UI or a complete 3D scene. React Three Fiber is a React renderer for three.js: you build scenes with cameras, lights, meshes, and materials, and its own documentation recommends mastering React and three.js before you start. Shaders targets a different problem: layers of effects (backgrounds, textures, distortions, image and video styling) that you stack without thinking about geometry or cameras.
There’s another difference that matters today: at the time of writing this note, WebGPU support in React Three Fiber comes with its version 10, which is still in alpha; Shaders is WebGPU from the ground up. If you need 3D models, physics, or virtual reality, React Three Fiber and its ecosystem remain the option. If you want an animated hero or a glass effect on your landing without learning three.js, Shaders is the shortest path.
Does WebGPU work in all browsers?
Not yet in all, but the failure is graceful: on a device without WebGPU, Shaders’s canvas becomes transparent, you see what’s behind it, and the rest of the page works normally. In practice, a solid background color behind the effect is your fallback.
According to the WebGPU implementation status page (updated August 13, 2026):
- Chrome and Edge: enabled on Windows, macOS, and ChromeOS, and on Android 12+ for most GPUs. On Linux, only with Intel Gen12+ and recent NVIDIA drivers over Wayland; on everything else, behind a flag.
- Safari: enabled on macOS, iOS, and iPadOS 26.
- Firefox: enabled on Windows and macOS. On Linux and Android it’s still Nightly only or behind a flag.
To test a specific machine, Shaders runs a real renderer check at Browser check — Shaders, without uploading anything.
Does Shaders send telemetry?
Yes, by default in production. According to its documentation, Shaders collects anonymous usage data: the domain where the effect is installed and the FPS at runtime. It claims it doesn’t capture personal information, and telemetry is automatically disabled on localhost and in development. To disable it in production, just use a prop:
<Shader disableTelemetry={true}>
<LinearGradient />
</Shader>
If you’re delivering it to clients, put that decision in your checklist rather than discovering it in a privacy review.
Can it be used with Claude Code or Cursor?
Yes, via Shaders’s MCP server, which according to the documentation allows an agent like Claude Code or Cursor to install and edit effects for you. The MCP and CLI are free; to bring Pro presets and sections through them you need a subscription.
Is it ready for production?
The package is: version 4.0.2 is on npm, published with provenance attestations from GitHub Actions. The figure of over 16,000 design engineers using the tool is from the manufacturer itself, it’s not independently verified, and the public repository is recent. Pin the version, keep the fallback background, and treat custom primitives as experimental, as the documentation does.
What about you? What Shaders effect would you put first on your landing: an animated background, glass, or something that follows the cursor?
- Pure CSS
- three.js or React Three Fiber
- An effects component library
- I prefer another option (tell us which)
Comment below or, if this article reached you by email, reply directly to the email: your reply is published here.
Related: Animated ASCII art for your web: 191 free pieces for HTML, React, and Astro