Introducing: ShaderPad

Teeny web visuals for everyone—plus link fixes, “dead tech?” debates, and jokes

TLDR: ShaderPad, a 5.8kb open-source tool for adding slick visuals to websites, launched. Fans praised the tiny footprint, but the comments duked it out over older tech versus newer approaches and begged for drop‑in HTML components—plus one hero fixed a broken demo link, setting the tone for practical drama.

ShaderPad just dropped: a tiny open-source tool to slap eye-catching visuals on a website without lugging in huge code. The dev boasts it’s “smaller than your favicon” and over 30x lighter than big libraries, and the comments immediately turned the launch into a variety show of praise, nitpicks, and spicy side-eye.

First on stage was a helpful fix: rgbrgb loved the demos but called out a broken link—and even posted the working examples like a community MVP. Then came the fireworks: avaer questioned the choice of GLSL (a shader language) and WebGL2 (an older web graphics tech), calling it a “dead evolutionary branch” and pushing for support for newer approaches. Translation: fans of the newest browser tech want future-proofing, not nostalgia.

Another crowd split formed around how to use it. spankalee wants a simple HTML tag you can drop anywhere—those “web components” like <shader-doodle>—while ShaderPad ships as a small code library. Minimalists cheered the lean approach; convenience lovers yelled “just let me paste a tag!” Meanwhile, jokesters couldn’t resist the “throwing shade” puns and one-upped the size brag with “smaller than my attention span.” It’s art, it’s code, it’s drama—exactly the internet’s favorite cocktail.

Key Points

  • ShaderPad is an open-source, lightweight library for embedding shaders on websites with minimal setup.
  • The library focuses on small size (5.8 KB gzipped) and simplicity, contrasting with larger tools like Three.js.
  • Performance design keeps work on the GPU, chains multiple passes in one pipeline, and caches detection results for tasks like face/pose tracking.
  • Features include autosizing, save/share utilities, history buffers, and integrations with MediaPipe.
  • AI was used extensively for documentation scaffolding and as a creative aid once documentation was in place, though core design emphasized restraint over feature bloat.

Hottest takes

"the link in your blogpost is broken." — rgbrgb
"WebGL2 is a dead evolutionary branch," — avaer
"I like versions of this that are web components" — spankalee
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.