Paper made its Paper Shaders library fully open source this July, releasing all 30+ WebGL shader effects — mesh gradients, noise textures, halftone patterns, aurora backgrounds, and more — under the Apache 2.0 license, free for commercial use with no attribution requirement forcing a paid tier.
What’s actually in the library
Paper Shaders is deliberately narrow and hand-curated rather than an infinite generative system: a fixed set of 30+ effects, each polished and consistent with the others, installable via npm or designed visually in Paper’s own editor. The output is zero-dependency JavaScript — no runtime library baggage, works directly with React or vanilla JS — which matters for anyone shipping to production where bundle size and dependency count are real constraints, not just developer convenience.
Why “hand-curated and free” beats “generative and paid” for a lot of real use
The natural comparison is Figma’s generative shader feature, which can produce effectively unlimited shader variations on demand. Paper Shaders takes the opposite bet: a smaller, fixed, deliberately consistent set of effects that all share a visual language, now available for free. For a designer or developer who needs “a good mesh gradient” or “a working aurora background” today, without iterating through a generative tool’s output space hoping to land on something usable, a curated preset that just works is often the faster and more reliable path — and now it costs nothing.
Going open source also removes the main reason a team might have chosen Figma’s generative option instead: cost. With Paper Shaders’ actual preset library now free, the case for reaching for a generative alternative narrows to situations that genuinely need something outside those 30+ presets — a real but smaller set of cases than “I need a shader effect” broadly.
What this signals about the shader-tools market
Paper Shaders going free arrives in the same season as Shaders v3 (a separate, still-commercial component library covered here previously) rebuilding its own engine on TypeGPU, and ShaderVine positioning itself specifically for AI-agent-driven shader workflows. A market with this much active investment — commercial libraries competing on rendering performance, a formerly-paid library going free to compete on price, and agent-native tooling emerging alongside both — suggests web shader effects have crossed from a niche, mostly-hand-coded practice into infrastructure worth building a real product layer around.