Shader Effects Inc. shipped Shaders v3 on July 14 — the biggest update yet to its framework-agnostic component library for creative WebGPU effects, moving from what the company describes as “a library of GPU-powered components” toward a full design platform for production-ready shader work.
The rendering engine is the real story
Under the hood, v3 replaces its previous rendering approach with a proprietary engine built on TypeGPU, a TypeScript-first WebGPU toolkit. The practical result: production builds average 3x smaller bundles than the previous version, and shader compilation runs up to 25x faster. For anyone who’s shipped WebGPU/WebGL effects to production, those numbers target the two things that actually slow teams down — bundle bloat that hurts page-load metrics, and slow iteration loops during development where every shader tweak means another compile-and-wait cycle.
An editor built for juggling multiple shaders at once
The redesigned editor adds an infinite canvas, letting a developer or designer lay out and compare multiple shaders side by side rather than working on one in isolation — a workflow closer to how design tools like Figma handle multiple artboards than how shader editors have traditionally worked. Real-time updates and direct transform controls on layers mean changes are visible immediately rather than requiring a manual refresh cycle.
New effect primitives in v3 include raymarched 3D shapes (geometry defined and rendered through the raymarching technique rather than traditional polygon meshes — well suited to the organic, morphing forms that are hard to build with standard mesh tools) and dedicated text layers, extending the library beyond backgrounds and abstract effects into typography-driven interactive design.
Why framework-agnostic matters here
Shaders supports Vue, React, Svelte, Solid, plain JavaScript, and Framer — a deliberately wide net for a category of tool (GPU shader effects) that’s historically been either locked to a specific framework’s ecosystem or required hand-rolling raw WebGPU/WebGL calls with no component abstraction at all. For creative coders building client work across different tech stacks, that breadth is arguably as important as the performance numbers: it’s one shader-effects toolchain that travels with you regardless of which framework a given project uses.